bnhm / reservemapper Goto Github PK

Some users on slow connections may want to limit to less results (e.g. 5,000) than the current default while other users on fast connections may be OK with much more (e.g. 90,000). More than 90,000 i worry about performance concerns.

Create a dropdown to set Max Results:

5,000
15,000 (default)
30,000
90,000

from the Ecoengine API

• Soil database - the localities are georeferenced
• CalPhotos - map the images that are georeferenced
• Species checklists are not georeferenced but are associated with field stations so maybe be able to link to the bigcb catalog lists? (eg. https://bigcb.berkeley.edu/cgi/bigcb_query?table=catalog&Admin=&username=&where-GeoExtent=Blue+Oak+Ranch+Reserve&orderby=DatasetName)

Currently vector files are included with this codebase.
Better is to have a configuration file that points to a directory (e.g. in github) where
WKT vector files can live. This way we can dynamically add new reserves by
adding new files to Github (and also, change boundaries)

From michelle, download all results

A button to Reset all parameters!

Enable downloading checklists as CSV

When viewing the Species stats table, it would be useful to add Family as a way to groupby.

confession: I dont know all the leafy and buggy things so I need a family to help sort those out! (I'm sure I'm not the only one)

Also, love the ascending/descending column sort!

directed to checklist table & stats... check other places as well

The datasets listed here, need to be accessible in ReserveMapper.

Steps:

1. Create an API that sits on top of the current application
   https://bigcb.berkeley.edu/cgi/bigcb_show_catalog?special=all

2. Create a link in reservemapper to fetch data for datasets.

Current spatial queries are merely bounding box queries, but GBIF supports queries on polygons (see https://www.gbif.org/developer/occurrence#parameters geometry query parameter for details).

Best approach is to provide a checkbox to query on box OR to query on polygon

Stats panel shows stats for just the MAX possible results.
Add a message saying that if MAX results reached then
one can download results to see all

Clearly explain how each option on the queryForm works using a tooltip feature.
See plantphenology.org for how this can work.

bug with the display of popups: select any area of interest field when the map is zoomed in and a marker near the top of the screen is clicked, the popup will either appear and then disappear, or appear mostly out of view

wishlist item to show summary charts of stats, for ex:

• total number of records from search by InstitutionCode, by Taxonomy (but could be messy), by Basis of Record
• by collectionCode within the subset of InstitutionCode

For example, typing "Bufo boreas" does not display Bufo boreas because it is listed as a synonym of Anoxorys boreas. So.. we need to fix the drop-down list to display synonyms.

e.g.
https://api.gbif.org/v1/species/suggest/?q=Bufo%20bo&rank=species

This is partially dependent on AmphibiaWeb/SpeciesLookup#5 for the species lookup service

for now, we can include class/order for the other checklists pretty easily (from MoL).

• already in API with coordinates
• one option is have a toggle that is enabled after doing a search on a reserve that allows seeing the soils in the region.
• API should allow hyperlinking to the samples detail page (eg. https://bigcb.berkeley.edu/cgi/bigcb_soil_public?step=form&action=change&SoilID=10&&username=&Access=)

These two checklists should be available for all reserves/bounding areas.

• reconcile the Search by Any Term (Quercus lobata) which results in any Quercus species and Search by Taxonomy where you have to select an identification + author (results differ then)

try search on yosemite... never get to Table

functional boundaries are different than the legal -- so should be clear. However discussion may be needed about whether RM should show this.

Can think about a variety of site-specific layers for each site..
can define, for example, WMS layers in a configuration file to add for each site
http://www.marine-geo.org/tools/web_services.php#gmrt

https://gis.cnra.ca.gov/arcgis/rest/services/Boundaries

let's brand this a bit better!

For an example see the bottom of the VTM site: http://vtm.berkeley.edu/#/home
Can we please add a logo to the bottom of the left sidebar? (logos are here now- shared Google folder )
thanks!

this was a required/requested feature of the Explore tool. As we add in more options of intersecting layers and data, it will be increasingly more valuable and useful

see the flagged updates needed. Also the up/down icons used in table are deprecated (or something)
see screenshot:

Add GBIF and Calphotos logos to homepage

These are resources specific to reserves so maybe we just need to offer a link to available checklists if they are available for a reserve.
Ex. Search on BORR
Datasets exists in bigcb database so link to this page:
https://bigcb.berkeley.edu/cgi/bigcb_query?table=catalog&Admin=&username=&where-GeoExtent=Blue+Oak+Ranch+Reserve&orderby=DatasetName

Ex. Search on Jenny Pygmy
No datasets exists so display or disable the linked button.

Just looking for Something simple for now.

could be polygon or point data from a hosted KML file? (eg link from Google Maps if it's uploaded there?) Need a use case to really flesh this out.

Currently a user can select multiple checklists but it returns nothing in this case.. expected behavior is to return all of the checked lists

someplace to view the GBIF API call

stats on just specific epithet not super useful

We need a way to search within CalPhotos results. Going through 100s of photos is not useful when I only want to see a specific species or class

Maybe from the Statistics tab we can select a species and have it rerun search so that we can see only those species on the Map view?

Other ideas?

What would be the best way to do this? If we premise the reservemapper that we are exploring datasets associated with reserves than again, we can allow searching on Calphotos as an option but would have to be separate from the current search boxes.
Open for discussion.

This happened in cases where incomplete data was present in returned result from API.