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
Some devices do not know how to handle GPX tracks well (Mainly Gramin).
I have some code in my site that converts all the tracks to a single route.
And some code to convert all track segments to a single segment.
I thought this library might be a good fit for this logic.
Below is the code - assuming issue #12 is resolved:
Single segment:
@airbreather Do you think this code will make it to this library or not?
I'm asking since I'm working on upgrading NTS libraries and would like to do it in a single commit, I don't mind waiting a bit for this to be implemented in order to remove the code from my repository.
Do you think this code will make it to this library or not?
Probably not for a while. The main purpose of NetTopologySuite.IO.GPX is to convert back and forth between NTS and GPX.
IMO, the data model here isn't a really great foundation to actually build on for your application's own domain model, since it's primarily driven by the constraints of having to match a >14-year-old XML schema. So I'd expect this use case to be handled somewhat "automatically", via a process like:
Load your own domain model, perhaps from a GPX file provided by the user
Do whatever your application does
Export your domain model, perhaps to a GPX file that you build via whatever constraints are imposed by your target device
I have my own domain model, don't worry :-), but I think it's easier to convert GPX data to GPX data when one need to save to file in a specific way, otherwise I'll need to write almost the same conversion logic on every "scenario" instead of simple manipulations.
GPX maybe old, but it's one of the most common formats I've seen to be used, so I'm guessing it's here to stay.
airbreather
changed the title
Support GPX manipulation
Support merging multiple paths together
Sep 13, 2018
Some devices do not know how to handle GPX tracks well (Mainly Gramin).
I have some code in my site that converts all the tracks to a single route.
And some code to convert all track segments to a single segment.
I thought this library might be a good fit for this logic.
Below is the code - assuming issue #12 is resolved:
Single segment:
Single route:
The text was updated successfully, but these errors were encountered: