...
Description
There are a number of AVS addresses that use a non-existent block lot.
These are currently generating exceptions of the type "no matching block - lot".
We are waiting for DBI to confirm how we can identify these addresses (e.g. 0000-lot = '000'?)
These address do .
We expect that most of these addresses will have a valid street and street number.
These addresses are called "right of way addresses".
The ETL is currently rejecting these addresses (no matching block - lot).
The EAS application is designed to prevent addresses from being created outside a parcel boundary.
We were not planning on supporting this type of address until a later release.
DPW wants this feature as well.
Option 1 (increase scope)
Use a "right of way" polygon map layer to support this feature
There are a couple of challenges
...
It appears that there will be 2 chucks of work here.
First we will have to introduce the notion of a "service parcel".
The service parcel would be a citywide parcel with a unique block-lot (e.g. 0000-000) that would support service addresses at arbitrary locations.
The web application behavior may be imperfect in some edge cases (user adds an address in the middle of the bay) but this may not require any changes if the application behavior is reasonable.
I think this work will take less than a day.
The second challenge will be to write some additional ETL code - possibly non-trivial.
I think this work may take as many as 3 days.
Option 2 (maintain scope)
Defer loading these addresses from AVS until the next release.
I assume we would have to focus on this issue in the very next release.
...