Israel Hiking map

When the renderer supports this, I have no problem writing a conversion script.
Until then, no point in changing anything.

Most MTB single tracks are only designated by it’s name and a line of clear ground when you get there.
All but few of the ITC footpaths are currently forbidden for MTB and from another POV few of the hundreds MTB tracks are marked.

hikebikemap also renders relation but not the names (and for some reason osmc:symbol=black:white:black_bar)

Update: lonvia does not render names in relations.

Yes, and that’s why these ways are named.
I also tend to add “Single” to the name (both Hebrew and English)
But these are irrelevant to this discussion. It’s just like any other named way.
Even where the INT goes over a named way, the way’s name prevails.

Ok.
I think this discussion is how to have maps that show shields and colored ways according to markings in real life.
For this, wherever there’s a colored marking, we’d like to mimic it on the map.
It’s irrelevant whether the way is a single, residential, INT, mtb (or even the Red Camel under RTG… :wink: )

I believe that rendering the relation’s name in hikebikemap wouldn’t work very well.
hikebikemap is raster based, so what would you do when a segment belongs to several different routes?
On an interactive map you could have pop-ups with all the names of a specific segment, or take a different approach, like Lonvia’s Routes Pop-up.

talkat.

So we agree MTB singles are to be named outside the relation.
It should only be done also were relation are used (Einav, Masua-Ajur-Masua, Adulam, K20, haruvit) and we have a pretty good solution.

Update from Colin (the hikebike man) -
Black trail marks will be supported soon
INT marking will not be supported in the seen future

When a way should have a name - Let it be named so. :slight_smile:

As I understand it, Einav and Adulam and Diefenbaker are ok, and should be named.

K20, Tsfonit, Dromit - Maybe, I’m not so sure…
(Tsfonit and Dromit are slang names, but then again so are many of the singles, which are named, so I really don’t know.)

How do you feel about these guidelines?

talkat.

I changed the INT to:
osmc:symbol=blue:orange:blue_bar:white_lower

It seems to be supported by Nop’s icons, so I’m keeping my fingers crossed…

talkat.

גהנום, גן-עדן, פילו, מחוץ לגדר, בתוך הגדר, תותחים
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?

See our wiki here
If it’s not clear, let’s work on clearing this.

talkat.

  1. What is RTG (Sorry for my ignorance)?
  2. How to choose lwn/nwn/ncn/lcn etc.
  3. How does one tell the operator?