You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if clicking on the globe icon in the occurrence overlay opened up a map view for that entity. This could be a simple call to the api to reload the same page but appending &view=MAP to the end of the url and replacing a search query with a unique ID. I have it working with the Occurence ID, but something similar would also likely be possible with any unique identifier (GBIF ID etc), as some occurrence records may not have a GUID like field.
Clicking on:
Would load the map view via a call that looks like this /specimen/search?occurrenceId=F9210E4D-35FF-FB40-9799-E35E27F3C6E0&view=MAP (/specimen may be /occurrence for other instances)
The text was updated successfully, but these errors were encountered:
I'd rather extend the occurrence view with richer content. As it is now it is largely a stub without important features such as a map, video and audio, iiif links.
Especially since we will need occurrences pages on a url of their own.
Yes that sounds great, especially having occurrence pages being accessible through a dedicated url. Having the map/audio/video integrated within the occurrence view itself sounds fantastic
It would be nice if clicking on the globe icon in the occurrence overlay opened up a map view for that entity. This could be a simple call to the api to reload the same page but appending
&view=MAP
to the end of the url and replacing a search query with a unique ID. I have it working with the Occurence ID, but something similar would also likely be possible with any unique identifier (GBIF ID etc), as some occurrence records may not have a GUID like field.Clicking on:
Would load the map view via a call that looks like this
/specimen/search?occurrenceId=F9210E4D-35FF-FB40-9799-E35E27F3C6E0&view=MAP
(/specimen
may be/occurrence
for other instances)The text was updated successfully, but these errors were encountered: