Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Here is the mapping between AVS and EAS.  To help clarify the purpose of each field, I use the FGDC Street Address Data Standard. Here is the latest and most complete reference or you can just take a look at draft 2 which is usually adequate.

EAS Field

XML Field

FGDC Field

AVS Field

Example

Comment

addresses.address_id int

key

  na

  base_number_prefix

 

 

address_base.base_number

 

 

_prefix char(10)

base_number_suffix prefix

  address number prefix

 

jurisdiction

 

 

longitude

 

 

latitude

 

 

street_name

 

 

street_name_suffix

 

 

unit_number_prefix

 

 

unit_number

 

 

unit_number_suffix

 

 

create_tms

 

 

retire_tms

 

 

disposition

 

 

mailing

 

 

block

 

 

lot

 

 

apn

 

 

timestamp

 

 

action address_base.base_number int

base_number

address number

AVS_ADDRESSES.STREET_NUMBER NUMBER(6)

 

 

address_base.base_number_suffix char(10)

base_number_suffix

address number suffix

 

 

 

?

?

?

AVS_ADDRESSES.STREET_NUMBER_SFX VARCHAR2(1)

V, A, C, P

todo - how do we map this?

address_base.zone_id int

jurisdiction

community place name

 

 

FGDC field is approx

address_base.geoemtry.longitude float

longitude

address longitude

 

 

 

address_base.geoemtry.latitude float

latitude

address latitude

 

 

 

address_base.street_segment.st_name char(29)

street_name

street name

AVS_STREETS.STREET_NAME VARCHAR2(28)

 

todo - problem with field width

address_base.street_segment.st_type char(6)

street_name_suffix

street name post type

AVS_STREET_SUFFIXES.STREET_SFX VARCHAR2(2)

 

data type mismatch is accomodated in xml

addresses.unit_num_prefix char(5)

unit_number_prefix

na

 

 

 

addresses.unit_num char(20)

unit_number

unit identifier text

AVS_ADDRESSES.UNIT NUMBER(6)

 

todo - is data type mismatch

addresses.unit_num_suffix char(10)

unit_number_suffix

na

AVS_ADDRESSES.UNIT_SFX VARCHAR2(10)

 

 

addresses.unit_type_id int

na

unit type

na

suite, apartment

 

na

na

na

AVS_ADDRESSES.ADDRESS_TYPE VARCHAR2(10)

PRIMARY, ALTERNATE, ALIAS

 

addresses.create_tms datetime

create_tms

na

 

 

 

addresses.retire_tms datetime

retire_tms

na

AVS_ADDRESSES.END_DATE DATE

 

 

addresses.disposition_code int

disposition

address lifecycle status

 

 

FGDC field is approx

na

na

address official status

AVS_ADDRESSES.VALID VARCHAR2(1)

 

EAS combines this with address life cycle status

addresses.mailable_flg boolean

mailing

na

 

 

 

parcel.block_num char(5)

block

na

AVS_STRUCTURES.BLOCK VARCHAR2(5)

 

 

parcel.lot_num char(5)

lot

na

AVS_STRUCTURES.LOT VARCHAR2(4)

 

todo - field with mismatch

na

 

building identifer

AVS_STRUCTURES.STRUCTURE_NUMBER VARCHAR2(2)

 

 

parcel.blk_lot char(9)

apn

na

 

 

 

addresses_history.last_change_tms datetime

timestamp

na

 

 

 

addresses_history.history_action char(10)

action

na

 

 

 

addresses.unq_adds_id int

na

na

AVS_ADDRESSES.ADDRESS_KIND VARCHAR2(10)

DBI, ASSESSOR