There are some ways of using the GBIF API that will work alot better for us rather than the current query, which is slow and breaks after 50K records. An example of our current search against the GBIF API looks like:
GBIF MAP API-- has a png and a vector tile service-- instead of returning the JSON for every record return images of query results and overlay:
Documentation is here https://www.gbif.org/developer/maps
Live usage of png is here https://www.gbif.org/occurrence/map?occurrence_status=present showing billions of
Live usage of vector tiles is here https://www.gbif.us/data/?view=MAP (it needs a proper loader, so be patient)
Faceted Searching (useful for the Statistics Tab):
Following is a thread excerpted from the GBIF portal-feedback log: https://github.com/gbif/portal-feedback/issues/4678
There are some ways of using the GBIF API that will work alot better for us rather than the current query, which is slow and breaks after 50K records. An example of our current search against the GBIF API looks like:
GBIF MAP API-- has a png and a vector tile service-- instead of returning the JSON for every record return images of query results and overlay:
Faceted Searching (useful for the Statistics Tab):
WKT Polygon Searching (instead of bounding box):