RFC for geospatial indexing #87
Open
Conversation
This file contains hidden or 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
Signed-off-by: Adam Kaczmarek <[email protected]>
adamk-janea
force-pushed
the
geospatial-rfc
branch
from
1132bab to
8335d89
Compare
Signed-off-by: Adam Kaczmarek <[email protected]>
Signed-off-by: Adam Kaczmarek <[email protected]>
yairgott
reviewed
May 15, 2025
yairgott
reviewed
May 21, 2025
|
|
||
| ## Open Questions | ||
|
|
||
| - **Coordinate Reference Systems**: Should multiple coordinate reference systems be supported, or should the system standardize on WGS 84? |
There was a problem hiding this comment.
IMO, starting with WGS 84 is a good approach while keeping in mind that additional reference systems could be supported in the future.
| ## Open Questions | ||
|
|
||
| - **Coordinate Reference Systems**: Should multiple coordinate reference systems be supported, or should the system standardize on WGS 84? | ||
| - **3D Geospatial Data**: Should three-dimensional data (latitude, longitude, altitude) be supported in the future? |
There was a problem hiding this comment.
It would be good to keep this in mind as a potential future enhancement during implementation.
|
|
||
| - **Coordinate Reference Systems**: Should multiple coordinate reference systems be supported, or should the system standardize on WGS 84? | ||
| - **3D Geospatial Data**: Should three-dimensional data (latitude, longitude, altitude) be supported in the future? | ||
| - **Advanced Spatial Queries**: Should additional spatial predicates (e.g., intersects, contains) be supported beyond radius and bounding box searches? |
There was a problem hiding this comment.
Same as the previous comment.
yairgott
approved these changes
May 23, 2025
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.
No description provided.