Skip to content
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

Closed
stepps00 opened this issue Jul 29, 2016 · 9 comments
Closed

Backfill existing administrative WOF records with HASC code field #380

stepps00 opened this issue Jul 29, 2016 · 9 comments
Labels

Comments

@stepps00
Copy link
Contributor

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

@thisisaaronland
Copy link
Contributor

What is the relationship with issue #221

@stepps00
Copy link
Contributor Author

Looking at the wof-unlocode-subdivisions-todo.csv.txt file in issue #221, it seems the UN-LOCODE for say, Virginia, would be US-VA. The HASC code for Virginia is US.VA. According to the statoids site, each country has a unique two-letter code, which is the same as its ISO 3166-1 code. Then, each primary subdivision and each secondary subdivision of a country has a code that is unique within its primary division.

So, San Francisco County, for example, would have a HASC code of US.CA.SF. From my understanding the UN-LOCODE does not include secondary administrative subdivisions.

@thisisaaronland
Copy link
Contributor

what is the purpose / function of the HASC code?

@stepps00
Copy link
Contributor Author

Concordance with statoids; mesoshapes (new county and locality polygon import files) will have the HASC code included as an attribute field.

@thisisaaronland
Copy link
Contributor

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.

@nvkelso
Copy link
Contributor

nvkelso commented Jul 29, 2016

They each go in fits and starts, sometimes Statoids leads, sometimes
UN/LOCODE, but the HASC will usually have more details available, and we
have been given permission to use the HASC codes in Who’s On First for
concordances & etc. (Both should lead ISO codes.)

On Fri, Jul 29, 2016 at 12:00 PM, Aaron Straup Cope <
notifications@github.com> wrote:

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.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#380 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO895Isjjeb72ZBzU8tXpajbUUhl3ks5qak3igaJpZM4JYchr
.

@thisisaaronland
Copy link
Contributor

Permissions?

The UN/LOCODEs are complete down to the region - the issue is mostly just geocoding / name matching.

@stepps00
Copy link
Contributor Author

Related to: #581

@nvkelso
Copy link
Contributor

nvkelso commented Mar 22, 2017

Forward dup of #581.

@nvkelso nvkelso closed this as completed Mar 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants