BDMS-864: fix map layer feature limits for water wells and locations layers#294
BDMS-864: fix map layer feature limits for water wells and locations layers#294ksmuczynski wants to merge 1 commit into
Conversation
Preview DeploymentPreview URL: https://preview-kas-bdms-864-fix-map-ui-well-record-feat-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
|
@ksmuczynski Nice! This change is working for me, I now see 9937 water wells, and 11148 locations. 2 of the locations are way outside NM like you mentioned, but that seems unrelated to this ticket. |
|
@chasetmartin Great! And yes, I confirmed that the three locations plotting outside of NM are the result of this PR being pushed to staging. The coords for these locations have been updated in production, so when this fix gets pushed there, it shouldn't be an issue. |
| label: locations.label, | ||
| color: '#607d8b', | ||
| enabled: locations.exists && isLayerActive('ogc-locations'), | ||
| ...HIGH_COUNT_LAYER_LIMITS, |
There was a problem hiding this comment.
I think it might be simpler to increase the defaults in useOGCLayer.ts
OcotilloUI/src/hooks/useOGCLayer.ts
Line 27 in 4635809
There was a problem hiding this comment.
@jirhiker But wouldn't this apply to all layers, potentially slowing down the app?
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
useThingLayers.tsx.locationsandwater_wellsOGC map layers.Notes
Any special considerations, workarounds, or follow-up work to note?