Callpoint’s Geocoder
Callpoint Spatial has been geocoding using G-NAF since 2004. How does this benefit your business?
We have the expertise and capability to help you via our cloud-deployed services:
- Geocode via web services API (SOAP or REST) to enable your systems to talk directly with ours
- Batch Geocode a text or Excel file. When complete, your users receive an email with the download link
Our cloud-deployed Geocoder is located at https://www.callpointspatialgeocoder.com. We use Australian Data Centres and employ https for end-to-end data encryption.
Callpoint Spatial Geocoder – high level overview
Key Features
Built using G-NAF | Callpoint Spatial's Geocoder operates solely on Australian addresses. It is based on and highly optimised for G-NAF, being the authoritative Australian geocoded address dataset compiled and quarterly updated by PSMA. We have actively used and licensed G-NAF since 2004, and have proactively enhanced our Geocoder as G-NAF has evolved. |
Extensive address parsing | Addresses can include extraneous text, especially so in legacy databases. Callpoint Spatial's Geocoder includes extensive address parsing and resolution capabilities. For example: s6 near rear lane entrance 400 ggeorge st sydney Our Geocoder extracts the relevant address within G-NAF: SHOP 6T/400 GEORGE STREET, SYDNEY NSW 2000 |
High yield | At times there are multiple errors within an address. For example: 500 haris rd sudnee Callpoint's Geocoder dives deep to extract the relevant address within G-NAF being: 500 HARRIS STREET, ULTIMO NSW 2007 |
Comprehensive result codes | Callpoint Spatial's Geocoder delivers a comprehensive, informative set of structured result codes. This differs to the single digit only approach offered by some alternatives. In the above example, the result code includes: 21 [SUDNEE:SYDNEY],22 [HARIS:HARRIS],31 [ROAD:STREET],41 [SYDNEY:ULTIMO],70,71,82 Where the following codes are defined as: 21: LocalitySoundex; 22: StreetCloseWord 31: StreetTypeDifferent; 41: LocalityNeighbour In other words, our Geocoder returns for each address, the specific transformations that it performed. This can be useful for your audit and analysis processes. |
Fallback options | A number of user settable options are provided to cater for a variety of use cases. These include range tolerance, street locality and locality level. |
Geocode precision | Fallback options beg the question: to what level of precision do the latitude longitude coordinates refer? The Geocode Precision field returns a single value that indicates whether the returned coordinates are at the address, unique road feature or unique locality feature level. |
Rich ABS attribution | To help with geo-demographic analysis, we return ABS data including the associated Mesh Block, Mesh Block Category, SA1, SA2, SA3, SA4 and Remoteness Index Name and Code. To help with historical cross-referencing, the Collector District is also returned. Our Geocoder also returns the 28 SEIFA columns across the four groups being IRSAD, IRSD, IER and IEO. |
Road Category | Are you a researcher and need to know the category of road associated with a given address? For instance, whether an address represents a local road, national highway or other? Our Geocoder includes a license option where the Transport Hierarchy Code (THC) from PSMA's Transport and Topography dataset is returned as a field. |
Street Intersections | Do you need to geocode street corners? Our corner capability is built using our quarterly updated Street Intersection dataset. Addresses such as "cnr King & George Sydney" are validated as: KING STREET CNR GEORGE STREET, SYDNEY NSW 2000 By contrast, "Kong & George Sodnee" is corrected to: KING STREET CNR GEORGE STREET, SYDNEY NSW 2000 In both cases, the coordinates of the street intersection (-33.868736, 151.206953) in this example are returned. |
API or Batch | Do you want the flexibility to geocode either a text/ Excel file or via API (REST/ SOAP)? Our Geocoder provides both options. |