After writing about the GeoMap bug in query builder that makes the GeoMap plugin crash when accessed from certain queries, I thought of a few things that aren’t bugs but would be nice improvements to the geospatial functions of Specify.
1. Allow GeoMap Button on forms other than Locality.
Currently it’s not possible to put the GeoMap button on any form except Locality. As such, it requires a lot of clicking to get to a map from the CO form (CO → CE → Locality->GeoMap Button, 4 clicks if you know exactly where to look, and most users do not).
2. Allow an embedded map element on CO and CE forms.
Currently, there are ‘Specify Network’ “Loc” buttons at the top of every CO form that map all occurrences of the CO’s currently determined PreferredTaxon. It makes little sense to have a species distribution map available from the CO form in a single click when it takes 4 clicks and specialized knowledge of Specify’s data model to display the position of just theCO record itself on a map. I’d love to be able to have an embedded map element (as a tab, or a conditional panel, perhaps) directly on the CO form.
3. Improve the Spatial Search function.
Currently, it’s a real hassle to use, as you have to drag two pins one after the other from Null Island to wherever on the globe you wish to search. It would be much more effective 1. to be able to search complex polygons rather than simple rectangles, and 2. to be able to place and remove the boundary pins wherever the user wants rather than have to click and drag preexisting pins across the map.
4. Allow admin to disable point-clustering in Leaflet maps
Point clustering in Leaflet is useful in speeding up plotting of many records, but in many cases it is desirable to see points plotted individually at various spatial extents. The DB admin should be able to set a preference, or alternatively the users should be able to choose between a clustered vs point view of a given set of records.
GBIF/Symbiota/Arctos/iNat already implement all of the above features in occurrence record pages/queries, so these are definitely features that users expect from biodiversity databases.
If anyone else in the community wants to see these changes, or has any ideas/suggestions for GeoMap and geospatial functions, feel free to add them to the comments!