11
Handling geographical intersections
Source: directus/directus#19329 · opened by @vidhav
Summary When looking at the source code for [_intersects]( and [_intersects_bbox]( it seems to me that they both do the same thing - send in any valid [GeoJSON geometry object]( and if it intersects, you get a result. This makes sense for the "intersects" filter, but a bbox implies that you have an actual [bounding box]( - in this case the coordinate of the lower left, and the upper right corners of the box: for Norway the bbox would be [4.34028279580897, 57.7491183943321, 31.2191612226094, 71.2506114447295]. Basic Example Motivation • By treating _intersects_bbox as an actual bounding box, the meaning of the filter, and why it is different from _intersects becomes much clearer. • This would also align Directus more closely with GIS standards. • The database can query an actual bounding box instead of a square polygon. - Can improve performance. - Could be useful if Directus were to support other coordinate systems in the future (I've …
No pledges yet. Be the first to back this.
Comments
Similar requests
Support 'Features' from the GeoJSON spec to store address data in the Map Field
11 votes · 0 comments
Best Practices for Handling Translations in a Multilingual Website
3 votes · 0 comments
Ability to create separate areas of collections
29 votes · 0 comments
Flows support for saving binary data as a file
31 votes · 0 comments
Add support for accessing raw request body in custom endpoints
2 votes · 0 comments
No comments yet.