Webplanner: zoom level after search
Solved
Hi,
Following a recent change, when searching for a location using lat/lng the map centers to that location but sets the zoom level to 11 which is not very pleasant.
Searching by name sets zoom to 18.
Originally, before V2 I think, both got set to zoom 17. There was a change which caused them both to be set to 18. Now we have 18 and 11. Why does it keep changing?
Please would you fix the lat/lng search so it sets zoom the same as search by name.
There might be a case for not changing the zoom level at all - i.e. position the map to the point and leave the zoom level unchanged from that which the user has already set. If not, then 17 or 18 would be fine IMO but 11 is not.
The same problem 
confirmed. I'd vote for NOT changing the current zoom level at all.
confirmed. I'd vote for NOT changing the current zoom level at all.
Users may not even know the search field accepts a coordinate. This inline field text says "search address or place". Maybe a tooltip could fully describe the search options.
Users may not even know the search field accepts a coordinate. This inline field text says "search address or place". Maybe a tooltip could fully describe the search options.
Hi all,
thanks for the feedback, the devs have been notified.
Hi all,
thanks for the feedback, the devs have been notified.
All "land features" or "map features" have envelope defining their "span" or "bounds". So a city has larger bounds than a restaurant. These bounds are either exact or estimated, but they are no guess work most of the times. Client applications should follow that "bounds recommendation" when moving map to the result. There are no zoom levels specified. (No altitude for a drone with hanging camera. Just a recommendation for a bounding box to fit in). However when it comes to coordinates there is no guidance and recently I just estimated some bounds. That was necessary for unification Android/web/iOS. Now there is much smaller bounds for coordinates (like a point of interest, real point like a guidepost).
All "land features" or "map features" have envelope defining their "span" or "bounds". So a city has larger bounds than a restaurant. These bounds are either exact or estimated, but they are no guess work most of the times. Client applications should follow that "bounds recommendation" when moving map to the result. There are no zoom levels specified. (No altitude for a drone with hanging camera. Just a recommendation for a bounding box to fit in). However when it comes to coordinates there is no guidance and recently I just estimated some bounds. That was necessary for unification Android/web/iOS. Now there is much smaller bounds for coordinates (like a point of interest, real point like a guidepost).
Hi, thanks for the explanation and prompt attention. I guess I always search for points with a small bounds so always saw 17 (then 18).
Anyway, search by lat/lng now gives zoom 15 for me, and that is OK - much better than 11.
Hi, thanks for the explanation and prompt attention. I guess I always search for points with a small bounds so always saw 17 (then 18).
Anyway, search by lat/lng now gives zoom 15 for me, and that is OK - much better than 11.
Replies have been locked on this page!