Thread: [Gpsbabel-misc] Bounds in GPX XML
Brought to you by:
robertl
From: Lilian M. <lil...@ya...> - 2006-05-17 20:57:07
|
Hello, On my web sitte (www.utagawavtt.com) a user posted a GPX file encoded with GPSBabel. When tryiing to open it with some applications like CompeGPS, CartoExploreur, it was impossible. Looking inside the file I was surprised to see this line : <bounds minlat="50.350435800" minlon ="2.638216700" maxlat="50.431755500" maxlon="2.725816000" /> Replacing this line with <bounds>minlat="50.350435800" minlon ="2.638216700" maxlat="50.431755500" maxlon="2.725816000"</bounds> it worked. So I checked the GPX doc and found that the metadata representation is : <bounds> <http://www.topografix.com/gpx/1/1/#type_boundsType> boundsType </bounds> Any clue why GPSbabel doesn't follow the specification here ? Rgds Lilian |
From: Ron P. <ro...@pa...> - 2006-05-17 21:11:11
|
Lilian Morinon wrote: > <bounds minlat="50.350435800" minlon ="2.638216700" > maxlat="50.431755500" maxlon="2.725816000" /> > Replacing this line with > > <bounds>minlat="50.350435800" minlon ="2.638216700" > maxlat="50.431755500" maxlon="2.725816000"</bounds> > > it worked. > > So I checked the GPX doc and found that the metadata representation is : > <bounds> boundsType > <http://www.topografix.com/gpx/1/1/#type_boundsType> </bounds> > > Any clue why GPSbabel doesn't follow the specification here ? Because the "XML Instance Representation" you're quoting doesn't match the actual schema? If you look at the actual schema, you get a completely different story: <xsd:complexType name="metadataType"> <xsd:sequence> <-- elements must appear in this order --> <xsd:element name="name" type="xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:string" minOccurs="0"/> <xsd:element name="desc" type="xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:string" minOccurs="0"/> <xsd:element name="author" type="personType <http://www.topografix.com/gpx/1/1/#type_personType>" minOccurs="0"/> <xsd:element name="copyright" type="copyrightType <http://www.topografix.com/gpx/1/1/#type_copyrightType>" minOccurs="0"/> <xsd:element name="link" type="linkType <http://www.topografix.com/gpx/1/1/#type_linkType>" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="time" type="xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:dateTime" minOccurs="0"/> <xsd:element name="keywords" type="xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:string" minOccurs="0"/> <xsd:element name="bounds" type="boundsType <http://www.topografix.com/gpx/1/1/#type_boundsType>" minOccurs="0"/> <xsd:element name="extensions" type="extensionsType <http://www.topografix.com/gpx/1/1/#type_extensionsType>" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="boundsType"> <xsd:attribute name="minlat" type="latitudeType <http://www.topografix.com/gpx/1/1/#type_latitudeType>" use="required"/> <xsd:attribute name="minlon" type="longitudeType <http://www.topografix.com/gpx/1/1/#type_longitudeType>" use="required"/> <xsd:attribute name="maxlat" type="latitudeType <http://www.topografix.com/gpx/1/1/#type_latitudeType>" use="required"/> <xsd:attribute name="maxlon" type="longitudeType <http://www.topografix.com/gpx/1/1/#type_longitudeType>" use="required"/> </xsd:complexType> This says that minlat, minlon, maxlat, and maxlon are attributes. GPSBabel is following the specification; it's the other programs that are broken. |
From: Lilian M. <lil...@ya...> - 2006-05-17 21:14:43
|
Thanks. I should have mentionned that the GPX version was 1.0 Any difference then ? Lilian=20 -----Message d'origine----- De : gps...@li... [mailto:gps...@li...] De la part de Ron = Parker Envoy=E9 : mercredi 17 mai 2006 23:11 =C0 : Lilian Morinon Cc : gps...@li... Objet : Re: [Gpsbabel-misc] Bounds in GPX XML Lilian Morinon wrote: > <bounds minlat=3D"50.350435800" minlon =3D"2.638216700"=20 > maxlat=3D"50.431755500" maxlon=3D"2.725816000" /> Replacing this line = with > =20 > <bounds>minlat=3D"50.350435800" minlon =3D"2.638216700"=20 > maxlat=3D"50.431755500" maxlon=3D"2.725816000"</bounds> > =20 > it worked. > =20 > So I checked the GPX doc and found that the metadata representation is = : > <bounds> boundsType > <http://www.topografix.com/gpx/1/1/#type_boundsType> </bounds> > =20 > Any clue why GPSbabel doesn't follow the specification here ? Because the "XML Instance Representation" you're quoting doesn't match = the actual schema? If you look at the actual schema, you get a completely different story: <xsd:complexType name=3D"metadataType"> <xsd:sequence> <-- elements must appear in this order --> <xsd:element name=3D"name" type=3D"xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:string" minOccurs=3D"0"/> <xsd:element name=3D"desc" type=3D"xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:string" minOccurs=3D"0"/> <xsd:element name=3D"author" type=3D"personType <http://www.topografix.com/gpx/1/1/#type_personType>" minOccurs=3D"0"/> <xsd:element name=3D"copyright" type=3D"copyrightType <http://www.topografix.com/gpx/1/1/#type_copyrightType>" = minOccurs=3D"0"/> <xsd:element name=3D"link" type=3D"linkType <http://www.topografix.com/gpx/1/1/#type_linkType>" minOccurs=3D"0"=20 maxOccurs=3D"unbounded"/> <xsd:element name=3D"time" type=3D"xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:dateTime" minOccurs=3D"0"/> <xsd:element name=3D"keywords" type=3D"xsd <http://www.topografix.com/gpx/1/1/#ns_xsd>:string" minOccurs=3D"0"/> <xsd:element name=3D"bounds" type=3D"boundsType <http://www.topografix.com/gpx/1/1/#type_boundsType>" minOccurs=3D"0"/> <xsd:element name=3D"extensions" type=3D"extensionsType <http://www.topografix.com/gpx/1/1/#type_extensionsType>" = minOccurs=3D"0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name=3D"boundsType"> <xsd:attribute name=3D"minlat" type=3D"latitudeType <http://www.topografix.com/gpx/1/1/#type_latitudeType>" = use=3D"required"/> <xsd:attribute name=3D"minlon" type=3D"longitudeType <http://www.topografix.com/gpx/1/1/#type_longitudeType>" = use=3D"required"/> <xsd:attribute name=3D"maxlat" type=3D"latitudeType <http://www.topografix.com/gpx/1/1/#type_latitudeType>" = use=3D"required"/> <xsd:attribute name=3D"maxlon" type=3D"longitudeType <http://www.topografix.com/gpx/1/1/#type_longitudeType>" = use=3D"required"/> </xsd:complexType> This says that minlat, minlon, maxlat, and maxlon are attributes. =20 GPSBabel is following the specification; it's the other programs that = are broken. ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, = security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache = Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Gpsbabel-misc mailing list Gps...@li... To unsubscribe, change list options, or see archives, visit: https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc ___________________________________________________________________________ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set |
From: Robert L. <rob...@us...> - 2006-05-17 21:40:37
|
Lilian Morinon wrote: > Thanks. I should have mentionned that the GPX version was 1.0 > Any difference then ? The file you sent me is valid GPX 1.0, which is exactly what it claims to be: SAXCount -v=always -n -s /tmp/utgtrack-677.gpx /tmp/utgtrack-677.gpx: 313 ms (1260 elems, 845 attrs, 2518 spaces, 12470 chars) I strongly suspect you have readers that don't read valid GPX 1.0. (That's the nice thing about GPX - there's a very clearly defined line in the sand between the reader and the writer.) |
From: Robert L. <rob...@us...> - 2006-05-17 21:16:01
|
Lilian Morinon wrote: > When tryiing to open it with some applications like CompeGPS, > CartoExploreur, it was impossible. I don't have either of those programs, but I'd I'd be interested in seeing the file. > Looking inside the file I was surprised to see this line : > > > > <bounds minlat="50.350435800" minlon ="2.638216700" maxlat="50.431755500" > maxlon="2.725816000" /> > > Replacing this line with > > <bounds>minlat="50.350435800" minlon ="2.638216700" maxlat="50.431755500" > maxlon="2.725816000"</bounds> That's a very odd encoding. As one of the GPX spec group, I'd never have signed up for that syntax. Does it *really* use that data or does it see an empty bounds tag and, since it's optional anyway, compute its own BB anyway. I just spot checked our own output on a validator, and checked the output Mapsource and ExpertGPS and they both agree with the first. Far more likely, you're mixing GPX 1.1 and GPX 1.0 here. Bounds did move from a top-level tag into metadata. Our writer defaults to 1.1 and if you have readers that can't cope with 1.0, you need to tell us to write 1.1. RJL |
From: Lilian M. <lil...@ya...> - 2006-05-17 21:24:47
|
Hello, Thanks for the support and quick reply. I have mentionned the issue to CompeGPS and CartoExploreur (Bayo) support. Lilian -----Message d'origine----- De : gps...@li... [mailto:gps...@li...] De la part de Robert = Lipe Envoy=E9 : mercredi 17 mai 2006 23:16 =C0 : Lilian Morinon Cc : gps...@li... Objet : Re: [Gpsbabel-misc] Bounds in GPX XML Lilian Morinon wrote: > When tryiing to open it with some applications like = CompeGPS, > CartoExploreur, it was impossible. I don't have either of those programs, but I'd I'd be interested in = seeing the file. > Looking inside the file I was surprised to see this line : >=20 >=20 >=20 > <bounds minlat=3D"50.350435800" minlon =3D"2.638216700" maxlat=3D"50.431755500" > maxlon=3D"2.725816000" /> >=20 > Replacing this line with >=20 > <bounds>minlat=3D"50.350435800" minlon =3D"2.638216700" maxlat=3D"50.431755500" > maxlon=3D"2.725816000"</bounds> That's a very odd encoding. As one of the GPX spec group, I'd never have signed up for that syntax. Does it *really* use that data or does it see = an empty bounds tag and, since it's optional anyway, compute its own BB = anyway. I just spot checked our own output on a validator, and checked the = output Mapsource and ExpertGPS and they both agree with the first. Far more likely, you're mixing GPX 1.1 and GPX 1.0 here. Bounds did move from a top-level tag into metadata. Our writer defaults to 1.1 and if you have readers that can't cope with 1.0, you need to tell us to write 1.1. RJL ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, = security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache = Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Gpsbabel-misc mailing list Gps...@li... To unsubscribe, change list options, or see archives, visit: https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc ___________________________________________________________________________ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set |