<div dir="ltr">Any thoughts from the GBIF team?<div><br></div><div>Best, Scott<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, May 15, 2018 at 9:36 AM Scott Chamberlain <<a href="mailto:myrmecocystus@gmail.com">myrmecocystus@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Another user of a package that uses rgbif reported I think the same problem <a href="https://github.com/ropensci/spocc/issues/187" target="_blank">https://github.com/ropensci/spocc/issues/187</a> <div><br></div><div>Best, Scott<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, May 15, 2018 at 7:54 AM Scott Chamberlain <<a href="mailto:myrmecocystus@gmail.com" target="_blank">myrmecocystus@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, <div><br></div><div>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.</div><div><br></div><div><a href="https://api.gbif.org/v1/occurrence/search?limit=300&offset=0&geometry=POLYGON%28%28-0.1%2050.0%2C14.3%2050.0%2C14.3%2042.5%2C-0.1%2042.5%2C-0.1%2050.0%29%29&" target="_blank">https://api.gbif.org/v1/occurrence/search?limit=300&offset=0&geometry=POLYGON%28%28-0.1%2050.0%2C14.3%2050.0%2C14.3%2042.5%2C-0.1%2042.5%2C-0.1%2050.0%29%29&</a> <br></div><div><br></div><div>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?</div><div><br></div><div>Best, Scott<br></div></div></blockquote></div></blockquote></div>