Xsd for OpenCpn specific gpx files

[VanOfBees]

I'm building an application that I want to be able to generate opencpn specific gpx files. I see the gpx extensions tag contains opencpn elements namespace xmlnspencpn="http://www.opencpn.org". Is there somewhere I can find an xsd that defines this namespace?

Any pointers would be great, if this is the wrong forum for this I apologise and would be grateful to be pointed into the correct place.

[bdbcat]

VanOfBees... (the image that comes to mind is powerful...) There is no XSD yet. Not enough dev resources... I would be very happy if you could start us off in that direction. You can get the initial tags from just looking at a sample XML file from OCPN, like navobj.xml. If you can concoct a minimal XSD, we'll find a way to get it hosted on opencpn.org Thanks Dave

[Rasbats]

An old thread but...

Has anyone made any progress with this?

It would be useful for plugin work such as 'ocpn_draw' etc and could be extended to allow OpenCPN to display features available from other proprietary gpx extensions.

Mike

[Rasbats]

Work has started on a schema (xsd) for OpenCPN GPX files.

https://github.com/Rasbats/opencpn_schema

Early days. We would welcome pull requests updating the initial xsd schema file with the tags already in use by OpenCPN (Not Garmin or Topografix tags).

An explanation of how schema are used and how they are relevant to OpenCPN will be published shortly.

Initial development work is being done locally with the Chrome Web Server extension (127.0.0.1:8887). You would need to set up a similar environment to test/validate your work.

At present I am using the free Community Edition of Liquid Studio 2020 for writing and testing the OpenCPN schema.

https://www.liquid-technologies.com/...-community-key

Mike

[Rasbats]

Github has been updated for the tags presently used by OpenCPN:

https://github.com/Rasbats/opencpn_schema

The schema uses elements for each of the tags. For the future I think complex types need to be created. I don't think these can be used at the moment or the base code will be broken. A new tag could employ a complex type and the corresponding opencpn code could then use that tag.

The schema has some complex types already as part of the testing process.

Mike