simpleType geoMetadataSummaryKeyValues

type | restriction of xs:NMTOKEN
properties |
base | xs:NMTOKEN
facets |
Kind | Value | Annotation
enumeration | title |
appinfo
A name to succinctly identify the dataset to user. For example, &quot;San Francisco, California&quot;.
enumeration | description |
appinfo
A brief textual description or summary of the content of the dataset. For example, &quot;LANDSAT 7 satellite imagery taken over northern Scotland&quot;.
enumeration | coordinateSystem |
appinfo
The spatial reference frame used to represent the data (e.g., GD, UTM, or LCC). The list of valid codes that can be used in this field are defined in ISO/IEC 18026. In the case of UTM, the zone number should also be specified in the format &quot;UTM Zx&quot;, where the zone number is in the range [1,60]. For example, &quot;UTM Z11&quot;.
enumeration | horizontalDatum |
appinfo
The name of the geodetic datum. The list of valid codes that can be used in this field are defined in ISO/IEC 18026. For example, &quot;W84&quot;.
enumeration | verticalDatum |
appinfo
The name of the vertical datum (geoid). The list of valid codes that can be used in this field are defined in ISO/IEC 18026. For example, &quot;W84&quot;.
enumeration | ellipsoid |
appinfo
The name of the geodetic ellipsoid. The list of valid codes that can be used in this field are defined in ISO/IEC 18026. For example, &quot;WE&quot;.
enumeration | extent |
appinfo
The bounding coordinates for the dataset given in spatial reference frame specified by the coordinateSystem keyword. These are provided in the order eastmost, southmost, westmost, northmost. An example for GD is: &quot;-180.0 -90.0 180.0 90.0&quot;.
enumeration | resolution |
appinfo
SFFloat resolution, or ground sample distance, given in units of length base units. For example, &quot;30&quot;.
enumeration | originator |
appinfo
A string defining the originator of the data, for example the author, agency, organization, publisher, etc. For example, &quot;John Doe, Any Corporation, Some Town, Some Country&quot;
enumeration | copyright |
appinfo
Any appropriate copyright declaration that pertains to the data. For example, &quot;(c) Copyright 2000, Any Corporation. All rights reserved. Freely distributable.&quot;
enumeration | date |
appinfo
A single date/time, or a date/time range, defining the valid time period to which the data pertains. Dates are specified in the format &quot;YYYY MM DD [HH:MM]&quot;. Years in the current time period should be specified using four digits (EXAMPLE &quot;1999&quot; or &quot;2001&quot;). Years can have other than four digits and can be negative. A date range is specified by supplying two values separated by a &quot;-&quot; (hyphen) character. An optional time can be supplied should this level of accuracy be required. Times are to be specified in 24-hour format with respect to GMT. For example, &quot;1999 01 01 00:00 - 1999 12 31 23:59&quot;.
enumeration | metadataFormat |
appinfo
A string that specifies the format of the external metadata description specified by the url field of the GeoMetadata node. For example, &quot;FGDC&quot;, &quot;ISO TC211&quot;, &quot;CEN TC287&quot;, or &quot;OGC&quot;.
enumeration | dataUrl |
appinfo
A hypertext link to the source data used to create the X3D node(s) to which this metadata pertains. Multiple dataUrl keyword/value pairs can be specified in order to provide alternative locations for the same source data. For example, &quot;https://www.foo.bar/data/sf1&quot;.
enumeration | dataFormat |
appinfo
A free-text string that describes the format of the source data used to create the X3D node(s) to which this metadata pertains. This refers to the source data specified by the dataUrl keyword (if present). For example, &quot;USGS 5.5-min DEM&quot;.
annotation |
appinfo
The enumeration keys for the GeoMetadata summary field. This list is unbounded, additional enumeration values are allowed.
source | <xs:simpleType name="geoMetadataSummaryKeyValues"> <xs:annotation> <xs:appinfo>The enumeration keys for the GeoMetadata summary field. This list is unbounded, additional enumeration values are allowed. </xs:appinfo> <!-- Note that strict validation does not occur via X3D XML schema since MetadataString/MetadataFloat nodes allow any value, additional quality assurance (QA) performed by X3D Schematron and X3dTidy.xslt. --> <xs:documentation source="https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#t-keywordsandvalues"/> </xs:annotation> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="title"> <xs:annotation> <xs:appinfo>A name to succinctly identify the dataset to user. For example, &quot;San Francisco, California&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="description"> <xs:annotation> <xs:appinfo>A brief textual description or summary of the content of the dataset. For example, &quot;LANDSAT 7 satellite imagery taken over northern Scotland&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="coordinateSystem"> <xs:annotation> <xs:appinfo>The spatial reference frame used to represent the data (e.g., GD, UTM, or LCC). The list of valid codes that can be used in this field are defined in ISO/IEC 18026. In the case of UTM, the zone number should also be specified in the format &quot;UTM Zx&quot;, where the zone number is in the range [1,60]. For example, &quot;UTM Z11&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="horizontalDatum"> <xs:annotation> <xs:appinfo>The name of the geodetic datum. The list of valid codes that can be used in this field are defined in ISO/IEC 18026. For example, &quot;W84&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="verticalDatum"> <xs:annotation> <xs:appinfo>The name of the vertical datum (geoid). The list of valid codes that can be used in this field are defined in ISO/IEC 18026. For example, &quot;W84&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="ellipsoid"> <xs:annotation> <xs:appinfo>The name of the geodetic ellipsoid. The list of valid codes that can be used in this field are defined in ISO/IEC 18026. For example, &quot;WE&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="extent"> <xs:annotation> <xs:appinfo>The bounding coordinates for the dataset given in spatial reference frame specified by the coordinateSystem keyword. These are provided in the order eastmost, southmost, westmost, northmost. An example for GD is: &quot;-180.0 -90.0 180.0 90.0&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="resolution"> <xs:annotation> <xs:appinfo>SFFloat resolution, or ground sample distance, given in units of length base units. For example, &quot;30&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="originator"> <xs:annotation> <xs:appinfo>A string defining the originator of the data, for example the author, agency, organization, publisher, etc. For example, &quot;John Doe, Any Corporation, Some Town, Some Country&quot;</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="copyright"> <xs:annotation> <xs:appinfo>Any appropriate copyright declaration that pertains to the data. For example, &quot;(c) Copyright 2000, Any Corporation. All rights reserved. Freely distributable.&quot;</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="date"> <xs:annotation> <xs:appinfo>A single date/time, or a date/time range, defining the valid time period to which the data pertains. Dates are specified in the format &quot;YYYY MM DD [HH:MM]&quot;. Years in the current time period should be specified using four digits (EXAMPLE &quot;1999&quot; or &quot;2001&quot;). Years can have other than four digits and can be negative. A date range is specified by supplying two values separated by a &quot;-&quot; (hyphen) character. An optional time can be supplied should this level of accuracy be required. Times are to be specified in 24-hour format with respect to GMT. For example, &quot;1999 01 01 00:00 - 1999 12 31 23:59&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="metadataFormat"> <xs:annotation> <xs:appinfo>A string that specifies the format of the external metadata description specified by the url field of the GeoMetadata node. For example, &quot;FGDC&quot;, &quot;ISO TC211&quot;, &quot;CEN TC287&quot;, or &quot;OGC&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="dataUrl"> <xs:annotation> <xs:appinfo>A hypertext link to the source data used to create the X3D node(s) to which this metadata pertains. Multiple dataUrl keyword/value pairs can be specified in order to provide alternative locations for the same source data. For example, &quot;https://www.foo.bar/data/sf1&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="dataFormat"> <xs:annotation> <xs:appinfo>A free-text string that describes the format of the source data used to create the X3D node(s) to which this metadata pertains. This refers to the source data specified by the dataUrl keyword (if present). For example, &quot;USGS 5.5-min DEM&quot;.</xs:appinfo> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy