-
Notifications
You must be signed in to change notification settings - Fork 159
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
Split up data and polygons #7
Comments
This was done, now we have
Each resource has a |
Couldn't this been done also in a way that doesn't require at the separation into two files for each "region"? For example as an array property in the respective feature's
This would make maintenance and PRs easier, I believe. A full separation between geometry and resource would only been needed if we would like to allow an n to m relationship between these (e.g. a joint inter-regional forum). |
Yes, I considered that, but I think this way is:
|
ok, I guess it comes down to a matter of taste 😉, but:
|
Before we go too wild adding all the things, we should separate the data from the polygons so that we don't run in to the kind of geojson duplication we see in editor-layer-index.
The text was updated successfully, but these errors were encountered: