Comments (3)
Talking at Github is fine, while it discuss my profiles or Github wiki content for particular details.
If it may be interesting for broad Brouter audience, Brouter group can be considered as well..
I would separate the routing case topic to points:
-
Wrong mapping to fix routing, wrong routing to fix mapping
Mapping should reflect the way physical conditions, status and marking. Routing algorithms must be based on what the map vector data contains, not what is in the terrain. It is not good idea to bend routing algorithm for cases the mapping is incorrect. -
Suggestion : I recommend to fix the [mapping] as mentioned below.(https://www.openstreetmap.org) ( BRouter rd5 file have 7-10 days update frequency ), and to temporarily use the Brouter nogo points.
-
Used mapping
Even if there is marked surface=gravel, it is marked not only as international cycleroute, but even as highway=cycleway, with access bicycle=designated. So the routing can legitimately suppose it is usable for bicycle travelling.
Default Brouter profiles even take all highway=cycleway as perfect. My profiles are more hesitating ( but not avoiding ), seeing surface=gravel. -
surface=gravel and the case fixing of mapping - gravel is often used, more or less correctly for quite a range of surfaces, from loose gravel through water-bound/macadam to compacted surface ( where surface=compacted should be used). I suggest possible mapping actions, based on the terrain survey. All 4 of them are evaluated in the profile"
- reconsider the proper surface=* tag, but what i understands there is loose gravel, so surface=gravel should be correct
- consider usage tracktype=* tag
- consider smoothness=* tag
- consider mtb:scale=* tag
-
Traveling gravel : I often go through gravel roads on my trekking bike. They are seldom like really loose gravel. They are often more or lass flattened by the traffic or explicitly by the roler , or integrated with the soil bases into tracktype=grade2 or grade3. So they fit to some range of applicable smoothness=* and tracktype=* values.
-
Trekking-fast - the profile is NOT intended for racing/fast road bikes.
It is trekking profile just shifted little toward paved roads. Use original Fastbike profile, or change the MTB_factor from -0.5 ( Trekking-fast) to -1.5 - -2.0 ( Fastbike-like).
It would not avoid gravel, but would assign it very low priority.
from brouter-profiles.
about the placing, it could be as well as placing discussion to the group, while raising the issue with short summary to GH issue page, cross-linking them. The issue page has advantage it is harder to be forgotten.
from brouter-profiles.
Right i see how it makes sense..probably a rare case that an official cycleway is that garbage
from brouter-profiles.
Related Issues (20)
- cost for routing over "ford" HOT 16
- Profile Hiking/Trekking near nature HOT 17
- Missing route types used in Budapest HOT 13
- traffic_calming nodes not evaluated for cost factor HOT 3
- sidewalk HOT 1
- Main vs dedicated profiles HOT 9
- Missing Commuting profile HOT 2
- Electric bicycle trailer for children HOT 16
- Profiles do not contain expressions for context way (error Osmand 2019/07) HOT 6
- Brouter-profile for touring cyclists with luggage -> long-distance travel HOT 7
- > a script to generate the content of this repo directly might be useful. HOT 1
- Ascent in hiking profile HOT 12
- Avoiding yield/stop signs HOT 7
- Road-race bike profile with 5=No-Flats mode HOT 2
- Ignore bicycle=use_sidepath ways HOT 3
- Add penalty for railway crossings?! HOT 2
- Trekking-dry and other profiles select 16%+ descent on grade2 track HOT 4
- profile=hiking-mountain routes over way with foot=no
- Cross-country skiing profile for Android app
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from brouter-profiles.