[API-users] Some geometry searches seem to not be working
jlegind at gbif.org
Thu May 31 14:26:44 CEST 2018
I know that we are using the left-hand rule to interpret polygons and the url you sent does not comply with this. The left-hand rule demands that when you travel along the polygon points, the area on the left-hand side of the direction you are travelling will be the inside of the shape. If you want a ring shape the inner polygon must comply with the right-hand rule.
This would be a nice feature to have for checking the validity of polygons. You can test the coordinate pairs here: http://geojsonlint.com/
Let me know if this helps.
From: API-users [mailto:api-users-bounces at lists.gbif.org] On Behalf Of Scott Chamberlain
Sent: 30 May 2018 18:25
To: api-users at lists.gbif.org
Subject: Re: [API-users] Some geometry searches seem to not be working
Any thoughts on this GBIF team?
On Fri, May 18, 2018 at 8:53 AM Scott Chamberlain <myrmecocystus at gmail.com<mailto:myrmecocystus at gmail.com>> wrote:
Any thoughts from the GBIF team?
On Tue, May 15, 2018 at 9:36 AM Scott Chamberlain <myrmecocystus at gmail.com<mailto:myrmecocystus at gmail.com>> wrote:
Another user of a package that uses rgbif reported I think the same problem https://github.com/ropensci/spocc/issues/187
On Tue, May 15, 2018 at 7:54 AM Scott Chamberlain <myrmecocystus at gmail.com<mailto:myrmecocystus at gmail.com>> wrote:
Users of rgbif have been reporting problems with geometry parameter in /occurrence route not working sometimes. It does indeed appear to work sometimes, but other times, it appears I think to be using latitude, but ignoring longitude. It's hard to give reproducible examples for command line or so, but here's a query where the longitude values appear to be all over the map, whereas latitude appear to be in the bounds.
using hasGeospatialIssue doesn't appear to help so I'm guessing there could be user error on my part or perhaps something going on with geometry WKT usage?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the API-users