sul-dlss / earthworks

Geospatial discovery application for Stanford University Libraries.
https://earthworks.stanford.edu
Other
21 stars 3 forks source link

Raster image doesn't support feature inspection #1080

Closed thatbudakguy closed 1 month ago

thatbudakguy commented 2 months ago

For https://earthworks.stanford.edu/catalog/stanford-qz033pg4379, if you click in the viewer...nothing happens? Unclear why this is true of that record but not e.g. https://earthworks.stanford.edu/catalog/stanford-pc204zy5923, another georeferenced raster that does support inspection. Possibly a bug, maybe a data problem?

dnoneill commented 2 months ago

Looks to be a data problem. The data coming from the wms server for qz033pg4379 and qh711pf3383 return

{"version":"1.1.1","exceptions":[{"code":"OperationNotSupported","locator":"QUERY_LAYERS","text":"Either no layer was queryable, or no layers were specified using QUERY_LAYERS"}]}

However, mr099qm5693 which is in a similar format works perfectly.

thatbudakguy commented 1 month ago

Pending some data investigation by @kimdurante.

kimdurante commented 1 month ago

I think I have found the source of this issue. In GeoServer, if you select Layers from the left hand menu and search for a druid (ex. qz033pg4379) and then go to the Publishing tab. Under Layer settings, there are 2 checkboxes 'Queryable' and 'Opaque.' If 'Queryable' is checked, the layer will allow for feature inspection.

For this file, I reloaded GeoServer thinking that might matter. So while a Features panel expands, nothing is showing there yet. This may take ~24hrs. https://earthworks.stanford.edu/catalog/stanford-qz033pg4379 However, you can see it working on the PURL embed: https://purl.stanford.edu/qz033pg4379

I tried it on this file as well, without reloading and it now allows for feature inspection: https://earthworks.stanford.edu/catalog/stanford-fn566hh7972

I'm not sure why, but many of our raster layers have the Queryable box unchecked, or if there is a way we can change it programmatically

thatbudakguy commented 1 month ago

Sounds like the work here is now:

kimdurante commented 1 month ago

I have set all layers on both the public and restricted GeoServers as 'Queryable.' The queryable property can either be True or False. There is probably something in the GIS Delivery robots that needs to be updated to always be True, unless there is some reason why we wouldn't want this (I can't think of any).

peetucket commented 1 month ago

see https://github.com/sul-dlss/gis-robot-suite/pull/911#issuecomment-2251549090 for some comments on a potential fix I have that may require some more testing