...
Extract-Transform-Load (ETL)
Enterprise Addressing System (EAS)
Department of Public Works (DPW)
Department Building Inspection (DBI)
Parcel - includes attribute data as well as geometry
Street segment - includes attribute data as weel as geometry
Address Verification System (AVS): DBIs address system
Parcels
Parcel Creation - DPW
...
Parcel retirement occurs at DPW.
Parcel retirement is a special kind of update.
Every week night an automated extract-transform-load (ETL) job retires parcels in EAS based on data from DPW.
If a parcel is newly retired, addresses that are linked to the retired parcel are marked as "invalid".
An "invalid" address may be retired or may remain active.
The decision to retire an address is made by an EAS reviewer.
A reviewer may decide to keep an address active, even with a retired parcel, if there is permit activity on that parcel.
However, in most cases the reviewer will retire an "invalid" address.
The You can read more about invalid addresses here.
The DPW process for retiring parcels is non-trivial and is documented here (need link).
...
In rare cases, an address must be created immediately using a parcel that does not yet officially exist.
In these cases, an EAS Reviewer can "provision" a parcel within EAS.
This creates an unofficial or "provisioned" parcel in EAS.
The EAS Reviewer then requests that the offcial official parcel be created by DPW and must provide documentation from the assessor-recorder to DPW.
This step is currently a manual process and uses email; it should be automated and message driven.
When the official parcel is eventually created by DPW, the nightly ETL uses the block-lot to update the provisioned parcel, and marks the provisioning as complete.
...
Street segment retirement occurs at DPW.
Street segment retirement is a special kind of update.
Every week night an automated extract-transform-load (ETL) job runs that retires street segments in EAS based on data from DPW.
If a street segment is newly retired, addresses that are linked to the retired street segment are marked as "invalid".
You can read more about invalid addresses here.
The DPW process for retiring street segments is non-trivial and is documented here (need link).
Street Segment Provisioning - EAS
In very rare cases, an address must be created using a street segment that does not yet officially exist.
In these cases, an SFGIS staff member must "provision" a street segment for EAS.
This process is described here.
This is a manual process; automation may be expensive.
SFGIS staff then requests that the official street segment be created by DPW and must provide documentation to DPW.
Street Name Creation - DPW
Street name creation is automatically handled by the night street ETL.
Street Name Change - DPW
Street name changes are automatically handled by the night street ETL.
Addresses
Invalid Addresses
Anchor | ||||
---|---|---|---|---|
|
In EAS, an "invalid" address may be retired or may remain active.
The decision to retire an address is made by an EAS reviewer.
A reviewer may decide to keep an address active, even with a retired parcel, if there is permit activity on that parcel.
However, in most cases the reviewer will retire an "invalid" address.
Address Create/Update/Retire - EAS
Addresses are created, updated, anmd retired using the EAS web application.
Address Change Requests
When an address is created, updated, or reitred, it must go through a change request process.
A requester submits a change request for review.
A reviewer typically approves a change request, but may also reject a change request.
Once the change request is approved, the address becomes visible to all EAS users,
and a change notification is sent to AVS. Read more about the change notification below.
Note that certain parts of the address are not mutable such as the the street and street number.
Address
...
Change Notification - EAS
Anchor | ||||
---|---|---|---|---|
|
When a reviewer approves a change request, a change notification message is sent to AVS.
The message looks like this.
Once EAS went into production (Feb 15 2012) AVS became essentially a replication target for EAS.
We are using a point to point web servce for this process.
We should probably move towards a message bus type of approach.