October 2015 - API-users - lists.gbif.org

Counts per degree cell
by Scott Chamberlain 29 Oct '15

29 Oct '15

Hi all! AFAIK, what the route http://data.gbif.org/ws/rest/density/list used to provide is gone, right? If so, I imagine that it was too expensive computationally? If not, might it come back? Some users requesting that kind of data. Thanks! Scott

2 2

dateline queries
by jorrit poelen 29 Oct '15

29 Oct '15

Hi! When searching for occurrences by geometry I am using the following WKT polygon: POLYGON((116.71875 55.7765730186677,116.71875 90,87.1875 90,87.1875 55.7765730186677,116.71875 55.7765730186677)) This polygon is intended to cover parts of eastern Russia, Alaska, northern Canada and Greenland. For some reason, the GBIF results include the inverted longitudinal selection. Does GBIF support dateline wrapping for it’s spatial queries? If so, how should I form the geometry to capture this? thx, -jorrit PS1 Is there a github issue list than I can post this at? PS2 For context, please see a working prototype at: http://www.effechecka.org/#geometry=POLYGON%28%28116.71875%2055.77657301866…

2 1

Get a '400 Bad Request'
by Maria Cubillos 22 Oct '15

22 Oct '15

Hi, when I try to sent a request to http://api.gbif.org/v1/species?name=Allium%20Sativum&limit=1&callback=jQuer… from browser which has Language option in español(Latinoamerica) this send Accept-Language: en-US,en;q=0.8,es;q=0.6,es-419;q=0.4 in the headers, then I recive a 400 Bad Request. This only happend when I have this language option. With español(Latinoamerica) General 1. Request URL: http://api.gbif.org/v1/species?name=Allium%20Sativum&limit=1&callback=jQuer… 2. Request Method: GET 3. Status Code: 400 Bad Request 4. Remote Address: 130.226.238.135:80 1. Response Headersview source 1. Accept-Ranges: bytes 2. Access-Control-Allow-Origin: * 3. Age: 0 4. Connection: keep-alive 5. Content-Length: 72 6. Content-Type: text/plain 7. Date: Thu, 22 Oct 2015 14:59:13 GMT 8. Server: Jetty(9.2.z-SNAPSHOT) 9. Via: 1.1 varnish 10. x-api-url: /v1/species?name=Allium%20Sativum&limit=1&callback=jQuery214020442963019013405_1445525943637&_=1445525943638 11. X-Varnish: 282045222 2. Request Headersview source 1. Accept: */* 2. Accept-Encoding: gzip, deflate, sdch 3. Accept-Language: en-US,en;q=0.8,es;q=0.6,es-419;q=0.4 4. Connection: keep-alive 5. Host: api.gbif.org 6. Referer: http://192.168.206.86:7000/?taxonRecordName=Allium+Sativum&abstract= 7. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2537.0 Safari/537.36 3. Query String Parametersview sourceview URL encoded 1. name: Allium Sativum 2. limit: 1 3. callback: jQuery214020442963019013405_1445525943637 4. _: 1445525943638 Without español(Latinoamerica) General Remote Address:130.226.238.135:80 Request URL: http://api.gbif.org/v1/species?name=Allium%20Sativum&limit=1&callback=jQuer… Request Method:GET Status Code:200 OK Response Headers view source Accept-Ranges:bytes Access-Control-Allow-Origin:* Age:0 Connection:keep-alive Content-Length:1031 Content-Type:application/javascript Date:Thu, 22 Oct 2015 16:46:26 GMT Server:Jetty(9.2.z-SNAPSHOT) Via:1.1 varnish x-api-url:/v1/species?name=Allium%20Sativum&limit=1&callback=jQuery21406685116644948721_1445532365523&_=1445532365524 X-Varnish:282682159 Request Headers view source Accept:*/* Accept-Encoding:gzip, deflate, sdch Accept-Language:en-US,en;q=0.8,es;q=0.6 Connection:keep-alive Host:api.gbif.org Referer:http://localhost:7000/ User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/41.0.2272.76 Chrome/41.0.2272.76 Safari/537.36 Query String Parameters view source view URL encoded name:Allium Sativum limit:1 callback:jQuery21406685116644948721_1445532365523 _:1445532365524 -- *María Fernanda Cubillos Vargas*Investigadora Asistente - Sistema de Información sobre Biodiversidad de Colombia (SIB Colombia) *Instituto de Investigación de Recursos BiológicosAlexander von Humboldt**Avenida Paseo Bolivar (Circunvalar) 16-20 * *PBX: (57) 1 320 2767 Ext. 1154Bogotá, D.C., Colombia* Antes de imprimir este mensaje, piensa si realmente necesitas hacerlo. ¡Gracias!

1 0

eventDate parameter in occurrence/search?
by Kumiko Totsu 16 Oct '15

16 Oct '15

Hi all, I found a problem using 'eventDate' in the occurrence API. I could only get results by range queries but not with a date. 14 results between 2014-03-10 and 2014-03-11 http://api.gbif.org/v1/occurrence/search?institutionCode=NIES&eventDate=201… 0 result on 2014-03-11 (It should be 14 results) http://api.gbif.org/v1/occurrence/search?institutionCode=NIES&eventDate=201… 0 result on 2014-03-10 http://api.gbif.org/v1/occurrence/search?institutionCode=NIES&eventDate=201… The example below is totally fine, so it seems that not all data have this problem. 14 results between 2015-03-17 and 2015-03-18 http://api.gbif.org/v1/occurrence/search?institutionCode=NIES&eventDate=201… 14 results on 2015-03-18 http://api.gbif.org/v1/occurrence/search?institutionCode=NIES&eventDate=201… 0 result on 2015-03-17 http://api.gbif.org/v1/occurrence/search?institutionCode=NIES&eventDate=201… Is there anything wrong with data or API? Cheers, Kumiko -------------------------------------------------------- Kumiko Totsu Center for Environmental Biology and Ecosystem Studies National Institute for Environmental Studies, Japan totsu.kumiko(a)nies.go.jp --------------------------------------------------------

2 3