This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 8%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Autosuggest results are bringing back census-designated places (CDPs). Since these are not actual cities, they are causing data validation issues in our data audits from our state department (South Carolina)
for example:
955 E Lee results in (see attachment) . Wade Hampton is not an actual city/town. It's a census designated place. (you can see such places by looking this CDP up via https://edits.nationalmap.gov/apps/gaz-domestic/public/search/names)
Can Autosuggest results exclude these localities that are not actual cities? or can a parameter be added to enable excluding them? Other CDPs we've encountered in our area: Berea, Five Forks, Gantt, Parker and Sans Souci, Wade Hampton and Welcome
example code:
$.ajax({
method: 'post',
dataType: 'jsonp',
jsonp: 'jsonp',
url: 'https://dev.virtualearth.net/REST/v1/Autosuggest',
data: {
key: "our key",
query: request,
includeEntityTypes: 'Address',
userLocation: "[our location]",
userMapView: [our map],
maxResults: 10,
userRegion: 'US',
countryFilter: 'US'
},
Hi @ETSDGCS Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here. We will check with the team on this issue and get back to you with more details. Please stay tuned to this thread for more information.
thanks, looking forward to what you discover.
Hi @ETSDGCS Just a quick update that the team is still investigating this issue internally. I would keep you updated as soon as we have more information on this. I understand that this situation may have caused some inconvenience, and I want to express my gratitude for your efforts and patience in handling it. Please stay tuned to this thread for more updates in the next few days.
Hi @ETSDGCS ,
The team is indeed looking at this issue but to set expectations, it can take more than a month for a data fix to be reflected in the AutoSuggest experience because it is a trained model. That means that the training set needs to be ingested and the experience retrained then deployed and that is why such fixes can take what might seem and unreasonable amount of time. I have validated that as of today the issue is still occurring.
Sincerely,
IoTGirl
@IoTGirl Thanks for the reply. It is appreciated. We understand and look forward to when the issue is resolved. Based on your response, it sounds like the issue was confirmed and is actually being addressed and that we can expect to see it fixed in the next couple of months possibly?
Hi @ETSDGCS Yes, your understanding is correct. The team could replicate the issue and are working on a fix. The fix could roll out in a month. We will update the thread to notify you once the fix is released. Thank you for your patience.
Hi @ETSDGCS
I am no longer able to repro using https://www.bing.com/api/maps/sdkrelease/mapcontrol/isdk/autosuggestui . Can you please validate that this is fixed for you as well?
Sincerely,
IoTGirl
Still showing Wade Hampton as a city, which it is not.
Ok I have sent them this sample. Can you confirm that the next one in the list is the expected result?
Thanks! I will update the issue report with this detail
Oh, but the duplicate issue, that is gone right?
There was never a "duplicate issue". The issue is that Autosuggest results are bringing back census-designated places (CDPs) as if they are cities, but they are not.
Nothing in this post mentions a duplicate issue. I think you are confused.
I see how the screenshot sort of shows duplicates, but this is not the issue I posted about. The census designated place issue the bigger issue here.
Sorry this took so long but the last of the Census designated places should be gone as well as the duplication issue along side it. We get data from a number of different feeds and this was coming from more than one source.
No, it's still not fixed. still showing through the API call and on bing maps website.