of course this only applies to osm.org/way/21912165/history

Hey fuggi,

in this changeset you changed the tracktype to "3" (before it was "grade4"). I am correcting this to "grade3". I guess, this was just a mistake. But in case I am mistaken the wiki for tracktype: osm.wiki/DE:Key:tracktype

feel free to contact me

Cheers

sry, of course it only applied to this node osm.org/node/5736895787/history

Hello OF-1,

I just wanted to let you know that I changed your access value "Kunden Brauerei Berg" to "customers". I don't know if you know this value...

Cheers

Hey Theodin,

I guess the tracktype=grade1 was just forgotten to be removed here? Because we are on a highway=path here...

Cheers

Also true for osm.org/way/352844689 and osm.org/way/352844700

Hello fischerhuder,

may I suggest that you fallback to ground instead? From what I understand grass, clay, sand, earth, gravel or pebblestone are more specific values for ground. (And dirt is "probably very similar to ground"). So ground should be closer to reality-

unpaved could also mean "compacted".

Adding tracktype (to tracks) and smoothness is always a good idea :-)

Cheers and thanks for discussion
Ze0zohk1

PS: And also all the best for 2021

@Teddy73: Did you mean to use "highway=service" here?

Hello fischerhuder,

thanks for replying. First of all: ";" should be used when combining multible value (so sand and dirt is represented as "sand;dirt"). But the problem with such values are that data consumers have a hard time understanding them.

I would either stick with one value (or at least try it) or split the way. But honestly, when the surface changes every 20 m I would not split the way (just because it is too much effort). But that is up to everyone to decide. (Also you now how sandy the way really is.)

Also to consider: unpaved ways rarely really have just one single material as surface. So when 80 % of a way are material1 and 20 % material2 I think it is absolutely fine to use material1 as value.

Final words: I recommend reading osm.wiki/Key:surface and checking https://taginfo.openstreetmap.org/keys/surface#values for common values.

Cheers

@AlaskaDave: I know all of this. I am just curious what Sean Noble meant with this value. Imagine that there were a special material denoted "sand/dirt" which is not equal to "sand;dirt". Maybe sounds silly, but as I mentioned above, the value "sand/dirt" is pretty popular on taginfo (it is more popular than any other ";" combination). TLTR: I am interested in Sean Noble comments on the semantic of "sand/dirt" (and yes, I assume that the semantic is the same as "sand;dirt"). Cheers

Hey ew742, I think iD is just auto-completing. If the surface consists out of sand and dirt the value "sand;dirt" should be used. But two values are not difficult to handle by data consumers. So personally I try to choose the dominating value.

Hey AlaskaDave,

thanks for replying. I know, but that is the reasons I am asking. I was wondering, why there are so many uses (compared to other combinations) on taginfo. And I was thinking about if there is more to it...

Hello 4290_Landwirt,

please don't delete ways present in reality. Set access to no, if access is not allowed. Deleting ways which are present is vandalism.

Cheers

Hello jagdpächter,

thanks for you edit! I noticed your edits here some time ago. I hope you are still reading your OSM mails. You have added names to e.g. landuse=meadow like "Jagdfläche". This does not sound like a name for a meadow. The name tag should be used when it is really called "Jagdfläche". The name's purpose is not to describe the usage. Also the description should be more than one word. The description tag may be shown to users. E.g. name=Hexenwiese. description:en=On this meadow witches... some interesting store...

Also I noticed you added surface=Gras_Laub to many ways. English is preferred. If there are multiple values use ; to separate them. So e.g. grass;leaves (everything in lower case). However, it is preferred to use just a single value.

Feel free to reach out to me. Cheers

Hey ielham, thanks for your help! Cheers

Hey Sean Noble,

you tagged this way osm.org/way/732214733 with surface=dirt/sand. What does this mean? Does it mean dirt and sand (and if, shouldn't dirt;sand be used or is "/" convention in US?)? Cheers

Hey ew742,

you tagged this way osm.org/way/761817170 with surface=dirt/sand. What does this mean? Does it mean dirt and sand (and if, shouldn't dirt;sand be used?)? I am asking, because there are quite some usages on taginfo and I don't understand, what is special about this combination. Cheers

Hey Betafranz,

you tagged this way osm.org/way/877900114 with surface=dirt/sand. What does this mean? Does it mean dirt and sand (and if, shouldn't dirt;sand be used?)? I am asking, because there are quite some usages on taginfo and I don't understand, what is special about this combination. Cheers

Hey fischerhuder,

you tagged this way osm.org/way/32856133 with surface=dirt/sand. What does this mean? Does it mean dirt and sand? I am asking, because there are quite some usages on taginfo and I don't understand, what is special about this combination. Cheers

Hello ielham, in this change set you added surface=paving_stones:double_t. What does the suffix "double_t" means? Looks like c++ :D

e.g. osm.org/way/292716564

Cheers

Hey PicLaSelle, you added a few ways in this changeset which you tagged with surface=unpaved_minor (e.g. osm.org/way/687254745). What does unpaved_minor mean? Cheers