User:Threefoursixninefour

From OpenStreetMap Wiki
Jump to: navigation, search

I currently live near London and map parts of those as and when I can add useful information. I also know some areas of Switzerland, Germany and France very well and map those - especially the parts where at the moment there is not much detail.

These are some of the notes that I have made while mapping, here for the record and as a reference.

Restricted roads

There are a lot of these in Switzerland, leading from the main roads well up into the mountains. They show a standard "no vehicles" sign, usually with a qualification, and may be private or state owned; even if the road is privately owned the prohibition has the force of law. I've followed the convention when tagging these for access:

Both of these also with foot=yes; bicycle=yes unless those are specifically prohibited.

Some of these roads may also be used by the general public on payment of a toll. I've tagged these as the first of the above with a barrier=gate; toll=motor_vehicle; motor_vehicle=permissive at the access point. There is some discussion on the Tag=access talk page.

Trübsee, near Engelberg

There seems to be some dispute about the spelling of this name, whether "Trübsee" or "Trüebsee", even on the official SwissTopo maps, even to the extent of using two different spellings for the same feature at different scales! However, all of the signs and official documentation in the area seem to use the former, and this is borne out by the Google search results:

  • "Trubsee" = 18,300
  • "Trübsee" = 113,000
  • "Truebsee" = 22,700
  • "Trüebsee" = 6,430

with the vast majority of these being for "Trübsee" or its unaccented equivalent. So this is the spelling that I've stuck to.

Naming of cable cars (in German speaking countries)

It would be nice if these showed useful information both on the map and when searching/routing. So the convention that I'm following at the moment is to try to avoid any ambiguities by naming:

Way: "Luftseilbahn"/"Materialbahn" Valley-destination Mountain-destination
End stations: just the plain name of the destination place
Terminal buildings: "Talstation"/"Bergstation" name-of-place

Where there is more than one starting or ending point in a particular place, the end stations and terminal buildings get disambiguated with the name of the other end, in (brackets). The names will be replaced by appropriate terms in the local language for non German-speaking areas, of course.

So, for example, the Nechimatt-Diegisbalm cable car has the names:

Way: Luftseilbahn Nechimatt-Diegisbalm
Bottom station node: Nechimatt
Bottom station building: Talstation Nechimatt
Top station node: Diegisbalm
Top station building: Bergstation Diegisbalm

However, the Wolfenschiessen-Wissiflue cable car, since there is more than one cable car station in Wolfenschiessen, has the names:

Way: Luftseilbahn Wolfenschiessen-Wissiflue
Bottom station node: Wolfenschiessen (Wissiflue)
Bottom station building: Talstation Wolfenschiessen (Wissiflue)
Top station node: Wissiflue
Top station building: Bergstation Wissiflue

Crossings and signals at junctions

This is the convention that I've used for mapping the combination of traffic light controlled junctions with pedestrian crossings, at multi-lane junctions and roundabouts. Typically the traffic lights controlling the entry to these also control the pedestrian crossing for that lane, while the corresponding exit lane has a pedestrian crossing only.

             ^    v
             |    |
             P    T
             |    |
-->------T---+----+---P------>--
             |    |
--<------P---+----+---T------<--
             |    |
             T    P
             |    |
             ^    v

So the traffic lights "T" are tagged with highway=traffic_signals; crossing=traffic_signals, while the pedestrian crossings "P" are tagged with highway=crossing; crossing=traffic_signals. Note that this applies to the style of junction/crossing typically found in the UK, where there is no "give way to pedestrians when turning" rule and the traffic signals prevent any traffic across the pedestrian crossing when there is a green signal for pedestrians. Other countries may vary.

Summer toboggan runs

For example: at Ristis (Engelberg), Wirzweli (Dallenwil), Fräkmüntegg, Willingen (DE). Taking the already existing tags of the first of these as an example, they are tagged with:

area=no; attraction=summer_toboggan; leisure=track; oneway=yes; sport=toboggan; tourism=attraction.

Note that these are currently not rendered correctly by the standard renderer (the track is not shown). Possibly openstreetmap-carto issue #574.

The run at Sternrodt (south of Bruchhausen, DE) does get rendered in both OSM and OsmAnd+. The tags that it uses are:

attraction=summer_toboggan; railway=preserved.

A more appropriate tag might be railway=miniature instead of railway=preserved, assuming that it gets rendered properly.

So a combined set of tags that will give appropriate rendering and search results (which is hopefully not tagging for the renderer since nothing is actually incorrect or inappropriate) is:

area=no; attraction=summer_toboggan; leisure=track; oneway=yes; sport=toboggan; railway=miniature; tourism=attraction.

See Tag:sport=toboggan and DE:Tag:sport=toboggan for additional information.

Large waterways

Care is needed when mapping these as relations, to include islands or other enclosed features. If there are any are tags on the outer members, they will be rendered as an area which will cover up any islands or interior features, see openstreetmap-carto issue #3294. See waterway=riverbank for detailed information; in summary, the basic tags required are:

Relation: type=multipolygon; name=*; natural=water; water=river or other as appropriate
Outer members: No tags
Inner members: name=*; place=island (or place=islet if very small); area=yes if no other area tags

Waterway locks

These are described in detail at lock=*. In summary, the tags for each part of the lock are:

River way through the lock: lock=yes; lock_name=*; waterway=river or waterway=canal as appropriate
Lock chamber outline: natural=water; water=lock; name=* - which should be the name of the lock as for lock_name=* above, or the specific name of the chamber if there are more than one (e.g. as at Teddington Lock); ref=* - in the form "Lock ##" where the locks are numbered starting from the downstream end (unless another official referencing scheme is in use for that waterway); wikipedia=*. The name will then be rendered on the map. If there is only one lock chamber then put the wikipedia=* and ref=* tags on it; otherwise, mark the approximate centre of the site with the place=locality, the name=* of the lock and the wikipedia=* and ref=* tags. For the River Thames see Locks_and_weirs_on_the_River_Thames on Wikipedia for a list, number upwards with Richmond Lock being 1.
Gates: waterway=lock_gate - as a line if possible, because it looks better on the rendered map (making the direction obvious).
Gates and weirs: set foot=permissive, bicycle=permissive if allowed as a public route. Do not continue the highway=* way over the gate or weir, or it will be given the priority in rendering, which is wrong - the waterway feature is the important one. The access tags should still be used for routing.
Weirs: note that this cannot be an area (see waterway=weir).

There does not appear to be a mapping convention for boat slides or rollers at locks (as illustrated at File:BoveneyLock04.JPG). For the moment I have continued the river route along the way (because it is a route that appropriate boats can follow, and sometimes (e.g at Sunbury Lock) there is a small part of the river flowing), and tagged it with waterway=river; name=* - the river name; lock=yes; lock_name=* - in the form "XXXX Lock Boat Rollers"; boat=yes; canoe=yes; motorboat=no. Then mark the location with a node (or possibly a line if of significant length) tagged leisure=slipway; name=* - same as lock_name=* above.