Logiqx / gp3s-coros

GPS3S wishlist for future COROS firmware releases
Creative Commons Zero v1.0 Universal
1 stars 0 forks source link

Rename <cog> in GPX export to <course> #15

Closed Logiqx closed 7 months ago

Logiqx commented 2 years ago

The GPX generated by COROS includes <cog> elements which causes problems for common GPX libraries.

The official GPX 1.0 schema definition defines <xsd:element name="course" type="gpx:degreesType" minOccurs="0"/>.

The consequence of this issue is that some GPX parsers such as gpxpy cannot access the COG data, expecting it to be <course> (as per the GPX schema) and not <cog>.

Please rename <cog> to <course> in the XML export. However, please do NOT change any field names in the FIT export.

Notes: 1) <sat> and <hdop> elements are correct, meeting the schema definition - http://www.topografix.com/GPX/1/0/gpx.xsd 2) Please do NOT rename the developer field in the FIT exports as that would cause issues for existing speedsurfing software. 3) Issue # 11 also requests that <speed> be included in GPX exports.

I have been writing some notes relating to GPX files, speed and issues specifically affecting the COROS implementation:

Logiqx commented 1 year ago

Note: I've written a document detailing all of the issues in GPX files generated by COROS:

https://logiqx.github.io/gps-wizard/gpx/issues/coros.html

Logiqx commented 1 year ago

I've add further clarification to the original description, including links to my GPX articles.

Logiqx commented 7 months ago

Closing this issue as it is covered by #19 (ensure GPX compliance)