Could conceivably be added, sure (for reference - relevant part of schema is http://www.topografix.com/gpx/1/1/#type_wptType ). In fact, it should be fairly straightforward to drop in as they'll need processing (at ingest) independently of the trackpoints anyway
I guess you'd then want to be able to do something like
$gpx->listWaypoints();
To return all included Waypoints, or
$gpx->getWaypoint($wp-id);
To grab by a numerical identifier. Maybe even be able to retrieve by the name specified in the source GPX?
$gpx->getWaypointByName('foo');
Probably also worth adding something to the JSON metadata to indicate whether there are any waypoints included.
Have come across a slight hiccup with the implementation so far.
When exporting JSON, we only pass out the journey property (and conversely, only populate that when reading in from a JSON source). The current implementation adds waypoints as a completely separate property (as, really, they should be), which means they won't be included in a JSON dump.
Changing the JSON output so that it no longer solely pushes out journey would change the structure of the output and break b/c.
Although I don't overly like it as a solution, waypoints (and if they're added at a later date, route points) should probably be added as a property of journey to ensure they're included in the JSON output. Perhaps grouped under "related" or similar
All properties defined within wptType in the spec will always be present in the output, however if they weren't present in the source they will be null
Activity
2016-02-13 09:59:51
Could conceivably be added, sure (for reference - relevant part of schema is http://www.topografix.com/gpx/1/1/#type_wptType ). In fact, it should be fairly straightforward to drop in as they'll need processing (at ingest) independently of the trackpoints anyway
I guess you'd then want to be able to do something like
To return all included Waypoints, or
To grab by a numerical identifier. Maybe even be able to retrieve by the name specified in the source GPX?
Probably also worth adding something to the JSON metadata to indicate whether there are any waypoints included.
2016-02-20 22:12:10
So, we're going to want to look at creating a new object property to house the waypoints, and add the various possible attributes
Note that waypoints can have their own extensions (for example)
So support for those may need to be added later
2016-02-20 22:12:58
2016-02-20 22:38:27
Webhook User-Agent
View Commit
2016-02-20 22:42:03
When exporting JSON, we only pass out the journey property (and conversely, only populate that when reading in from a JSON source). The current implementation adds waypoints as a completely separate property (as, really, they should be), which means they won't be included in a JSON dump.
Changing the JSON output so that it no longer solely pushes out journey would change the structure of the output and break b/c.
Although I don't overly like it as a solution, waypoints (and if they're added at a later date, route points) should probably be added as a property of journey to ensure they're included in the JSON output. Perhaps grouped under "related" or similar
2016-02-20 22:46:27
Webhook User-Agent
View Commit
2016-02-20 22:53:27
Where the structure of a waypoint is as follows
All properties defined within wptType in the spec will always be present in the output, however if they weren't present in the source they will be null
2016-02-20 23:08:00
2016-02-20 23:08:03
2016-02-20 23:08:32
2016-02-20 23:10:52
2017-07-04 12:07:42
2017-07-04 12:07:42
2017-07-04 12:07:46