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

Support user uploaded boundaries #216

Open
timlinux opened this issue Feb 11, 2024 · 0 comments
Open

Support user uploaded boundaries #216

timlinux opened this issue Feb 11, 2024 · 0 comments
Assignees

Comments

@timlinux
Copy link
Collaborator

We would like to be able to create projects where the administration boundaries are provided by the project owner.

The functionality should support popular geospatial file formats such as:

  • geojson
  • geopackage
  • geoparquet
  • shapefile

Upon uploading the dataset, the user should indicate columns that correspond to:

  • Boundary level
  • Boundary name
  • Boundary unique code

Conceivably we could support multiple layers (e.g. admin0, admin1) to represent different administration levels, or we could require a single layer which contains different admin levels codified by their 'Boundary level' column to indicate which level they represent.

Additionally, it would be good to store a reference for the layer such that the boundaries can be cited if needed.

Internally we should load the user uploaded boundaries into the postgresql backend and serve them back to the project as as_mvt vector tiles so they they are essentially the same delivery mechanism as pulling boundaries from GeoRepo.

Where Ucodes and other GeoRepo specific API calls, this GeoSight-side implementation should completely replace the need for GeoRepo, emulating the appropriate API calls if needed or providing an alternate logic path for ucode lookups etc.

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

No branches or pull requests

2 participants