User:Ivom

From OpenStreetMap Wiki
Jump to: navigation, search


Hi,

I live and work in Antwerp and I map my local surrounding and my cycletrips.

Mapping intents

  • Mapping Antwerp and surroundings
  • Tagging long distance bicycle LF-routes (ncn) and the node-networks (rcn) in Belgium and South-Netherlands

Stuff

  • Owned an Etrex Venture (2001)
  • Used the Garmin Etrex Venture Cx (2006-2008): Good unit, functionally speaking, not only for OSM specifically. Bought into the Garmin/Navteq deal (EuroCity Navigator maps), before I knew about OSM.
  • Upgraded to Garmin Etrex Legend HCx Unit (2008-): more sensitive, but functionally the same as the old Venture Cx. If you can obtain a Cx-model for OSM-mapping in rural land, then you might save some money, since the HCx only comes in handy in urban areas.
  • My ideal mapping rig looks like this:
  1. recumbent bicycle (da's een ligfiets in het Nederlands)
  2. mounted Etrex Unit on bicycle
  3. Powershot A620 photo camera

The recumbent allows for resting the camera in your lap and ride some 30 km extra then what I am used to with a normal bicycle (70km). I use the camera to do drive-by-shooting of streetnames and document road state. With some practice and 'helping' the camera with limiting it's capabilities regarding, shutterspeed, flash and resolution, I get reasonable results regarding image quality.

Poi for Cycle_map

This is for the dutch and belgian (or those that venture there) that carry a Garmin device with the fantastic OSM_Map_On_Garmin/Cycle_map.

Add a so-called gpi-file as an extra file to download for end-users. My do-it-your-self solution below (bash-script, e.g. go-linux or install cygwin on Windows and experiment). You will need wget, sed and gpsbabel also to do your thing.

In short my solution comes down to this:

  1. download the osm-data you need
  2. transform it to the proper gpi format for garmin
  3. place the result in your SD-card (create a folder named Poi in the Garmin folder on the SD-card)

This construction can be easily extended to create other Garmin Poi database files.

#!/bin/bash

#name of the resulting poi file
POINAME=cyclenodes

#specific datatype (only one) to find data for
DATATYPE=rcn_ref

# OSMXAPI precicate for this datatype
PREDICATE="[${DATATYPE}=*]"

# Boundingbox to limit the resulting download of osm data
BBOX="[bbox=4,50,6,52]"

# retrieve osm source data
wget -O downloaded-${POINAME}.osm http://www.informationfreeway.org/api/0.5/node${PREDICATE}${BBOX}

# in some cases you will want the tag to be published as the pois name, then invoke some sed incantation
sed "s/${DATATYPE}/name/" downloaded-${POINAME}.osm > processed.osm

# let gpsbabel do it's thing; transform the osm data into a gpi file
# place the resulting file in Garmin SD-card under directory Garmin/Poi see [[OSM_Map_On_Garmin/POI]]
gpsbabel -i osm -f processed.osm -o garmin_gpi,category="${POINAME}" -F ${POINAME}.gpi          

#drop the original data, you won't need it I guess
rm processed.osm

Please note: It would be great to have a specific icon associated to this special POI-file. Gpsbabel supports that with the bitmap-option, but I have not found the way to actually display that icon properly. Nevertheless, having at least the possibility to find nodes near you should be of some help when you lose the way, whilst you are getting tired and the sun slowly sinks in the west...

Tagging examples

Basic Information

  • According to the Belgian highway code, all designated cycle ways/paths are entities separate from the main road, either physically or separated by road markings. Those ways/paths are indicated with the following road signs (tagging examples included):
Signage Tagging suggestions
Belgium-trafficsign-d7.svg D7
highway=* cycleway=track cycleway:traffic_sign=D7
highway=* cycleway=lane cycleway:traffic_sign=D7
highway=cycleway cycleway:traffic_sign=D7
Belgium-trafficsign-d9 bicycle foot.svg D9
highway=* cycleway=track cycleway:segregated=yes cycleway:traffic_sign=D9
highway=* cycleway=lane cycleway:segregated=yes cycleway:traffic_sign=D9
highway=cycleway foot=yes cycleway:segregated=yes cycleway:traffic_sign=D9
Belgium-trafficsign-d10.svg D10
highway=* cycleway=track cycleway:foot=yes cycleway:segregated=no cycleway:traffic_sign=D10 
or when it's used on an isolated pathway
highway=path bicycle=yes foot=yes segregated=no traffic_sign=D10)
  • All roads/paths which do not display the signs depicted above, but where cycling is allowed are best tagged with highway=* (use: unclassified, path etc, depending upon the basic road type) and then bicycle=yes if explicitly signed. Check User:Eimai/Belgian_Roads#Restrictions to determine the correct tags in case of missing road signs.
  • Roads with striped markings on the nearside edge of the road: the insides are cycle lanes. If the above road signs are missing (or you missed them) then use the road markings to determine the correct tagging procedure. Refer to highway code, artikel7.4
  • Some cycle paths may also be depicted by:
