[8472] migrate point field to GeoDjango to allow filtering by distance Part 2 #6116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to allow filtering by distance on a database level. - add restframework-gis - add new mixins which handle conversion between geojson and GeoDjango fields - use spatialite instead of sqlite to support gis/GeoDjango
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Migrate the point field of kiezradar, project, plans, bplans and extprojects to GeoDjango to allow things like filtering by distance, validate if a point is in the berlin polygon etc. This is quite a big change but I couldn't come up with any other good solution. The actual notification part is still missing though.
depends on liqd/adhocracy4#1775
I fixed some issues I found after deploying this on dev
Tasks