See whether it makes sense to use turf.js for more client-side GIS work instead of doing Postgres stuff. I think the biggest issue is data usage on mobile clients, but if we're generally returning all of the parks to the client anyway, that wouldn't be an issue.
See whether it makes sense to use turf.js for more client-side GIS work instead of doing Postgres stuff. I think the biggest issue is data usage on mobile clients, but if we're generally returning all of the parks to the client anyway, that wouldn't be an issue.