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

Update docs to explain our policy on OccupancyType vs SubaddressType #159

Open
jeancochrane opened this issue Jan 9, 2017 · 0 comments
Open

Comments

@jeancochrane
Copy link
Member

@jeancochrane jeancochrane commented Jan 9, 2017

More discussion in this PR and #132.

Basically, we need a policy for differentiating between OccupancyType and SubaddressType, since our use of the two tags differs from the URISA standard. From my interpretation of the existing training data, I'm inclined to say that SubaddressType divides an address into a smaller unit (e.g. an office suite, a mailroom, a floor) while OccupancyType defines the endpoint of an address (e.g. an apartment, a room).

This definition introduces some interesting ambiguities: some common tokens (room, floor) could be OccupancyType or SubaddressType based on their context. For example, suite would normally be an OccupancyType, but in the context of suite 30 room 406 it would become a SubaddressType.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.