Groups: Member
Posts: 1
|
I need someone from MelissaData to help in correcting several errors in the data set answers we get from address verification and geocoding using MelissaData. Helpdesk tickets have gone unanswered and our customers are asking each to switch to another service.
The problem occurs when we try and verify our data sets via Zip Code, or Lat/Lon and MelissaData is either returning the wrong city name or a misspelled city name. For example, Clinton Township, MA is returned to us as "Clinton Twp"--which is wrong and causes data queries to fail for our client sites.
Another example is when a particular address isn't found MelissaData returns a location in center zip code--but then the city name isn't reset properly.
We have been trying for weeks to get someone to talk too about these issues. My business can't afford for my data verification service to incorrectly verify data--it's kind of the whole point isn't it?
I need help. Please. Tell me another method of how we can get these errors addressed besides "Helpdesk" tickets that go unanswered or uncorrected. Call me. Email me. Snail mail, I don't care, but please, somebody help.
|
Groups: Administration
Posts: 20
|
Hi Mike,
I am the DQT Assistant manager (not Helpdesk) and I will help answer your questions. However, I need some more information.
1) What is the date of the data you are using. You can find that out several ways: - Tell me the month of the last update you installed - Tell me the modified dates of your data files - Tell me what GetDatabaseExpirationDate() returns for you.
2) Give me the zip code for the example you provided (Clinton Twp)
3) Give me an example input/output for this case that you describe (Another example is when a particular address isn't found MelissaData returns a location in center zip code--but then the city name isn't reset properly.)
Thank you.
|