...
| 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>
|
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 | FGDC | AVS |
|---|---|---|
key |
|
|
base_number_prefix |
|
|
base_number |
|
|
base_number_suffix |
|
|
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 |
|
|