Added geo existence check to place page chart filtering logic

[dwnoble]

• Adds geo data existence check for child places & peer places map
• Sequentially checks geoJsonCoordinatesDP3 (lowest-resolution) and falls back to geoJsonCoordinatesDP2 if no geoJsonCoordinatesDP3 is available.
• This check adds a good amount of latency to the chart filtering process (the response time is around ~4s total for California)

Before

After

[gmechali]

LGTM - but do you think it's worth the additional latency that you call out?
Perhaps something we could try is to hide the geo existence check behind a feature flag so that if we start seeing some other metrics drop (and we fear it could be latency related), we can turn it off easily?

[dwnoble]

LGTM - but do you think it's worth the additional latency that you call out? Perhaps something we could try is to hide the geo existence check behind a feature flag so that if we start seeing some other metrics drop (and we fear it could be latency related), we can turn it off easily?

The latency should be OK in prod due to the caching & cache warming. Agreed it would be good to have a feature flag for this. I'll leave this for a follow-up, but maybe the feature flag behavior can be:

• Enabled: Perform geo existence check from this PR
• Disabled: Only show maps for a limited subset of places that we know we have geos for (Earth + US Places?)