none
includeNeighborhood no longer returning results in virtual earth API RRS feed

  • Question

  • I have a script to update the neighborhood settings based on latitude/longitude using dev.virtualearth api. Shortly after the script was finished, tested and working, virtual earth api stopped responding with neighborhood information, regardless of includeNeighborhood=1 get parameter being passed in.

    Any ideas why this feature disappeared? Or when the feature will return?

    Here's the response I get:

    Request: http://dev.virtualearth.net/REST/v1/Locations/47.542758000000000,-122.321692000000000?includeNeighborhood=1&o=xml&key=myAPIKey

    <Response xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/search/local/ws/rest/v1">
    <Copyright>
    Copyright © 2012 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.
    </Copyright>
    <BrandLogoUri>
    http://dev.virtualearth.net/Branding/logo_powered_by.png
    </BrandLogoUri>
    <StatusCode>200</StatusCode>
    <StatusDescription>OK</StatusDescription>
    <AuthenticationResultCode>ValidCredentials</AuthenticationResultCode>
    <TraceId>
    a94bf3f898e34679902de58ecf92a312|SN1M001067|02.00.105.1600|SN1MSNVM002301, SN1MSNVM001334
    </TraceId>
    <ResourceSets>
    <ResourceSet>
    <EstimatedTotal>1</EstimatedTotal>
    <Resources>
    <Location>
    <Name>6667 Carleton Ave S, Seattle, WA 98108</Name>
    <Point>
    <Latitude>47.542736157774925</Latitude>
    <Longitude>-122.32162646949291</Longitude>
    </Point>
    <BoundingBox>
    <SouthLatitude>47.538873440204249</SouthLatitude>
    <WestLongitude>-122.32925551360194</WestLongitude>
    <NorthLatitude>47.5465988753456</NorthLatitude>
    <EastLongitude>-122.31399742538389</EastLongitude>
    </BoundingBox>
    <EntityType>Address</EntityType>
    <Address>
    <AddressLine>6667 Carleton Ave S</AddressLine>
    <AdminDistrict>WA</AdminDistrict>
    <AdminDistrict2>King Co.</AdminDistrict2>
    <CountryRegion>United States</CountryRegion>
    <FormattedAddress>6667 Carleton Ave S, Seattle, WA 98108</FormattedAddress>
    <Locality>Seattle</Locality>
    <PostalCode>98108</PostalCode>
    </Address>
    <Confidence>Medium</Confidence>
    <MatchCode>Good</MatchCode>
    <GeocodePoint>
    <Latitude>47.542736157774925</Latitude>
    <Longitude>-122.32162646949291</Longitude>
    <CalculationMethod>Interpolation</CalculationMethod>
    <UsageType>Display</UsageType>
    <UsageType>Route</UsageType>
    </GeocodePoint>
    </Location>
    </Resources>
    </ResourceSet>
    </ResourceSets>
    </Response>



    Wednesday, March 28, 2012 10:10 PM

Answers

  • I have looked into this further. The issue is not that this functionality has stopped working, but that their is no neighbourhood infromation for the area you are looking in. This is not a regression in the service i.e. nothing broke. It just hasn't been fully supported everywhere yet. Our data team is looking into this.

    http://rbrundritt.wordpress.com

    Friday, April 13, 2012 11:19 AM

All replies

  • We have been able to verify this issue and will escalate this to the geocoding team.

    http://rbrundritt.wordpress.com

    Tuesday, April 3, 2012 10:54 AM
  • I have looked into this further. The issue is not that this functionality has stopped working, but that their is no neighbourhood infromation for the area you are looking in. This is not a regression in the service i.e. nothing broke. It just hasn't been fully supported everywhere yet. Our data team is looking into this.

    http://rbrundritt.wordpress.com

    Friday, April 13, 2012 11:19 AM
  • Any ETA on the fix?
    Tuesday, July 3, 2012 8:29 PM