#36417 closed Bug (needsinfo)
Intersects result not matching 'not disjoint' result for geography field
Reported by: | Jiro Shirota | Owned by: | |
---|---|---|---|
Component: | GIS | Version: | 5.1 |
Severity: | Normal | Keywords: | |
Cc: | Claude Paroz | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The following two queries don't always result in the same output.
.filter(my_geography_field__intersects=polygon) .exclude(my_geography_field__disjoint=polygon)
Also the intersects example above is significantly slower.
It may be that ::geometry casting needs to be applied to a geography field all the time (not just for operations supported for geography). Possibly remove the second condition in the following if statement?
Change History (2)
comment:1 by , 3 weeks ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
Type: | Uncategorized → Bug |
comment:2 by , 3 weeks ago
Cc: | added |
---|
Note:
See TracTickets
for help on using tickets.
Hello Jiro Shirota, thank you for taking the time to create this ticket. Unfortunately, we'll need more information in order to investigate this issue further. In particular, it would be helpful if you could provide:
Without these details, it's difficult to determine whether this is a bug in Django or an issue with the specific usage or environment. If you're unsure how to isolate the problem or would like guidance from other users, feel free to post on the Django Forum, where community members can help troubleshoot and clarify expected behavior. There is a specific category for GeoDjango.
For now, I'm going to close this ticket as
needsinfo
following the ticket triaging process, but please feel free to reopen it once you're able to provide the additional details.