Google Floods Part 3: Adding Inundation Maps; COUNTRY=cambodia

[lowriech]

This adds inundation polygons from the Google Floods API.

https://www.loom.com/share/5b430b093ee546139f5ccbe3299c60c9?sid=049273de-18ff-4b6a-8718-b1a164c82b52

[lowriech]

@gislawill this is updated to call gauges, rather than rely on a previous call passing its attributes

[github-actions]

Build succeeded and deployed at https://prism-1332.surge.sh
(hash 0338024 deployed at 2024-10-10T14:53:52)

[gislawill]

Seeing kind of a weird bug while doing QA, the flood layer is loading in with various shades for the same data. It's very intermittent — changes with each page reload. I'm digging into figure it out. @ericboucher, have you see this in the past with any other layers?

Darkest (correct)	Medium	Light

[ericboucher]

@gislawill I have not seen this before. Could this be a bug linked to the opacity?

[gislawill]

@gislawill I have not seen this before. Could this be a bug linked to the opacity?

I don't believe so - the opacity is always coming through as .9 (tested it at 1 just to be sure too). I think it may have to do with layer order. The theory being that if it's rendered under 1 admin level its somewhat lighter, 2 admin layers and it's much lighter. The layer order in the canvas doesn't necessary match the layer order in jsx so I think I'll have to play around with "beforeId" prop to test it out

[wadhwamatic]

@gislawill - I've not been able to access the flood inundation layer through the surge deployment, but it works locally. Here's the error I see on surge:

Things look good locally. I've not seen the shading error you mentioned.

[gislawill]

@gislawill - I've not been able to access the flood inundation layer through the surge deployment, but it works locally.

Oh weird, it looks like this https request to the prism-api is getting redirected to a http request by cloudflare the prism-api. I'm not sure why that would be but I'll look into it