Closed james-minton closed 1 year ago
I don't think there's anything I can do in this repo to hide it. It might be easier + better, in the long run, to remove it from the source data.
Fair enough! I think I'll rerun the data toward the end of this process just in case anything else comes up, so we can table the DC issue for now.
@james-minton I updated the original comments "TBDs" based on the email discussion. (Logo link and copyright notice) I'll go ahead and implement them as well.
Perfect!
@cfhull re:
the list of user-selected locations (which is populated by searching or clicking on the map) should be specific to the level of geography that is active at any point (states/cities), with no crossover
In the dev deploy I'm seeing this works, and it seems as though any stored locations are wiped out when changing the geography type. E.g. select states, click some and add them to the list, then switch to cities, click and add to the list, then back to states—states is empty.
It would be preferable for stored locations to persist when toggling back and forth between geography selections, though only for the currently selected type (states only lists states, etc.).
This has three parts:
font-size
for the geography selection dropdown larger - equivalent to ~14pxI believe it's showing up as a state because it's in state-level data as well as cities. Chris, should I re-run the ETL with DC's row omitted, or is there another front end option? (ETL is a pain to run but I can do it if that's best.)