Page Comparison

...

The latest accepted revision is "example 10".
Here is a sample xml file and here is the field mapping.

The latest proposed revision is "example 11".
Here is a sample xml file.

...

Code Block

<addressChangeNotification>
    <address>
        <key>419709</key>
        <base_number_prefix></base_number_prefix>
        <base_number>1</base_number>
        <base_number_suffix></base_number_suffix>
        <jurisdiction>PRESIDIO</jurisdiction>
        <longitude>-122.418876252</longitude>
        <latitude>37.774694542</latitude>
        <street_name>SOUTH VAN NESS</street_name>
        <street_name_suffix>
            <abbreviated>AVE</abbreviated>
            <unabbreviated>AVENUE</unabbreviated>
        </street_name_suffix>
        <unit_number_prefix>XXX</unit_number_prefix>
        <unit_number>300</unit_number>
        <unit_number_suffix>YYY</unit_number_suffix>
        <create_tms>2010-08-13 12:15:43.828000</create_tms>
        <retire_tms>2010-08-13 18:41:16.149255</retire_tms>
        <disposition>provisional</disposition>
        <mailing>True</mailing>
        <block>3506</block>
        <lot>001</lot>
        <apn>3506001</apn>
    </address>
    <timestamp>2010-08-13 18:41:16.149255</timestamp>
    <action>retire</action>
</addressChangeNotification>

Example 11
Anchor

...

example11xml

...

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_prefix (char 10)
XML Field: base_address/base_number_prefix
FGDC Field: address number prefix (text)
AVS Field: na
Example:
Comment: EAS has no data in this field
TODO: add field to AVS?

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:

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: widen AVS field

EAS Field: address_base.geometry.longitude (double)
XML Field: base_address/longitude
FGDC Field: address longitude (double)
AVS Field:
Example:
Comment:

EAS Field: address_base.geoemtry.latitude (double)
XML Field: base_address/latitude
FGDC Field: address latitude (double)
AVS Field:
Example:
Comment:

EAS Field: address_base.street_segment.st_name (char 29)
XML Field: base_address/street_name
FGDC Field: street name (text)
AVS Field: AVS_STREETS.STREET_NAME VARCHAR2(28)
Example:
Comment:
TODO: AVS must truncate width

EAS Field: address_base.street_segment.st_type (char 6)
XML Field: base_address/street_name_suffix
FGDC Field: street name post type text
AVS Field: AVS_STREET_SUFFIXES.STREET_SFX (VARCHAR2 2)
Example:
Comment: data type mismatch is accomodated in xml mapping

EAS Field: zone.zipcode (int)
XML Field: base_address/zipcode
FGDC Field: zip code
AVS Field: ?
Example:
Comment:
TODO: add this to EAS change notification message (and remove "jurisdiction"); map to AVS field

EAS Field: address_base.create_tms (datetime)
XML Field: base_address/create_tms
FGDC Field:
AVS Field:
Example:
Comment:

EAS Field: address_base.last_change_tms (datetime)
XML Field: base_address/last_change_tms
FGDC Field:
AVS Field:
Example:
Comment:

EAS Field: address_base.retire_tms (datetime)
XML Field: base_address/retire_tms
FGDC Field:
AVS Field:
Example:
Comment:

EAS Field: addresses.address_id (int)
XML Field: unit_address/address_id
FGDC Field: na
AVS Field: na
Example:
Comment: EAS primary key for unit address

EAS Field: addresses.unit_num_prefix (char 5)
XML Field: base_address/unit_number_prefix
FGDC Field: na
AVS Field:
Example:
Comment:
TODO: EAS will drop this field from database schema

EAS Field: addresses.unit_num (char 20)
XML Field: base_address/unit_number
FGDC Field: unit identifier (text)
AVS Field: AVS_ADDRESSES.UNIT (NUMBER 6)
Example:
Comment:
TODO: AVS must widen field

EAS Field: addresses.unit_num_suffix (char 10)
XML Field: base_address/unit_number_suffix
FGDC Field: na
AVS Field: AVS_ADDRESSES.UNIT_SFX (VARCHAR2 10)
Example:
Comment:
TODO: EAS will drop this field from database scehma

EAS Field: addresses.unit_type_id->d_unit_type.unit_type_description (varchar 50)
XML Field: unit_address/unit_type
FGDC Field: unit type (text)
AVS Field: na
Example: suite, apartment
Comment:
TODO: EAS will add this field to the XML - do we need to map it to an AVS field?

