-
Notifications
You must be signed in to change notification settings - Fork 143
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
Ensure GEOSGeometry
instances have srid
#11366
Comments
whatisgalen
added a commit
that referenced
this issue
Aug 20, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 20, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 20, 2024
Closed
11 tasks
renaming this ticket to reflect the bug at stake: instances of |
whatisgalen
changed the title
standardize srid assignment
Ensure GEOSGeometry instances have srid
Aug 20, 2024
whatisgalen
changed the title
Ensure GEOSGeometry instances have srid
Ensure Aug 20, 2024
GEOSGeometry
instances have srid
This was referenced Aug 20, 2024
Closed
whatisgalen
added a commit
that referenced
this issue
Aug 20, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 20, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 20, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 22, 2024
closing this as the default srid for django GEOSGeometry classes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there are numerous places where an srid as a kwarg is hard-coded (typically 4326). There are also two kwargs in
settings.py
:and
We should replace hard-coded references of 4326 with the first kwarg in settings, and wherever we instantiate a
GEOSGeometry
(or its extensions likePolygon
) we should also set the srid like so:Polygon(data, srid=int(settings.PREFERRED_COORDINATE_SYSTEMS[0].get("srid", 4326))
The text was updated successfully, but these errors were encountered: