We're upgrading our driving directions page from Bing Maps V7 to V8. So far so good, except for the absence of the RouteResponseCode enumeration.
Here's the V8 documentation page:
https://msdn.microsoft.com/library/mt750371.aspx
The page does not show a method of gaining access to this enumeration. In V7 this attribute was made available through Microsoft.Maps.Directions.RouteResponseCode. Now it appears removed.
Can I still access this enumeration, or do I need to hardcode the values now?
Strange. It was documented but doesn't seem to be in the SDK. Will have the team look into this to see if it was removed, or if it simply wasn't exposed publicly.
Related
I'm getting 404's from my own site (regardless of browser) as well as the Bing Maps V8 Interactive SDK. On my site this leads to Uncaught TypeError: Microsoft.Maps.Location is not a constructor errors. I'm guessing this means Bing Maps is having problems and not my code because of the missing .js file? Anything I can do to mitigate this?
Looks like Microsoft fixed their issue. It is working now.
I have also reported this to Microsoft. All my screens that use the web controls have stopped working and report 404 problems on .js routines
I'm able to reproduce this. Looks like Bing Maps is down. We can report this to the Bing Maps Enterprise support team here: https://www.microsoft.com/en-us/maps/support (Bing Maps shows up under the developer tools category in the first form). I'll also report this from my end.
Update
The support team is now reporting that this issue has been resolved. I can confirm things are working on my end. I believe you can request details about the outage from the support team and they will send out an incident report once one is created (likely in the next couple of days).
Is it possible to retrieve an existing classic style, even though they are no longer supported?
I have a URL that used to point at our style, but now I get json that looks like this:
{
message: "Classic styles are no longer supported; see https://blog.mapbox.com/deprecating-studio-classic-styles-d8892ac38cb4 for more information"
}
My company was sidelined by the depreciation of classic styles. It required some emergency hotfixes to get things up and running again, but our maps no longer have our signature look. We had a professional design our classic style, and now we want to convert it to MapBox Studio.
Does our previous style still exist? If it does, how can we retrieve it?
Thank you!
They wrote on a blog entry:
We made the decision to stop active maintenance of the core technology that powers these maps (CartoCSS) back in 2016. However, we continued to support Classic Styles through our Legacy Maps and Legacy Static Images APIs.
Here is the documentation about the Legacy Maps: https://docs.mapbox.com/api/legacy/maps/
In my case, it was faster to change to the new API. The old access token was still working. Here is how to implement it: https://docs.mapbox.com/help/troubleshooting/migrate-legacy-static-tiles-api/
It appears that Bird's Eye View is no longer available in V8. Can anyone confirm that this is actually the case or if there is any way of still using Bird's Eye View in the new version?
Microsoft's documentation about this is very poor, so I just pieced the information together from various sources.
For example:
1.
In their MapTypeId Enumeration the 'birdseye' option doesn't exist anymore.
This used to exist in V7.
2.
Bing's own snippet generator for embeded maps has an option to add the Bird's Eye View, but when checked it only adds a "View bird's eye" link under the map which redirects you to www.bing.com with the Bird's Eye View selected.
3.
When embedding a V7 map, the Bird's Eye option is available in the navigation bar:
In V8 the option doesn't exist:
UPDATE: I have received an email reply from Microsoft stating that Bird's Eye View isn't yet available in V8, but will be at a later point. Here is their reply:
"Birdseye imagery is currently not available in Bing Maps V8. The
migration guide doesn’t mention Birdseye imagery but it does state
that anything that isn’t mentioned is planned to be in the V8 control.
Currently the Birdseye imagery in Bing Maps V7 is very old, some
images are 10+ years old. This is one of the highest points of
customer DSAT that we have. We have collected a lot of new imagery,
but it still needs to be processed so that it can be exposed to the V8
map control.
Additionally we are creating a new user experience around
Birdseye as the current experience isn’t as fluid as it can be and is
an issue for many. Processing the imagery takes several months to do.
Developing the new user experience will also take a few months. We are
currently planning to have the new Birdseye experience in V8 by the
Microsoft Build conference which is near the end of March 2017 (8
months from now)."
It's not available because Microsoft are renewing the images for it.
It will be available again in the future.
See this thread
Even though birdseye is listed now in the enumeration doc for v8, this morning (Monday) I discovered that, even thought it seemed to be working Friday, though now that I think about it seems like it was more aerial than bird's eye, my map was rendering in some sort of messed up default view that didn't obey viewbox settings. I changed the view type to aerial and it works again. The really odd thing is that IE and Edge were messed up, but Chrome was not.
I am trying to show routes using BING maps REST service , but the map image with routes does not show up sometimes (shows blank map) , but after refreshing the html page it shows up.
I have contructed below URL
http://dev.virtualearth.net/REST/v1/Imagery/Map/Road/Routes?wp.0=300%20Albemarle%20Road,,,Charleston,29407-7593&wp.1=1000%20Fort%20Johnson%20Road,,,Charleston,29412-8898&wp.2=1525%20Avenue%20B%20South,,,North%20Charleston,29405-2328&mapVersion=v1&mapSize=800,600&zoomLevel=10&key="my bing map key"
I've taken a look at this. I was able to reproduce the error with your URL. I tried modifying it by removing the extra comma's and the removing the last part of the zip codes (zip+4) since those are not supported. After doing that I was still able to reproduce this issue, but much less frequently. I suspect that there may be a couple servers that are out of sync on Bing Maps side, thus the inconsistency. I'll notify the engineering team so they can look into this.
We got a customer looking after an event called Floriade placed in the city of venlo in the Netherlands. This point of interest is sometimes shown on the autocompletion under Floriade 2012. I say sometimes shown as we used to see it, then it disappeared, now it is back again.
1-How can I be sure that the autocompletion (through Google Places API) is showing this point of interest ?
2- What is enabling a point to be in this autocompletion or not ?
If a place has a Google Places page, e.g http://maps.google.com.au/maps/place?cid=14788366310032789085 it is guaranteed to be returned by a Places Autocomplete API.
You may have experienced a bug in the API. If it occurs again please report it on the issue tracker: http://code.google.com/p/gmaps-api-issues/issues/entry?template=Places%20API%20-%20Bug
Another way to guarantee that your application will show a place is to perform a 'Place Report Request' using the Google Places API with your API Key. This will instantly add a place and make it available to your API Key, then if the place is approved by Google if will be available to anyone.
Cheers
Chris