Belgium-trafficsign-f99a foot bicycle horse.svg F99a Belgium-trafficsign-f99b bicycle foot.svg F99b Belgium-trafficsign-f99c foot horse bicycle.svg F99c

or by a C3 sign accompanied by a special permission (granted to bicycles).

Belgium-trafficsign-c3.svg or Belgium-trafficsign-c3.svg
Belgium-trafficsign-m2.svg    Belgium-trafficsign-m3.svg

Have a look at User:Eimai/Belgian_Roads#Paths which deals with tagging paths in this category. This wiki page does not handle these cases.

Meetfiets data van Fietsersbond

trilfiets at work

Er zijn in Vlaanderen in 2008 en 2009 door de Fietsersbond vele honderden kilometers fietspaden afgefietst om de qualiteit ervan op wetenschapelijke wijze te bepalen. De gegevens kunnen potentieel in OpenStreetMap worden ingegeven op bestaande wegen en vrijliggende fietspaden. Nog niet bestaande wegen moeten via gps data worden ingegeven en kunnen daarna worden voorzien van de gewenste meetfietsgegevens.

Tijdens de metingen wordt per gelijkvormig bestraat tracé een gemiddelde trillingswaarde bepaald. Daarnaast worden de breedte van het fietspad, het materiaal van het fietspad en de bufferruimte tussen de rijweg en het fietspad bepaald. Je vind een overzichtelijk rapport over het verzamelen van de fietscomfortmetingen en de daaraan verbonden conclusies, terug op de website van de fietsersbond [hier]

Hieronder volgt een aanzet om de meetgegevens, met een fiets met trillingssensor (verder trilfiets genoemd), toe te voegen aan OSM.

Vrijliggende fietspaden highway=cycleway

Tag Description
cycleway.width=2.50 breedte van het fietspad in meters
cycleway.buffer=9.25 optioneel
cycleway.surface=asphalt andere mogelijkeden zijn doorgaans concrete, concrete plates, paving_stones, paving_stones:20, paving_stones:30, cobblestone, cobblestone:flattend, ground en gravel
cycleway.comfort=5 deze waarde is afkomstig uit de metingen van de trillingssensor van de meetfiets
cycleway.comfort:device=mark1 type van trilfiets (mark1) om later metingen met elkaar te kunnen vergelijken

Aanliggende Fietspaden (nabij de rijweg)

Het gaat hier om wegen die getagged worden met cycleway=lane of cycleway=track

Tag Description
cycleway.width=2.50 breedte van het fietspad in meters
cycleway.buffer=2.50 breedte van de ruimte die het fietspad en de rijweg scheiden. Denk hierbij aan parkeerplaatsen, grasperkjes of haagjes.
cycleway.surface=asphalt andere mogelijkeden zijn doorgaans concrete, concrete plates, paving_stones, paving_stones:20, paving_stones:30, cobblestone, cobblestone:flattend, ground en gravel
cycleway.comfort=5
cycleway:comfort.device=mark1

In het geval je een weg wilt taggen waarlangs zich twee verschillende soorten fietspaden liggen gebruik je de volgende tag voor breedte om de rechtse kant in de richting van de way: cycleway:right.width=2.50


Tag:cycleway.buffer=*
Status: Draft (under way)
Proposed by: ivom
Tagging: cycleway.buffer=*
Applies to: way
Definition: Defines the space in meters, between a cycleway and a closely related way that carries motorized traffic. The reason for this tag is that cycleways are regularly tied 1-on-1 to a adjecent highway=* and drawing a separate cycleway is either too cumbersome or in appropriate with regards to the road layout. Note: This tag implies the availability of cycleway=track or cycleway=lane on the way this tag is placed on.
Drafted on: 2009-07-01
RFC start: *
Vote start: *
Vote end: *
Tag:cycleway.width=*
Status: Proposed (under way)
Proposed by: ivom
Tagging: cycleway.width=*
Applies to: way
Definition: Defines the width in meters of a cycleway. Note: This tag implies the availability of cycleway=track, cycleway=lane or highway=cycleway on the way this tag is placed on.
Drafted on: 2009-07-01
RFC start: 2010-02-24
Vote start: *
Vote end: *


Tag:cycleway.surface=*
Status: Draft (under way)
Proposed by: ivom
Tagging: cycleway.surface=*
Applies to: way
Definition: Defines the type of pavement of a separate or cycleway embedded on a highway=*. Possible values are among others: concrete, concrete plates, paving_stones, paving_stones:20, paving_stones:30, cobblestone, cobblestone:flattend, ground and gravel
Rendered as: Future rendering should depend on the type of pavement. Note: This tag implies the availability of cycleway=track, cycleway=lane or highway=cycleway on the way this tag is placed on.
Drafted on: 2009-07-01
RFC start: *
Vote start: *
Vote end: *