Skip to navigation
By Communications taxCommunications Geo SaaS Pro SOAP guide

Geocode Lat Long

View as Markdown

The GeocodeLatLong method accepts a latitude and longitude coordinate pair and returns the single best match.

GeocodeLatLong Example

This request contains the latitude (latitude) and longitude (longitude) coordinates for the location. Leave source (Source) blank.

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/"> <s:Header> <o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <o:UsernameToken> <o:Username>USERNAME</o:Username> <o:Password>PASSWORD</o:Password> </o:UsernameToken> </o:Security> </s:Header> <s:Body> <tem:GeocodeLatLong> <tem:latitude>35.991130741436415</tem:latitude> <tem:longitude>-78.90267307450108</tem:longitude> <tem:Source/> </tem:GeocodeLatLong> </s:Body></s:Envelope>

Response

The GeocodeLatLongResponse contains basic address information for a single matching address based on the coordinate pair. The record returned contains:

  • CassAddress is nil since CASS validation is not performed on a lat/long geocode request
  • Census block ID (CensusBlockGroup) and tract ID (CensusTract) fields are included but set to 0
  • PCode, FeatureID, and FipsCode
  • Results are from NavTeq (NetworkID is nt)
  • AFC Geo SaaS Pro Soap is 99.9% confident in this result (Score is 0.9999)

View the Response XML

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <s:Header> <o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <u:Timestamp u:Id="_0"> <u:Created>2019-02-07T17:03:31.176Z</u:Created> <u:Expires>2019-02-07T17:08:31.176Z</u:Expires> </u:Timestamp> </o:Security> </s:Header> <s:Body> <GeocodeLatLongResponse xmlns="http://tempuri.org/"> <GeocodeLatLongResult xmlns:a="http://schemas.datacontract.org/2004/07/EZGeoSaaS" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <a:Alternate>0</a:Alternate> <a:CassAddress i:nil="true"/> <a:CensusBlockGroup>0</a:CensusBlockGroup> <a:CensusTract>0</a:CensusTract> <a:CityName>DURHAM</a:CityName> <a:Country>USA</a:Country> <a:County>DURHAM</a:County> <a:ErrorMessage/> <a:FeatureID>2403521</a:FeatureID> <a:FipsCode>3706319000</a:FipsCode> <a:FipsPlaceName>DURHAM</a:FipsPlaceName> <a:Incorporated>true</a:Incorporated> <a:InputAddress xmlns:b="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> <b:string/> <b:string/> </a:InputAddress> <a:Latitude>35.991130741436415</a:Latitude> <a:Longitude>-78.902673074501081</a:Longitude> <a:NetworkID>nt</a:NetworkID> <a:PCode>2757800</a:PCode> <a:PostalCode/> <a:PostalCodeExtension/> <a:PrimaryJurisdictionName>DURHAM</a:PrimaryJurisdictionName> <a:PrimaryJurisdictionPCode>2757800</a:PrimaryJurisdictionPCode> <a:Score>0.99996893240562246</a:Score> <a:SecondaryUnit/> <a:SpecialTaxDistrictName i:nil="true"/> <a:SpecialTaxDistrictPCode>-1</a:SpecialTaxDistrictPCode> <a:StandardizedAddress xmlns:b="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> <b:string></b:string> <b:string>DURHAM,NC null</b:string> </a:StandardizedAddress> <a:StateName>NC</a:StateName> <a:StreetName/> <a:StreetNumber/> <a:TaxJurisdictionName>DURHAM</a:TaxJurisdictionName> <a:TimeZone/> <a:UnderlyingFipsCode>3706319000</a:UnderlyingFipsCode> </GeocodeLatLongResult> </GeocodeLatLongResponse> </s:Body></s:Envelope>

See Also

Input

Results

Part of the Communications Geo SaaS Pro SOAP guide integration guide. Open the full “Geocode Lat Long” milestone on Avalara to see every page in this section.