Bing basemap zooms too far

[Anonymous User]

Hello,

I am using the Bing basemaps in our custom AppBuilder applications, and I have noticed that when you zoom in too far that the map disappears.  The problem that I am seeing is that it occurs in some applications, but not others, and I'm not sure how to prevent it from happening. 

The application that the map DOES NOT disappear in will simply only allow you to zoom in to the point where if you were to zoom in one more level it would disappear.  The applications that the map DOES disappear in, you can zoom in way further than the map will display, but the map just disappears and you can't see anything at all.

Is this a setting or a bug?  If there is a workaround, please let me know.

[Anonymous User]

I am using the out of the box AppBuilder with all of the predefined customization options. 

The map simply disappears and has a plain white background.

[AdrianWelsh]

Could you add an Esri basemap as your actual basemap and then load the Bing map on top of it as just a regular layer? Then when the Bing fades out, then Esri will become visible? This may slow performance but it may be a solution...

[Anonymous User]

It wouldn't really be helpful...see the images below:

This first image shows the closest zoom allowed by Bing.  You can clearly see the poles that we want to look at.

Now here is Esri's basemap...you can barely see anything, with the exception of the traffic signal on the right side.

This particular example isn't even a bad one either.  Most of the time you can't make out the poles at all...  Bing does a really good job at reducing shadowing as much as possible, and there is little to no building skew that occurs due to camera angle. 

[AdrianWelsh]

So, the issue is that Bing is not allowing the last level of zoom, is that right? If so, then it's a Bing issue and would need to be resolved through Bing, I would think.

[Anonymous User]

In the example image I showed above, if I zoom in one more level, it goes white.  The thing that is weird is that this result only happens in some cases, and I'm not really sure what factor is different to make it happen. 

Basically I have 2 applications that reference the exact same data layers, the only difference being the queries that are applied.  One application zooms to the level shown in the image and then will not go further no matter how many times you click the zoom button or scroll wheel, which is the desired result.  In the other application, though, the map lets you zoom further, resulting in the basemap disappearing and giving a white background.

I could be wrong, but given that the desired results are seen in one case, I don't believe it is a Bing problem.

The results are seen whether you're within the web application or in the map viewer, so I don't think it's an app problem either. 

[AdrianWelsh]

Thanks for clarifying. I'm guessing the desired result is for the zoom to halt at the lowest Bing level and not zoom further (like you're seeing where it fades out). Is that right?

From what I have seen before, this is a result of the underlying basemap properties. I could be wrong, but it seems like Bing is allowing it to zoom further in that particular location and not others. But, I don't have a way to test this.

In any case, if you are wanting to stop people from zooming too far, there may be a solution here:

ArcGIS Online - Need to prevent users from zooming in too close or out too far 

It seems some found it helpful and others did not.

There also may be help here too:

https://community.esri.com/thread/180303 

But, again, I could be interpreting this all wrong as well!

[Anonymous User]

Yes, you are correct in your assumption.  Those links look pretty useful.  I'll read through the comments and see what I can find. 

I'll have to test out your theory on basemap properties as well.  I'll open both example applications and zoom in the exact same location to see if it is location based.  I don't believe this is the case, but I can't say for sure until I test it out. 

Thanks!