From OpenStreetMap Wiki
Jump to navigation Jump to search

recycled plastic enviro path surface

Recycled plastics are being used for some paths e.g. National Park path over sand - What is the correct surface for these type so that these can be measured and identified easily? Ewen Hill (talk) 12:55, 9 July 2019 (UTC)

Recycled shredded polymers are widely used for equestrian arenas and ménages, amongst others, in the UK. Perhaps a tag of surface=fibre would cover these and any other similar materials?
Here's a link to a page describing the types of fibre material commonly used, at least in the UK:-
Recycled plastic fibre material.
For the path example in the Mapillary image above perhaps surface=sett with material=plastic? --John Grubb (talk) 17:33, 21 July 2019 (UTC)

gravel / water-bound / macadam

The two images for "gravel" seem to show two different sorts of surface:

Surface gravel.jpg

the lower one gravel clearly without sand


the upper one might be a mixture of sand and gravel, also called "water-bound macadam"

Should "gravel" also be used for "water-bound macadam"? Or should we divide them: gravel mixed with sand (macadam) from gravel without sand (less quality for bicycles)? --Mueck 21:47, 17 April 2009 (UTC)

  • (I swapped your images: think their positions match your words now :)). Distinguishing compacted sand+gravel mixes from loose gravel would be really useful round here. What do you say to:
Key Value Description Photograph
surface gravel Any surface consisting of aggregate material (rock chippings, bits of sand, pebbles or slag: all mixed together). The surface can be compacted or loose: this is a rather general tag, for backwards-compatibility reasons (photo showing several types?)
surface compacted_gravel An aggregate surface consisting of gravel chips (possibly mixed with sand or smaller particles) which has been rolled flat to make a fairly smooth, tightly-bound surface. Surfaces with this tag should resist being dug into with a bike wheel or a toe tip even if the top layer has a few loose stones. Surface gravel.jpg
surface loose_gravel An aggregate surface consisting of gravel chips which haven't been rolled flat or bound together with anything. Can be tricky to cycle along. Surfaces with this tag can be scraped away or dug into with a bike wheel or toe tip. Dscf1582-800.jpg
  • Both forms can go by the name "water-bound macadam", if I'm reading wikipedia:Macadam, so we should perhaps not use that term (similarly, "tarmac", which can mean all sorts of things in everyday usage). For me, the important quality is compactedness vs. looseness rather than binding agents - two-wheelers tend to go sideways on the loose stuff, but compacted gravel surfaces can be quite nice. I've also left the existing surface=gravel in there for backwards-compatibility purposes. --achadwick 21:40, 23 April 2009 (UTC)
  • Should we distinguish between deliberately-rolled surfaces that have been compacted with a roller and those that have had some compaction from passing vehicles? --achadwick 21:40, 23 April 2009 (UTC)
