LupinSun

Well, the profile I created and use is also based on these parameters (obviously only the way-tags part). I'll give you the example of my profile for enduro motorcycles: one...

1) - because perhaps the section to be indicated is really small and short, for example I used the smoothness tag on difficult fords to cross, but the same thing...

Response in English: Hi EssBee, 1) I understand your point about the length of the segment being a factor in smoothness. However, I believe that there are still cases where...

I want to clarify that I don't want to be insistent, annoying, or anything else, but just to understand and improve this wonderful project, of which I am also a...

> @LupinSun, the profile is nice, but I cannot find any significant difference in behavior with BRouter 1.7.0 vs. BRouter 1.6.3. > > Both `downhillcutoff` and `uphillcutoff` are set to...

> @LupinSun You should add your brf file as you have published in the Locus forum named "enduro v3 profile problem.brf" > I attached the profile to the first post,...

> It would be interesting to know what caused this error in v1.6.3. However, so far I have not been able to find the cause. > If so, on brouter-web...

> The idea behind `uphillcutoff` and `downhillcutoff` is to tell BRouter when and when not to penalize changes in elevation. > - `uphillcutoff=5` means that an increase in elevation is...

> Yes, as soon as brouter.de and bikerouter.de update the BRouter version running in the background to v1.7.0 or newer, you will no longer be able to generate the red...

> > So it means that if uphillcutoff=5 than slope more than ~5 will be exclude to the compute? > > `uphillcutoff=5` means that BRouter treats roads that are less...