...
Here is the latest and most complete reference or you can just take a look at draft 2 which is usually adequate.Here is a foo
Click Here for number suffix.
Click Here for unit number.
...
EAS Field: address_base.base_address_id (int)
XML Field: base_address_id
FGDC Field: na
AVS Field: na
Example:
Comment: EAS primary key
...
EAS Field: address_base.base_address_num (int)
XML Field: base_address/base_number
FGDC Field: address number (int)
AVS Field: AVS_ADDRESSES.STREET_NUMBER (NUMBER 6)
Example:
Comment:
...
...
| Anchor | ||||
|---|---|---|---|---|
|
...
number suffix
EAS Field: address_base.base_address_suffix (char 10)
XML Field: base_address/base_number_suffix
FGDC Field: address number suffix (text)
AVS Field: AVS_ADDRESSES.STREET_NUMBER_SFX (VARCHAR2 1)
Example: "1/2"
Comment: MAD-122
TODO: resolve column width issue
Discussion
The issue here is that widening the AVS column would trigger significant changes in many parts of DBIs systems.
Moreover, much of that work would be tossed out when they adopt the new permitting system within 1-2 years.
Here are the alternatives
1) Change the AVS column to char 10.
As stated above, this will be expensive and the ROI will be low.
...
EAS Field: addresses.unit_num_prefix (char 5)
XML Field: na
FGDC Field: na
AVS Field:
Example:
Comment:
TODO: EAS will drop this field from database schema
...
| Anchor | ||||
|---|---|---|---|---|
|
EAS Field: addresses.unit_num (char 20)
XML Field: base_address/unit_number
FGDC Field: unit identifier (text)
AVS Field: AVS_ADDRESSES.UNIT_SFX (VARCHAR2 10)
Example:
Comment:
TODO: change addresses.unit_num (char 20) to addresses.unit_num (char 10) (no data loss)
Discussion: We put the unit_num into the AVS unit suffix as a whole because unit_num could be any arbitrary char 10 string with or without an integer at the beginning.
...