Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdate docs to explain our policy on OccupancyType vs SubaddressType #159
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
More discussion in this PR and #132.
Basically, we need a policy for differentiating between
OccupancyTypeandSubaddressType, 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 thatSubaddressTypedivides an address into a smaller unit (e.g. an office suite, a mailroom, a floor) whileOccupancyTypedefines the endpoint of an address (e.g. an apartment, a room).This definition introduces some interesting ambiguities: some common tokens (
room,floor) could beOccupancyTypeorSubaddressTypebased on their context. For example,suitewould normally be anOccupancyType, but in the context ofsuite 30 room 406it would become aSubaddressType.