The AVS addresses are imported into EAS via a one time ETL.
Once EAS goes live, this ETL will be turned off.
Here I describe in general the processing that occurs during the ETL.
You can see the most of the code at these URLs
http://code.google.com/p/eas/source/browse/trunk/etl/sql/avs_load/f_init_avs_addresses_ddl.sql http://code.google.com/p/eas/source/browse/trunk/etl/sql/avs_load/f_load_ddl.sql http://code.google.com/p/eas/source/browse/trunk/etl/src/commands.py#1799 http://code.google.com/p/eas/source/browse/#svn%2Ftrunk%2Fetl%2Fsql%2Favs_load
but the execution path is not trivial.
'invalid street number suffix'
The domain values are here
http://code.google.com/p/eas/source/browse/trunk/etl/sql/migrate_1-0_beta_to_1-0_prod/d_address_base_number_suffix_ddl.sql
'street name does not exist'
The domain values are specified by DPW.
We do not use fuzzy string matching.
'street suffix does not exist in street dataset'
The domain values are specified by DPW.
We do not use fuzzy string matching.
'street - street suffix combination does not exist'
The domain values are specified by DPW.
We do not use fuzzy string matching.
'referenced parcel has no geometry'
parcel data from DPW
'no matching block - lot'
parcel data from DPW
'block lot values are inconsistent'
Check for consistency across the columnes block, lot, and block-lot.
'length of concatenated unit num exceeds 10'
We concatenate avsa.unit and avsa.unit_sfx using
http://code.google.com/p/eas/source/browse/trunk/etl/sql/avs_load/f_concatenate_unit_ddl.sql
The result must fit into char 10.
'invalid end date value'
Some of the end date values cannot be cats into the date type.
Add Comment