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 ... 30
Similarly, I have a script in use for termux, that downloads and properly places RD5 files of BRouter and Mapsforge compatible MAP files for OpenAndroMaps or ( useful for central Europe, with frequent updates ).

The download is intelligent enough, skipping downloading if the local files are "new enough", with threshold set in the script.

It is driven by a list of abbreviated parameters.

"./ 0 1 cz"
downloads to the target folders
RD5 files for Czech Republic
and Czech Republic map from

For different locations, it may not be directly usable, until modified to download relevant files.

For this case, take it as inspiration and a template to modify.

Sent from my Xiaomi MI A2 via Tapatalk

I have recently written and tested the  Linux port of Windows batch sedbatch.bat, used for mass generation of my BRouter profiles from respective templates.

It creates very interesting possibility to create profiles directly on an Android device, using termux, a great Linux terminal emulator for Android.
( It e.g. allows you to install and use the git command, python, ipython and more.)

It works with all bike/foot/car repositories,
additionally to Windows version optionally with develop GitHub branch as well.

Link to the script on GitHub:

Below is copied the current legend comment from the script:

# Ver 1.1 Fixed generation for Hiking-wet profiles ( by error identical to dry ones )
# Ver 1.2 Parameter "main" generates only main/major profiles
# Ver 1.2.1 Fixed names of Trekking-Dry/Wet profiles ( Was Poutnik instead of Trekking ])
# Ver 1.3.1 Added Shortest-P profile
# Ver 1.3.2 windows batch ported to Linux Bash
# Ver 1.4 Improved script parameter logic. Action paramaters are bike/car/foot, modifiers are master/develop and all/main
#         Implemented termux path specifics and profike copying
# automatically generates a bunch of Brouter profiles
# based on the bike/car/foot profile templates by Poutnik
# When launched,
#   1/  it create a working subfolder in a folder where the script resides
#   2/  it downloads latest bike/car/foot profile template from GitHub depository
#   3/  it generates end user profiles by automatic subtitution of parameters
#   4/  it packs them into a single ZIP archive and deletes the working subfolder content.
#   5/  it optionally copies profiles to the scriot folder
#          or from termux private space to Android storage.
# ******************************************************
#                     P R E R E Q U I S I T I E S
# ******************************************************
# 0 This bash script can be run
#   either on a desktop Linux
#   either on Android within Linux terminal emulator termux.
# Points 1-5 applies only if to be run on an Android device
# 1 Install termux ( Linux terminal emulator for Android )
#   Read links below for more
# 2 Run termux, what open Linux terminal emulator
# 3 Execute "termux-setup-storage"
#   if you want to grant termux permissions to write profile files out of its sandbox
#   to be able to copy profiles to Android storage.
#   It is recommendec not to copy directly to live profiles2 folder.
#   (run "apt update && apt upgrade" to make sure that this tool is available)
#   See  more at
# 4 Check if sed and wget commands are available.
#   If not, install them by "pkg install sed" resp. "pkg install wget"
# 5 Check and define withing the script code
#   your desired target folder for copying profiles.
# 6 If run on Linux, or on termux without jailbreak
#   ( the script is testing both )
#   the optional (aside of zip with profiles)
#   is redirected to the folder the scriot resides.
# 7 Both Linux and termux expects placing the sedbatch script
#    (subject of later renaming, remsins for historical reasons )
# 8 
# The expects particular command line parameters to do anything.
# "" without parameters lists this legend.
# "" can be provided by arbitrary sequence of keywords:
# bike car foot main all master develop copy nocopy           
# bike, car, foot are "action" keywords, generating respective profiles from a profile template
# all(default), main are  modifiers, setting scope of generated profiles ( all or the most important)
# master(default), develop are modifiers determining the github repository branch, where the profile template is located
# nocopy(default), copy, copies profiles to Android storage ( jailbroken termux )
# or to the script folder.
# Examples of usage'
# " bike" generates all profiles from bike trekking template
# and stores them in
# and generates the all profiles for all car, bike and foot transportation modes
# " main develop bike" generates only selected major profiles from bike trekking template
# from develop branch
# " copy main foot all bike develop main car"
# generates  major profiles for hiking, all profiles for bike trekking
# and selected profiles from car template develop branch.
# Additionally, profiles are copied to selected folder

Sent from my Xiaomi MI A2 via Tapatalk

Troubles & Questions / Re: navigation hints "straight"
« on: August 16, 2019, 18:48:37 »
for now, you can use this set of profiles, (stored in the attached zip ),
generated from the current Github Development branch of my profile template,
where PriorityClassifier is reverted to the original.

Additionally, I have already written a Linux script, that can generate my profiles from github template
directly on the target Android device, using termux,  ,a great Android emulator of the Linux terminal.

It already works, tested on desktop Linux. there is remaining final termux testing of the final profile placement in BRouter profiles2 folder.

termux wiki
Termux on Google Play

Troubles & Questions / Re: navigation hints "straight"
« on: August 13, 2019, 08:13:43 »
For riding a bike across (not only ) cities, consider also the  Jacob's profile for streetbikes:

#          A BRouter profile suited for a streetbike           #
#                                                              #
#          It was built to do light bike touring with          #
#          a non-suspension citybike with narrow tires         #
#          It prioritizes good ways, but allows some           #
#          more offroad ways to avoid traffic and to           #
#          follow nicer routes                                 #

that is more focused toward city specifics, while my profiles are more focused on out of city scenarios.

I was supporting Jacob's learning curve and he has put very thorough thoughts into his profile.

Sent from my Xiaomi MI A2 via Tapatalk

Troubles & Questions / Re: navigation hints "straight"
« on: August 12, 2019, 13:23:11 »
Note that I think BRouter internal logic should evaluate the 2 below straight ahead scenarios differently, but it is how it is now:

1/ leaving a "higher" way that is turning away
( giving a hint, as it does now )

2/ crossing  a "higher" way via "lower" way
( not giving a hint, what may be desired )

Sent from my Xiaomi MI A2 via Tapatalk

Troubles & Questions / Re: navigation hints "straight"
« on: August 12, 2019, 05:57:24 »
Note that even if the Shortest profile shares the same hint settings as the Trekking profile,
it is the default profile for pedestrians. For bicycles, the default profile is the Trekking one.

BRouter uses the profile parameter PriorityClassifier to determine, if a turning or straight ahead hint should be provided, or if it should remain silent.

The more significant ( logically, supposedly visually as well ) ways have higher value.

The straight ahead hint is provided, if some   of the other ways has the PriorityClassifier value HIGHER than the straight ahead way to be taken.

The turning hint is provided, if some   of the other ways have the SAME OR HIGHER PriorityClassifier value, compared to the turning way to be taken.

Below are listed differences in  PriorityClassifier between BRouter default profiles ( Shortest, Trekking) and my bicycle profiles.

My profiles use finer value granularity for some of lower than unclassified ways.

It brings both pros and cons for straight ahead hints.

Pros are you get the straight ahead hint to continue along a "lower way" if you are going along a "higher" but turning way, where you get no hint from BRouter default profiles.

E.g. you are going along turning residential, but you should continue on the straight ahead paved grade1 track.

Cons are you get the straight ahead hints when going along a lower way, repeatedly crossing higher ways.

E.g. you are going along a cycleway in parallel to a major road, crossing residential roads.

I offer several options:

1/Use for now built-in bicycle profiles like Trekking

2/Modify your copy of Trekking-LCR-Dry profile, replacing my PriorityClassifier by the original one.

3/ I am going to modify my profiles to avoid typical excessive scenarios, possibly even reverting to original
and/or create a switch flag between original and mine Priority Classifier.

Technical note: For suggestion, questions or complaints related to my bicycle profiles, it is preferred to ( additionally?) create a GitHub issue in my repositories

for general profile topics

for my bicycle profikes behaviour or the code of my bicycle profile template.



assign priorityclassifier =

  else if ( highway=residential|living_street ) then  6
  else if ( highway=service                   ) then  6
  else if ( highway=cycleway                  ) then  6
  else if ( bicycle=designated                ) then  6
  else if ( highway=track                     ) then if tracktype=grade1 then 6 else 4
  else if ( highway=bridleway|road|path|footway ) then  4
  else if ( highway=steps                     ) then  2
  else if ( highway=pedestrian                ) then  2
  else 0

#Trekking FCR Dry

assign priorityclassifier = (

  else if ( highway=residential|living_street ) then  16
  else if ( highway=service                   ) then  14
  else if ( tracktype=grade1                  ) then  6
  else if ( highway=cycleway                  ) then  6
  else if ( bicycle=designated                ) then  6
  else if ( highway=bridleway                 ) then  4
  else if ( highway=track|road|footway        ) then  4
  else if ( highway=steps|path|pedestrian     ) then  2
  else 0

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 02, 2019, 17:33:10 »

Yes. But:
Sweden.osm.db + --> POIDB NOT DISPLAYED

Perhaps the app is not looking for "the same filename but ext", but for hard coded lower case variant.

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 02, 2019, 15:30:39 »
Linux filesystem is case sensitive.

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 11:34:42 »
isn't it same like when you pick real magnifier? It also displays the same object but enlarged. And not some modified scaled clone. Are we talking about magnifying glass on the screenshot below? If so, which scale is incorrect?

I am sorry, I have used wrong terminology. :-)

I mean the zoom lock feature. It magnifies the the whole map area just by pixel upsampling, compared to the nominal state.

As it applies to the whole map area, it should be IMHO reflected by the map scale as well, or the scale should be suppressed, as no scale is better than wrong scale.

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 09:06:09 »
I wonder for some time already, when I use the magnifying glass button, why it keeps the original zoom scale ?

Would not be better to display the scale the map has after zooming ?

Or, not to display it at all, instead of being wrong ?

Odesláno z mého Mi A2 pomocí Tapatalk

I confirm such a frequent behaviour.

If it was permanent, the cause is often a missing icon in the applied map theme. But this is not that case, being temporary.

Odesláno z mého Mi A2 pomocí Tapatalk

Troubles & Questions / Re: Phone Compatibility with 3.38+
« on: June 05, 2019, 06:02:02 »
Not sure if still valid, but @menion have mentioned using Google play feature to make the release available just to subset of randomly selected users, releasing it to all later. It can serve as a pilot testing, if some nasty bug sneaks through to the release.

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 04, 2019, 08:32:01 »

@Andrew Heard
interesting observation. As @tommi correctly mentioned, if screen is off, there is no visible map = no matter what I changed, it should have no effect here. If only running is track recording (is it?) then it is surprising, because I did not touched anything regards track recording service for a long time. Please keep tracking and confirm this, thanks.

Do I understand it right that the Kalman filtering of position applies only to screen rendering, while track recording uses unfiltered data ? But even if not, I guess battery impact would be minimal.

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 03, 2019, 13:04:06 »

But another idea, you could internally do a quality upscale when user downloads low resolution raster maps. You could do quality upscaling and offer such maps, if license allows, in your store and become wealthy.

High quality upscaling of high contrast edgy raster graphics is much more sophisticated than upscaling of photos.

Upscalers often use advanced, edge directed interpolation, some even with support of outputs of neural network training, like NNEDI3 library of Avisynth video frameserver.

Odesláno z mého Mi A2 pomocí Tapatalk

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 12:15:57 »
I have noticed several times something similar, redrawn after forced zooming in/out. 

Odesláno z mého Mi A2 pomocí Tapatalk

Pages: [1] 2 3 ... 30