1 |
9559
|
tao
|
<?xml version="1.0" encoding="UTF-8"?>
|
2 |
|
|
<schema targetNamespace="http://www.opengis.net/gml/3.2" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" version="3.2.1 2010-01-28">
|
3 |
|
|
<annotation>
|
4 |
|
|
<appinfo source="urn:x-ogc:specification:gml:schema-xsd:dynamicFeature:3.2.1">dynamicFeature.xsd</appinfo>
|
5 |
|
|
<documentation>See ISO/DIS 19136 15.6.
|
6 |
|
|
A number of types and relationships are defined to represent the time-varying properties of geographic features.
|
7 |
|
|
In a comprehensive treatment of spatiotemporal modeling, Langran (see Bibliography) distinguished three principal temporal entities: states, events, and evidence; the schema specified in the following Subclauses incorporates elements for each.
|
8 |
|
|
|
9 |
|
|
GML is an OGC Standard.
|
10 |
|
|
Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved.
|
11 |
|
|
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
|
12 |
|
|
</documentation>
|
13 |
|
|
</annotation>
|
14 |
|
|
<include schemaLocation="feature.xsd"/>
|
15 |
|
|
<include schemaLocation="direction.xsd"/>
|
16 |
|
|
<element name="dataSource" type="gml:StringOrRefType">
|
17 |
|
|
<annotation>
|
18 |
|
|
<documentation>Evidence is represented by a simple gml:dataSource or gml:dataSourceReference property that indicates the source of the temporal data. The remote link attributes of the gml:dataSource element have been deprecated along with its current type.</documentation>
|
19 |
|
|
</annotation>
|
20 |
|
|
</element>
|
21 |
|
|
<element name="dataSourceReference" type="gml:ReferenceType">
|
22 |
|
|
<annotation>
|
23 |
|
|
<documentation>Evidence is represented by a simple gml:dataSource or gml:dataSourceReference property that indicates the source of the temporal data.</documentation>
|
24 |
|
|
</annotation>
|
25 |
|
|
</element>
|
26 |
|
|
<group name="dynamicProperties">
|
27 |
|
|
<annotation>
|
28 |
|
|
<documentation>A convenience group. This allows an application schema developer to include dynamic properties in a content model in a standard fashion.</documentation>
|
29 |
|
|
</annotation>
|
30 |
|
|
<sequence>
|
31 |
|
|
<element ref="gml:validTime" minOccurs="0"/>
|
32 |
|
|
<element ref="gml:history" minOccurs="0"/>
|
33 |
|
|
<element ref="gml:dataSource" minOccurs="0"/>
|
34 |
|
|
<element ref="gml:dataSourceReference" minOccurs="0"/>
|
35 |
|
|
</sequence>
|
36 |
|
|
</group>
|
37 |
|
|
<element name="DynamicFeature" type="gml:DynamicFeatureType" substitutionGroup="gml:AbstractFeature">
|
38 |
|
|
<annotation>
|
39 |
|
|
<documentation>States are captured by time-stamped instances of a feature. The content model extends the standard gml:AbstractFeatureType with the gml:dynamicProperties model group.
|
40 |
|
|
Each time-stamped instance represents a 'snapshot' of a feature. The dynamic feature classes will normally be extended to suit particular applications. A dynamic feature bears either a time stamp or a history.</documentation>
|
41 |
|
|
</annotation>
|
42 |
|
|
</element>
|
43 |
|
|
<complexType name="DynamicFeatureType">
|
44 |
|
|
<complexContent>
|
45 |
|
|
<extension base="gml:AbstractFeatureType">
|
46 |
|
|
<group ref="gml:dynamicProperties"/>
|
47 |
|
|
</extension>
|
48 |
|
|
</complexContent>
|
49 |
|
|
</complexType>
|
50 |
|
|
<element name="DynamicFeatureCollection" type="gml:DynamicFeatureCollectionType" substitutionGroup="gml:DynamicFeature">
|
51 |
|
|
<annotation>
|
52 |
|
|
<documentation>A gml:DynamicFeatureCollection is a feature collection that has a gml:validTime property (i.e. is a snapshot of the feature collection) or which has a gml:history property that contains one or more gml:AbstractTimeSlices each of which contain values of the time varying properties of the feature collection. Note that the gml:DynamicFeatureCollection may be one of the following:
|
53 |
|
|
1. A feature collection which consists of static feature members (members do not change in time) but which has properties of the collection object as a whole that do change in time .
|
54 |
|
|
2. A feature collection which consists of dynamic feature members (the members are gml:DynamicFeatures) but which also has properties of the collection as a whole that vary in time.</documentation>
|
55 |
|
|
</annotation>
|
56 |
|
|
</element>
|
57 |
|
|
<complexType name="DynamicFeatureCollectionType">
|
58 |
|
|
<complexContent>
|
59 |
|
|
<extension base="gml:DynamicFeatureType">
|
60 |
|
|
<sequence>
|
61 |
|
|
<element ref="gml:dynamicMembers"/>
|
62 |
|
|
</sequence>
|
63 |
|
|
</extension>
|
64 |
|
|
</complexContent>
|
65 |
|
|
</complexType>
|
66 |
|
|
<element name="dynamicMembers" type="gml:DynamicFeatureMemberType"/>
|
67 |
|
|
<complexType name="DynamicFeatureMemberType">
|
68 |
|
|
<complexContent>
|
69 |
|
|
<extension base="gml:AbstractFeatureMemberType">
|
70 |
|
|
<sequence>
|
71 |
|
|
<element ref="gml:DynamicFeature" minOccurs="0" maxOccurs="unbounded"/>
|
72 |
|
|
</sequence>
|
73 |
|
|
<attributeGroup ref="gml:AssociationAttributeGroup"/>
|
74 |
|
|
</extension>
|
75 |
|
|
</complexContent>
|
76 |
|
|
</complexType>
|
77 |
|
|
<element name="AbstractTimeSlice" type="gml:AbstractTimeSliceType" abstract="true" substitutionGroup="gml:AbstractGML">
|
78 |
|
|
<annotation>
|
79 |
|
|
<documentation>To describe an event — an action that occurs at an instant or over an interval of time — GML provides the gml:AbtractTimeSlice element. A timeslice encapsulates the time-varying properties of a dynamic feature -- it shall be extended to represent a time stamped projection of a specific feature. The gml:dataSource property describes how the temporal data was acquired.
|
80 |
|
|
A gml:AbstractTimeSlice instance is a GML object that encapsulates updates of the dynamic—or volatile—properties that reflect some change event; it thus includes only those feature properties that have actually changed due to some process.
|
81 |
|
|
gml:AbstractTimeSlice basically provides a facility for attribute-level time stamping, in contrast to the object-level time stamping of dynamic feature instances.
|
82 |
|
|
The time slice can thus be viewed as event or process-oriented, whereas a snapshot is more state or structure-oriented. A timeslice has richer causality, whereas a snapshot merely portrays the status of the whole.
|
83 |
|
|
</documentation>
|
84 |
|
|
</annotation>
|
85 |
|
|
</element>
|
86 |
|
|
<complexType name="AbstractTimeSliceType" abstract="true">
|
87 |
|
|
<complexContent>
|
88 |
|
|
<extension base="gml:AbstractGMLType">
|
89 |
|
|
<sequence>
|
90 |
|
|
<element ref="gml:validTime"/>
|
91 |
|
|
<element ref="gml:dataSource" minOccurs="0"/>
|
92 |
|
|
</sequence>
|
93 |
|
|
</extension>
|
94 |
|
|
</complexContent>
|
95 |
|
|
</complexType>
|
96 |
|
|
<element name="history" type="gml:HistoryPropertyType">
|
97 |
|
|
<annotation>
|
98 |
|
|
<documentation>A generic sequence of events constitute a gml:history of an object.
|
99 |
|
|
The gml:history element contains a set of elements in the substitution group headed by the abstract element gml:AbstractTimeSlice, representing the time-varying properties of interest. The history property of a dynamic feature associates a feature instance with a sequence of time slices (i.e. change events) that encapsulate the evolution of the feature.</documentation>
|
100 |
|
|
</annotation>
|
101 |
|
|
</element>
|
102 |
|
|
<complexType name="HistoryPropertyType">
|
103 |
|
|
<sequence>
|
104 |
|
|
<element ref="gml:AbstractTimeSlice" maxOccurs="unbounded"/>
|
105 |
|
|
</sequence>
|
106 |
|
|
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
|
107 |
|
|
</complexType>
|
108 |
|
|
</schema>
|