-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backfill existing administrative WOF records with HASC code field #380
Comments
What is the relationship with issue #221 |
Looking at the wof-unlocode-subdivisions-todo.csv.txt file in issue #221, it seems the UN-LOCODE for say, Virginia, would be So, San Francisco County, for example, would have a HASC code of |
what is the purpose / function of the HASC code? |
Concordance with statoids; mesoshapes (new county and locality polygon import files) will have the HASC code included as an attribute field. |
if we can infer the UN/LOCODE from them then so much the better. The UN/LOCODE stuff is necessary for a standardized naming convention for repos. |
They each go in fits and starts, sometimes Statoids leads, sometimes On Fri, Jul 29, 2016 at 12:00 PM, Aaron Straup Cope <
|
Permissions? The UN/LOCODEs are complete down to the region - the issue is mostly just geocoding / name matching. |
Related to: #581 |
Forward dup of #581. |
Add a new field to existing records in Who's on First that includes HASC codes.
Example of HASC codes for US counties:
http://www.statoids.com/yus.html
Other sources:
http://www.statoids.com/ihasc.html
https://en.wikipedia.org/wiki/Hierarchical_administrative_subdivision_codes
The text was updated successfully, but these errors were encountered: