Parse POINT(...) as GeoPoint in a SPARQL query
#1731
Merged
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
Signed-off-by: Johannes Kalmbach <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1731 +/- ##
=======================================
Coverage 89.92% 89.93%
=======================================
Files 393 393
Lines 37614 37599 -15
Branches 4231 4231
=======================================
- Hits 33823 33813 -10
+ Misses 2494 2483 -11
- Partials 1297 1303 +6 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Johannes Kalmbach <[email protected]>
Conformance check passed ✅No test result changes. |
|
hannahbast
approved these changes
Feb 4, 2025
hannahbast
changed the title
GeoPoints in a query
hannahbast
changed the title
GeoPoints in a queryPOINT(...) as GeoPoint in a SPARQL query
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.
Specifying an explicit
POINT(...)in a SPARQL query could lead to a segmentation fault because it wasn't actually parsed as aGeoPoint. This is now fixed.