OpenAndroMaps will switch to Multilanguage “V4” Maps mid of 2019.
Single Language “V3” Maps will be updated till July 2019 – so, dear users AND APP-Developers, please switch to V4 maps.
As a service for the big community of LOCUS users OpenAndroMaps now offers a DirectInstallButton for V4 Maps too on the download-pages.
The ony real disadvantage over V3 maps, as I know, is that Locus does not support automatic map switching with V4 maps.
Finally its snowing, not that much but more like a real winter than the 20°C we hat here in Austria in October.
So outdoor cycling and season is more or less over and time to look back and report the improvements for OAM Maps in 2018.
Most innovations and improvements are the result of suggestions from the forum.
So I recommend to take a look at the forum area from time to time.
Click here for the forum topic “Elevate News” where @Tobias constantly reports the numerous improvements of the Elevate / Elements rendertheme.
This works without registration. If you want to register please make sure to use a “reputable” email address – the spam filter is strict cause otherwise I have to delete not 5 but 500 fake / spam registrations every day.
The problem was that rendering of OSM Objects like roads, forrests, lakes, rivers,.. was completely skipped when these objects exeeded the mapborders.
@Steffen, a “C” programmer who supported the OAM Team with his knowledge for several times, compiled a special Version of OSMCONVERT that now _really_ works on Windows7/64 and preserves these objects. So now lakes are blue even when these exeed the map-coverage. Most important is this for the Great Lakes in Canada an Africa.
And – now its possible to simplify map borders with a better coverage cause map borders now can cut through lakes without loosing details.
For most of the 280 maps the coverage / mapborders have been simplfied.
This looks much better, the problems for rendering objects at the borders are reduced – lots of work but for 90% done now.
@Michael has finished a monster-project. He worked through all “places” in the OSM database and assigned kategories to places depending on the population of these places. This means assignement of places to zoom-levels now is much more accurate than before – this a huge improvement.
Second @Michael has worked through all “peaks” and cleared all foulty ele-tags like elevations set in “feet” cleared to “meter”, eliminated wired chars… – so now the algorithms from @MaxBe work on a clean databbase resulting in accurate rendering of peaks and saddles.
Improved rendering of several more variants of cycle-lanes in conjunction with “oneway”
@Sonny has firther improves the integration of free LIDAR (Laser) elevation data.
For detail maps of Great Britain we spipped from Viwefinder3 elevation data to the improved NASA SRTMV3 1″ Dataset with 10m contourlines:
Like rendering of house_numbers assigned to Relations,
Map of Pyrenees now covers whole Northern Spain from Atlantic to Mediterranean Sea so hikers on the Jakonsweg need only one, small map for Northern Spain,
….
The OAM-Team wish you a pleasant a Winter!
For two years after the Nov 2016 edition of the world overview maps I have worked on the curation of additional content to be put on top of the variouis background maps for the different zoom levels. Why ? I am a curious traveler to places where “always on” is (still) a lie. In the case of interest in something about a country or region or province, too much jumping back and forth from offline Wikipedia (like Aard2 or Kiwix) is annoyance. So, I put a number of information directly into the world overview maps:
– The capitals of countries, states and provinces of many countries are shown in 3 different colours, in English and local language (if significantly different).
– Islands and archipelagos, in particular the remote ones, are hard to spot on maps – here is remedy by highlighting them, from zoom level 3 up.
– Triggered by an OAM forum discussion about visibility of peaks, and with the help of Max’ algorithm to select, 100s of important peaks are highlighted.
– Also the major ocean deeps are shown.
Some insights into the process: the current MOBAC rendering tool with the Mapsforge library embedded does not provide a proper visibility of labels like settlement names. Even big cities may not show up at all. Using Maperitive in addition allows to take control of the label renditions in a predictable way. Unfortunately, Maperitive has a bug omitting the leftmost or rightmost of a label for a fraction of a label. Playing with scope and zoom around the affected place the missing parts can be added in a manual patch step (at least for the most visible cases like highlighted capitals – I hope I caught those all). Once you go this route, this opens an additional option: make larger settlements dominate the label display in a much more accurate way than the simple city-town-village-… attributes in OSM would allow. Hence now also the size of the settlement labels increases by population (in 11 catagories), if provided in the OSM data set (hopefully correctly!), otherwise a minimum assumption is made for the OSM categories city, town and village. As Maperitive is an OSM tool, this is achieved by amending the original data with categories of population sizes. Those “PopCat” tags are now also embedded in Christian’s OAM maps. They can be used by themes to select (restrict) the settlement names to be displayed. The adaption of the latest Elevate theme is on my list for 2018, but maybe somebody else is faster 
Bottom line: the intent behind all that is to have essential geo information at a finger tip, fully OFFLINE. A sort of companion for Offline Wikipedia. Enjoy!
Michael Bechtold
Elevate updates don’t bring huge changes anymore, but smaller ones, that, when added up, make a big difference altogether. Therefore once again the hint here that only with current map styles and maps all improvements get visible. Recently those were important changes in Elevate, and some smaller ones as well. Look at the legend for further information.
The newest downloads and the changelog can be found as always on the Elevate page, and for e-mail notifications for further updates of Elevate just subscribe to this thread in the forum.
Best regards,
Tobias
Dear members of the OpenAndroMaps community,
another year is drawing to a close, already the sixth year for OAM.
Time to say “thanks” to all the people contibuting new, better Data for OAM like
@Sonny constantly integrates new LIDAR (LaserScan) elevation data, wherever available for free, into the existing viewfinder/nasa dataset – resulting in the most reliable contourlines available on free maps.
@MaxBe who found a way to sort mountain peaks by “importance” so we could render the important ones in lower zoom-levels – an improvement that is included in the december map update.
I also like to thank all users who made the effort to register in our forum and give hints, suggestions and error reports. This is very important for us as we can be routine-blinded or just lack the time to test every map update for errors. Although our standard is and can only be absolutely professional, we do all this in our rare spare time and with only a tiny budget.
Our goal is to sustain and enhance this project and ask you kindly to further support us.
The OAM team wishes you all a merry christmas!
Yes, I know..
Kommunikation from my side to the OpenAndroMaps community could – and should – be better (by far) 
A lot of improvements happened during 2017 – OAM is’nt on idle at all, we are working hard to improve, add new Features, include external Data, aso..
Maps:
Website:
However the best of all is about to come.
December update will bring a real great improvement for hikers and alpinists.
Best regards
Team of OAM
The OpenAndroMaps website will switch to secure transfer protocoll according HTTPS / SSL this week.
This step is required by the Google guidlines to provide the HTTPS / SSL for all sites that require user inputs such as comments, user accounts, or forums.
This is an important step ahead in data security, which has been supported on the side of OpenAndroMaps since long by flanking, server-side actions like Intruderdedection, protection against BruteForce attacks and integration into various blacklists.
UPDATE 2017-08-22 18:00h MEZ: Done, the Website is running on fine on SSL, no mixed contend any more – we have a green lock-symbol on all pages. I have tested all functions and have’nt found any bug. However, if you experience problems please post here as comment or in the forum.
Best regards, Christian
With the update of the maps next week there are critical changes in the structure of the maps. The difficulties of the mountain paths are rendererd slightly different (the sac_scale).
The renderthemes are now prepared for this change, please install these updated themes.
Elevate/Elements Theme install
Hi,
Until today sac_scale was preprocessed to carry only 4 levels:
T1,T2,T3 and T4, while T4 included T5+T6 too.
Now sac_scale will be extended for all levels = T1 – T6 (August update), so seperate levels for T1,T2,T3,T4,T5,T6
This includes some minor changes:
DAV_SCALE “black” is transformed to SAC_SCALE=T5 (was T4 so far)
If a way includes any “via_ferrata” tag/value SAC_SCALE is set to “T6” (was T4 so far)
_and_
in a second step (October) raw_sac_scale will be no longer supported = removed from Tag-Mapping!
SO: sac_scale T4 will NO LONGER INCLUDE T5+T6 > T5 AND T6 are seperate values from August update on.
THIS MEANS: You have to extend existing rules for sac_scale=T4 to “sac_scale”=”T4|T5|T6”
AND existing rules for “raw_sac_scale” have to be extended to “sac_scale|raw_sac_scale”
Please prepare your themes.
This have to be made in a 2-step process:
Extend your rules so that sac_scale prozesses T5 and T6 too.
So if you have a rule :
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<rule e="way" k="sac_scale" v="T1"> <line stroke="#FFAA00" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> <rule e="way" k="sac_scale" v="T2"> <line stroke="#3052FF" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> <rule e="way" k="sac_scale" v="T3"> <line stroke="#FF0000" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> <rule e="way" k="sac_scale" v="T4"> <line stroke="#000000" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> |
extend it to:
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<rule e="way" k="sac_scale" v="T1"> <line stroke="#FFAA00" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> <rule e="way" k="sac_scale" v="T2"> <line stroke="#3052FF" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> <rule e="way" k="sac_scale" v="T3"> <line stroke="#FF0000" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> <rule e="way" k="sac_scale" v="T4|T5|T6"> <line stroke="#000000" stroke-width="0.65" stroke-dasharray="17,1" stroke-linecap="butt" /> </rule> |
from October on you can create additional, seperate rules for T5/T6
If you use a raw_sac_scale, extend the rules:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
<rule e="way" k="raw_sac_scale|sac_scale" v="RT1|T1"> <some settings..../> </rule> <rule e="way" k="raw_sac_scale|sac_scale" v="RT2|T2"> <some settings..../> </rule> <rule e="way" k="raw_sac_scale|sac_scale" v="RT3|T3"> <some settings..../> </rule> <rule e="way" k="raw_sac_scale|sac_scale" v="RT4|T4"> <some settings..../> </rule> <rule e="way" k="raw_sac_scale|sac_scale" v="RT5|T5"> <some settings..../> </rule> <rule e="way" k="raw_sac_scale|sac_scale" v="RT6|T6"> <some settings..../> </rule> |
So everyone making themes for OpenAndroMaps have to ensure that everything renders fine when expanding the sac_scale and finally deleting raw_sac_scale. I know its annoying – however there is no other way to ensure that the maps render fine in future.
Additional TAGS that will be removed from tag-mapping by end of October:
I’m terribly sorry about this, however recently I discovered that there is a limit of max. 15 Tags in the MapsforgeWriter per OSM_Object so I have to reduce the amount of tags – otherwise we end up in white tiles rendering the maps at is was the case with parts of upper Austria last weeks.
See discussion of this issue at MapsforgeDevGroup:
https://groups.google.com/forum/?fromgroups=#!topic/mapsforge-dev/kQKfCMGk2Ec
Best regards
Christian
Multilingual maps- what does this mean?
As an example: The OpenStreetMap database provides NAMES for most objects like Citys, Roads, Churches, Rivers, aso.. in different languages. So for the map of Israel usually in hebrew, arabian, english, maybe in german. For maps of Russia usually in russian and english.
Up to now only one language per maps was possible to include and display on our smartphones.
So providing two languages for one maps for OAM meant making – and for you, downloading two different maps.
With the new, multilingual maps it is possible to include different languages while making the map and switching map-language in an APP – if an APP is compatible with these maps AND provides a language switcher. This is the case for ORUXMAPS and LOCUS for Android and Cruiser for Android + PC.
Here you see a small screencast of ORUXMAPS switching between russian and englich using the map of Moscow:
So we decided to provide the multilingual maps on OpenAndroMaps.
The effort for providing two different versions of the maps (old single and new multilingual = 250 each) is crazy.
However, we are aware that a lot of APPs still only support the old “V3” single-language maps – and keeping our users in mind we will support both versions for while, as far and long as our resources will allow this.
For now we provide the new multilingual “V4” maps for download to PC AND for direct install to ORUXMAPS. The download/install buttons for these maps are RED, the included languages are shown for each map as abbreviations in square brackets. The new map files itself are identified by a “_ML” suffix.
So, eg., while the name of old map is “Germany.map” the name of the multilingual map is “Germany_ML.map”
For more information klick here
The old maps that we provided in different languages will be available in future only in one language (usually native lang. or english) – this is the case for all russian mapps, several maps for Asia aso. PLUS the multilingual version.
The POI files for the multilingual maps are included in the zip-files of the maps. With the next update of ORUXMAPS these POI-files will be installed in the right place on your Smartphone if chose direct install.
Next posting will deal with the complete redesign of the categorie-structure of the OpenAndroMaps POI-files.
Best regards
Tobias & Christian
