Finalize how to handle multiple addresses

[pdxmele]

• Just do building = yes and no address?
• Or import multiple overlapping points of addresses?
• Can we do address ranges where it makes sense (all addresses must be on the same street)?

[pdxmele]

We've decided to leave these to phase 2, but then what? Is wiki description accurate?

Currently:
"Addresses are connected to a building through a taxlot id. In the vast majority of cases, this is a 1:1 mapping, however there are some cases where there are many addresses associated to a property containing many buildings.

Some buildings have multiple addresses associated with them. Where this is the case, the addresses will be assigned to nodes inside the building polygon. No addresses will be assigned to the building, since there is no way to determine which, if any, of them is the "primary" address.

In the case where there are multiple buildings and multiple addresses, with no way to distinguish, then a site boundary will be generated, and nodes will be created inside that polygon, but not on any given building. If for some reason that is not possible, then no addresses will be assigned at this time."

[darrell]

I think we've got the one building to multiple addresses handled (see issue #21).

Let's get a count of the multi to multi cases and analyze them in more detail before we tackle that part.

[darrell]

FWIW, at the RLIS Meeting today, it was strongly suggested that we contact Portland, since they're about to release an all new addresses dataset. We should integrate that into our build instead of the RLIS version, unless we want to wait for the February data release, which will have all of that included.