Don't use MapSource or GPX Converter to generate GPX files
Wed, 07/04/2007 - 3:11pm
theTraveler
16 years
Currently, MapSource and GPX converter are incorrectly generating GPX files. In each WaypointExtension tag, it has a 'SchemaLocation' attribute which keeeps referencing the same schema with the same target namespace. If you're generating GPX format just for the sake of generating without utilizing the benefit of GPX specification, then I recommend waiting until the problem is corrected and continue uploading CSV files. I've notified Garmin of the bug, but not sure how soon they'll fix it.
Currently, these apps are creating GPX files as text files with Xml tags rather than creating it as an Xml document using DOM (see http://www.w3.org/TR/DOM-Level-2-Core/introduction.html). It's obvious that they just modified their CSV output logic to 'look' like Xml document without fully understanding of Xml document architecture.
You can tell which one is badly formatted by either opening it with an Xml editor (which you'll get an error) or Notepad (or something similar) and you'll notice that each WaypointExtension has same namespaces/schema declaration. This is not allowed in Xml and will definitely cause compatibility issues in the future.
When the group that maintains POI loader updates the software to treat GPX files with DOM, it most likely will 'puke' loading GPX-like files generated by MapSource. When that happens, it'll render these files useless.
I've recently uploaded a POI for Pei Wei restaurant. Load it to your unit and play with it. If you're intrested in leveraging the GPX specification for your future POI creation, I'll be happy to help.
P.S. When my 660 saves my favorites to current.gpx, it is correctly saving the data in GPX specification, so at least the group developing the firmware is aware of this. Lets hope they can influence the group that maintains MapSource.
Currently, MapSource and GPX converter are incorrectly generating GPX files. In each WaypointExtension tag, it has a 'SchemaLocation' attribute which keeeps referencing the same schema with the same target namespace. If you're generating GPX format just for the sake of generating without utilizing the benefit of GPX specification, then I recommend waiting until the problem is corrected and continue uploading CSV files. I've notified Garmin of the bug, but not sure how soon they'll fix it.
Currently, these apps are creating GPX files as text files with Xml tags rather than creating it as an Xml document using DOM (see http://www.w3.org/TR/DOM-Level-2-Core/introduction.html). It's obvious that they just modified their CSV output logic to 'look' like Xml document without fully understanding of Xml document architecture.
You can tell which one is badly formatted by either opening it with an Xml editor (which you'll get an error) or Notepad (or something similar) and you'll notice that each WaypointExtension has same namespaces/schema declaration. This is not allowed in Xml and will definitely cause compatibility issues in the future.
When the group that maintains POI loader updates the software to treat GPX files with DOM, it most likely will 'puke' loading GPX-like files generated by MapSource. When that happens, it'll render these files useless.
I've recently uploaded a POI for Pei Wei restaurant. Load it to your unit and play with it. If you're intrested in leveraging the GPX specification for your future POI creation, I'll be happy to help.
P.S. When my 660 saves my favorites to current.gpx, it is correctly saving the data in GPX specification, so at least the group developing the firmware is aware of this. Lets hope they can influence the group that maintains MapSource.
Garmin nüvi® 660, iPhone 8gb (Technology is not the solution. It's only a tool to help you achieve it.)