Go Down

Topic: Speed zone data in easily converted format (Read 873 times) previous topic - next topic

CrossRoads

Oh, and its 12Mbyte of this stuff.

50,000 lines deep it has this kind of stuff
Code: [Select]

<xs:element name="MapProduct" type="Family_t"/>

<xs:complexType name="Family_t">
    <xs:sequence>
        <xs:element name="Name" type="xs:string"/>
        <xs:element name="InstallationID" type="xs:positiveInteger" minOccurs="0">
            <xs:annotation><xs:documentation>This element is a globally unique identifier to be used for equality comparison
            to determine if an installed map product is an older/equal/newer version of a to-be-installed map product.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="DataVersion" type="xs:positiveInteger" minOccurs="0">
            <xs:annotation><xs:documentation>If two instances have an equal InstallationID element then this element can be compared to determine
            if this instance is older/equal/newer. Larger values are newer.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="DataFormat" type="DataFormat_t"/>
        <xs:element name="ID" type="xs:positiveInteger" minOccurs="0">
            <xs:annotation><xs:documentation>This element is not present for legacy products.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="IDX" type="xs:string" minOccurs="0">
            <xs:annotation><xs:documentation>The path to the IDX file for this product.
            This path is relative to the location of an instance document of this schema.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="MDR" type="xs:string" minOccurs="0">
            <xs:annotation><xs:documentation>The path to the MDR directory for this product.
            This path is relative to the location of an instance document of this schema..
            Processors should be tolerant of the presence or lack of a trailing directory separator in this path.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="TRF" type="xs:string" minOccurs="0">
            <xs:annotation><xs:documentation>The path to the TRF file for this product.
            This path is relative to the location of an instance document of this schema.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="TYP" type="xs:string" minOccurs="0">
            <xs:annotation><xs:documentation>The path to the TYP file for this product.
            This path is relative to the location of an instance document of this schema.</xs:documentation></xs:annotation>
        </xs:element>
        <xs:element name="UnlockURL" type="xs:anyURI" minOccurs="0"/>
        <xs:element name="SubProduct" type="Product_t" maxOccurs="unbounded"/>
    </xs:sequence>
</xs:complexType>


and
Code: [Select]

<xsd:complexType name="TrackSeg_t">
    <xsd:sequence> <!-- elements must appear in this order -->
      <xsd:element name="trkpt" type="gpx:TrackPoint_t" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>

  <xsd:complexType name="TrackPoint_t">
    <xsd:sequence> <!-- elements must appear in this order -->

  <!-- Position info -->
  <xsd:element name="ele" type="xsd:decimal" minOccurs="0"/>
  <xsd:element name="time" type="xsd:dateTime" minOccurs="0"/>
  <xsd:element name="course" type="gpx:degreesType" minOccurs="0"/>
  <xsd:element name="speed" type="xsd:decimal" minOccurs="0"/>
  <xsd:element name="magvar" type="gpx:degreesType" minOccurs="0"/>
  <xsd:element name="geoidheight" type="xsd:decimal" minOccurs="0"/>

  <!-- Description info -->
  <xsd:element name="name" type="xsd:string" minOccurs="0"/>
  <xsd:element name="cmt" type="xsd:string" minOccurs="0"/>
  <xsd:element name="desc" type="xsd:string" minOccurs="0"/>
  <xsd:element name="src" type="xsd:string" minOccurs="0"/>
  <xsd:element name="url" type="xsd:anyURI" minOccurs="0"/>
  <xsd:element name="urlname" type="xsd:string" minOccurs="0"/>
  <xsd:element name="sym" type="xsd:string" minOccurs="0"/>
  <xsd:element name="type" type="xsd:string" minOccurs="0"/>

  <!-- Accuracy info -->
  <xsd:element name="fix" type="gpx:fixType" minOccurs="0"/>
  <xsd:element name="sat" type="xsd:nonNegativeInteger" minOccurs="0"/>
  <xsd:element name="hdop" type="xsd:decimal" minOccurs="0"/>
  <xsd:element name="vdop" type="xsd:decimal" minOccurs="0"/>
  <xsd:element name="pdop" type="xsd:decimal" minOccurs="0"/>
  <xsd:element name="ageofdgpsdata" type="xsd:decimal" minOccurs="0"/>
  <xsd:element name="dgpsid" type="gpx:dgpsStationType" minOccurs="0"/>

  <!-- you can add your own privately defined trkpt elements at the end of the trkpt -->
  <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax"/>
    </xsd:sequence>
<xsd:attribute name="lat" type="gpx:latitudeType" use="required"/>
<xsd:attribute name="lon" type="gpx:longitudeType" use="required"/>
  </xsd:complexType>

for about 6,000 lines.
Then another couple thousand lines of stuff.
Designing & building electrical circuits for over 25 years. Check out the ATMega1284P based Bobuino and other '328P & '1284P creations & offerings at  www.crossroadsfencing.com/BobuinoRev17.
Arduino for Teens available at Amazon.com.

robtillaart


I think this XML stuff is an Xml Schema Definition, it is a description of how XML data should look like, which fields and constraints etc. However the data seems binary, not XML so ... ?  Could the XSD be used to describe the binary structure ?  ...
Rob Tillaart

Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -
(Please do not PM for private consultancy)

J.C. Woltz

Thank you everyone!

If I get to a usable point, I will let you know.

Go Up