Required for map display
- The dataset must be published or accessible with the API token you entered.
- The dataset must contain Geospatial metadata with a geographic bounding box.
- The selected Dataverse collection filter must include the collection where the dataset is stored.
Required for data-type filtering
- Add a Citation metadata Keyword → Term.
- Use one of the controlled values: ADCP, Wind/current, Wave, CTD, or Other.
- All data types is only a map option. Do not store it as a dataset keyword.
Filter-specific reasons
- If “Only datasets containing files” is enabled, metadata-only datasets are hidden.
- If “Only datasets with PNG graphs/images” is enabled, the dataset must contain at least one .png or image/png file.
- If time filtering is enabled, the dataset must have a Dataverse Time Period that matches the selected range.
The first search may take a little time because the backend fetches dataset metadata and builds one cached map snapshot. After that, collection, data type, PNG, file, time, and text filters happen instantly in the browser using that snapshot. The snapshot does not react to live Dataverse changes automatically. Press Live refresh to bypass the cache and fetch the newest published metadata/files from Dataverse. Only changing the API token requires rebuilding the snapshot.