| Geocoding highways |
Geocoding an address with a house number
For successful address matching (also called geocoding) at the house level, the address must contain a certain combination of fields.
Possible combinations for successful geocoding are
NOTE: European geocoding doesn't use the State/Province field, but it does require the Country field.
Each address you attempt to geocode costs the credit charge for the address data source you use. Pricing is based on the actual data source used. There is no cost for attempted requests that fail.
Partial address support means that if you do not provide the complete address, you can still get a list of candidates based on the information you have entered. For example, if you only enter a city name, the result list contains cities whose name matches the name you entered. Address Finder can perform four levels of geocoding, with levels 3 and 4 representing partial address geocoding.
Level 1: House-level geocoding, returning the x,y coordinates of a complete address, such as 380 New York St, Redlands, CA 92373
Level 2: Intersection geocoding, returning the x,y coordinates of the intersection of two cross streets, such as New York St AT Pine Ave, Redlands, CA 92373
Level 3: Street-level geocoding, returning the centroids of each street segment and area, such as 100-200 New York St, 92373 or New York St, 92373
Level 4: Place-level geocoding, returning the centroid of the place, such as Redlands, CA.
To turn on partial address support, first use the method getInfo to see which data sources support partial addresses, then set the object parameter AddressFinderOptions.partialAddress="true".
The following list shows the possible address combinations you can input to Address Finder to receive geocoding information.
|
Data input to Address Finder |
partialAddress="false" |
partialAddress="true" |
||
|---|---|---|---|---|
|
Level 1 |
Level 2 |
Level 3 |
Level 4 |
|
| house number, street, city, state/province, postal code |
x |
|
|
|
| house number, street, city, state/province |
x |
|
|
|
| house number, street, postal code |
x |
|
|
|
| street, cross street, city, state/province, postal code |
|
x |
|
|
| street, cross street, city, state/province |
|
x |
|
|
| street, cross street, postal code |
|
x |
|
|
| street, postal code |
|
|
x |
|
| city, postal code (city is ignored) (Place Finder) |
|
|
|
x |
| city, state/province (Place Finder) |
|
|
|
x |
| city (Place Finder) |
|
|
|
x |
| postal code (Place Finder) |
|
|
|
x |
| street, city (street is ignored) (Place Finder) |
|
|
|
x |
Address Finder supports the native language of the geocoding country.
IP address geocoding often returns results for the organization that owns the IP address block instead of the actual computer IP address. This is because IP address geocoding does not consider private IPs, virtual private networks (VPNs), or internal network blocks. In the case of America Online (AOL), which uses proxies to manage its vast network traffic, users are identified with "aol" in the region and city field and a general rounded latitude/longitude point (meant to represent the center of the United States).
P.O. Boxes are geocoded to the ZIP Code centroid. The centroid is calculated based on the streets in that postal code area.
For information on geocoding codes, see Geocoding codes.
To geocode an intersection, use the following syntax:
Street1 at Steet2, City, State/Province
The "auto" data source is recommended for geocoding highways and interstates.
The syntax in the following samples for naming highways and interstates should work for any Address Finder data source:
SR 101 at I405, Sherman oaks, CA
US 101 at I405, Sherman oaks, CA
I10 at US 30, Redlands, CA
US 30 at I10, Redlands, CA
I90 at I481, East Syracuse, NY
Visit the Feedback page to give comments or suggestions about the ArcWeb Developer's Guide.