Update to 2017 Census

[montyvesselinov]

Any plans to update us-10m to represent the latest county FIPS.

https://cdn.jsdelivr.net/npm/us-atlas@2/us/10m.json

[domoritz]

We could do that. Wanna send a pull request?

[montyvesselinov]

Sure! Do you have examples how to convert to vega topo json format somewhere?

[jheer]

One thing to keep in mind is what examples and test specifications in Vega and/or Vega-Lite may be using a dataset before we make any updates. Will it break existing test cases? In the case of geo data, might the inclusion of different ids/regions break joins (lookups) with other (also "outdated") data sets?

While Vega keeps a separate folder of data sets for test cases to guard against breakage due to vega-datasets updates, the online examples do pull from vega-datasets and so could be subject to breakage. For example, the unemployment choropleth might break with updated data to us-10m.json.

I'm (in general) supportive of using more recent examples, but I want to make sure we are keeping these downstream effects in mind. Adding new files with timestamps is probably preferable to overwriting existing files. Thanks!

[jwoLondon]

Perhaps timestamp the file names (us10m_2017.json etc.).

[montyvesselinov]

Yes, it will be better to call it us10m_2017.json. The FIPS change regularly.

Do you have an example how to convert?

[domoritz]

I’d prefer not to have multiple versions of the same data unless it causes issues with the existing examples.

[domoritz]

@montyvesselinov I want to cut a 2.0 release and include this update. I think the only way forward is to also include an updates unemployment dataset (and include a year such as unemployment_2017.csv. Can you send a pull request in the next few days?

[domoritz]

Closing as we are moving to v2 now.