Search results

• Tutorial:Contact Verify Component Field Mappings
  ...columns are mapped, this column and ZIP/Postal Code must be mapped for the GeoCoder output column to be populated with nine-digit ZIP + 4® accuracy. There are four options that control how the GeoCoder feature of the CVC acquires the data it needs for geocoding. The first, '''
  43 KB (6,888 words) - 19:26, 21 August 2012
• MatchUp Object:Matchcode Components
  ...rdinates(Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  7 KB (1,041 words) - 20:27, 1 June 2018
• SSIS:Personator World:Address
  :The AddressKey can be used by other Melissa services, such as Geocoder or RBDI.
  12 KB (1,750 words) - 00:49, 17 November 2017
• MatchUp Object:Matchcodes
  ...dinates (Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  8 KB (1,184 words) - 22:19, 5 August 2015
• Contact Zone:Build History
  *Address, Phone, Name, and email objects updated to Build 2381. Geocoder and IPlocator are updated to build 2362.
  8 KB (1,085 words) - 21:14, 27 October 2017
• Personator Consumer:Build History
  ...Re-work of Geocoding Engine to replace direct database access to using the GeoCoder API.
  9 KB (1,304 words) - 01:13, 7 March 2023
• MAILERS+4:Build History
  *GeoCoder Object build updated to 17333. ::*'''Added Quick List Items''': GeoCoder, ELOT, CBSA and NameParse.
  36 KB (4,649 words) - 00:56, 21 January 2023
• FAQ:SSIS:Data Quality Components
  ...e other Melissa Data Objects i.e for Email Object replace mdEmail.dll, for GeoCoder mdGeo.dll, etc.
  10 KB (1,551 words) - 22:27, 20 August 2020
• Listware for Excel:Build History
  *Geocoder result codes are now suppressed if not lat/long output.
  10 KB (1,371 words) - 00:34, 1 June 2023
• Unison:Global Address Verification
  ...field. The AddressKey can be used by other Melissa Data services, such as Geocoder or RBDI.
  19 KB (2,990 words) - 01:42, 19 November 2022
• Pentaho:MatchUp:Component Properties
  ...inates (Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  13 KB (2,056 words) - 21:16, 28 October 2016
• Contact Zone:MatchUp:Component Properties
  ...inates (Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  13 KB (2,041 words) - 00:31, 5 January 2017
• Pentaho/Contact Zone:MatchUp:Component Properties
  ...inates (Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  13 KB (2,062 words) - 20:57, 11 January 2017
• Result Code Details
  |Image=[[Image:ICON_API_GeoCoderObject.png|84px|GeoCoder Object|link=#GeoCoder Object]] |Link=[[#GeoCoder Object|GeoCoder<br>Object]]
  128 KB (19,482 words) - 23:27, 19 February 2024
• SSIS:Global Verify:Address
  :The Address Key can be used by other Melissa Data services, such as Geocoder or Delivery Indicator.
  17 KB (2,727 words) - 01:45, 29 November 2022
• Tutorial:Matchcode Editor
  ...inates (Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  16 KB (2,506 words) - 21:42, 14 August 2012
• Contact Zone:Contact Verify:Address
  ...e fields are mapped, this field and ZIP/Postal Code must be mapped for the GeoCoder output fields to be populated with nine-digit ZIP + 4 accuracy.
  22 KB (3,623 words) - 01:07, 3 January 2017
• Pentaho:Contact Verify:Address
  ...e fields are mapped, this field and ZIP/Postal Code must be mapped for the GeoCoder output fields to be populated with nine-digit ZIP + 4 accuracy.
  22 KB (3,622 words) - 00:06, 28 May 2015
• SSIS:Contact Verify:Address
  ...e fields are mapped, this field and ZIP/Postal Code must be mapped for the GeoCoder output fields to be populated with nine-digit ZIP + 4 accuracy.
  23 KB (3,626 words) - 00:06, 10 November 2015
• Pentaho/Contact Zone:Contact Verify:Address
  ...e fields are mapped, this field and ZIP/Postal Code must be mapped for the GeoCoder output fields to be populated with nine-digit ZIP + 4 accuracy.
  23 KB (3,629 words) - 17:31, 11 January 2017
• SSIS:MatchUp:Component Properties
  ...inates (Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distanc
  17 KB (2,657 words) - 22:09, 10 February 2017
• API:FAQ
  ...ing the download and update procedure for Address, Name, Phone, Email, and Geocoder objects are now located in the extras directory.
  16 KB (2,678 words) - 01:25, 16 February 2022
• Personator Consumer:Request
  :::The GeoCoder Object uses WGS 84 standard, an Earth-centered, Earth-fixed terrestrial ref
  36 KB (4,869 words) - 19:32, 4 December 2023
• Personator Identity:Response
  :The AddressKey can be used by other Melissa Data services, such as Geocoder or RBDI.
  46 KB (6,225 words) - 23:38, 26 February 2024
• Global Address Verification:Response
  :The AddressKey can be used by other Melissa Data services, such as Geocoder or RBDI.
  44 KB (5,742 words) - 01:33, 17 November 2023
• Result Codes
  |Geocoder is in Demo mode and a zip code outside the Demo range was detected. |Geocoder data files are expired. Please update with the latest data files.
  90 KB (14,655 words) - 23:27, 19 February 2024
• Build History:Address Object
  ...ing the download and update procedure for Address, Name, Phone, Email, and Geocoder objects are now located in the extras directory. Currently, they are only a
  43 KB (6,487 words) - 01:25, 7 March 2023

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