Our zips data identifies counties just by their name, e.g. Suffolk.
Geocodio identifies them like Suffolk County. This would cause
problems for county-level incentives, which need the location's county
to match the county name in authorities.json.
It's not trivial to adapt one format into the other (the second word
isn't always "County"; you can't just chop off the last word of the
Geocodio value; etc.) so instead, let's identify counties using a
consistent non-human-friendly identifier.
One other little advantage of the FIPS code is that the first five
digits of a tract ID are the county's FIPS code. We're not making use
of this fact yet, but it may come in handy.
Two concurrent minor changes:
I removed the county name from the location object returned in the
API, since we're not passing the county name around anymore. We
could add it back in, but neither the embed nor PEP uses it anyway,
so I'm thinking that can wait until it's needed.
I made it so that the authorities object in the API response only
contains names and logos, not the other bits that specify the
authority's geographic scope. Those aren't part of the public API,
and I'd rather not let them become so. (Embed and PEP are not using
them.)
Description
Our zips data identifies counties just by their name, e.g.
Suffolk. Geocodio identifies them likeSuffolk County. This would cause problems for county-level incentives, which need the location's county to match the county name inauthorities.json.It's not trivial to adapt one format into the other (the second word isn't always "County"; you can't just chop off the last word of the Geocodio value; etc.) so instead, let's identify counties using a consistent non-human-friendly identifier.
One other little advantage of the FIPS code is that the first five digits of a tract ID are the county's FIPS code. We're not making use of this fact yet, but it may come in handy.
Two concurrent minor changes:
I removed the county name from the
locationobject returned in the API, since we're not passing the county name around anymore. We could add it back in, but neither the embed nor PEP uses it anyway, so I'm thinking that can wait until it's needed.I made it so that the
authoritiesobject in the API response only contains names and logos, not the other bits that specify the authority's geographic scope. Those aren't part of the public API, and I'd rather not let them become so. (Embed and PEP are not using them.)I used this document to manually convert existing county names (it doesn't have territories, but I just got those from the tract IDs): https://transition.fcc.gov/oet/info/maps/census/fips/fips.txt
Test Plan
yarn test