search

kmlchemist / kml-schema

Automatically exported from code.google.com/p/kml-schema
0 stars 0 forks source link

Track properties are unordered #10

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The XSD 1.1 schema currently uses the <all> compositor; however this makes it 
impossible to correlate timestamps with other time-varying data items. For 
example, this Track instance is schema-valid:

<Track  xmlns="http://www.opengis.net/kml/2.2">
  <when>2010-05-28T02:02:09Z</when>
  <when>2010-05-28T02:02:35Z</when>
  <coord>-122.205712 37.373288 152.000000</coord>
  <coord>-122.204678 37.373939 147.000000</coord>
  <when>2010-05-28T02:02:44Z</when>
  <when>2010-05-28T02:02:53Z</when>
  <when>2010-05-28T02:02:54Z</when>
  <coord>-122.203572 37.374630 142.199997</coord>
  <when>2010-05-28T02:02:55Z</when>
  <when>2010-05-28T02:02:56Z</when>
  <coord>-122.203329 37.374780 141.199997</coord>
  <coord>-122.207881 37.371915 156.000000</coord>
  <coord>-122.203451 37.374706 141.800003</coord>
  <coord>-122.203207 37.374857 140.199997</coord>
</Track>

At least the when, coord, and angles elements should be ordered.

Original issue reported on code.google.com by rjmart...@gmail.com on 7 Oct 2014 at 6:29

GoogleCodeExporter commented 9 years ago 
An implementation should interpret this document as follows:
- Assuming that there equal numbers of when, coord and angles elements...
- Extract all the <when> elememts in document sequence order
- Extract all the <coord> elememts in document sequence order
- Extract all the <angles> elememts in document sequence order
- Treat these as parallel arrays, matching the elements by their numerical 
index.

Original comment by alchem...@google.com on 7 Oct 2014 at 9:56