Is your feature request related to a problem? Please describe.
Need to test and validate dateline crossing bounding boxes (+-180).
This is a requirement for the ocean community.
While returning results, they will not be the correct results due to the reordering of the coordinates, rather than spliting at the dateline.
{ "type": "geo", "field": "spatialCoverage", "active": true, "values": { "minLat": -60, "maxLat": 60, "minLon": 120, "maxLon": -120 } }
this filter is incorrect. returns things between -120 and 120, rather than
-180 to -120 and 120 to 180
?subj schema:spatialCoverage ?spatialCov .
?spatialCov schema:geo ?geo .
?geo schema:latitude ?lat .
?geo schema:longitude ?lon .
FILTER(?lat >= -60 && ?lat <= 60 && ?lon >= -120 && ?lon <= 120) .
}
should be:
Done this before by splitting at the dateline, and creating two filters/queries.
FILTER(?lat >= -60 && ?lat <= 60 && ( ?lon >= -180 && ?lon <= -120) || ( ?lon >= 120 && ?lon <= 180) ) .
Is your feature request related to a problem? Please describe.
Need to test and validate dateline crossing bounding boxes (+-180).
This is a requirement for the ocean community.
While returning results, they will not be the correct results due to the reordering of the coordinates, rather than spliting at the dateline.
this filter is incorrect. returns things between -120 and 120, rather than
-180 to -120 and 120 to 180
should be:
Done this before by splitting at the dateline, and creating two filters/queries.