גהנום, גן-עדן, פילו, מחוץ לגדר, בתוך הגדר, תותחים
it’s all slang.
It would have been nice if mtb:name was supported somewhere …
I’m good with this guidelines with a remaining issue of INT.
It’s a lot of work but IMO off-road INT parts should be named.
Yes, I already said that slang is already used in named singles, and I’m ok with it (although, I would add “Single”)
Hopefully, someone will come up with a renderer that supports this.
Many parts of it are already named.
It shouldn’t be a problem for someone with basic scripting knowledge to go over the relation, look for (warning, geek pseudo code!)
((highway=track || highway=path) && (name == null))
and set name, name:en, name:he, name:ru, name:am.
talkat.
Can anyone provide good examples (with link if possible) of naming schemes for “simun shvilim” and bike singles, bike paths in israel?
Also, is hikebikemap.de searchable or have a “jump to location” feature?
ilan
I’ve just confirmed with Colin.
Although the above is correct according to the osmc:symbol documentation, and Nop’s icons,
his hikebikemap doesn’t support this.
So we’re back to the drawing board…
I thought about changing it to:
osmc:symbol=blue:blue:white_bar
Which would render a blue background, with a white bar (sort of reverse colors from a blue_bar)
It would make the INT distinct (the only one with a non-white background), and will keep the blue-white colors.
But white_bar isn’t supported as well…
Thoughts?
osmc:symbol=blue:white:blue_bar
like any other blue troute?
talkat.
Of the currently available options I like the current result in Lonvia which is equivalent to-
osmc:symbol = blue:orange:blue_bar
simply because its unique and eye catching.
Any appearance of white in a dual color symbol will not pop up to the eye.
I’m not sure hikebikemap support this, but you can try.
If you change anything in the INT osmc:symbol, please keep the “note” tag that has the correct value (not yet supported…)
i.e. osmc:symbol=blue:orange:blue_bar:white_lower
talkat.
Ok I’ll change it and will check later this evening.
Generally speaking I propose to use hikebike as the renderer to tag to when we tag for the renderer.
Hi!
As I can see, Colin has already advised you pretty well on the handling of the tagging scheme.
The first color may be rendered so you are able to follow different colored hiking routes sharing the same ways or crossings even if it’s all too small to show trailblazing signs.
If you want a quick feedback on how your tagging might turn out on a map, you don’t need to wait for online maps to update. You could also use MapComposer to create a Garmin map or a bitmap map (vio Kosmos) yourself. osmc: stands for OSM Composer, it knows all the available symbols. Unfortunately, the UI is in German only ATM.
For networks, you really should use the established network=nwn/rwn/lwn.Your current Wiki entry is in contradiction with established tagging schemes:
network itc/kkl The authority that maintains the route
- Network is intended for the level of network (by distance, importance) regardless of who marked the trail. The english terms are also used in other countries e.g. in Germany
- Operator is used for the authority that maintains the route.
See http://wiki.openstreetmap.org/wiki/Walking_Routes#Relations
You are starting fresh here and you have the chance to make it easy. So I would recommend you don’t introduce contradictions where currently there are none.
As for the missing symbols: The list is extended as needed. There have been several requests for orange symbols recently, so I guess it needs extending. Unfortunately, it is not quite as easy as drawing the rectangle. The osmc:symbol is primarily intended to create vector maps with trailblazing for Garmin devices. To do this, every symbol needs a Garmin ID that is displayed on all devices and not already used by Garmin. Those IDs are getting scarce.
Your symbols definitely are _stripes not _bars. The multicolored case could be done with a _stripe_left in orange or in white. Is that list complete or is that only some examples?
I will have to think about what is the best way to do this.
Nop
Following all the feedback in this thread, and also Lonvia’s map (see the routes tab) I suggest we change our standard tagging as follows:
network=nwn/lwn/ncn/lcn/etc.
I suggest we keep this in accordance with the wiki.
operator=itc/kkl
This might change in the future.
I’d put kkl and rtg in the same tag, and itc in a tag of its own, as the itc paints the shields on the routes in all of Israel, no matter if the area is public, under kkl, rtg, or anyone else.
P.S. On a recent count, we have 70 routes.
That’s 15 new routes in 4 days!
talkat.
Done.
Most are network=nwn as they had route=hiking
A few are network=ncn, e.g. TLV-JM-Bike-Route
Nes Ziona Scenic is lcn.
Almost all are operator=itc
TLV-JM-Bike-Route is operator=kkl
Please fix where appropriate. (Adulam? Single Einav? Canada Park?)
talkat.
For the rest of us, could you post, in a different thread, a clear procedure on how to tag a blazed route into OSM?
- What is RTG (Sorry for my ignorance)?
- How to choose lwn/nwn/ncn/lcn etc.
- How does one tell the operator?
I believe this list is all we need, without the last two entries.
In theory (i.e. according to the back of ITC maps), there also exist two-stripe markings with one stripe white and the other black/green/red/blue, for the so-called “urban trails”.
-
RTG = Rashut HaTeva VeHaGanim.
-
I suggest that if it’s a local initiative, like the Nes Ziona Bike Route, then it’s ln. Otherwise it’s nn.
In most cases it’s a hiking route, unless it’s a specific bike route, like the TLV-JM-Bike-Route.
Actually, some of the routes are marked as for off-road vehicles (think 4x4, Jeeps, etc.) but in essence it’s a hiking route.
- That’s a tricky one…
The ITC is the one that paints the shields on all official routes in Israel.
Some of the routes are inside KKL or RTG areas (and residential, and open areas, etc.)
However, some of the routes are maintained by others, like the TLV-JM-Bike-Route, which is maintained by KKL, and bears a different kind of shield (not 3-stripes, but sort of a circle with an image and an arrow)
And news from this week: RTG has 5 new bike routes as a pilot.
talkat.
I suggest (and have previously sugested the same) adopting the standard nwn/lwn and that all but the national routes will be taged as locale.
This is in acordance with the ITC colouring scheme.
This is also in acordance with the distance of the routes (it’s extremely easy to tell the national routes from locale ones).
I’m not sure KKL formaly maintains trail marking in the form of the regular coloured stones (which we reffer to in the map) but KKL does use different markers then the regular ITC ones (mostly estatic wooden signposts with colourde triangles and the name of the route).
I suggest the thumb law - all three colours routes will be marked as operator=itc
I agree. Sounds good.
What about this refinement?
Natioanl: nwn
3-colors: rwn
Transparent: lwn
As I wrote above, KKL has its own type of markings.
But for now, all the renderers support only 3-color-markings, so let’s stick with them.
Maybe we should see if we could help Lonvia and/or hikebikemap to support our markings as well.
That way we will have our lovely map, and hopefully, other countries would be able to benefit from it.
Can you go over the routes that are maintained by KKL and set operator=kkl ?
Or find their list in the KKL web site?
I wonder if a complete list of all marked routes is available.
We can produce one, with colour, trailhead, length, etc.
but it’s far from benig complete, but maybe if we have it, people would see OSM’s benefit here, and contribute to make the list complete.
talkat.
Something like this… 
It’s a work in progress. Need to add images for the shields, divide into networks, etc.
talkat.
My previous proposal (somewhere in the first page of this thread) was
Nationl routes - nwn
Shvil Israel is a typical member of this group
White:colour:white - lwn
Kisalon northen scenic route (BTW the name is official as it appears on KKL signposts along the route) is a typical member
Special (mostly KKL initiatives) - rwn
This is soewheat gray area but the JM-TLV bicycle route probably falls here
I will check later about the usage in other countries.
The current table has good choice of fields.
My suggestion:
route=hiking:
nwn - INT only
rwn - Special named (Golan, Jesus, Emek Ha’Ma’ayanot, Sovev Kineret, Jerusalem) and the unnamed long “regional” routes (purple)
lwn - all the rest
route=bicycle:
ncn - the future “Israel Cycle Route”
rcn - JM-TLV, “Sovev Kineret” for bicycles
lcn - all the rest (e.g. Ness Ziona Scenic, Canada Park Black)