...
You can see the most of the code at these URLs
| Code Block |
|---|
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.
In any case here I walk through the process mostly in english.
I will try to call out the places where I have to generalize.
We start by doing to blanket validations and standardizing some values.
This is done in this db proc: http://code.google.com/p/eas/source/browse/trunk/etl/sql/avs_load/f_init_avs_addresses_ddl.sql
and includes the following
'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
...
'invalid end date value'
Some of the end date values cannot be cats into the date type.
We also standardize dates, "unit number" values, and street number suffixes.
At this point we have "excepted" addresses that we know we cannot process.
We take each remaining address and try to load it into EAS.
This proceeds from the base address, to the unit address, to the unit address - parcel link.
This is detailed here in http://code.google.com/p/eas/source/browse/trunk/etl/sql/avs_load/f_load_ddl.sql