[Bug]: AreaMap cannot use numeric fields from geojson

[hughess]

Describe the bug

If you try to use a numeric field for the geoId prop of AreaMap, the areas will not render on the map. Using string fields works as expected

Steps to Reproduce

Create a map using a geojson with a numeric field (e.g., WARD in this geojson: https://opendata.dc.gov/datasets/DCGIS::wards-from-2022/about)

Logs

No response

System Info

No response

Severity

serious, but I can work around it

Additional Information, or Workarounds

Workaround:
Use a string field as the geo ID

Possible issue / solution:
In the AreaMap, there are some references that use [ ] to retrieve information from the geojson. When using a number it behaves differently than if a string was passed (assumes it is index location). The functions need to be updated to handle numeric inputs as strings so the lookup completes correctly.

Error handling should also be added to hep troubleshoot issues with geojson files and geoIDs