Or the behavier could be determined whether we are in sandbox mode or not?This may be a good idea - let it depend on the precise height in the sandbox mode, and use the default behavior outside. But I remember someone wanted also a complete manual control, although that can be problematic - once you rise up and go fast, it could generate gazillion incoherent requests to Google Maps.
Actually the default behavior is to respond to a filtered height above the ground, at least that way it worked
Location: | Altitude: | Ruler displayed on Google Maps: |
North Germany, near North Sea: | 13m | 200m/1000ft |
Somewhere in Spain: | 630m | 1km/1mi |
Somewhere in Tibet: | 4900m | 10km/5mi |
...once you rise up and go fast, it could generate gazillion incoherent requests to Google Maps.In order to prevent this a delay in the requests could be established.
If your statement above would apply, then at all visited location the Google Maps ruler should show about "200m/1000ft"?Note I said filtered, using a coarse LOD level that changes very slowly, and does not correspond to the precise height.
There already is, but the point is that requesting high detail data when you are high above is pointless, that's why there's the adaptive mode, after all. But maybe it could be made better....once you rise up and go fast, it could generate gazillion incoherent requests to Google Maps.In order to prevent this a delay in the requests could be established.