API:FAQ:Capabilities:Address Standardization: Difference between revisions
Jump to navigation
Jump to search
Created page with "{{CustomTOC}} ==Service, DPV, and geocoding directory update? How are the updates delivered?== EWS - Weekly CASS/DPV/LACSLink/SuiteLink/AddressPlus - Monthly Canada - Monthly ..." |
m Admin moved page FAQ:API Capabilities:Address Standardization to API:FAQ:Capabilities:Address Standardization without leaving a redirect |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{CustomTOC}} | {{CustomTOC}} | ||
==Service, DPV, and geocoding directory update? How are the updates delivered?== | ==Service/DPV/GeoCoding Updates== | ||
===Service, DPV, and geocoding directory update? How are the updates delivered?=== | |||
EWS - Weekly | EWS - Weekly | ||
CASS/DPV/LACSLink/SuiteLink/AddressPlus - Monthly | CASS/DPV/LACSLink/SuiteLink/AddressPlus - Monthly | ||
| Line 10: | Line 11: | ||
==What is your geocoding data source and what type(s) of information is available (i.e. state code, FIPS county code, census tract, block group, census block detail, etc.)?== | ==GeoCoding Data Source and Information Type== | ||
===What is your geocoding data source and what type(s) of information is available (i.e. state code, FIPS county code, census tract, block group, census block detail, etc.)?=== | |||
TomTom and Navteq are the sources for GeoCoding data. Data fields returned include: County Name/FIPS Code/CBSAs/Census Block/Census Tract, and Lat/Long. | TomTom and Navteq are the sources for GeoCoding data. Data fields returned include: County Name/FIPS Code/CBSAs/Census Block/Census Tract, and Lat/Long. | ||
==Does your solution contain/support NCOALink and LACSLink features? If so, is this an add-on or regular feature? How often are data updates provided?== | ==NCOALink and LACSLink Features and Updates== | ||
===Does your solution contain/support NCOALink and LACSLink features? If so, is this an add-on or regular feature? How often are data updates provided?=== | |||
LACSLink is included with Address Object at no additional charge with monthly updates. NCOALink is available with the SmartMover Web Service as add-on pricing. 24/48-month processing is updated weekly. | LACSLink is included with Address Object at no additional charge with monthly updates. NCOALink is available with the SmartMover Web Service as add-on pricing. 24/48-month processing is updated weekly. | ||
==Explain how your tool is capable of performing address scrubbing in online as well as batch mode?== | ==Address Scrubbing Online/Batch== | ||
===Explain how your tool is capable of performing address scrubbing in online as well as batch mode?=== | |||
The Address Object functions by populating input properties, calling a processing method VerifyAddress( ) and retrieving the results from output properties. This methodology works in both modes by looping through each new record retrieving the results, calling clear properties before populating the input for the next record. | The Address Object functions by populating input properties, calling a processing method VerifyAddress( ) and retrieving the results from output properties. This methodology works in both modes by looping through each new record retrieving the results, calling clear properties before populating the input for the next record. | ||
==Explain in detail how your tool identifies and scrubs undeliverable addresses such as vacant lots, condemned building, etc…== | ==Undeliverable Address Identification/Scrubbing== | ||
===Explain in detail how your tool identifies and scrubs undeliverable addresses such as vacant lots, condemned building, etc…=== | |||
The Delivery Point Validation table and UAA table are part of the National Data files that allow Address Object to recognize these types of addresses and flag them as undeliverable. Vacant addresses are flagged with the appropriate Results Code. | The Delivery Point Validation table and UAA table are part of the National Data files that allow Address Object to recognize these types of addresses and flag them as undeliverable. Vacant addresses are flagged with the appropriate Results Code. | ||
==Explain in detail how your tool identifies and scrubs vanity address/alias address.== | ==Vanity Address Identification/Scrubbing== | ||
===Explain in detail how your tool identifies and scrubs vanity address/alias address.=== | |||
A vanity or alias address is used in some cities and is a holdover from the past; Examples would be 114th Ave which is locally called River Road. Address Object will convert these addresses automatically by consulting the vanity table to a deliverable street address during processing. | A vanity or alias address is used in some cities and is a holdover from the past; Examples would be 114th Ave which is locally called River Road. Address Object will convert these addresses automatically by consulting the vanity table to a deliverable street address during processing. | ||
==Explain how your solution handles dual address lines. (i.e. P.O. box and street address).== | ==Dual Address Lines== | ||
===Explain how your solution handles dual address lines. (i.e. P.O. box and street address).=== | |||
Only one valid address is processed per call, Address1 or Address2. If Address1 is valid, Address Object will only return Address2 without processing. If Address2 contains a suite, it will be output in the Suite field upon processing. | Only one valid address is processed per call, Address1 or Address2. If Address1 is valid, Address Object will only return Address2 without processing. If Address2 contains a suite, it will be output in the Suite field upon processing. | ||
==Explain how your tool is able to handle swapping address lines. (i.e. rearranges address lines to conform to USPS guidelines).== | ==Address Line Swapping== | ||
===Explain how your tool is able to handle swapping address lines. (i.e. rearranges address lines to conform to USPS guidelines).=== | |||
Address Object will process Address1 if valid and return back the USPS information. However, if Address1 is not valid and Address2 is valid, Address Object will swap Address2 and Address1, and validate Address2. | Address Object will process Address1 if valid and return back the USPS information. However, if Address1 is not valid and Address2 is valid, Address Object will swap Address2 and Address1, and validate Address2. | ||
==Explain how your solution supports the ZIP move and eLOT features.== | ==ZIP Move and eLOT Features== | ||
===Explain how your solution supports the ZIP move and eLOT features.=== | |||
eLOT database is invoked by Address Object and verified addresses are appended with an eLOT Lot Order/Number seamlessly if the option is set. The ZIP-Move database is part and parcel of the National Data files that are used by Address Object when verifying US addresses. | eLOT database is invoked by Address Object and verified addresses are appended with an eLOT Lot Order/Number seamlessly if the option is set. The ZIP-Move database is part and parcel of the National Data files that are used by Address Object when verifying US addresses. | ||
==Explain how your solution supports assigning latitude, longitude, census track and fips code to the address data.== | ==Assigning Latitude, Longitude, Census Track, FIPS Code== | ||
===Explain how your solution supports assigning latitude, longitude, census track and fips code to the address data.=== | |||
The MD GeoCoder Object will append the lat/long, as well as Census Tract/Block group information to the address record (at the 11 digit ZIP Code level). | The MD GeoCoder Object will append the lat/long, as well as Census Tract/Block group information to the address record (at the 11 digit ZIP Code level). | ||
==Explain in detail the level of geocoding options available in your tool. For example, Zip/Centroid level, Address level, parcel/point level etc.== | ==Level of GeoCoding Options== | ||
===Explain in detail the level of geocoding options available in your tool. For example, Zip/Centroid level, Address level, parcel/point level etc.=== | |||
GeoCoding is available at no charge to the 5-digit level. Add-on pricing is available for 9-digit as well as Delivery Point 11-digit level. | GeoCoding is available at no charge to the 5-digit level. Add-on pricing is available for 9-digit as well as Delivery Point 11-digit level. | ||
==Explain in detail how your solution supports local municipal taxes that are compliant with new regulatory requirements (i.e. KY city/county taxes, MN Tri-city Fire Surcharge, WV Surcharge, Mine Subsidence, etc…).== | ==Local Municipal Tax Support== | ||
===Explain in detail how your solution supports local municipal taxes that are compliant with new regulatory requirements (i.e. KY city/county taxes, MN Tri-city Fire Surcharge, WV Surcharge, Mine Subsidence, etc…).=== | |||
This is not a capability of the product line. | This is not a capability of the product line. | ||
==Explain in detail how your solution supports 2010 census tract changes. What are your plans to maintain existing census track versus implementing new census tract data in 2010.== | ==2010 Census Tract Change Support and Existing Census Tract Maintenance== | ||
===Explain in detail how your solution supports 2010 census tract changes. What are your plans to maintain existing census track versus implementing new census tract data in 2010.=== | |||
Because the GeoCoder Object is refreshed with updated data, it will automatically be up to date with 2010 Census Data The GeoCoder Object will thereby incorporate the 2010 Census Track data, but Melissa Data will not have the history of the misc. changes. | Because the GeoCoder Object is refreshed with updated data, it will automatically be up to date with 2010 Census Data The GeoCoder Object will thereby incorporate the 2010 Census Track data, but Melissa Data will not have the history of the misc. changes. | ||
==Explain how your solution supports suggestion lists. In other words, explain how your solution provides additional “pop up” addresses that are near matches to the original input address. Is the suggestion list available as part of your base solution?== | ==Suggestion List Support== | ||
===Explain how your solution supports suggestion lists. In other words, explain how your solution provides additional “pop up” addresses that are near matches to the original input address. Is the suggestion list available as part of your base solution?=== | |||
The FindSuggestion method of Address Object can be used to find a suggestion for address records that do not verify. Simply request the FindSuggestion and FindSuggestionNext iteratively until you have a list of suggestions, starting with the best guess first. Also, Address Object’s StreetData interface can be used to find correct ranges. For example, if you get an address with an incorrect range, you can use StreetData to pull out all the possible ranges for that street. If you get an incorrect suite, you can pull out all the possible suite values. With this tool, if you have the street name of an apartment complex, you can pull out all the suites that are present in that complex. This interface supports the use of wildcards so that “Park*” will return any street that begins with “Park” in that particular ZIP Code. | The FindSuggestion method of Address Object can be used to find a suggestion for address records that do not verify. Simply request the FindSuggestion and FindSuggestionNext iteratively until you have a list of suggestions, starting with the best guess first. Also, Address Object’s StreetData interface can be used to find correct ranges. For example, if you get an address with an incorrect range, you can use StreetData to pull out all the possible ranges for that street. If you get an incorrect suite, you can pull out all the possible suite values. With this tool, if you have the street name of an apartment complex, you can pull out all the suites that are present in that complex. This interface supports the use of wildcards so that “Park*” will return any street that begins with “Park” in that particular ZIP Code. | ||
==Explain how your solution identifies and maps natural hazard and fire protection classification zones for insurance purposes.== | ==Natural Hazard and Fire Protection Classification Zones for Insurance Purposes== | ||
===Explain how your solution identifies and maps natural hazard and fire protection classification zones for insurance purposes.=== | |||
This is not a direct capability of the product line. However, using the accurate lat/longs from GeoCoder Object, this information can be accurately mapped in certain GIS software. | This is not a direct capability of the product line. However, using the accurate lat/longs from GeoCoder Object, this information can be accurately mapped in certain GIS software. | ||
[[Category:API]] | [[Category:API]] | ||
[[Category:FAQ]] | |||
[[Category:Data Quality Suite]] | [[Category:Data Quality Suite]] | ||
[[Category:Reference]] | [[Category:Reference]] | ||
Latest revision as of 21:41, 12 June 2014
Service/DPV/GeoCoding Updates
Service, DPV, and geocoding directory update? How are the updates delivered?
EWS - Weekly CASS/DPV/LACSLink/SuiteLink/AddressPlus - Monthly Canada - Monthly GeoCoder - Quarterly IpLocator - Quarterly
The Options for delivery are download and mailed DVDs.
GeoCoding Data Source and Information Type
What is your geocoding data source and what type(s) of information is available (i.e. state code, FIPS county code, census tract, block group, census block detail, etc.)?
TomTom and Navteq are the sources for GeoCoding data. Data fields returned include: County Name/FIPS Code/CBSAs/Census Block/Census Tract, and Lat/Long.
NCOALink and LACSLink Features and Updates
Does your solution contain/support NCOALink and LACSLink features? If so, is this an add-on or regular feature? How often are data updates provided?
LACSLink is included with Address Object at no additional charge with monthly updates. NCOALink is available with the SmartMover Web Service as add-on pricing. 24/48-month processing is updated weekly.
Address Scrubbing Online/Batch
Explain how your tool is capable of performing address scrubbing in online as well as batch mode?
The Address Object functions by populating input properties, calling a processing method VerifyAddress( ) and retrieving the results from output properties. This methodology works in both modes by looping through each new record retrieving the results, calling clear properties before populating the input for the next record.
Undeliverable Address Identification/Scrubbing
Explain in detail how your tool identifies and scrubs undeliverable addresses such as vacant lots, condemned building, etc…
The Delivery Point Validation table and UAA table are part of the National Data files that allow Address Object to recognize these types of addresses and flag them as undeliverable. Vacant addresses are flagged with the appropriate Results Code.
Vanity Address Identification/Scrubbing
Explain in detail how your tool identifies and scrubs vanity address/alias address.
A vanity or alias address is used in some cities and is a holdover from the past; Examples would be 114th Ave which is locally called River Road. Address Object will convert these addresses automatically by consulting the vanity table to a deliverable street address during processing.
Dual Address Lines
Explain how your solution handles dual address lines. (i.e. P.O. box and street address).
Only one valid address is processed per call, Address1 or Address2. If Address1 is valid, Address Object will only return Address2 without processing. If Address2 contains a suite, it will be output in the Suite field upon processing.
Address Line Swapping
Explain how your tool is able to handle swapping address lines. (i.e. rearranges address lines to conform to USPS guidelines).
Address Object will process Address1 if valid and return back the USPS information. However, if Address1 is not valid and Address2 is valid, Address Object will swap Address2 and Address1, and validate Address2.
ZIP Move and eLOT Features
Explain how your solution supports the ZIP move and eLOT features.
eLOT database is invoked by Address Object and verified addresses are appended with an eLOT Lot Order/Number seamlessly if the option is set. The ZIP-Move database is part and parcel of the National Data files that are used by Address Object when verifying US addresses.
Assigning Latitude, Longitude, Census Track, FIPS Code
Explain how your solution supports assigning latitude, longitude, census track and fips code to the address data.
The MD GeoCoder Object will append the lat/long, as well as Census Tract/Block group information to the address record (at the 11 digit ZIP Code level).
Level of GeoCoding Options
Explain in detail the level of geocoding options available in your tool. For example, Zip/Centroid level, Address level, parcel/point level etc.
GeoCoding is available at no charge to the 5-digit level. Add-on pricing is available for 9-digit as well as Delivery Point 11-digit level.
Local Municipal Tax Support
Explain in detail how your solution supports local municipal taxes that are compliant with new regulatory requirements (i.e. KY city/county taxes, MN Tri-city Fire Surcharge, WV Surcharge, Mine Subsidence, etc…).
This is not a capability of the product line.
2010 Census Tract Change Support and Existing Census Tract Maintenance
Explain in detail how your solution supports 2010 census tract changes. What are your plans to maintain existing census track versus implementing new census tract data in 2010.
Because the GeoCoder Object is refreshed with updated data, it will automatically be up to date with 2010 Census Data The GeoCoder Object will thereby incorporate the 2010 Census Track data, but Melissa Data will not have the history of the misc. changes.
Suggestion List Support
Explain how your solution supports suggestion lists. In other words, explain how your solution provides additional “pop up” addresses that are near matches to the original input address. Is the suggestion list available as part of your base solution?
The FindSuggestion method of Address Object can be used to find a suggestion for address records that do not verify. Simply request the FindSuggestion and FindSuggestionNext iteratively until you have a list of suggestions, starting with the best guess first. Also, Address Object’s StreetData interface can be used to find correct ranges. For example, if you get an address with an incorrect range, you can use StreetData to pull out all the possible ranges for that street. If you get an incorrect suite, you can pull out all the possible suite values. With this tool, if you have the street name of an apartment complex, you can pull out all the suites that are present in that complex. This interface supports the use of wildcards so that “Park*” will return any street that begins with “Park” in that particular ZIP Code.
Natural Hazard and Fire Protection Classification Zones for Insurance Purposes
Explain how your solution identifies and maps natural hazard and fire protection classification zones for insurance purposes.
This is not a direct capability of the product line. However, using the accurate lat/longs from GeoCoder Object, this information can be accurately mapped in certain GIS software.