You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be a great addition if we could add the origin from where a feature was extracted.
For example if you have GPX file with a track and a route, you will receive two features, but you don't know which feature was the track and which feature was the route.
Waypoints are obviously type: 'Point', so that would be straight forward. But at least for route and track it would be handy if one could determine which is which.
I could provide a PR for this adding a field to the properties like origin: wpt|rte|trk (or something along these lines).
The text was updated successfully, but these errors were encountered:
It would be a great addition if we could add the origin from where a feature was extracted.
For example if you have GPX file with a track and a route, you will receive two features, but you don't know which feature was the track and which feature was the route.
Waypoints are obviously
type: 'Point'
, so that would be straight forward. But at least for route and track it would be handy if one could determine which is which.I could provide a PR for this adding a field to the properties like
origin: wpt|rte|trk
(or something along these lines).The text was updated successfully, but these errors were encountered: