What are the objectives of this effort? Examples:Beamform to increase SNR for detection.Detect every click of a rare species.Verify data quality.
Diagram
Type
xs:string
Properties
content
simple
minOccurs
0
Source
<xs:element name="Objectives" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>What are the objectives of this effort? Examples: Beamform to increase SNR for detection. Detect every click of a rare species. Verify data quality.</xs:documentation></xs:annotation></xs:element>
<xs:element name="Method" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>High-level description of the method used.</xs:documentation></xs:annotation></xs:element>
Serves as a foreign key into the ensembles collection and must match an Id element in an ensemble document. Ensembles are used to group instruments together for a common purpose (e.g. large aperture array).
Diagram
Type
xs:string
Properties
content
simple
Source
<xs:element name="EnsembleId" type="xs:string"><xs:annotation><xs:documentation>Serves as a foreign key into the ensembles collection and must match an Id element in an ensemble document. Ensembles are used to group instruments together for a common purpose (e.g. large aperture array).</xs:documentation></xs:annotation></xs:element>
Serves as a foreign key into the Deployments collection and must match an Id element in a deployment document.
Diagram
Type
xs:string
Properties
content
simple
Source
<xs:element name="DeploymentId" type="xs:string"><xs:annotation><xs:documentation>Serves as a foreign key into the Deployments collection and must match an Id element in a deployment document.</xs:documentation></xs:annotation></xs:element>
<xs:element minOccurs="0" name="Method" type="xs:string"><xs:annotation><xs:documentation>Text based description of algorithm or citation</xs:documentation></xs:annotation></xs:element>
Name of software that implements the algorithm or supports human analysts. This might be the name of a plug-in or extension module that is part of a larger program or system.
Diagram
Type
xs:string
Properties
content
simple
Source
<xs:element name="Software" type="xs:string"><xs:annotation><xs:documentation>Name of software that implements the algorithm or supports human analysts. This might be the name of a plug-in or extension module that is part of a larger program or system.</xs:documentation></xs:annotation></xs:element>
Structured tags to describe parameters used in algorithm execution.
Diagram
Properties
content
complex
minOccurs
0
Model
ANY element from TARGET namespace 'http://tethys.sdsu.edu/schema/1.0'
Source
<xs:element name="Parameters" minOccurs="0"><xs:annotation><xs:documentation>Structured tags to describe parameters used in algorithm execution.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element>
<xs:element name="SupportSoftware" maxOccurs="unbounded" minOccurs="0"><xs:annotation><xs:documentation>Software required in addition to the algorithm itself, e.g. Matlab, Ishmael, PAMGUARD, Triton, etc.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="Software" type="xs:string"/><xs:element name="Version" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>Software version identifier.</xs:documentation></xs:annotation></xs:element><xs:element name="Parameters" minOccurs="0"><xs:annotation><xs:documentation>Structured tags to describe parameters used in algorithm execution.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element>
Structured tags to describe parameters used in algorithm execution.
Diagram
Properties
content
complex
minOccurs
0
Model
ANY element from TARGET namespace 'http://tethys.sdsu.edu/schema/1.0'
Source
<xs:element name="Parameters" minOccurs="0"><xs:annotation><xs:documentation>Structured tags to describe parameters used in algorithm execution.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element>
We do not fully conform to the onlineResources of ISO 19115
Diagram
Properties
content
complex
minOccurs
0
maxOccurs
unbounded
Attributes
Wildcard: ANY attribute from TARGET namespace 'http://tethys.sdsu.edu/schema/1.0'
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="onlineResource"><xs:annotation><xs:documentation>We do not fully conform to the onlineResources of ISO 19115</xs:documentation></xs:annotation><xs:complexType><xs:anyAttribute namespace="##targetNamespace"/></xs:complexType></xs:element>
<xs:element name="Data" maxOccurs="unbounded" minOccurs="0"><xs:complexType><xs:sequence maxOccurs="1"><xs:element maxOccurs="1" name="URI" type="xs:string"><xs:annotation><xs:documentation>Data that are not stored within the schema. This may take the form of a URI or other textual value. In the Tethys server, the value here permits retrieval of the data by visitng a URL related to the current document. The URI will just consist of the filename that was submitted, e.g., AdditionalData.zip or Calculations.hdf. A combination of the document Id and the filename can be used to download the data. For example, if AdditionaData.zip was submitted with the document localization document Id CINMS32B as BespokeData, one could retrieve the data by visiting: http://myTethysServer.local:9779/Attach/Localizations/CINMS32B?URI=AdditionalData.zip The above URL would need to be updated for the appropriate server, port, and protocol (http vs. https).</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="Comment" type="xs:string"/></xs:sequence></xs:complexType></xs:element>
Data that are not stored within the schema. This may take the form of a URI or other textual value. In the Tethys server, the value here permits retrieval of the data by visitng a URL related to the current document. The URI will just consist of the filename that was submitted, e.g., AdditionalData.zip or Calculations.hdf. A combination of the document Id and the filename can be used to download the data. For example, if AdditionaData.zip was submitted with the document localization document Id CINMS32B as BespokeData, one could retrieve the data by visiting:http://myTethysServer.local:9779/Attach/Localizations/CINMS32B?URI=AdditionalData.zipThe above URL would need to be updated for the appropriate server, port, and protocol (http vs. https).
Diagram
Type
xs:string
Properties
content
simple
maxOccurs
1
Source
<xs:element maxOccurs="1" name="URI" type="xs:string"><xs:annotation><xs:documentation>Data that are not stored within the schema. This may take the form of a URI or other textual value. In the Tethys server, the value here permits retrieval of the data by visitng a URL related to the current document. The URI will just consist of the filename that was submitted, e.g., AdditionalData.zip or Calculations.hdf. A combination of the document Id and the filename can be used to download the data. For example, if AdditionaData.zip was submitted with the document localization document Id CINMS32B as BespokeData, one could retrieve the data by visiting: http://myTethysServer.local:9779/Attach/Localizations/CINMS32B?URI=AdditionalData.zip The above URL would need to be updated for the appropriate server, port, and protocol (http vs. https).</xs:documentation></xs:annotation></xs:element>
ANY element from TARGET namespace 'http://tethys.sdsu.edu/schema/1.0'
Source
<xs:element name="UserDefined" minOccurs="0"><xs:annotation><xs:documentation>Any user-defined elements may be stored here.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element>
How often are these data updated?as-needed, unplanned, or yearly
Diagram
Type
restriction of xs:string
Properties
content
simple
Facets
enumeration
as-needed
enumeration
unplanned
enumeration
yearly
Source
<xs:element name="UpdateFrequency"><xs:annotation><xs:documentation>How often are these data updated? as-needed, unplanned, or yearly</xs:documentation></xs:annotation><xs:simpleType><xs:restriction base="xs:string"><xs:enumeration value="as-needed"/><xs:enumeration value="unplanned"/><xs:enumeration value="yearly"/></xs:restriction></xs:simpleType></xs:element>
<xs:element name="Longitude" type="ns1:LongitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees East [0, 360)</xs:documentation></xs:annotation></xs:element>
<xs:element name="Latitude" type="ns1:LatitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees North [-90, 90]</xs:documentation></xs:annotation></xs:element>
Bounding box for tempo-spatial data from northwest to southeast quadrant. If elevation/depth information is available, separate depth boundaries are given as well.Note that longitudes are always degrees east. When a track crosses 0° east, the northwest longitude will be > than the souteast longitude (e.g. a 2° path from 359°E to 1°E)
<xs:element name="Bounds"><xs:annotation><xs:documentation>Bounding box for tempo-spatial data from northwest to southeast quadrant. If elevation/depth information is available, separate depth boundaries are given as well. Note that longitudes are always degrees east. When a track crosses 0° east, the northwest longitude will be > than the souteast longitude (e.g. a 2° path from 359°E to 1°E)</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="NorthWest"><xs:complexType><xs:sequence><xs:element name="Longitude" type="ns1:LongitudeValueType"/><xs:element name="Latitude" type="ns1:LatitudeValueType"/></xs:sequence></xs:complexType></xs:element><xs:element name="SouthEast"><xs:complexType><xs:sequence><xs:element name="Longitude" type="ns1:LongitudeValueType"/><xs:element name="Latitude" type="ns1:LatitudeValueType"/></xs:sequence></xs:complexType></xs:element><xs:element minOccurs="0" name="Elevations"><xs:complexType><xs:sequence><xs:element name="MinElevation_m" type="xs:double"/><xs:element name="MaxElevation_m" type="xs:double"/></xs:sequence></xs:complexType></xs:element><xs:element minOccurs="0" name="Depth"><xs:complexType><xs:sequence><xs:element name="MinDepth_m" type="xs:double"/><xs:element name="MaxDepth_m" type="xs:double"/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element>
<xs:element name="Longitude" type="ns1:LongitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees East [0, 360)</xs:documentation></xs:annotation></xs:element>
<xs:element name="Latitude" type="ns1:LatitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees North [-90, 90]</xs:documentation></xs:annotation></xs:element>
<xs:element name="Longitude" type="xs:double"><xs:annotation><xs:documentation>Expressed in degrees East [0, 360)</xs:documentation></xs:annotation></xs:element>
<xs:element name="Latitude" type="xs:double"><xs:annotation><xs:documentation>Expressed in degrees North [-90, 90]</xs:documentation></xs:annotation></xs:element>
Integrated Taxonomic Information System (ITIS) Serial NumberSee www.itis.gov
Diagram
Type
xs:integer
Properties
content
simple
Source
<xs:element name="tsn" type="xs:integer"><xs:annotation><xs:documentation>Integrated Taxonomic Information System (ITIS) Serial Number See www.itis.gov</xs:documentation></xs:annotation></xs:element>
Taxnomic unit to which this TSN belongs, e.g. species, family, etc. This can be inferred in schemata that are hierarchical such as ITIS.xsd, and is typically only used in flattened schemata.
Diagram
Type
xs:string
Properties
content
simple
minOccurs
0
Source
<xs:element minOccurs="0" name="taxon_unit" type="xs:string"><xs:annotation><xs:documentation>Taxnomic unit to which this TSN belongs, e.g. species, family, etc. This can be inferred in schemata that are hierarchical such as ITIS.xsd, and is typically only used in flattened schemata.</xs:documentation></xs:annotation></xs:element>
<xs:element name="completename"><xs:annotation><xs:documentation>Scientific name for this taxa</xs:documentation></xs:annotation><xs:simpleType><xs:restriction base="xs:token"><xs:whiteSpace value="collapse"/></xs:restriction></xs:simpleType></xs:element>
<xs:element name="vernacular" type="ns1:vernacularType"><xs:annotation><xs:documentation>Common names for this taxa.</xs:documentation></xs:annotation></xs:element>
<xs:complexType name="DescriptionType"><xs:annotation><xs:documentation>Text based description of process.</xs:documentation></xs:annotation><xs:sequence><xs:element name="Objectives" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>What are the objectives of this effort? Examples: Beamform to increase SNR for detection. Detect every click of a rare species. Verify data quality.</xs:documentation></xs:annotation></xs:element><xs:element name="Abstract" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>Overview of effort.</xs:documentation></xs:annotation></xs:element><xs:element name="Method" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>High-level description of the method used.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="DataSourceType"><xs:annotation><xs:documentation>Indicates the deployment or ensemble from which the process (e.g. detector) derived information.</xs:documentation></xs:annotation><xs:choice><xs:element name="EnsembleId" type="xs:string"><xs:annotation><xs:documentation>Serves as a foreign key into the ensembles collection and must match an Id element in an ensemble document. Ensembles are used to group instruments together for a common purpose (e.g. large aperture array).</xs:documentation></xs:annotation></xs:element><xs:element name="DeploymentId" type="xs:string"><xs:annotation><xs:documentation>Serves as a foreign key into the Deployments collection and must match an Id element in a deployment document.</xs:documentation></xs:annotation></xs:element></xs:choice></xs:complexType>
<xs:complexType name="AlgorithmType"><xs:annotation><xs:documentation>Description of an algorithm or process.</xs:documentation></xs:annotation><xs:sequence><xs:element minOccurs="0" name="Method" type="xs:string"><xs:annotation><xs:documentation>Text based description of algorithm or citation</xs:documentation></xs:annotation></xs:element><xs:element name="Software" type="xs:string"><xs:annotation><xs:documentation>Name of software that implements the algorithm or supports human analysts. This might be the name of a plug-in or extension module that is part of a larger program or system.</xs:documentation></xs:annotation></xs:element><xs:element name="Version" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>Software version identifier</xs:documentation></xs:annotation></xs:element><xs:element name="Parameters" minOccurs="0"><xs:annotation><xs:documentation>Structured tags to describe parameters used in algorithm execution.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element><xs:element name="SupportSoftware" maxOccurs="unbounded" minOccurs="0"><xs:annotation><xs:documentation>Software required in addition to the algorithm itself, e.g. Matlab, Ishmael, PAMGUARD, Triton, etc.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="Software" type="xs:string"/><xs:element name="Version" type="xs:string" minOccurs="0"><xs:annotation><xs:documentation>Software version identifier.</xs:documentation></xs:annotation></xs:element><xs:element name="Parameters" minOccurs="0"><xs:annotation><xs:documentation>Structured tags to describe parameters used in algorithm execution.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType>
Integrated Taxonomic Information System species identifier http://www.itis.gov/ for positive numbers. Negative numbers are used for physical phenomena.
Attribute used to denote groups within a species or other taxonomic unit. This can be useful for subpopulations or for denoting hypotheses. For example, many echolocation clicks can be identified to the family Hyperoodontidae (beaked whales), but not to a species. Using the Group attribute can help to distinguish between different types of beaked whale clicks without knowing which species family member produced them.
Source
<xs:complexType name="SpeciesIDType"><xs:annotation><xs:documentation>Integrated Taxonomic Information System species identifier http://www.itis.gov/ for positive numbers. Negative numbers are used for physical phenomena.</xs:documentation></xs:annotation><xs:simpleContent><xs:extension base="xs:integer"><xs:attribute name="Group" type="xs:string"><xs:annotation><xs:documentation>Attribute used to denote groups within a species or other taxonomic unit. This can be useful for subpopulations or for denoting hypotheses. For example, many echolocation clicks can be identified to the family Hyperoodontidae (beaked whales), but not to a species. Using the Group attribute can help to distinguish between different types of beaked whale clicks without knowing which species family member produced them.</xs:documentation></xs:annotation></xs:attribute></xs:extension></xs:simpleContent></xs:complexType>
Event identifier. Optional tag typically in ISO datetime format YYYY-MM-DDTHH:MM:SSZ identifying this event uniquely within the stream (detections, localizations, etc.). For human analysts, it is typical to use the time at which the detection was made. When used, the combination of the event and attributes that uniquely identify the set of detections (or document name) must be unique.
<xs:simpleType name="EventType"><xs:annotation><xs:documentation>Event identifier. Optional tag typically in ISO datetime format YYYY-MM-DDTHH:MM:SSZ identifying this event uniquely within the stream (detections, localizations, etc.). For human analysts, it is typical to use the time at which the detection was made. When used, the combination of the event and attributes that uniquely identify the set of detections (or document name) must be unique.</xs:documentation></xs:annotation><xs:restriction base="xs:string"/></xs:simpleType>
<xs:complexType name="BespokeDataType"><xs:sequence><xs:element name="Abstract" type="xs:string"/><xs:element name="Data" maxOccurs="unbounded" minOccurs="0"><xs:complexType><xs:sequence maxOccurs="1"><xs:element maxOccurs="1" name="URI" type="xs:string"><xs:annotation><xs:documentation>Data that are not stored within the schema. This may take the form of a URI or other textual value. In the Tethys server, the value here permits retrieval of the data by visitng a URL related to the current document. The URI will just consist of the filename that was submitted, e.g., AdditionalData.zip or Calculations.hdf. A combination of the document Id and the filename can be used to download the data. For example, if AdditionaData.zip was submitted with the document localization document Id CINMS32B as BespokeData, one could retrieve the data by visiting: http://myTethysServer.local:9779/Attach/Localizations/CINMS32B?URI=AdditionalData.zip The above URL would need to be updated for the appropriate server, port, and protocol (http vs. https).</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="Comment" type="xs:string"/></xs:sequence></xs:complexType></xs:element><xs:element name="UserDefined" minOccurs="0"><xs:annotation><xs:documentation>Any user-defined elements may be stored here.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:any maxOccurs="unbounded" minOccurs="0" namespace="##targetNamespace" processContents="skip"/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="MetadataInfo"><xs:annotation><xs:documentation>Information about who is responsible for this metadata record, when it was created, and how often it is updated.</xs:documentation></xs:annotation><xs:sequence><xs:element name="Contact" type="ns1:ResponsibleParty"/><xs:element name="Date" type="xs:dateTime"><xs:annotation><xs:documentation>Last update.</xs:documentation></xs:annotation></xs:element><xs:element name="UpdateFrequency"><xs:annotation><xs:documentation>How often are these data updated? as-needed, unplanned, or yearly</xs:documentation></xs:annotation><xs:simpleType><xs:restriction base="xs:string"><xs:enumeration value="as-needed"/><xs:enumeration value="unplanned"/><xs:enumeration value="yearly"/></xs:restriction></xs:simpleType></xs:element></xs:sequence></xs:complexType>
<xs:simpleType name="LongitudeValueType"><xs:annotation><xs:documentation>Longitude is expressed in degrees East [0,360)</xs:documentation></xs:annotation><xs:restriction base="xs:double"><xs:minInclusive value="0"/><xs:maxExclusive value="360"/></xs:restriction></xs:simpleType>
<xs:simpleType name="LatitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees North [-90,90]</xs:documentation></xs:annotation><xs:restriction base="xs:double"><xs:minInclusive value="-90"/><xs:maxInclusive value="90"/></xs:restriction></xs:simpleType>
<xs:complexType name="LongLat3List"><xs:annotation><xs:documentation>List of longitudes [0,359), latitudes (-90,90) elevations in meters, depths in meters and timestamps. Only Longitudes and Latitudes are mandatory.</xs:documentation></xs:annotation><xs:sequence><xs:element name="Longitudes" type="ns1:Longitudes"/><xs:element name="Latitudes" type="ns1:Latitudes"/><xs:element minOccurs="0" name="Elevations_m" type="ns1:Elevations_m"/><xs:element minOccurs="0" name="Depths_m" type="ns1:Depths_m"/><xs:element name="Timestamps" type="ns1:Timestamps"/><xs:element name="Bounds"><xs:annotation><xs:documentation>Bounding box for tempo-spatial data from northwest to southeast quadrant. If elevation/depth information is available, separate depth boundaries are given as well. Note that longitudes are always degrees east. When a track crosses 0° east, the northwest longitude will be > than the souteast longitude (e.g. a 2° path from 359°E to 1°E)</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="NorthWest"><xs:complexType><xs:sequence><xs:element name="Longitude" type="ns1:LongitudeValueType"/><xs:element name="Latitude" type="ns1:LatitudeValueType"/></xs:sequence></xs:complexType></xs:element><xs:element name="SouthEast"><xs:complexType><xs:sequence><xs:element name="Longitude" type="ns1:LongitudeValueType"/><xs:element name="Latitude" type="ns1:LatitudeValueType"/></xs:sequence></xs:complexType></xs:element><xs:element minOccurs="0" name="Elevations"><xs:complexType><xs:sequence><xs:element name="MinElevation_m" type="xs:double"/><xs:element name="MaxElevation_m" type="xs:double"/></xs:sequence></xs:complexType></xs:element><xs:element minOccurs="0" name="Depth"><xs:complexType><xs:sequence><xs:element name="MinDepth_m" type="xs:double"/><xs:element name="MaxDepth_m" type="xs:double"/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType>
<xs:complexType name="LongLatAlt"><xs:sequence><xs:element name="Longitude" type="xs:double"><xs:annotation><xs:documentation>Expressed in degrees East [0, 360)</xs:documentation></xs:annotation></xs:element><xs:element name="Latitude" type="xs:double"><xs:annotation><xs:documentation>Expressed in degrees North [-90, 90]</xs:documentation></xs:annotation></xs:element><xs:element name="Altitude_m" type="xs:double" maxOccurs="1" minOccurs="0"/></xs:sequence></xs:complexType>
Attribute used to denote groups within a species or other taxonomic unit. This can be useful for subpopulations or for denoting hypotheses. For example, many echolocation clicks can be identified to the family Hyperoodontidae (beaked whales), but not to a species. Using the Group attribute can help to distinguish between different types of beaked whale clicks without knowing which species family member produced them.
<xs:attribute name="Group" type="xs:string"><xs:annotation><xs:documentation>Attribute used to denote groups within a species or other taxonomic unit. This can be useful for subpopulations or for denoting hypotheses. For example, many echolocation clicks can be identified to the family Hyperoodontidae (beaked whales), but not to a species. Using the Group attribute can help to distinguish between different types of beaked whale clicks without knowing which species family member produced them.</xs:documentation></xs:annotation></xs:attribute>
Contains a subset of the OpenGIS SensorML ContactGroup(http://www.opengis.net/sensorML/1.0). Parsing the full SensorML schema will slow down processing.
<xs:group name="ContactGroup"><xs:annotation><xs:documentation>Contains a subset of the OpenGIS SensorML ContactGroup (http://www.opengis.net/sensorML/1.0). Parsing the full SensorML schema will slow down processing.</xs:documentation></xs:annotation><xs:choice><xs:element name="Person" type="ns1:Person"/><xs:element name="ResponsibleParty" type="ns1:ResponsibleParty"/></xs:choice></xs:group>
<xs:group name="LongLat"><xs:annotation><xs:documentation>Spherical reference system</xs:documentation></xs:annotation><xs:sequence><xs:element name="Longitude" type="ns1:LongitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees East [0, 360)</xs:documentation></xs:annotation></xs:element><xs:element name="Latitude" type="ns1:LatitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees North [-90, 90]</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:group>
<xs:group name="LongLat3"><xs:sequence><xs:element name="Longitude" type="ns1:LongitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees East [0, 360)</xs:documentation></xs:annotation></xs:element><xs:element name="Latitude" type="ns1:LatitudeValueType"><xs:annotation><xs:documentation>Expressed in degrees North [-90, 90]</xs:documentation></xs:annotation></xs:element><xs:element name="Depth_m" type="xs:double"/></xs:sequence></xs:group>
<xs:group name="tsngroup"><xs:annotation><xs:documentation>This describes one entity, e.g. a kingdom, a phylum, a species, etc.</xs:documentation></xs:annotation><xs:sequence><xs:element name="tsn" type="xs:integer"><xs:annotation><xs:documentation>Integrated Taxonomic Information System (ITIS) Serial Number See www.itis.gov</xs:documentation></xs:annotation></xs:element><xs:element minOccurs="0" name="taxon_unit" type="xs:string"><xs:annotation><xs:documentation>Taxnomic unit to which this TSN belongs, e.g. species, family, etc. This can be inferred in schemata that are hierarchical such as ITIS.xsd, and is typically only used in flattened schemata.</xs:documentation></xs:annotation></xs:element><xs:element name="completename"><xs:annotation><xs:documentation>Scientific name for this taxa</xs:documentation></xs:annotation><xs:simpleType><xs:restriction base="xs:token"><xs:whiteSpace value="collapse"/></xs:restriction></xs:simpleType></xs:element><xs:element name="vernacular" type="ns1:vernacularType"><xs:annotation><xs:documentation>Common names for this taxa.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:group>