Some FIPS codes and ZCTAs start with "0"; if vertices are integer type then these leading zeros are lost. Vertex IDs should still be unique, but post-processing (e.g., joining model results to a shapefile for mapping) will require an extra step of detecting these missing leading zeros and restoring them. Long-term, it's better to have vertexes as strings. This might be best handled in the ingestion of the data structures that define the vertexes (rather than in the linked module), where we can define the relevant column types as str.
Some FIPS codes and ZCTAs start with "0"; if vertices are integer type then these leading zeros are lost. Vertex IDs should still be unique, but post-processing (e.g., joining model results to a shapefile for mapping) will require an extra step of detecting these missing leading zeros and restoring them. Long-term, it's better to have vertexes as strings. This might be best handled in the ingestion of the data structures that define the vertexes (rather than in the linked module), where we can define the relevant column types as
str.https://github.com/eho-tacc/episimlab/blob/0ef4048ed72aa86dbfebafd9689184e79cfcbc31/episimlab/setup/coords.py#L39