kgjenkins / cugirjs Goto Github PK

similar to current CUGIR site

With OpenIndexMaps geojson data in the browser, we can:

• show data availability by using different colors
• label or add tooltips for each mapsheet
• search for a mapsheet by name or id -- issue #15
• better calculate which mapsheet is clicked, without having to make a WFS call
• click to unselect mapsheets
• download multiple files at once -- issue #14

Would it help to split UI functions into a separate Sift-ui file (which could include the map-related parts, or else put those into a Sift-geo file)?

Given an index map, we could automatically create an item for each subset, improving the user experience when searching by text or map.

To create the new items, we would want to:

• calculate the bbox from the feature geometry
• add the subset name/label to the title
• replace the "place" field
• copy other fields as appropriate

Since generated downloads are handled via WFS, allow users to select a bbox on the map to download a clipped dataset.

Rank search results by spatial relevance, something like this:

relevance = overlapArea / mapArea * overlapArea / itemArea

This should give a number 0 to 1, where 0 is irrelevant and 1 is perfect.

This computation will only need to be done for matches, and using bboxes will probably suffice

When displaying attribute info for a clicked feature, mousing over an attribute name should display the attribute definition from the FGDC metadata.

Clicking a raster map should fetch the raster value and that point.

Users should be able to search for a mapsheet/feature by name or id.

Need to figure out how to rank results such that smaller datasets near the point are ranked higher than large statewide datasets.

Currently, when the map is clicked, a WFS request is sent using the bbox of a specific point. Unless the map is zoomed way in, it is very difficult to click a point.

Instead of a single point (zero-area) bbox, calculate and send a bbox of the clicked pixel (or slightly larger).

https://docs.geoserver.org/latest/en/user/production/container.html#enable-cors

GeoServer's WFS GetFeature appears to return any feature whose bbox contains the requested location, even if the feature itself does not contain that location.

Once the WFS results are received, filter results using something like leaflet-pip.

If there are legitimate multiple matches (for example, closely-spaced points, or overlapping polygons) then perhaps provide some way for the user to iterate through the matches.

Currently, user can click multiple features to highlight, add to list, and then download all files at once. This works in Chrome, but in Firefox, some files don't get downloaded.

Maybe try increasing the timeout a bit.

Provide options for how to sort results (relevancy, date, title, etc)

Also record the bbox used for the search in the URL hash, so that results are in the same order when user returns to the search results.

Try removing it and just defining map styles in config.js.

Add geojson and kml downloads via WFS.