Dear Mauro,

Thank you for contacting us. 
Today you need to do 2 web service calls for this behaviour - one to lookup the 
species ID and a second to create the map.

Attached is a simple example showing this.

I hope this helps,
Tim




On 19 Mar 2015, at 03:09, Mauro Cavalcanti <maurobio at gmail.com> wrote:

> Dear ALL,
> 
> Before the implementation of the new GBIF Portal, it was possible to generate 
> distribution maps for a given species using an API call as follows:
> 
> http://data.gbif.org/species/taxonName/ajax/returnType/concept/view/ajaxMapUrls/provider/1/?query=
> 
> where the value of the "query parameter" was a species name.
> 
> This API call has been used by Roderick Page in his "iSpecies" web 
> biodiversity data aggregator, as well as in my own "eSpecies" (sort of a 
> clone of Page's iSpecies, written in Python, see 
> sourceforge.net/projects/especies).
> 
> Unfortunately, with the new GBIF Portal is seems that all API calls have 
> changed and I got lost attempting to find out how to reproduce the previous 
> behaviour using the new API. I presume it is still possible to generate 
> distribution maps with the new API, but could not find out how. Can anyone 
> offer some hints?
> 
> Thanks in advance for any assistance you can provide.
> 
> With warmest regards,
> 
> -- 
> Dr. Mauro J. Cavalcanti
> E-mail: maurobio at gmail.com
> Web: http://sites.google.com/site/maurobio
> _______________________________________________
> API-users mailing list
> API-users at lists.gbif.org
> http://lists.gbif.org/mailman/listinfo/api-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gbif.org/pipermail/api-users/attachments/20150319/ead3e43f/attachment.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gbif.org/pipermail/api-users/attachments/20150319/ead3e43f/attachment-0001.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gbif.org/pipermail/api-users/attachments/20150319/ead3e43f/attachment-0002.html>

Reply via email to