User talk:Foxandpotatoes

From OpenStreetMap Wiki
Jump to: navigation, search

OSM Forêt de Soignes / Zoniënwoud highways tagging guidelines (draft)

010 is the highway physically designed for motor cars, forestry trucks, etc.? yes, goto 100 | no, goto 015

015 is it designated for horses? yes, goto 140 | no, goto 020

020 is it designated for bicycle? yes, goto 165 | no, goto 200

100 tag highway=track (e.g. drève, etc., with access for forestry trucks)

105 tag surface=asphalt or surface=concrete or surface=gravel or surface=ground, etc. (e.g. Drève de Lorraine, Drève des Tumuli)

110 precise restrictions e.g. motorcar=no or bicycle=yes, etc.

115 if appliable, tag oneway=yes or oneway=no

120 if appliable, tag noexit=yes or noexit=no

140 tag highway=bridleway

145 tag surface=* with paved | unpaved | asphalt | concrete | cobblestone | gravel | sand

165 tag highway=cycleway

170 tag surface=* with paved | unpaved | asphalt | concrete | cobblestone | gravel

200 tag highway=path

205 tag surface=* with paved | unpaved | asphalt | concrete | cobblestone | compacted | gravel

210 tag bicycle=yes or bicycle=no or bicycle=designated

215 tag horse=yes or horse=no or horse=designated

220 tag foot=yes or foot=no or foot=designated

225 tag motorcycle=yes or motorcycle=no or motorcycle=designated

230 tag access=*

Other features


  1. See also:
  2. Refer to the tagging scheme of the Forêt de Fontainebleau, France.
  3. (path and not footway; IMHO footway is for urban areas; see: Footway: For designated footpaths, i.e. mainly/exclusively for pedestrians.)

Foxandpotatoes 22:04, 10 November 2009 (UTC)

Foxandpotatoes 18:35, 17 January 2010 (UTC)

Mapping party timeline (Newbies Digest, Vol 31, Issue 32, message 3)

Here's a timeline based on what I learned from the first of the Atlanta, GA, USA mapping parties (prep work for SOTM '10). Warning: contains shameless plugs.

Week before the event:

 1. Use JOSM to compare the existing map data against the aerial imagery.
 2. If the imagery is high enough resolution, identify and tag as many
 landmarks as practical (buildings, parking lots, etc...)
 3. Divide the campus out into to whatever size chunks make sense to you
 and make sure there's at least 1 GPSr available per chunk.
 4. If possible, start assigning chunks to people as they sign up for the
 event. Try for groups of 2-4 mappers.
 5. Make sure you have access to a flatbed scanner.

Day before the event:

 1. Go to and print hard copy reference maps of
 each chunk at various zoom levels.  Make sure to leave some overlap between
 printouts. Mark each printout with whatever chunk it applies to.
 2. Install JOSM, GPSBabel, Yahoo Imagery fix for JOSM, etc... on each
 workstation that will be used after the walking portion of the event.
 3. Install whatever JOSM plugins you feel are appropriate. (walking
 papers, buildings tool, WMS, usertools, etc...)

Start of the event:

 1. Pass out pens, walking papers and GPSrs to each mapping group.
 2. Make sure each group knows how to use the Average function in the
 3. Have each group use the walking papers to sketch / write down their
 observations.  Whenever practical, shoot a waypoint next to anything
 interesting and mark the waypoint number on the walking papers (saves time
 trying to name the waypoint in the GPSr memory).  Alternatively, use
 netbooks with the LiveGPS and Surveyor plugins)

After finishing the groundwork portion of the event:

 1. Have one person collect and start scanning all of the walking papers.
 2. Have each group use GPSBabel to generate 2 GPX files from their
 1. File 1 should be only the waypoints without any tracks.  - Each mapper
    in each group will need a copy of this file.
    2. File 2 should be the tracks without any waypoints. - Upload this
    file to the OSM servers as a public trace.
    3. (NOTE: This was a workaround for a JOSM bug that kept waypoints
    from importing if the GPX file had tracks in it).
    3. Pass the paperwork back to each group.  Open the waypoints GPX in
 JOSM, and download the OSM data for the area.
 4. Use the walking-papers plugin to download the scanned paperwork as a
 rectified image in JOSM.  (Note: there's a bug in the walking-papers plugin
 that will freeze JOSM if you download the walking-papers imagery before the
 OSM data.)
 5. Start Mapping.

Hope this helps, DiverCTH (Chris)

Foxandpotatoes 13:20, 19 September 2009 (UTC)

Guide pour ajouter un radar sur OpenStreetMap

D'après Tuxicoman | 20 septembre 2016 | Article | 3 commentaires

Voici comment ajouter un radar dans Openstreetmap et qu’il soit visible dans OsmAnd.

Placer un point en dehors de la route, à l’emplacement du radar. Ajouter les attributs suivant au point:



Vu que le point est hors du chemin, ce n’est pas suffisant pour qu’il soit pris en compte lors de la navigation. Il faut ajouter une relation qui aura les attributs suivants :




name=speed camera

Enfin, il faut ajouter les points à la relation. Le point « device » est celui qui correspond à l’emplacement du radar. Le point « from » celui du début de la zone surveillée par le radar. Le point « to » celui de la fin de la zone surveillée par le radar.

Dans l’éditeur de carte JOSM, ca ressemble à cela: radar-osm relation-radar-osm

3 COMMENTS AW 20 septembre 2016 Hello,

Concernant les radars en général, comment connaitre le début et la fin de la zone surveillée ? Comment cartographier un radar de feu rouge ? Pour l’instant, et pour pouvoir les repérer, je mets maxspeed=0 et une note et/ou un fixme.

Bàt. gaziel 20 septembre 2016 Bonsoir quel attribut pour un radar de feu rouge ? ++ Tuxicoman 21 septembre 2016 Je n’ai jamais mis de radar de feu, désolé. ---

Fortifications tagging guidelines (Works ahead ...)

Key Value Element Comment Rendering Picture
building fortification Node Area Way * * *
ruins yes Node Area Way if applicable P l i 2 on kerb marked.jpg
fortification_type castle * * * [[]]
castle_type For more values, see : * * * *
fortification_type fortress * * * *
fortification_type bunker * * * *
fortification_type fort * * * *
* * * * * *
* * * * * *
* * * * * *
building=fortification fortification_type=fort historic=yes disused=yes