Search results

Jump to navigation Jump to search

Page title matches

Page text matches

  • Legacy
    |Image=[[Image:ICON_CSL_GeoCoder.png|84px|GeoCoder|link=GeoCoder]] |Link=[[GeoCoder]]
    3 KB (456 words) - 01:20, 18 February 2023
  • Returned Result Codes
    |[[Returned Result Codes:APIs#GeoCoder Object|GeoCoder Object]] |[[Returned Result Codes:Legacy Services#GeoCoder|GeoCoder]]
    4 KB (597 words) - 20:02, 13 January 2015
  • Reverse GeoCoder:Response
    ...d to make the request, the response will be in a certain protocol. Reverse GeoCoder supports these response protocols: XML, and JSON. :This is a string value that is the current revision number of Reverse GeoCoder.
    8 KB (1,062 words) - 18:48, 21 July 2020
  • Delivery Indicator:Build History
    **GeoCoder
    471 bytes (62 words) - 17:15, 12 December 2018
  • Contact Zone:Contact Verify:Component Settings
    ====GeoCoder/GeoPoint Object==== ;This box displays any error messages generated by initializing the GeoCoder Object.
    9 KB (1,449 words) - 00:58, 3 January 2017
  • Reverse GeoCoder:doLookupPostalCodes
    Reverse GeoCoder supports multiple protocols to access the service, including JSON, REST and Reverse GeoCoder requires the values of <code>Content-Type</code> and <code>Accept</code>.
    11 KB (1,474 words) - 17:11, 8 October 2021
  • Listware Plus:Description
    *Reverse GeoCoder
    842 bytes (121 words) - 00:25, 30 November 2023
  • Pentaho:Contact Verify:Advanced Configuration
    ====GeoCoder/GeoPoint Object==== ;This box displays any error messages generated by initializing the GeoCoder Object.
    10 KB (1,531 words) - 17:28, 23 December 2016
  • Pentaho/Contact Zone:Contact Verify:Advanced Configuration
    ====GeoCoder/GeoPoint Object==== ;This box displays any error messages generated by initializing the GeoCoder Object.
    10 KB (1,542 words) - 17:24, 11 January 2017
  • Email Verifier:Build History
    **GeoCoder
    619 bytes (86 words) - 17:19, 12 December 2018
  • Contact Verification Server
    *[[Media:DQT_WS_GeoCoder_RG.pdf|GeoCoder Reference Guide]]
    1 KB (163 words) - 16:33, 11 June 2021
  • Returned Result Codes:Legacy Services
    |[[Returned Result Codes:APIs#GeoCoder Object|GeoCoder Object]] |[[Returned Result Codes:Web Services#Reverse GeoCoder Web Service|Reverse GeoCoder Web Service]]
    11 KB (1,542 words) - 22:23, 3 March 2015
  • Reverse GeoCoder:FAQ
    [[Reverse GeoCoder|&larr; Reverse GeoCoder]] [[Category:Reverse GeoCoder]]
    3 KB (515 words) - 16:09, 2 August 2022
  • Reverse GeoCoder:Request
    Reverse GeoCoder supports multiple protocols to access the service, including JSON, REST, an Reverse GeoCoder requires the values of <code>Content-Type</code> and <code>Accept</code>.
    6 KB (767 words) - 16:10, 25 March 2021
  • Reverse GeoCoder:doLookup
    Reverse GeoCoder supports multiple protocols to access the service, including JSON, REST, an Reverse GeoCoder requires the values of <code>Content-Type</code> and <code>Accept</code>.
    14 KB (1,882 words) - 23:58, 6 December 2021
  • Name Parser:Build History
    **GeoCoder
    1,002 bytes (144 words) - 17:23, 12 December 2018
  • SSIS:Contact Verify:Advanced Configuration
    ====GeoCoder/GeoPoint Object (US & Canada)==== :Displays any error messages generated by initializing the GeoCoder Object.
    16 KB (2,517 words) - 16:45, 14 February 2018
  • SSIS:Contact Verify:GeoCode
    There are four options that control how the GeoCoder feature of the CVC acquires the data it needs for geocoding. The first, Not ...CVC, you can use the results based on those input columns as input for the GeoCoder. To do this, you must meet the minimum requirements for Address Verify: Add
    9 KB (1,360 words) - 01:04, 22 November 2017
  • Reverse GeoCoder:REST XML
    [[Category:Reverse GeoCoder]]
    2 KB (202 words) - 22:07, 6 December 2021
  • Reverse GeoCoder:XML
    [[Category:Reverse GeoCoder]]
    3 KB (226 words) - 22:08, 6 December 2021
  • Contact Zone:Contact Verify:GeoCode
    There are four options that control how the GeoCoder feature of the CVC acquires the data it needs for geocoding. The first, Not ...CVC, you can use the results based on those input columns as input for the GeoCoder. To do this, you must meet the minimum requirements for Address Verify: Add
    8 KB (1,307 words) - 01:08, 3 January 2017
  • Pentaho:Contact Verify:GeoCode
    There are four options that control how the GeoCoder feature of the CVC acquires the data it needs for geocoding. ...CVC, you can use the results based on those input columns as input for the GeoCoder. To do this, you must meet the minimum requirements for Address Verify: Add
    8 KB (1,305 words) - 00:16, 28 May 2015
  • Pentaho/Contact Zone:Contact Verify:GeoCode
    There are four options that control how the GeoCoder feature of the CVC acquires the data it needs for geocoding. ...CVC, you can use the results based on those input columns as input for the GeoCoder. To do this, you must meet the minimum requirements for Address Verify: Add
    8 KB (1,312 words) - 17:32, 11 January 2017
  • Returned Result Codes:APIs
    |[[#GeoCoder Object|GeoCoder Object]] |[[Returned Result Codes:Web Services#Reverse GeoCoder Web Service|Reverse GeoCoder Web Service]]
    12 KB (1,677 words) - 23:04, 18 September 2019
  • Phone Verifier:Build History
    **GeoCoder
    1 KB (150 words) - 17:31, 12 December 2018
  • Reverse GeoCoder:doLookupFromList
    Reverse GeoCoder requires the values of <code>Content-Type</code> and <code>Accept</code>. :This is a string value that is the current revision number of Reverse GeoCoder.
    13 KB (1,853 words) - 00:00, 7 December 2021
  • Data Quality Web Service:Build History
    *[4/12/2007] The Census Block field in the Geocoder package has reverted back to a 4 character string. It was originally reduce *[4/15/2006] The Census Block field in the Geocoder package is changing from a 4 character string to a 1 character sting. This
    3 KB (449 words) - 17:11, 12 December 2018
  • Property V3:Build History
    **GeoCoder
    1,001 bytes (135 words) - 01:18, 18 February 2023
  • Zip Search:Build History
    **GeoCoder
    1 KB (162 words) - 01:23, 7 March 2023
  • Reverse GeoCoder:Result Codes
    [[Category:Reverse GeoCoder]]
    1 KB (199 words) - 19:28, 8 March 2019
  • Reverse GeoCoder:REST JSON
    [[Category:Reverse GeoCoder]]
    2 KB (177 words) - 22:08, 6 December 2021
  • Returned Result Codes:Software
    |[[Returned Result Codes:APIs#GeoCoder Object|GeoCoder Object]] |[[Returned Result Codes:Web Services#Reverse GeoCoder Web Service|Reverse GeoCoder Web Service]]
    10 KB (1,482 words) - 19:57, 13 January 2015
  • Product Update Schedules
    |'''GeoCoder Mailers+4''' |'''GeoCoder Object'''
    5 KB (517 words) - 18:38, 20 April 2023
  • Street Search:Build History
    **GeoCoder
    1 KB (195 words) - 01:19, 7 March 2023
  • Build History:GeoCoder Object
    [[GeoCoder Object|&larr; GeoCoder Object]] *https://releasenotes.melissa.com/on-premise-api/geocoder-object/
    17 KB (2,628 words) - 01:27, 7 March 2023
  • API:FAQ:Capabilities:Address Standardization
    GeoCoder - Quarterly The MD GeoCoder Object will append the lat/long, as well as Census Tract/Block group inform
    6 KB (1,003 words) - 21:41, 12 June 2014
  • Pentaho:Contact Verify:Reporting
    ;Geocoder Details
    1 KB (219 words) - 17:00, 28 May 2015
  • Solaris 32/64 Bit GCC Deprecation Notice
    |Geocoder Object
    1 KB (187 words) - 18:52, 25 November 2014
  • Contact Zone:Contact Verify:Reporting
    ;Geocoder Details
    1 KB (220 words) - 01:09, 3 January 2017
  • Pentaho/Contact Zone:Contact Verify:Reporting
    ;Geocoder Details
    1 KB (226 words) - 17:39, 11 January 2017
  • Reverse GeoCoder:JSON
    [[Category:Reverse GeoCoder]]
    3 KB (254 words) - 22:08, 6 December 2021
  • Returned Result Codes:Web Services
    |[[Returned Result Codes:APIs#GeoCoder Object|GeoCoder Object]] |[[#Reverse GeoCoder Web Service|Reverse GeoCoder Web Service]]
    20 KB (2,887 words) - 17:38, 29 September 2017
  • Result Code Examples
    |[[#GeoCoder|GeoCoder]] ...................... ==GeoCoder==
    9 KB (1,162 words) - 23:30, 7 September 2023
  • Address Object:Expired Advisory
    ...rmation than provided in the Address Object, they are only returned in the GeoCoder Object.
    3 KB (405 words) - 01:20, 21 February 2023
  • Address Verifier:Build History
    **GeoCoder
    3 KB (436 words) - 17:04, 12 December 2018
  • Contact Zone:Global Verify:Output Address
    :The Address Key can be used by other Melissa Data services, such as Geocoder or Delivery Indicator.
    4 KB (567 words) - 00:13, 5 January 2017
  • Unison:US Address Verification
    ;GeoCoder Result Codes ;GeoCoder Place Name
    14 KB (2,132 words) - 17:58, 15 March 2024
  • Returned Result Codes:Enterprise Solutions
    |[[Returned Result Codes:APIs#GeoCoder Object|GeoCoder Object]] |[[Returned Result Codes:Web Services#Reverse GeoCoder Web Service|Reverse GeoCoder Web Service]]
    39 KB (5,907 words) - 22:40, 3 June 2019
  • Pentaho:Global Verify:Address
    :The Address Key can be used by other Melissa Data services, such as Geocoder or Delivery Indicator.
    7 KB (1,034 words) - 21:16, 9 June 2015
  • Pentaho/Contact Zone:Global Verify:Address
    :The Address Key can be used by other Melissa Data services, such as Geocoder or Delivery Indicator.
    7 KB (1,041 words) - 17:53, 11 January 2017

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

Retrieved from "http://wiki.melissadata.com/index.php?title=Special:Search"