Here is my analysis for the task of adding street name aliases to the change notification XML.
First, let's look at a small example xml fragment.
Here is an xml fragment from the existing eas change notification (as of 2011.09.15).
<base_address>
...
<street_name>PINE</street_name>
<street_name_suffix>
<abbreviated>ST</abbreviated>
<unabbreviated>STREET</unabbreviated>
</street_name_suffix>
...
</base_address>
As you can see this will not support aliases.
Also DPW is starting work to add pre and post direction next week.
This would be the "SOUTH" in "MISSION BAY BLVD SOUTH".
I will be meeting Eddy at DPW tomorrow and I will push for the FGDC model.
For too much information on the FGDC see:
http://www.fgdc.gov/standards/projects/FGDC-standards-projects/street-address
I have found this documemnt to contain about the right amount of information:
http://www.fgdc.gov/standards/projects/FGDC-standards-projects/street-address/AddressStandardFINAL.zip
Here is a fragment for CompleteStreetName that follows the FGDC postal address standard final draft.
<CompleteStreetName>
<StreetNamePreModifier></StreetNamePreModifier>
<StreetNamePreDirectional></StreetNamePreDirectional>
<StreetNamePreType></StreetNamePreType>
<StreetName>MISSION BAY</StreetName>
<StreetNamePostType>BLVD</StreetNamePostType>
<StreetNamePostDirectional>NORTH</StreetNamePostDirectional>
<StreetNamePostModifier></StreetNamePostModifier>
</CompleteStreetName>
And here is what I think we need for right now.
<CompleteStreetName>
<StreetNamePreDirectional></StreetNamePreDirectional>
<StreetName>MISSION BAY</StreetName>
<StreetNamePostType>BLVD</StreetNamePostType>
<StreetNamePostDirectional>NORTH</StreetNamePostDirectional>
</CompleteStreetName>
If we add aliases to the change notification,
and we were starting from scratch I would go this route...
<base_address>
...
<StreetSegment>
<StreetSegmentId>12345</StreetSegmentId>
<StreetNames>
<Primary>
<CompleteStreetName>
<StreetNamePreDirectional></StreetNamePreDirectional>
<StreetName>MISSION BAY NORTH</StreetName>
<StreetNamePostType>BLVD</StreetNamePostType>
<StreetNamePostDirectional></StreetNamePostDirectional>
</CompleteStreetName>
<StreetNamePostTypes>
<abbreviated>BLVD</abbreviated>
<unabbreviated>BOULEVARD</unabbreviated>
</StreetNamePostTypes>
</Primary>
<Alias>
<CompleteStreetName>
<StreetNamePreDirectional></StreetNamePreDirectional>
<StreetName>MISSION BAY BLVD NORTH</StreetName>
<StreetNamePostType></StreetNamePostType>
<StreetNamePostDirectional></StreetNamePostDirectional>
</CompleteStreetName>
<StreetNamePostTypes>
<abbreviated></abbreviated>
<unabbreviated></unabbreviated>
</StreetNamePostTypes>
</Alias>
<!-- additional aliases here -->
</StreetNames>
</StreetSegment>
...
</base_address>
This approach
- insluates us from impending changes at DPW
- supports alias
- supports various suffixes
- trys to follow the FGDC standard
However, a more concise appraoch would be...
<base_address>
...
<StreetSegment>
<Primary>
<street_name>MISSION BAY SOUTH</street_name>
<street_name_suffix>
<abbreviated>BLVD</abbreviated>
<unabbreviated>BOULEVARD</unabbreviated>
</street_name_suffix>
</Primary>
<Alias>
<street_name>MISSION BAY SOUTH BLVD</street_name>
<street_name_suffix>
<abbreviated></abbreviated>
<unabbreviated></unabbreviated>
</street_name_suffix>
</Alias>
<StreetSegment>
...
</base_address>
This simpler approach accomplishes our immediate goals.
I'll be talking to DPW tomorrow to see if we must to make changes in EAS
to prevent breakage when they make changes StreetNamePreDirectional and StreetNamePostDirectional
What should we do?
I still find myself leaning towards leaving the message as is
and changing the consumer over to use EAS IDs for the updates.
0 Comments