[GRASS-dev] New addon: v.in.pygbif from Code Sprint Bonn

[Blumentrath, Stefan]

Dear Code-sprinters (and others),

Thanks for the awesome event and the great time in Bonn!
It was really exciting and a lot of fun working together with all of you. The experience definitely - more than - compensated travel costs and conference fee!

With the kind support from Lucca and Vero, the v.in.pygbif addon I was working on in Bonn is now finally usable and committed to addons.
v.in.pygbif builds upon Helmuts v.in.gbif addon and adds the possibility to query and fetch species occurrence data directly from GBIF.
In fact, it is more or less a graphical frontend to the pygbif package (http://pygbif.readthedocs.io/en/latest/index.html), which thus is a dependency of v.in.pygbif.

The GBIF data which is provided in WGS84 is re-projected into the projection of the current location at import. Import of global occurrences is by default limited to current computational region. This limit can be skipped in latlon locations.
Here my question is: Should I allow for unlimited/restricted import also in other CRS with global application? If yes, could you point me to EPSG codes of CRS you like me to add?

v.in.pygbif offers most of the relevant filter options from pygbif. I did some more testing yesterday, but still not all options are fully tested (also because the content of the returns from GBIF API are hard to predict)...
Anyway, I just pushed v.in.pygbif to addons together with a basic documentation. So, I would be glad for any test and report of issues / enhancements.

Many thanks again to Lucca and Vero for extensive testing and help along the way.

Known toDo`s are:

-        Code clean up (e.g. some lines are a bit long)

-        Add a cleanup routing when the user cancels / kills the process

-        Handle layers in input mask map

-        Proper implement shell script output for matching of taxon names

I hope it is of use for some of you...

Kind regards,
Stefan

P.S.: I would wish that the GBIF API would also provide information about the coordinate precision, which should be available in GBIF. Unfortunately this information does not seem to be available through the GBIF API :(.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20160829/3f846ddf/attachment-0001.html>