Loading ...
Sorry, an error occurred while loading the content.

Re: [gpsxml] Re: Course element

Expand Messages
  • Robert Lipe
    ... If you actually need them (many don t) your options are 1.0 or to create/use an extension as cited. ... There is probably discussion in the archives from
    Message 1 of 10 , May 16, 2012
    • 0 Attachment
      >
      > So I guess if I want to use speed and course then I will have to stick
      > with the 1.0 schema.


      If you actually need them (many don't) your options are 1.0 or to
      create/use an extension as cited.


      > Is there a brief description somewhere of the differences and added
      > features of 1.1 compared to 1.0 ?


      There is probably discussion in the archives from when we created 1.1.

      The schemas are authoritative, but from the top of my head, <metadata>
      moved, <link> was changed to allow multiple links and introduce an
      incompatible syntax, and <extension> was added throughout.


      [Non-text portions of this message have been removed]
    • cbyh
      Thanks. So for fairly simple use, probably better to stick with 1.0.
      Message 2 of 10 , May 16, 2012
      • 0 Attachment
        Thanks. So for fairly simple use, probably better to stick with 1.0.
      • phil_hornby
        ... ... ...
        Message 3 of 10 , May 16, 2012
        • 0 Attachment
          --- In gpsxml@yahoogroups.com, "cbyh" <cbyh@...> wrote:


          > I am producing a GPS file using the 1.0 schema containing a track -
          here is a small part of it:
          >

          > <trkpt lat="10.311063" lon="-84.813530">
          > <ele>1401.10</ele>
          > <speed>3.33</speed>
          > <course>334.3</course>
          > <time>2012-05-04T21:00:38Z</time>
          > </trkpt>
          ...

          But the schema at http://www.topografix.com/GPX/1/0/gpx.xsd contains:
          >
          <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"/>
          >


          You've got <ele><speed><course><time>...

          when you need <ele><time><course><speed>



          [Non-text portions of this message have been removed]
        • Joshua Judson Rosen
          ... We use GPX 1.1 + Garmin s TrackPointExtensionv2 schema in FoxtrotGPS, which gets us support for speed, course, and a number of other useful parameters too:
          Message 4 of 10 , May 19, 2012
          • 0 Attachment
            "cbyh" <cbyh@...> writes:
            >
            > Thanks. So for fairly simple use, probably better to stick with 1.0.

            We use GPX 1.1 + Garmin's TrackPointExtensionv2 schema in FoxtrotGPS,
            which gets us support for speed, course, and a number of other useful
            parameters too:

            http://www8.garmin.com/xmlschemas/TrackPointExtensionv2.xsd

            --
            "Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))."
          Your message has been successfully submitted and would be delivered to recipients shortly.