It would be much nicer to show a value by the mouse as you move around, but these pre-built raster layers served through WMS don't easily support it. We could try out the GetFeatureInfo API in the future (maybe on-click; as you hover won't be fast enough). Or we could process the raw data ourselves and produce raster tiles in some format that's easier to query.
It would also be nice to match the NOx metric used by inspections: >40, 40-32, <32. But again with prebuilt raster data, we can't do much.
368. Demo at https://acteng.github.io/atip/defra/browse.html.
It would be much nicer to show a value by the mouse as you move around, but these pre-built raster layers served through WMS don't easily support it. We could try out the
GetFeatureInfoAPI in the future (maybe on-click; as you hover won't be fast enough). Or we could process the raw data ourselves and produce raster tiles in some format that's easier to query.It would also be nice to match the NOx metric used by inspections: >40, 40-32, <32. But again with prebuilt raster data, we can't do much.
Note this PR contains an attempt at the noise layer from http://www.extrium.co.uk/noiseviewer.html. It's disabled for two reasons: 1) I'm not sure they mean for it to be used publicly, even though the WMS server happily serves content without CORS problems. 2) They only have an HTTP endpoint. It works with
npm run dev, but not on GH pages or GCS because of https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content.