A traveller in Warsaw types Zlotaa 59. They mean Złota 59, and as of this release the online search finds it.
GLSearch now corrects common typos in online map search: a missing letter, an extra one, or a wrong one in the name of an address, a business or a place. The user picks the destination instead of retyping it.
The map is open on Warsaw, and someone types Eiffel Tower Paris France. GLMap search starts from the map center:
it opens the detailed maps around it and puts the nearest results first. The Eiffel Tower is 1,370 km away, in a
map file that such a search never opens.
This is what the engine does with that query now, and with the other queries from this post. Each word is coloured by the role the engine gives it:
Words with an orange border are places the engine looks up before the search itself, and a dashed border marks a place name that belongs to the name of something else. The dot marked “map center” is where the map is open, and the circle is the area where the detailed maps are searched.
GLMap 2.0 is our largest SDK update in years. It adds 3D terrain, one search flow for online and offline data, new pedestrian routing profiles, Vulkan rendering on Android, and much smaller reference applications for Swift and Kotlin.
Most of the new features are a property or a request type, and they work with downloaded data and the same way on iOS and Android.