OGC GML User Attributes
To access user attributes, click the properties button on a feature type in the workspace, and select the User Attributes tab.
Readers: For information on the parameters in this dialog that are common to all readers, see:
Writers: For information on the parameters in this dialog that are common to all writers, see:
User attributes control the generation of the GML application schema. The following table shows the attribute types that are supported.
Name |
A simple attribute, a list attribute, a structured attribute, or a geometry attribute. Simple attributes These attributes have no embedded period, and they are mapped into simple type properties in the GML application schema. List attributes These attributes end with a {} suffix, and are mapped into simple type property declarations whose maxOccurs are set to unbounded. Structured attributes These attributes have embedded periods. Each component in a structured attribute is separated by a period, and each component may also be a list. Structured attributes are mapped into complex type properties in the GML application schema. For example, the structured FME attributes changeHistory.Date and changeHistory.Reason are mapped into a changeHistory element whose complex type is defined as a sequence of Date and Reason elements both of which are defined as simple types. These attributes are used to control the name and the position of the GML geometry elements. Currently, only the generic xml_geometry type is supported, so the geometry attribute only specifies the name and the position for the GML geometric property. The type for the GML geometric property is determined via the instances of the data features. For example, if all instances of a named geometry corresponding to the geometry attribute are points, then the XSD written will have its geometric element declared as gml:PointPropertyType; if the specific GML geometry property type cannot be determined via the data features, then the geometric element is declared as gml:GeometryPropertyType. The attribute in the FME feature type definition representing the name of the geometry may end with a {} suffix. This is only used to indicate the multiple occurrences of a geometric property. For example, projectedGeometry{}, means that there will be 0 or more geometries with the projectedGeometry name. The {} suffix does not affect the name of the geometry in the FME feature, and the geometry name in the feature will never be indexed– it will simply be projectedGeometry (not projectedGeometry{0}, ..., projectedGeometry{n}). |
Type |
This format supports the following field types. xml_boolean This type corresponds to an XML built-in data type. xml_buffer Mapped to an unlimited length string, xs:string, or text buffer type. xml_byte This type corresponds to an XML built-in data type. xml_char(width) Mapped to the xs:string with a length or maxLength facet. xml_date This type corresponds to an XML built-in data type. xml_datetime This type corresponds to an XML built-in data type. xml_decimal This type corresponds to an XML built-in data type. xml_geometry Used the by GML reader and writer to designate an attribute name as a placeholder for a geometry column; therefore, xml_geometry will map to a GML geometric type. See Map Geometry Columns. xml_int16 This type corresponds to an XML built-in data type. xml_int32 This type corresponds to an XML built-in data type. xml_int64 This type corresponds to an XML built-in data type. xml_real32 This type corresponds to an XML built-in data type. xml_real64 This type corresponds to an XML built-in data type. xml_time This type corresponds to an XML built-in data type. xml_ubyte This type corresponds to an XML built-in data type. xml_uint16 This type corresponds to an XML built-in data type. xml_uint32 This type corresponds to an XML built-in data type. xml_uint64 This type corresponds to an XML built-in data type. xml_xml Used by the GML reader and writer to denote that an attribute name holds an XML fragment. There is no corresponding XML schema type. |
Width |
The width parameter controls the maximum characters that can be stored by the field. |