Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - poutnikl

Pages: 1 [2] 3 4 ... 39
Hmm, how should the XML parser decide, where the slashes separating folder names in the 2nd URL belong to ?



file:// treba vidiet ako protokol a to co je zatym je cesta a ta cesta niekedy moze zacinat s / - absolutna cesta a ak je to relativna cesta vtedy tam to lomitko v ceste na zaciatku nie je

Jasně, to dává smysl.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Themes - Vector maps / Re: [Theme] Voluntary UK
« on: May 08, 2020, 15:39:07 »
tags surface=paved|asphalt|concrete [|compacted
 or tracktype=grade1

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Locus Map (4+) / Re: Locus Map 4, discussion
« on: May 08, 2020, 12:07:01 »
Try LM4 form Apr 30

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Themes - Vector maps / Re: [Theme] Voluntary UK
« on: May 08, 2020, 05:12:46 »
It seems to me Elevate has maybe even better distinguishing than Desert, and puts more stress to routes over motorways. The truth is Desert distinguishes surfaces at lower zooms.  I like Desert theme very much as well.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Versions / Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« on: May 07, 2020, 04:28:55 »
@johnpercy Thanks, it did help in both LM3 dB file recognition and LM4 alpha dB file choice. But it is still little strange it is ever needed.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Versions / Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« on: May 06, 2020, 08:17:53 »
Edit: I see now I have mixed LM3 Pro and LM4 Alfa things together. As while OAM downloading is currently possible in LM3 only, the rest, related to LoPoint DB choice applies to LM4 alpha ( the DB recognition perhaps to both). But I am sure @menion will not get confused :-)

I have noticed 1 not very consistent thing, related to OpenAndromaps placement during Locus-actions OAM download. It has revealed itself with existence of  new beta Locus Poi OAM dB files.

If I download OAM map or its Poi DB from OAM site via Locus actions,
it places the files into mapsVector folder. LocusMap recognizes the <country> file, but not <country>_oam.osm.db file, when I try to select the POI dB file from LoPoint selection.

If I move both files to Europe subfolder, where already are respective LoMap files for European countries, LocusMap is able to recognize the POI dB file. If I move it back to mapsVector ( all moves with LM shut down ), it is not able to find DB file again.

I am not sure, if eventual change has to be done in LocusMap application, or in the locus-actions XML file on the OAM site. But I think either Locus should place the files during the download/unpacking to the respective region folder, either it should be able to recognize the POI *.osm.db file in mapsVector as well.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Locus Map (4+) / Re: Locus Map 4, discussion
« on: May 05, 2020, 06:25:38 »
When I have tried direct OAM map Locus download via Locus action link on site:


the download immediately fails (but it says it was successful as @johnpercy says below).  The same for UK_Saint_Helene ( 1 MB only on mobile data)  as a test case.

Doing so in LM3 Pro is OK.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Themes - Vector maps / Re: [Theme] OS Map (v3 maps)
« on: May 04, 2020, 11:47:30 »
For smaller on-place changes, like a theme tweaking, there is the good Android editor Quickedit.

It does not do code folding, but it supports XML syntax highlighting and regex.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk


Regarding changing zoom levels, you have to consider what tags are used and what zoom level the map elements appear at, this is different for different maps. Maps are usually provided with a tag-mapping xml file that defines what tags are used and when they appear.

Tag-mapping file was not needed. I have now made my mods of Elevate and Elevate  LE theme XMLs, making 3 changes:

LCN/NCN name captions appear already at  Zoom 11, where no RCN/LCN is displayed yet. So it is easily viewed at low zoom long distance planning.

I have cancelled the intense LCN/RCN display at zoom 12-13, as the network is often too dense and it disturbs perception of the map.

I have extended the emphasized routes display, originally for zoom 14+, to zoom levels 12-13, so they are displayed more decently.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I see. While I am generally more or less familiar with XML syntax, I cannot say so about map themes and their customisations.

My single attempt to modify zoom levels of displaying regional/local cycle routes in Elevate for V3 maps did not end well, but I may have given up too early. :-)

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I like WaymarksV2a very much and my favourite feature is the selective choice of turning on/off international, national, regional and local cycle networks. That is not possible in Elevate theme I usually use for cycling scenario.

Thank you very much for your work, as I miss the theme for V4 maps and I can imagine how much work it is.

I have noticed, the V4a / Cycling does not unfortunately display the cycle networks at any zoom yet.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Well, the IT is in the 2nd part only. :-) I have posted it for general audience, as some may take it as useful info, others not so much.

Yes, the BRouter servers take from OSM the daily difference files, process them and make the related daily BRouter differential and full updates.

You can check yourself:

For usual users nothing changes, they just notice in BRouter download manager less of data downloading and more of data processing.

The daily/frequent  updating makes sense mainly on the current data square only a/o if one impatiently waits for OSM update propagation.

Or, if one wants/needs to cut down the updating network data for whatever reason.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

.......BRouter has new data every 7 days. Correct the OSM, max. Wait 7 days and then renew routing data. Unfortunately, this is not automatic.......

This is not true anymore.

BRouter has already implemented daily differential updating of rd5 files not older than 8 days.  For rd5 files older than 8 days, the  download of the full updated file has to be done as was done before. The updating must be still trigerred manually by the user in BRouter download manager.

For illustration, my home BRouter rd5 square  E15_N45 has size about 80 MB.   rd5diff files for rd5 1-8 days old have sizes  1-3.5 MB. See E15-E45 rd5files

The 8 day diff update limit is IMHO  reasonable trade off between downloaded data amount and processing time, as rd5diff file dowload is much faster than the following data processing. For longer intervals, like updating after few weeks, the processing could take longer than the full file downloading.

For advanced users, already downloading rd5 files manually, or by scripts as my or similar , diff updating is not as straight forward.  For the diff updating out of BRouter application, it must use brouter.jar java application. e.g. on Linux or Windows.. See for more at BRouter Github issue Checksum of segment files #234   

It is possible to do so directly on Android device as via my private improved getmap script, but the additional prerequisites to the ones for is installed java and proot in termux (some details also in the above Github link). I can provide the script on request, but it is not for everybody. I am not sure, if anybody ever used my original full downloading script.

As an illustration, this is the working proof of concept, before updating of my getmap script:
Code: [Select]
md5 = $(md5sum -b E15_N45.rd5 | head -c32)
wget -N "$md5.rd5diff"
proot -0 java -cp brouter.jar btools.mapaccess.Rd5DiffTool E15_N45.rd5 $md5.rd5diff

Versions / Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« on: April 28, 2020, 20:16:23 »

This is definitely not a task for one evening ... I'm now little pushed by time to finish some less or more cosmetic improvements for LM4. Once it will be out, I really really wants to focus mainly on many incorrect algorithms on background so please remind me (again, sorry), this serious topic maybe half an year later. Thanks!

Sure :-) No big deal. Just nice to have.
I wish you being just pleased by the user feedback, not being frustrated by it.
Thanks for all your great work.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Pages: 1 [2] 3 4 ... 39