… which also means for the OAM team that the sports gear will be taken out and various projects planned for the winter will be tackled – be it with the bike, in the mountains or whatever.

The main thing is to get out into nature again!

You will probably meet me in June/July in Norway/Sweden/Finland, my beloved Scandinavia, on a white scooter. Unfortunately, I am no longer able to cycle for health reasons – anyway, never mind.
The Eurovelo NR1 leads through Norway along the most beautiful back roads along the coast, and thus also on the scooter, to the Nordkapp – of course also on this tour with the OpenAndroMaps and the BRouter.

The major summer update will therefore be rendered 2-3 weeks later, in mid/late July.

I am leaving on this holiday with a healthy conscience because…
The OAM project is on solid ground:

  • I have eliminated all programme fragments
  • many scripts have been rewritten from scratch and made clean
  • cleaned up the structure
  • the all tools have been changed towards licence-free
  • simplified the web hosting and paid for it 2 years in advance
  • all changes are _immediately_ transferred to a backup box at Hetzer via RSynch
  • Tobias and Michael, my two companions, have all the access data and a completely set-up test system.

Have a nice summer
the OAM team

 

The elevation data for Europe are now very accurate in many areas thanks to flight laser scanning.
Wherever these data are freely available, @Sonny collects them, checks them and interweaves them with Jonathan de Ferranti‘s Viewfinder panoramic elevation data in the areas not yet scanned.

The result is a constantly growing set of elevation data, the best that could be achieved without paying licence fees at the moment.
The accuracy is good enough to make sense for contour lines at 10 meters vertical distance. (which was definitely not the case so far).

To make a long story short:
The following maps are now available with 10m contour lines (more will follow):

Alps, Alps_East, Alps_West, Pyrenees, Austria, CanaryIslands, Corse, Czech_Republic, Great_Britain, UK_Scotland, Ireland, Madeira, Mallorca_Ibiza, Malta, Sardegna, Sicilia, Slovakia, Slovenia, Switzerland, Luxembourg, UK_Wales, UK_LakeDistrict, UK_IsleOfMan, UK_Shetlands

Baden-Wuerttemberg, Bavaria

 

 

New and updated Maps:

The Alps-West now also includes the neighbouring Rhone Valley.
New map: BalticStates (Estonia, Latvi, Lithuania as complete map)

More and more boundaries are grouped in relations and thus cannot be reliably processed by the MapsForgeWriter. In the meantime this is like a TikTokChallenge = who manages to create as many completely unnecessary relations as possible. At the islands of the Canary Islands and Madeira, every beach on even the smalest islands is occupied by countless border relations – these have to be filtered out with great effort.
That’s why I have now written this relation resolution from scratch for

boundary=administrative and Admin_Level=1 to 4
Means: national borders and federal states.
…and try to filter out the nonsense relations…

Extreme improvements were made for maps of South America, here even national borders were missing.

As Locus has a very good mapsforge support for V4 maps since version 3.38 and doesn’t need a special file structure also, a special Locus version of the map style files isn’t necessary anymore.

Elevate LE, which is necessary for the legacy V3 maps, is still available as separate download on the Elevate page.

Double Elements: as Elevate now has a new clean file structure, with quick install the old Elements file remains in the theme folder and can still be chosen with the map style choser (in addition to the new version).

This can be solved easily:

  • The simplest way (installations from 03/10/19): just press long on the old Elements icon with the black sun and choose delete (as in the screenshot below)
  • For installations between 30/09/19 and 02/10/19: delete both Elements installation by two long presses on the desert symbols, and install Elevate again via quick install
  • Delete with a file explorer all not needed files in the directory “/Locus/mapsVector/_themes/” on the internal SD card (or which custom theme directory was chosen in Locus); all files and folders with “ele” in the name except the folder “Elevate”; if you delete too much, just use quick install again

 

For most of you there are no changes ’cause 95% of OpenAndroMaps users already use the multilingual maps.

As already announced some time ago, we are now finally switching to the multilingual maps and drop support for the old V3-Maps. These have been around since 2015/16 and I think that 3 years is sufficient to say goodbye to old specifications and open new resources for new developments.

The development of the Mapsforge vector library is progressing and we would like to share with you the advantages and new features. We are working on a new version of the OpenAndroMaps which will be enhanced and modernized especially in the field of cycle- MTB- and hiking routes.

For this it is necessary to drop old Balast.

The 270 V3 maps will be updated in the next 3 weeks and will be available for download by January 2020.
Of course, the download pages will also be adapted accordingly. For now the separate download button for the POIs will be kept – although the POIs are included in the ZIP archives of the maps.

EndOfLife V3-Karten

Best regards

Team of OpenAndroMaps

There’s a new Elevate update after a while. With Elevate 4.3 there are new optional overlays: in the city map style small ways like paths and tracks can be switched off, so the map will be more clear and is better usable for motorists. In hiking resp. cycling/MTB it is now possible to mark paths and tracks where the usage by foot/bike is permitted – this is important in countries where usage is forbidden/private in the first place. Also in cycling now ways are marked especially which are allowed for cycling, but are maybe too steep/rough. And as always some smaller changes.

Some time ago an additional license was added, so Elevate can now be used commercially (but then changing it isn’t allowed). As Elevate is now the main mapstyle for OpenAndroMaps and not the Andromaps mapstyles, and not an additional exclusive one.

Elevate 2 is now deprecated and won’t be updated anymore, as it was already announced in the forum. Most apps, like c:geo recently, now support mapsforge rendertheme V4 mapstyles with mapstyle menus, therefore the parallel development doesn’t make much sense anymore.

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.

So here are the most important improvements for the OpenAndroMaps 2018:

– Mapborders: Skipped / missing Relations (white lakes eg.)

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.

– Map-Coverage:

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.

– Priority for rendering places and data-cleanup for peaks:

@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.

– Cycle Lanes / Oneway

Improved rendering of several more variants of cycle-lanes in conjunction with “oneway”

– Contourlines

@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:

  • UK_Scotland
  • UK_Wales (new)
  • UK_LakeDistrict (new)
  • Ireland

– Lots of minor improvements

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!

 

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.

  • a new overlay for extended road surface information
  • new via ferrata rendering
  • solid/dashed borders for cycleways
  • changed visibility information for paths without sac_scale
  • prominent peaks are now shown earlier and, if the app supports it, are prioritized
  • hiking waycolor is displayed along waymarks
  • the overlay contents have been rearranged a bit
  • access limits are much more accurate to the mode of transportation the map style is made for

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

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

Hi,

This is an information for Theme-Composers.
There will be an important change in tag-mapping for the OpenAndroMaps.

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 :

    <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:

      <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:

       <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:

  • raw_sac_scale (as mentioned above)
  • incline_dir
  • class_bicycle_mtb, class_bicycle_road (maybe we find a solution to transform _mtb to existing tags)
  • noexit

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