Paint by county

[raphaellaude]

Description

• Support variable paint/hover functions w/ single mapEvent
  • Add paint/hover function to mapStore
  • Refactor map hover and click event to use store's function
• Add (still slightly buggy) paint by county function (fixes Paint by County #68). Mostly works well but has a hard time with complex geometries. Need to dig into it a bit.

Discussion

• Advantage of this geometry-based paint-by-countie method over a data-based approach (i.e. having county FIPS in layer features) is we don't need to send that extra data down and could easily support paint-by-{{ insert geometry here }}
• Downside is it's slightly less reliable (for now) and may have slightly worse perf – though it feels fine to me. One idea is for any document using census geographies we could querySourceFeatures using an expression that slices the first five chars in the Path. In that case the geometry-based approach is more of a fallback but nice-to-have.
• Either way, the pattern of storing the function in the mapStore works v well.

Reviewers

• Primary: @mariogiampieri
• Secondary: @bailliekova

Checklist

• Added/Updated related documentation (if applicable).
• Added/Updated related unit tests (if applicable).

Screenshots (if applicable):

output.mp4

[raphaellaude]

Kind of an ugly hack for queryRenderedFeatures to work but was fine with it.

[raphaellaude]

Using this pattern made it really easy to handle different behaviors on hover without messing with map events.

[mariogiampieri]

i like it!

[mariogiampieri]

this looks good to me