DataTools Kleber Method Description

Method:
DataTools.Enhance.Address.Geocoding.Linz.Nz.Append WARNING: THIS METHOD HAS BEEN DISCONTINUED
Use to geocode New Zealand addresses with the LINZ dataset

Test:

Parameter	Value
AddressLine1
AddressLine2
AddressLine3
AddressLine4
Suburb
TownCityMailtown
Postcode
RequestId
RequestKey
DepartmentCode

Input Parameters:

Parameter	Description
AddressLine1	Address line 1
AddressLine2	Address line 2
AddressLine3	Address line 3
AddressLine4	Address line 4
Suburb	Suburb
TownCityMailtown	Town, City or Mailtown
Postcode	Postcode
RequestId	Optional user value to assist in linking DtRequests with DtResponses.
RequestKey	Required for user access verification. For client side script protect your Request Key by using the DataTools.Security.GenerateTemporaryRequestKey
DepartmentCode	Optional user value to allocate transaction usage by department. Limit of 50 unique Department codes per account.

Output Fields:

Field	Description
WGS-Longitude	Longitude - World Geodetic System coordinate system (WGS84)
WGS-Latitude	Latitude - World Geodetic System coordinate system (WGS84)
DEM-Longitude	Longitude - Digital Elevation Model coordinate system (DEM)
DEM-Latitude	Latitude - Digital Elevation Model coordinate system (DEM)
NZTM-Longitude	Longitude - New Zealand Transverse Mercator coordinate system (NZTM2000)
NZTM-Latitude	Latitude - New Zealand Transverse Mercator coordinate system (NZTM2000)

Supported Web Service API Interfaces:

Web Service Method: ProcessQueryStringRequest (REST)

Request Format: Url QueryString, Protocols: HTTP GET, HTTPS GET, Response Formats: JSON, XML*
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebService/DtKleberService.svc

Sample QueryString Request:
/ProcessQueryStringRequest?Method=DataTools.Enhance.Address.Geocoding.Linz.Nz.Append&AddressLine1=&AddressLine2=&AddressLine3=&AddressLine4=&Suburb=&TownCityMailtown=&Postcode=&RequestId=&RequestKey=&DepartmentCode=

Sample JSON Response:
{
   "DtResponse":{
      "RequestId":"",
      "ResultCount":"1",
      "ErrorMessage":"",
      "Result":[
         {
            "WGS-Longitude":"",
            "WGS-Latitude":"",
            "DEM-Longitude":"",
            "DEM-Latitude":"",
            "NZTM-Longitude":"",
            "NZTM-Latitude":""
         }
      ]
   }
}

Sample Code:

Web Service Method: ProcessXmlRequest (SOAP)

Request Format: XML over SOAP, Protocols: HTTP POST, HTTPS POST, Response Formats: XML, JSON*
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebServiceSoap/DtKleberService.svc
SOAP WSDL: https://customname.datatoolscloud.net.au/KleberWebServiceSoap/DtKleberService.svc?wsdl

Sample XML Request:
<DtRequest Method="DataTools.Enhance.Address.Geocoding.Linz.Nz.Append" AddressLine1="" AddressLine2="" AddressLine3="" AddressLine4="" Suburb="" TownCityMailtown="" Postcode="" RequestId="" RequestKey="" DepartmentCode="" />

Sample XML Response:
<DtResponse RequestId="" ResultCount="1" ErrorMessage="">
  <Result WGS-Longitude="" WGS-Latitude="" DEM-Longitude="" DEM-Latitude="" NZTM-Longitude="" NZTM-Latitude="" />
</DtResponse>

SOAP Envelope: The XML request is passed through a single parameter in the SOAP envelope <DtXmlRequest>. Where the development language requires the SOAP envelope contents to be defined manually, the additional step of encoding the Dt XML Request is required. The encoding required needs to transform "<" of the DtRequest to "<" and ">" to ">". See example below.

Sample SOAP Envelope:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/">
  <soapenv:Header/>
  <soapenv:Body>
    <tem:ProcessXmlRequest>
      <!--Optional:-->
      <tem:DtXmlRequest>
        &lt;DtRequest Method="DataTools.Enhance.Address.Geocoding.Linz.Nz.Append" AddressLine1="" AddressLine2="" AddressLine3="" AddressLine4="" Suburb="" TownCityMailtown="" Postcode="" RequestId="" RequestKey="" DepartmentCode="" /&gt;
      </tem:DtXmlRequest>
    </tem:ProcessXmlRequest>
  </soapenv:Body>
</soapenv:Envelope>

Batching Requests: Use the <DtRequests> (plural) tag to send through multiple requests in a single transaction.

<DtRequests>
    <DtRequest Method="DataTools.Enhance.Address.Geocoding.Linz.Nz.Append" AddressLine1="" AddressLine2="" AddressLine3="" AddressLine4="" Suburb="" TownCityMailtown="" Postcode="" RequestId="" RequestKey="" DepartmentCode="" />
    <DtRequest Method="DataTools.Enhance.Address.Geocoding.Linz.Nz.Append" AddressLine1="" AddressLine2="" AddressLine3="" AddressLine4="" Suburb="" TownCityMailtown="" Postcode="" RequestId="" RequestKey="" DepartmentCode="" />
</DtRequests>

Sample Code:

* Add the additional input parameter "OutputFormat=json" or "OutputFormat=xml" to change the response format from default.
* Add the additional input parameter "callback" to convert JSON responses to JSONP responses for across domains support.
CORS header included where callback is not defined.

Please Note:
Ensure you thoroughly test all the methods you are using and are happy with the results before going into production. DataTools is charged by the data suppliers for use of every method – therefore ALL calls to any method will incur a COST. When you register DataTools provides you with free credit to help with development and trialling of the service. Once that credit is used you will need to purchase a monthly subscription and/or top up to continue using the service, even for development purposes. Please check the Method Pricing List for all current costs. DataTools does not warrant or guarantee the quality of the results returned and will not be held responsible for any costs incurred by using a method. Should you have any questions please contact your Sales representative or the Client Services team.