Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Think about the in/out API + metadata #170

Open
gberaudo opened this issue Dec 8, 2023 · 0 comments
Open

Think about the in/out API + metadata #170

gberaudo opened this issue Dec 8, 2023 · 0 comments

Comments

@gberaudo
Copy link
Contributor

gberaudo commented Dec 8, 2023

Instead of "segments", should we take a multilinestring?
Then we will not need the "controlepoints" as geometries (these are the ends of the multilinestrings).
We need validators: all multilinestrings are continguous (think how to store empty segments).
Think about metadata.

We might want to wrap all in a featurecollection that would be debuggable in QGIS, for example.

Restore should be synchronous.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant