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

Integrate local boundary for altering GeoRepo - Model #219

Closed
3 tasks
meomancer opened this issue Feb 12, 2024 · 0 comments
Closed
3 tasks

Integrate local boundary for altering GeoRepo - Model #219

meomancer opened this issue Feb 12, 2024 · 0 comments
Assignees
Labels
🕓 3 - 4 hours It will take me between 2 hours to half a day. Kartoza Funded

Comments

@meomancer
Copy link
Collaborator

meomancer commented Feb 12, 2024

Child of #216

Currently we already have Reference Layer View and entity on our database
We can reuse this as our local database

TODO:

  • Add geometry field on entity model
  • Add is_remote on view model to indicate if the data is from georepo or local data
  • Add new model Levels, to have level information with number and name and link it to View
@meomancer meomancer added the 🕓 3 - 4 hours It will take me between 2 hours to half a day. label Feb 12, 2024
@meomancer meomancer self-assigned this Feb 12, 2024
@meomancer meomancer changed the title Intergrate local boundary for alternating GeoRepo Intergrate local boundary for alternating GeoRepo - Model Feb 12, 2024
@meomancer meomancer changed the title Intergrate local boundary for alternating GeoRepo - Model Intergrate local boundary for altering GeoRepo - Model Feb 12, 2024
@timlinux timlinux changed the title Intergrate local boundary for altering GeoRepo - Model Integrate local boundary for altering GeoRepo - Model Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕓 3 - 4 hours It will take me between 2 hours to half a day. Kartoza Funded
Projects
None yet
Development

No branches or pull requests

1 participant