EAS Field: addresses.disposition_code (int)
XML Field: unit_address/disposition
FGDC Field: address lifecycle status (text)
AVS Field:
Example: provisional, offical
Comment: FGDC field is approx
TODO: do we need to map this to an AVS field?

EAS Field: addresses.mailable_flg (boolean)
XML Field: unit_address/mailing
FGDC Field: na
AVS Field: na
Example:
Comment:

EAS Field: addresses.create_tms (datetime)
XML Field: unit_address.create_tms
FGDC Field: na
AVS Field:
Example:
Comment:

EAS Field: addresses.last_change_tms (datetime)
XML Field: unit_address.last_change_tms
FGDC Field: na
AVS Field:
Example:
Comment:

EAS Field: addresses.retire_tms (datetime)
XML Field: unit_address.retire_tms
FGDC Field: na
AVS Field: na
Example:
Comment:

EAS Field: address_x_parcel.parcel.block_num (char 5)
XML Field: address_parcel_link/parcel/block
FGDC Field: na
AVS Field: AVS_STRUCTURES.BLOCK (VARCHAR2 5)
Example:
Comment:

EAS Field: address_x_parcel.parcel.lot_num (char 5)
XML Field: address_parcel_link/parcel/lot
FGDC Field: na
AVS Field: AVS_STRUCTURES.LOT (VARCHAR2 4)
Example:
Comment:
TODO: field width mismatch - widen AVS field?

...

example11xml

The purpose of this version is to support the rework of the model precipitated by MAD-156.

Code Block


<?xml version="1.0" encoding="utf-8"?>
<addressChangeNotification>
    <base_address_part>
        <base_address>
            <base_address_id>157611</base_address_id>
            <base_number_prefix></base_number_prefix>
            <base_number_prefix></base_number_prefix>
            <base_number>53</base_number>
            <base_number_suffix></base_number_suffix>
            <longitude>-122.433538793</longitude>
            <latitude>37.734081063</latitude>
            <street_name>WILDER</street_name>
            <street_name_suffix>
                <abbreviated>ST</abbreviated>
                <unabbreviated>STREET</unabbreviated>
            </street_name_suffix>
            <zipcode>SF MAIN</zipcode>
            <create_tms>2010-06-28 15:33:10.437000</create_tms>
            <last_change_tms>2010-10-25 17:05:15.093000</last_change_tms>
            <retire_tms></retire_tms>
        </base_address>
        <action>no change</action>
    </base_address_part>

    <unit_address_part>
        <unit_address>
            <address_id>419583</address_id>
            <unit_number_prefix></unit_number_prefix>
            <unit_number>603</unit_number>
            <unit_number_suffix></unit_number_suffix>
            <base_unit_address_flag>False</base_unit_address_flag>
            <disposition>official</disposition>
            <mailing>True</mailing>
            <create_tms>2010-06-28 15:33:10.437000</create_tms>
            <last_change_tms>2010-10-25 17:05:15.093000</last_change_tms>
            <retire_tms></retire_tms>
        </unit_address>
        <action>no change</action>
    </unit_address_part>
    
    <address_parcel_link_part>
        <address_parcel_link>
            <id>68</id>
            <create_tms>2010-10-25 17:05:15.093000</create_tms>
            <last_change_tms>2010-10-25 17:05:15.093000</last_change_tms>
            <retire_tms></retire_tms>
            <parcel>
                <block>6745</block>
                <lot>089</lot>
                <apn>6745089</apn>
            </parcel>
        </address_parcel_link>
        <action>insert</action>
    </address_parcel_link_part>

</addressChangeNotification>

Anchor

	example11mapping
	example11mapping

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: 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_prefix (char 10)
XML Field: base_address/base_number_prefix
FGDC Field: address number prefix (text)
AVS Field: na
Example:
Comment: EAS has no data in this field
TODO: add field to AVS?

EAS Field: address_x_parcel.create_tms (datetimebase.base_address_num (int)
XML Field: base_address_parcel_link/createbase_tmsnumber
FGDC Field: naaddress number (int)
AVS Field: AVS_ADDRESSES.STREET_NUMBER (NUMBER 6)
Example:
Comment:
TODO: determine mapping

EAS Field: address_x_parcel.retire_tms (datetimebase.base_address_suffix (char 10)
XML Field: base_address_parcel_link/retire_tms/base_number_suffix
FGDC Field: naaddress number suffix (text)
AVS Field: ???AVS_ADDRESSES.STREET_NUMBER_SFX (VARCHAR2 1)
Example: "1/2"
Comment:
TODO: determine mapping

...

The purpose of this version is to support the rework of the model precipitated by MAD-156.

...

-122
TODO: widen AVS field