Geocoding Options

The following table lists the options that control how a location's coordinates are determined.

Note: As the EGM Module transitions its administrative tasks to a web-based Management Console, labels for the options may use different wording than what you see in Enterprise Designer. There is no difference in behavior.
Table 1. Geocoding Options for Venezuela

Parameter

Description

Option.GeocodeLevel

Specifies how precisely you want to geocode addresses. One of the following:

StreetAddress
The geocoder attempts to geocode addresses to a street address, but some matches may end up at a less precise location such as a postal code centroid, intersection, or shape path.
PostalCentroid
This option is not available for this country.
GeographicCentroid
The geocoder attempts to geocode addresses to the geographic centroid of a city or state.

Option.Interpolation

Y
Yes, perform address point interpolation.
N
No, do not perform address point interpolation.

Option.FallbackToGeographic

Specifies whether to attempt to determine a geographic region centroid when an address-level geocode cannot be determined.

Y
Yes, determine a geographic centroid when an address-level centroid cannot be determined. Default.
N
No, do not determine a geographic centroid when an address-level centroid cannot be determined.

Option.FallbackToPostal

Y
Yes, determine a postal code centroid when an address-level centroid cannot be determined. Default.
N
No, do not determine a postal code centroid when an address-level centroid cannot be determined.

Option.CoordinateSystem

A coordinate system is a reference system for the unique location of a point in space. Cartesian (planar) and Geodetic (geographical) coordinates are examples of reference systems based on Euclidean geometry. Spectrumâ„¢ Technology Platform supports systems recognized by the European Petroleum Survey Group (EPSG).

Each country supports different coordinate systems. Depending on the country, you have one or more of the following options:

Option.IncludeInputs

Specifies whether to return the formatted input street address and each input address element in a separate field. This feature can help you understand how the input address was parsed and identify specific input elements that could not be geocoded. For example, a returned HouseNumber.Input could contain an invalid house number in your input address.
You can specify parsed input returns for a specific country. For example, a REST API example for Canada is:
Option.CAN.IncludeInputs=Y
Note: Data vintage must be 2014 Q4 or newer to get Parsed Address Input returns. Also note that Parsed Address Input elements are not returned for every country.
Parsed Address Input elements are returned in separately labeled fields names with a .Input extension. For example:
  • FormattedInputStreet.Input
  • City.Input
  • Country.Input
  • HouseNumber.Input
  • Locality.Input
  • PostalCode.Base.Input
  • StreetName.Input
  • StreetSuffix.Input

    Other labeled fields are possible depending on the input address, country, and data source.

    Note: Parsed Address Input elements are not returned for every country. Also, because Geocode Address World geocodes to the geographic or postal level only (not street address), this does not return Parsed Address Input

    For many countries, if part of the input address could not be recognized as a specific address element, this content is returned in UnparsedWords.Input.

    For intersection addresses, the first entered street is returned in StreetName.Input and the second entered street name is returned in IntersectionIdStreet2.Input.