Because of possible rendering of surface values the next days or weeks I hurried up a little bit ;-) and added compacted to english and german surface-page. It is shorter and more flexible, because not only gravel may compacted. Some of the pebblestone-images also look very compact ;-) To the last question: We should look (only can look ...) at the result, not the method ;-) I don't know, if we should divide between gravel an loose_gravel, too, if compacted exists? --Mueck 21:32, 24 May 2009 (UTC)
*Every* way made of stone material will be compacted in time, either by a rolling machine or by regular usage. This isn't a criterium to be distinguished by a mapper. What he just *can* (and needs to) distinguish is whether a surface looks hard or soft, loose or firm. A macadam way/ waterbound surface (as invented by the Roman empire) has a firm surface, if well maintained. A gravel way has a loose surface, because it misses the binding (fine) components, although it may be compacted by masses of the traffic. As a consequence, a waterbound surface is good to walk, cycle, or ride on, whereas a gravel way bad to use, because the stones are loose. This is what needs to distinguish with stone material way, and this can be done easy and with relevance (as opposed to 'smoothness' what nearly every person sees different). 'Compacted' is unclear, 'gravel' and 'fine_gravel' quite clear. 'macadam' is more precise than 'fine_gravel' but very little known or common. So my vote is that gravel and fine_gravel are enough. You don't need more on common regular ways used by agricultural or forestry vehicles, except asphalt/concrete or dirt tracks. 'fine_gravel' just dont't mean that this way is made exclusively out of fine gravel components (this kind of way would be loose, don't last long, or endure heavy vehicles), just that fine_gravel is what can be seen on surface. A waterbound way made with a fine gravel surface is next to asphalt the best and most costly way, both in creating and maintenance, that's the reason why simple gravel ways can be seen more often in some areas -- Besides, the describing picture shows a way that lacks rolling and is just filled up, no way compacted. If this would have been done prior to the image, the passenger car wouldn't have created deep ruts like shown (Don't drive or ride on a waterbound way freshly made) --Taunide 18:54, 20 October 2011 (BST)
fine_gravel is a part of waterbound, but waterbound is not only fine_gravel.
"whereas a gravel way bad to use, because the stones are loose"
fine_gravel might be loose, too, for al longer time, if it is not used like in a proces for building waterbound macadam ways ... --Mueck 22:43, 20 October 2011 (BST)
Again, the pic here don't match your description what you want "compacted" should be, cause it's not showing a compacted surface, as could be seen in the tire ruts, period. If you want to promote "compacted" for this type of ways and be understand by other mappers you should start with a better picture and clearer description what's the difference to "gravel". --Taunide 10:47, 24 October 2011 (BST)
Not compacted? The street on the image looks very plane. It wouldn't be such plane, if it is not compacted. If not compacted, the tire ruts would be deeper ... Depending of usage of a way, there may be also some loose material on it ...
It might be, that your image is a better image for *compacted*...
Changing the old image for *fine_gravel* showing loose material to your new image for a compacted way is no "evidence" for your single person theory that fine_gravel is compacted ... --Mueck 16:45, 25 October 2011 (BST)
The old image didn't show a specific way, just a raw material, so the newer is better. Every way with a fine gravel surface needs to have a compound base structure, or it would not withstand pressure of heavy vehicles. I will not repeat myself here. We had the tag fine_gravel for more than a year without a definition and nobody seems to have a problem with it. Now I delivered a definition according to reality and tagging practice, what's the hell is your problem with it? --Taunide 09:21, 26 October 2011 (BST)
And compacted is defined for 2.5 years including ways like this on the new image. That's the problem we have had in with your single point of view ... And why should fine_gravel only be used for ways with heavy vehicles? And were is said, that loose gravel don't can have something stable beyond it? fine_gravel only defines the upper layer of a way like gravel, asphalt, sand, ... which all may have something beyond it, that we didn't see ... It's the upper layer, we only can map, and that's for your waterbound way NOT only fine_gravel. If the base layer of the way isn't stable enough for heavy vehicles, you will see it of deep tire ruts and can tag smoothness=bad or something like this, that's not a question of surface-key ... --Mueck 10:06, 26 October 2011 (BST)
You contradict yourself. If "outer surface" is all we can see (and should be mapped with this attribute) then "compacted" is wrong because it can't be seen. The fact that people bring a picture to show a "compacted" way which shows imprints of a small motorcar which demonstrates this way misses compaction at all, because compaction is made by rollers, not by vehicles simply using the way. Then "fine_gravel" and "gravel" are perfect: that's what can be seen!
Of course you can use "fine_gravel" for small park and garden ways alike too, but in the most common areas where ways like these showing up (and be mapped!): fields and forests you will see them with a firm underground, which in most cases can easily detected by most mappers as my pic shows. So that's the reason for this refreshed, typical picture.
As said above, an additional attribute (smoothness) brings no help. Fine_gravel is clearly defined so it's quite easy to decide when to tag gravel or fine_gravel (it may be not so clear with "gravel" and "compacted" but that's the problem of that's definition...). In contrast, every mapper has a different understanding of what is "smooth", so this attribute is next to worthless. With thousands of mappers all is needed here are CLEAR definitions -- with no more attributes as indespensable for clear description of a certain map item!
The problem with 'compacted' is, as stated above, that nearly all "gravel" ways are compacted too (at least if used by heavy vehicles), and therefore, mappers cannot decide what to tag. Keep on with it, if you like it, but keep fine_gravel too. Taggings will be much more impartial/objective.
--Taunide 11:31, 27 October 2011 (BST)
It's NO problem to see, if a way has only loose material or not.
In the german forum I posted just another (german) example from another user for uncompacted fine_gravel ways. --Mueck 22:09, 27 October 2011 (BST)
How to objectively distinguish between fine_gravel and compacted? The OSM-Wiki description is vague. According to Wikipedia macadam has a minimum stone size at the surface of 2cm and may be filled up with stone dust (water bound). Fine gravel is not allowed in a macadam road. In contrast a "fine_gravel" road has fine gravel on top and can be filled up with stone dust too. So the only difference between these two is the usage of fine gravel? Any objections adding this info to the OSM-Wiki?--Lukie80 (talk) 21:18, 2 May 2017 (UTC)
fine_gravel implies not compacted, it is a loose covering, while compacted means a hard surface without or with few loose material--Dieterdreist (talk) 23:13, 2 May 2017 (UTC)

"I need a surface tag for..."

Generally speaking, if you find you need a tag for something that isn't listed, have a look through the tagwatch listings (example) for the surface types that people have been using in the past, and copy them! Bear in mind though that this is largely driven by JOSM's presets.xml and the surface values it contains - people are lazy and tend to pick what's suggested :) --achadwick 21:53, 23 April 2009 (UTC)

Or OSMdoc --Mueck 21:35, 24 May 2009 (UTC)


Hi, I created a new tag for the middle of the way, for details see: User:John07/middle_tag Please leave some comments. John07

Cement vs. concrete

(moved from definition to discussion page) Why doesn't surface=cement exist? People generally think of a cement surface as being very smooth, good for tennis courts and skate parks, while concrete is very rough and good only for vehicles. (by unknown)

In actuality, both surfaces are made of concrete! The former is cement mixed with fine sand, the latter is cement mixed with sand and gravel. surface=concrete applies to both. (by unknown2)
the difference between cement and concrete is that concrete is cement plus filler. Whether the concrete is rough or not depends on the treatment of the surface and on the grain size of the filler ingredients. cement usually is deployed with filler, pure cement is usually not used (but the filler might be very fine). -- Dieterdreist 15:40, 15 July 2010 (UTC)
There is also a tag smoothness=*, no need to tag different concrete surfaces. --Scai 18:33, 16 July 2010 (UTC)
It makes a big difference which surface you have, they all sound different with a white cane, see OSM for the blind. Not only persons on wheels are interested in the surface. Lulu-Ann
Though concrete implies that a type of filler is used, it doesn't imply what type filler is used, and therefor say nothing about the smoothness of the end product. Concrete using fine gravel as filler is almost as smooth as pure cement, and with a treated surface makes no difference, while a concrete using a coars gravel often can be rougher, even with treatment. Therefor these two should be treated the same as a surface tag, while another tag can be used to describe the smoothness (smoothness=* is already in use) --Skippern 09:36, 20 July 2010 (UTC)

synthetic surface for sport pitch?

Some pitch use synthetic (not grass but synthetic for football) maybe this would be great to be added for football pitch to have surface=synthetic.--Yod4z 13:46, 12 September 2010 (BST)



Any objections about using this image for fine_gravel? --Michi 21:58, 17 November 2010 (UTC)

Have you ever tried to grab a "handfull of fine gravel" off a fine gravel way? This is just impossible because of it's compacted structure. "fine gravel" is just a surface. A fine gravel way consists of different types and sizes of stones. Just made out of fine gravel it wouldn't last long or endure heavy vehicles.
A good picture would show a way paved with fine_gravel, like this one: [[1]] --Taunide 19:13, 20 October 2011 (BST)
That's a nice image for "compacted". fine_gravel is only one part of waterbound macadam. Ways using fine_gravel only are sometimes found in gardening --Mueck 22:28, 20 October 2011 (BST)

::: I agree. "fine_gravel" should be loose like in gardens, in parks and in the mountains. "compacted" should be a compressed mixture of fine gravel and stone dust and is not loose at all.--Lukie80 (talk) 20:58, 24 April 2017 (UTC)--Lukie80 (talk) 20:49, 2 May 2017 (UTC)

Does anyone know, where "fine_gravel" is "created"? I only found, when it enters this page (18 Sep 2010 by Cmuelle8), but no discussion ... --Mueck 22:47, 20 October 2011 (BST)

fine_gravel, gravel, pebblestone fractions are created in a gravel pit or a quarry. Sorting is carried out using stationary or mobile :machines.
--Cz ja 16:15, 27 January 2018 (BST)

Steel grid bridges

This might be a North-American peculiarity, but we have quite a number of steel grid bridges here. An example image would be this. Having the ability to tag this would be great, especially for cyclists for whom this type of surface can be quite dangerous. Any thoughts? --Hobbesvsboyle 04:00, 29 March 2011 (BST)

I believe the best term would be 'metal grate' or 'open grate' - best not to include the type of metal. The latter is used on at least one sign: --NE2 06:46, 31 March 2011 (BST)
That makes sense. "Steel grid" is the only term I've heard around here (Upstate NY); we have one bridge with a warning sign in town and I'll check what it says. --Hobbesvsboyle 03:01, 1 April 2011 (BST)
Okay, I checked, and the warning sign says "steel deck". I like the material-neutral approach, though, and will use the "metal grate" tags for now. --Hobbesvsboyle 20:05, 5 April 2011 (BST)

surface=stones, surface=rock

Paths for non-motorised use (highway=footway, highway=path etc) should ideally always be tagged with surface. How can we tag the surface of paths full of either small or large rocks and stones. I would propose surface=stones.

Besides, I would also add surface=rock for rocky trails in the mountains, i.e. when the surface is a compact rock rather than many single rocks or stones. --solitone 16:50, 19 January 2012 (UTC)

surface:cycleway and surface:sidewalk

Cycleways tagged as cycleway=lane or cycleway=track often have different surfaces than that of the main road but currently such surfaces can't be tagged. I propose to introduce surface:cycleway=* to describe the surface of an associated cycleway that is not mapped as a separate way. Similar for an associated sidewalk=* where the surface could be tagged as surface:sidewalk=*. Any objections to add these tags to the main page? --polderrunner 21:38, 24 September 2012 (BST)

Hi, it is possible to tag this: cycleway:right:surface=* See TagWatch. You can replace the "right" with "left", "both" or without the middle subkey: cycleway:surface. (Note: footway:right:surface=* TagWatch is also more common than surface:footway=* TagWatch)--MasiMaster 13:46, 25 September 2012 (BST)
Ok, I didn't know about those tags. I had only looked for surface:*-something and found nothing (except the few cases I have tagged). Normally I would expect the first part of the key to be the tag type followed by subkeys to define the scope of the tag. That is how it works for e.g. oneway:bicycle or maxspeed:hgv. Since the 'reverse' tagging style is already in use for surface I won't go further with my proposal even though I'm not happy about the syntax of these tags. BTW, why do most of these tags specify the side of the road, that seems a bit redundant? --polderrunner 16:42, 25 September 2012 (BST)
Good question... Don't know why, but if on both sides is the same surface, you can use cycleway:both:surface=* or simplier cycleway:surface=*. --MasiMaster 18:17, 25 September 2012 (BST)
Please consider documenting those tags somewhere in the wiki, not everybody uses taginfo to search for them. --Scai 07:56, 26 September 2012 (BST)
I simply added this to Key:cycleway and DE:Key:cycleway. Feel free to edit or correct this. I plan also to add this to the Key:footway page. OK? --MasiMaster 15:40, 26 September 2012 (BST)
Seems ok to me, thanks. --Scai 19:18, 26 September 2012 (BST)
Would it be possible to also document these tags at surface=*? Many mappers would start looking here and not at cycleway=* for such surface tags. And don't forget the sidewalks! --polderrunner 20:20, 26 September 2012 (BST)
Now I added this at surface=*. In my point of view sidewalk can be a additionaly value for footway, like track/lane for cycleways. Syntax for sidewalks does not work (so I don't add this to footway & sidewalk):
I think this part better belongs to the footway- or sidewalk-talkpage. --MasiMaster 15:26, 27 September 2012 (BST)
footway=sidewalk is always (should be) used on separately drawn ways with highway=footway (or highway=cycleway, when cycling on sidewalk is allowed). "This is a footway + this footway is a sidewalk." Compare to sidewalk=left/right/both. Alv 18:50, 27 September 2012 (BST)
So what should be used for the surface of a sidewalk when it is marked as a property of the road (and not as a seperate pathway)? PinkShinyRose 17:07, 4 January 2013 (UTC)

Different surfaces on a segregated foot-/cycleway

How can we tag different surfaces on a segregated foot-/cycleway? I.e. cycleway-section has surface=asphalt and footway-section has surface=paving_stones. --MasiMaster 15:31, 27 September 2012 (BST)

Presumably an expansion of the access tags for the way could be used, such as foot:surface= and bicycle:surface= ? Or surface:foot= / surface:bicycle=. Or would it be surface:footway= and surface:cycleway=...? --John Grubb (talk) 15:44, 20 February 2019 (UTC)
If if is tagged with highway=footwag, maybe cycleway:surface=asphalt might be easiest for data consumers (since that tag should override surface=* when looking for bicycle routing. Otherwise, drawing the footway and the cycleway separately should be preferred here. Bxl-forever (talk) 09:48, 28 March 2019 (UTC)


This is often used at playgrounds to provide natural cushion, see rendering should probably something red-brownish --Stefanct 12:08, 23 December 2012 (UTC)

Existing values include:
--NE2 03:24, 24 December 2012 (UTC)
Is it worth distinguishing from surface=woodchips? Mateusz Konieczny (talk) 16:17, 3 June 2021 (UTC)


How about grouping physical condition of highways?

Like this (sport and path surfaces will be in another section):

From left (general tag) to right (more detailed surface description)

I think it's more intuitive than now.

General tag Tag Smoothness Description
surface=paved asphalt


metal (bridges etc.)

wood (bridges etc.)

excellent perfect surface (roller blade, skate board and all below)
good no bumps or potholes (racing bike and all below)
intermediate some bumps (city bike, sport cars, wheel chair, Scooter and all below)
bad damaged road (trekking bike, normal cars, Rickshaw and all below)
very_bad heavily damaged road (off-road vehicles and all below)
horrible close to impassable, huge potholes (ATV, tanks)




bad See above ^
surface=unpaved compacted excellent same as fine_gravel now
bad See above ^


bad See above ^








Fairly smooth surface


See above ^


See above ^
Paving stones may have "excellent" smoothness and so on Mateusz Konieczny (talk) 17:48, 10 March 2020 (UTC)

Ground vs earth

Following from this discussion in the tagging mailing list, it seems that ground and earth may be essentially the same thing. Since earth is much less used, could we recommend against using it and recommend using ground instead? This simplifies application development, translations and teaching significantly.--Fernando Trebien (talk) 14:42, 13 March 2014 (UTC)

+1 I'd rather have just one value, and ground seems the best choice.--solitone (talk) 15:22, 13 March 2014 (UTC)
Yes, there is no point in two different values for the same. Bulwersator (talk) 08:47, 1 May 2014 (UTC)
+1 I propose to change the wiki to deprecate the use of earth and dirt and use ground instead. --Viking81 (talk) 09:58, 8 April 2016 (UTC)

cobblestone:flattened vs sett

The wiki seems to discourage this value, and suggests sett instead. Besides, cobblestone:flattened and sett have the same picture. To me, "cobblestone:flattened" describes a pretty different paving, as show in these pictures [2], [3]. By contrast, these are examples of what I would consider "sett" [4], [5]. Can we describe better these two values?

—Preceding unsigned comment added by Solitone (talkcontribs) 13h17min de 28 de abril de 2014‎ (TC-3)

-1 Can't we use "stone" for that?
Yeah it's confusing which tag we should all be using. The page here has grouped "setts" under surface=cobblestone. "Cobblestone paving. "Cobblestone" is used in the colloquial meaning and includes the type of stones that would more precisely be called "setts"." but then it also lists surface=cobblestone:flattened with no description.
It's been that way since the big table of values was added this edit, and so since then it's never been very clear what "setts" should actually be mapped as. The problem is, many people including me would actually look at these "setts"/"flattened cobblestone" in real life, and we'd call them cobblestone, without making a fussy distinction. You only have to look at a google image search for 'cobblestone' to see that this word encompasses a variety, and mostly equates to setts/flattened cobbles these days.
As a result the majority of surface=cobblestone instances in the database will probably be setts/flattened cobbles in reality. Maybe that doesn't matter, but I think the situation would clearer without the 'cobblestone:flattened' tag suggestion on here.
Clearer would be 'cobblestone=flattened', an extra tag to allow anybody who worries about the distinction to make it.
-- Harry Wood (talk) 10:34, 30 August 2014 (UTC)

Current scheme bears all the legacy of direct adopting of natural language terms, and it seems to be really bad. surface=sett or surface=cobblestone:flattened are obviously reflecting the same real life entity - roughly squared stones, which are sub-classes of more general surface=cobblestone. In the same time, there is no specific tag for natural shaped (rounded) cobblestone. Therefore, if we have something tagged with surface=cobblestone, it has two contradictory meanings: "any kind of stone" and "not flattened stone", which is inadequate. --BushmanK (talk) 19:35, 6 December 2014 (UTC)


The wiki says that paving stones are equally sized concrete stones, with a flat top [... and] a perfectly regular shape.

I reckon this value may also be used for natural stones with a similar shape, e.g. [6].

I would therefore remove the word concrete from the description. --solitone (talk) 09:12, 29 April 2014 (UTC)

I think, it should be emphasized in the beginning, that paving stones are mechanically (by sawing or press-forming) perfectly shaped natural or artificial stones, intended to form regular pattern. They are not necessary equally sized, because there are paving patterns, utilizing more than one size of stones.
Current description does not give clear way to distinct paving stones and sett stones (latter ones are just roughly shaped to be rectangular). --BushmanK (talk) 19:21, 6 December 2014 (UTC)
Yes Solitone I agree with you. The current description seems to emphasise concrete a bit too much.
Also the illustrations show very small stones (which I would be tempted to call "tiles") forming regular patterns. Reading "paving stones" I tend to imagine larger paving flagstones like this: File:Pavement in North London.jpg. In this photo these are actually concrete flagstones, but yes an even more typical "paving stone" would be made of ...stone. Also I wouldn't say they do need to be equally sized. Can be a haphazardly sized, but the difference with setts is that they're flatter and more precisely tessellated. Unless I'm missing a better tag for this photo (let me know) I'll change the description a bit, and use that photo in place of one of the smaller tile photos.
-- Harry Wood (talk) 12:38, 18 January 2015 (UTC)
The way I understand it, mechanically perfectly shaped natural stone is tagged with sett. I've modified it.The RedBurn (talk) 09:29, 12 October 2016 (UTC)


I propose to remove maxspeed:practical recommendation, this idea was clearly considered as bad - see Key:maxspeed:practical#Voting Bulwersator (talk) 06:42, 23 August 2014 (UTC)

Not before there is a better alternative. A maxspeed:practical=15 on a desert dirt path is clearly 100 times more useful than any number of surface and tracktype attributes. RicoZ (talk) 09:04, 23 August 2014 (UTC)
Are you sure that it is a good idea to recommend adding it everywhere? Bulwersator (talk) 09:30, 23 August 2014 (UTC)
Everywhere where it is not realistic to guess a reasonable maxspeed from other attributes. There were already long discussions about tracktypes and some other of those attributes on the mailing lists, they are just as bad mess and subjective as maxspeed:practical. maxspeed:practical at least gives a numeric value which everyone can see and correct instead of second guessing what routing software might deduce from half a dozen of subjective attributes and country specific implicit assumptions.
The maxspeed:practical proposal should be imho improved to allow specification of vehicle types and things like seasons (including rainy season etc).RicoZ (talk) 10:00, 23 August 2014 (UTC)

stepping stones?

How about surface=stepping_stones? The value already exists for fords and I have used it here - but many times these ways are not through water so highway=footway+surface=stepping_stones would seem quite fitting. RicoZ (talk) 10:59, 30 August 2014 (UTC)

I've used this, seems like a good idea. Has existing use Here is an example, it's not crossing a river it's just to provide better footing at high tides. --Aharvey (talk) 13:11, 22 September 2020 (UTC)

Some language terms are country-specific

Ex: I have seen "macadam" used to describe both gravel and bitumen surfaces. In NZ a "metal" road is a gravel road. The gravel is also referred to as "road metal".

Because of this, use of these words needs to be avoided. --Beddhist (talk) 13:38, 25 August 2015 (UTC)

Children playground's surface

Hi all, tonight I went to a playground which I personally added to OSM, and noticed that the pavement wasn't made of concrete as I expected, but rather of that soft looking-like-tartan material (which allows children to softly land on the ground).

How could I map it? --Massic80 (talk) 22:07, 30 July 2017 (UTC)

surface=rubbercrumb ? RicoZ (talk) 12:07, 1 August 2017 (UTC)
Uh, I just noticed Tag:leisure=playground: thanks for the advice! --Massic80 (talk) 14:51, 1 August 2017 (UTC)

Rough trail surfaces of natural stones


There are two kinds of surface for hiking paths I have always missed in the values (and can’t even tell if they belong to the paved or unpaved section).

First, trails in mountain regions are often secured against erosion by setting large natural stones found on the spot (size well above 20 cm). This makes a rough, steppy, hardly-driveable but very robust surface.

I started to tag them surface=stone which has been used more than 3,000 times according to taginfo, but now I think this value is too unspecific and might include pebblestones, cobblestones or sett as well. I suggest to tag them surface=natural_stones (the singular natural_stone might suggest a closed rock surface instead of single stones).

Second, how about stoneflagged trails? I’ve often met them in England on trails crossing boggy ground. I suppose they’re simply made of natural stones roughly split into plates. I suggest to tag them surface=flagstone.

--Kreuzschnabel (talk) 06:00, 13 August 2017 (UTC)

  • "setting large natural stones" - I tag it as surface=cobblestone Mateusz Konieczny (talk) 21:08, 13 August 2017 (UTC)

Compacted vs dirt/gravel/etc.

Maybe we should state more clearly that the surface can only be considered compacted if it resists heavy rain and heavy loads (such as trucks). --Fernando Trebien (talk) 12:48, 27 December 2017 (UTC)

I think it would be difficult to judge solely on visual inspection. But you are right, there is no visual difference between compacted and fine_gravel according to the Wiki. Only the durability, which is defined by lower layers, defines the difference between both.

Cobbles should be described as rounded for clarity

According to both cobble on Wikipedia and this British consultant. --Fernando Trebien (talk) 11:28, 15 January 2018 (UTC)

+1 for rounded for cobblestones --Althio (talk) 09:58, 16 January 2018 (UTC)

This forum post summarizes some wikifiddling here and puts it in light of the opinions of British mappers (native speakers) and German mappers (which look like would be those most affected by any changes in definitions). --Fernando Trebien (talk) 13:56, 22 January 2018 (UTC)

Pebblestones for foot massage

Some trails are made of stones for foot massage. Mention how to tag.

Jidanni (talk) 14:21, 19 August 2018 (UTC)


The description is confusing, especially with the accompanying photograph.

"Long, narrow concrete elements for a two-tracked vehicle (motorcars) so that the tires always hit the concrete. There might be sand, ground, grass, pavers, asphalt, etc. in between them. Note that if you tag a single-tracked way you just use concrete, since there are no lanes."

The photo shows a single track way with two concrete strips, one for left-hand wheels, one for right. Around my way (rural south-west UK) these are commonly used on agricultural land where the farmer needs a hard roadway for access but also needs to reduce costs on materials (and because they may not need as many planning hoops jumped through). As they are not intended for public use and thus not subject to heavy traffic the rough strip in the middle is not an issue. I would contend that this type of roadway can be described by this tag but that it is very much applicable to single-track "roads" as this is the most common usage. I can't recall ever having seen a two-lane road built in this manner. I would suggest that the description be revised for clarity/accuracy, especially given the accompanying example in the photo. Views...? --John Grubb (talk) 15:19, 6 September 2018 (UTC)

surface unpaved

I am located, and doing editing, in a very rural part of north Florida. Many of the counties here are minimally funded, and unable to provide proper road pavement for tertiary streets. Their default road surface is crushed lime rock, which is delivered by the truck load (as required) and then smoothed with a road grader. The surface can, under ideal conditions, harden to something approaching the original limestone. Under less than ideal conditions, it sometimes develops 'sand pools'. I am coding these rural tertiary roads as surface=unpaved, although I wish there were a better choice. surface=compacted does not appear to fill the bill, although the lime rock is compacted in a form. I am open to any suggestions that more appropriately indicates the surface, as unpaved is quite non-specific.

RayOnTheFarm (talk) 13:42, 9 April 2019 (UTC)

Can you link some images of the situation? Based on description it sounds like surface=compacted to me Mateusz Konieczny (talk) 18:05, 9 April 2019 (UTC
I concur - surface=compacted seems to fit. Alternatively, as the limestone is crushed then perhaps surface=gravel would be appropriate? --John Grubb (talk) 10:56, 11 April 2019 (UTC)
Based on images it clearly surface=compacted. I created Tag:surface=compacted and added some detail about damage of compacted road Mateusz Konieczny (talk) 16:53, 12 April 2019 (UTC)
Having now also seen the photos I would agree that it is definitely surface=compacted. --John Grubb (talk) 18:18, 12 April 2019 (UTC)

I have the images, but for various reasons I am unable to get them to either upload to the wiki, nor to link in from Google Drive. Will work on it more tomorrow. --RayOnTheFarm (talk) 13:46, 10 April 2019 (UTC)

Default values

I do not believe these changes are actually supported by the links to a thread in which only some participants expressed that opinion. Other responses, e.g. [7], do not seem support the "add surface to every single road" recommendation. If the wiki comments on the topic at all, it should reflect these differences in opinion. --Tordanik 12:43, 6 March 2020 (UTC)

Do you think that is sufficient? Or maybe adding something about of minor value of surface=paved (especially on highway=motorway and other where it is obvious) or surface=unpaved (especially on tracktype=grade5 and other obvious cases)? Mateusz Konieczny (talk) 20:16, 6 March 2020 (UTC)

Really just "wood"?

surface	wood	 	Used for wood surfaced bridges, plank walkways, and garden decking

Perhaps differentiate plain wood vs. treated lumber, composite lumber[8]. Jidanni (talk) 03:18, 19 April 2020 (UTC)

Feel free to tag additional detail with a separate tag. For example surface=wood + wood=treated_lumber Mateusz Konieczny (talk) 23:33, 29 April 2020 (UTC)

Acrylic surface and DecoTurf value

DecoTurf is not a common name, but a brand name, and acrylic is also used in basketball courts and other sports grounds. So I think 'acrylic' should be used as the value. --Lepus (talk) 08:12, 9 June 2020 (UTC)

Note that according to it is not just acrylic ("layers of acrylic resin, rubber, silica, and other materials on top of an asphalt or concrete base"). While a nonbrand name may be a good idea I am not sure is "acrylic" meaning clear. In general, note that tagging mailing list may be a better place to discuss this. Mateusz Konieczny (talk) 12:24, 9 June 2020 (UTC)
Maybe you can refer to the description of other hardcourt brand, such as "GreenSet is a brand of acrylic hardcourt surface" and "Plexicushion is a brand of acrylic-based hardcourt tennis surface". Most hardcourt materials are acrylic based. And "hardcourt" seems to refer specifically to tennis courts, I'm not sure if it can be used elsewhere. --Lepus (talk) 05:26, 10 June 2020 (UTC)

How to map seashell-covered roads

In the Netherlands, small seashells are commonly used as a surface on footpaths and bicycle paths, in a way similar to fine gravel (initially loosely deposited, incrementally more compacted and fine-grained when traffic uses the road). For example, see here and here. In practice, I think these roads are oftend tagged as `fine_gravel`, but technically this does not conform to the description on this page, which is "A multilayer pavement with a stone or gravel basis and a topmost surface of firm, granular grit, basalt or quartz", but I would think shells are neither grit, nor basalt or quarts (though it seems that "Shell grit" is actually a term in use).

There are some roads tagged with `surface=shells`, which I suspect refer to this kind of road (this tag is almost exclusively used in the Netherlands it seems), but this is not documented here.

So, what is the recommended tagging for these roads? I suspect it is `fine_gravel`, then maybe the description could be adapted to make this explicit? If it is `shells`, then maybe that should be added to this page?

--Matthijskooijman (talk) 20:13, 4 August 2020 (UTC)

Colored pavement

See Talk:Rendering of road surface in standard OSM style#Colored pavers for thoughts about when a trail is actually red, blue, etc. Jidanni (talk) 05:13, 4 February 2021 (UTC)

Australian 'gravel road'

An Australian 'gravel road' typically contains a range of particle sizes ranging from clay to 20mm screenings. This range of particle sizes compacts to a firm road and might be maintained by annual grading. It is less commonly called a 'dirt road'.

Gravelsign.jpg Gravelcomposition.jpg

Gravelsign2.jpg Gravelcomposition2.jpg

Gravelsign3.jpg Gravelcomposition3.jpg

Below is a surface that may match the current description of surface=fine_gravel. I would descibe it as grit, the tourist authority call it granitic sand, it is not sand , it includes a range of particle sizes and compacts to a semi durable surface. The photo is of a bike trail, the Great Victorian Rail Trail Yea, Australia.

Finegravel.jpg Finegravelcomposition.jpg

Tonyf1 (talk) 07:27, 5 March 2021 (UTC)

@Tonyf1: The first three seems to match surface=compacted Mateusz Konieczny (talk) 08:50, 5 March 2021 (UTC)

Stone slabs / stone blocks

Hi! I'm looking for a surface=* value for stone slabs or blocks. Many steps are made of stone slabs or stone blocks and there are also footpaths made of stone slabs, such as in parks.

There are a few uses of surface=stone:plates (71) and surface=stone_plates (51), but that doesn't quite fit for stone blocks, although it doesn't make a difference in terms of the surface. Any opinions or ideas? --Dafadllyn (talk) 18:20, 9 March 2021 (UTC)

First and third looks like surface=paving_stones and I tagged them this way. Second I would mark as surface=sett Mateusz Konieczny (talk) 18:43, 9 March 2021 (UTC)
Another example of steps made of stone slabs
Thanks for your reply! Setts are much smaller stone blocks than the stone slabs (or stone blocks) used for steps. Aren't paving stones smaller too (see the examples for surface=paving_stones)? The slabs and blocks i have in mind are much larger, similar to surface=concrete:plates, but made of (natural) stone. --Dafadllyn (talk) 19:49, 9 March 2021 (UTC)
I agree that typical ones are smaller but I would not consider size here as defining part. And this pieces, are still much much smaller than typical (at least in my region) surface=concrete:plates Mateusz Konieczny (talk) 23:56, 9 March 2021 (UTC)
Actually, the definition of surface=paving_stones is a bit unfortunate anyway, because setts, cobblestones and grass pavers are usually also counted as paving stones. I'm still not completely convinced to map stone slabs and especially stone blocks as surface=paving_stones. Maybe some data consumers (e.g. cyclists or blind people) were interested in the difference between small artificial stones and bigger natural stone slates or blocks? Some other opinions? --Dafadllyn (talk) 20:28, 10 March 2021 (UTC)

Definition of surface=dirt

The definition of surface=dirt is quite contradictory: the definition of earth, which seems to mean earth/soil, says that it is a duplicate of dirt. However, dirt is said to be "very similar" to ground, which can mean grass, clay, sand, earth, gravel or pebblestone. What does surface=dirt really describe? --Dafadllyn (talk) 19:46, 7 April 2021 (UTC)

@Dafadllyn: maybe someone meant that earth/soil is quite similar to ground in general? (or used a different meaning of "dirt" but not sure is it viable to have a different meaning for it) Mateusz Konieczny (talk) 16:31, 3 June 2021 (UTC)

Loose stone chippings

Some paths and areas in parks are made of loose stone chippings. Unlike surface=fine_gravel, bicycles do leave imprints or, if the layer of stone chippings is thick, get stuck. How to tag this surface? surface=stone_chippings? --Dafadllyn (talk) 20:11, 7 April 2021 (UTC)

@Dafadllyn: I have seen used and used surface=gravel for that (which has hopelessly wide meaning) Mateusz Konieczny (talk) 16:32, 3 June 2021 (UTC)
@Mateusz Konieczny: Thanks, but i'd like to be more specific. --Dafadllyn (talk) 18:51, 8 June 2021 (UTC)

fibre-reinforced polymer composite grate surfaces

I'm using fibre_reinforced_polymer_grate for the fibre-reinforced polymer composite grate surfaces eg or common on walking paths. Not to be confused with a metal grate which looks similar but but different material. These surfaces usually have a rough coating on the top for traction (compared to a metal grate which is more slippery when wet), but has holes to allow water to pass through. --Aharvey (talk) 08:08, 18 April 2021 (UTC) is not loading @Aharvey: Mateusz Konieczny (talk) 16:33, 3 June 2021 (UTC)
Maybe you can use surface=fibre_reinforced_plastic:grate directly (instead of "polymer") and following surface=concrete:*? Though the holes and permeability part could possibly be separately tagged.
---- Kovposch (talk) 02:52, 4 June 2021 (UTC)