Overview: Which OC properties are implemented, which are missing

[following5]

The current draft defines these OC elements:

• cache
  • type
  • size
  • trip_time
  • trip_distance
  • requires_password
  • other_code (can occur multiple times)
  • logs
    • log (can occur multiple times)
      • id and uuid attributes
      • site_team_entry

These additional OC-specific properties exist which are missing in GPX:

• cache attributes => see OC attributes in GPX files #9
• cache regional information: country and NUTS entities -- this information is redundant to the coordinates and rather unreliable
• MP3 files attached to OCPL caches; I think these should rather be attached/linked to the text, like images.
• log types => see OC log types #7
• OCDE/Okapi log flags "needs maintenance" and "listing is outdated". I guess that this will be rarely implemented; we may rather consider to include it into the log text.
• type of addtional waypoints; there is an Okapi discussion: Add "trailhead" as extra waypoint okapi#462
• OCPL stage number of additional waypoints; don't know how they are used.

So what undoubtedly makes sense are the attributes and waypoint types, and the OCPL stage numbers may also be useful. But as we have open feature requests at OCDE regarding requires_password (high prio!) and other_code, I would prefer to go for a soon release of the scheme, and adding the missing things later.

(Edit 2 October: adjusted the current draft structure and added log types to the missing information)

[following5]

Ready to go for initial release?

[wrygiel]

I will have to leave up to you. I simply don't have time for OC and OKAPI nowadays. I didn't have time to review most of these fields, but I guess you know what you're doing :)

[following5]

I have released the initial elements.

[following5]

The OC GPX extension is now online in OKAPI and OCDE native code. OCPL will follow soon.

[andrixnet]

OCPL stage number can be equivalent to the Groundspeak's waypoint 2 letter code, I think