I’m not sure if I’m in the right place.
Just a quick note: I’m a big fan of OsmAnd and have been using the app for 10 years now – in the car and with my caravan all over Europe and on my bike – and I’ve also submitted a few POIs. So I just have a few creative questions and suggestions, and I don’t want to offer any unfounded criticism.
-
I’ve worked in IT for a long time and there I worked among other things in data organisation.
-
Now I have some questions to help me understand the strategy behind the Osmand database, and I also have a suggestion.
The maps of the European countries are being split up more and more, and I don’t understand the point of it. Splitting the maps triggers a new INIT-run every time a single map is loaded.
France 61 maps / total 9,8 gigabyte
Germany 33 maps / total11 gb
Italy 20 maps / total 5 gb
Spain 19 maps / total 4 gb
Austria 8 maps / total 1,8 gb
I’ve understood the previous breakdown by federal states / politcal regions - so for example Germany had 16 maps. Now there are 5 maps of the administrative districts for North Rhine-Westphalia alone ! In the past it was 1 map. The same with Bawaria (7 maps) and Baden-Württemberg (4 maps).
The same situation is the fragmentation of maps in France, Spain, Italy …
Even more questionable is the fragmentation among small countries such as Belgium, the Netherlands, Austria, Switzerland and the Czech Republic.
What’s the point of it all?
-
To navigate longer routes (e.g. from Warsaw to Nice or from Berlin to Bordeaux or from Cologne to Rome), I need, in any case the maps of all the countries that might lie along the way.
-
To navigate only in France or Germany, for example, I still need the full map of the country and perhaps also the countries ‘next door’ for „alternate routes“.
-
To ensure correct routing, all the necessary maps must be up to date.
-
Storage space on a modern smartphone (perhaps with an SD card) shouldn’t be a problem … and downloading just “a few” OsmAnd maps doesn’t make much sense
So what’s the point of splitting the cards into so many small units?
And … there’s one thing that could be reconsidered and perhaps changed.:
-
The whole database is initialised after each single map is downloaded.
-
If I update only Germany and France the db-init runs ninety-four times.
-
At present, the process of initialising the database several times takes considerably longer overall than downloading the maps (updates) with WiFi (router 5G/1200 mbps - fibre-optic cable from provider to the building distribution box).
- (Smartfone SAMSUNG A25 / Android 16 / 6 GB RAM / OSMAND data on fast micro-SD-Card 128 GB)
Can’t be done the db-init just once, after all the necessary maps have been downloaded?

