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
If one has a collection of routes (own collection from for example a plotter or another navigation program) the current storage format of uuid named files is not very convenient.
As a technical use I would like to convert the route data to either an array of route resources or a single FeatureCollection and have that in a file named myfeaturecolletionsomething.json and either place it in the ...resources/routes/ directory or use a UI (Freeboard?) to upload the file.
There's the issue of uuids for the routes that needs a permanently stored solution.
The resources plugin could
peek into the contents and recognize the format
assign uuids
save the file
This way management of route collections would be easy, just pass around the file. We should make the file also downloadable.
In our data model this also could introduce the idea of route collections: with name, source, description and updated properties.
The text was updated successfully, but these errors were encountered:
Closely related is the idea of read-only routes/resources. Not sure if editing routes in a collection from a source makes sense, maybe rather create a copy and edit that?
If one has a collection of routes (own collection from for example a plotter or another navigation program) the current storage format of uuid named files is not very convenient.
As a technical use I would like to convert the route data to either an array of route resources or a single FeatureCollection and have that in a file named
myfeaturecolletionsomething.json
and either place it in the...resources/routes/
directory or use a UI (Freeboard?) to upload the file.There's the issue of uuids for the routes that needs a permanently stored solution.
The resources plugin could
This way management of route collections would be easy, just pass around the file. We should make the file also downloadable.
In our data model this also could introduce the idea of route collections: with name, source, description and updated properties.
The text was updated successfully, but these errors were encountered: