Poutnik

You are generally right these profile should match, IF they are generated from the same profile template. The template version should be included in the profile header comments. Main and...

In fact, it is easy. All the development is done in respective github repositories for car/bike/hiking profile templates. The Brouter profiles repository serves more or less as a featured cloud...

I agree my current policy of updates of profile folders is for historical reasons rather weird. I may rewrite the batch file to automatically make copies to mainprofiles. I rather...

_So, the conclusion is that user eager to get the latest version should build from the dedicated sub-repositories, if I understood correctly_ Rather, either to download the master ( or...

Well, you are right. I was focused mainly on users. I will consider to create a developer wiki page. About issues, development and FR related to profile template, the best...

Initial versions: https://github.com/poutnikl/Brouter-profiles/wiki/Contribution-tips https://github.com/poutnikl/Brouter-profiles/wiki/Profile-developer-notes

@Phyks The bash script sedbatch, running in termux/Android, already works with git, producing zipped profile packages in my BRouter data folder. With a command modifier parameter, it could make the...

I already use the above 1.5/60 3.0/70 as default values in my template for some time as hills=1 parameter set. Some dual penalisation rate can be achieved via above mentioned...

For C. Kristol: Be aware MTB factor is a complex parameter, affecting the final uphillcost/cutoff values. That is reason why I introduced up/downcost/cutoff**VALUE** as initial values. The real final parameters,...

Yes, you are right, the effects on elevation cancel each other with the same values.