-
-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clearly state surface=compacted is only for machine compacted tracks #5927
Comments
I don't see this statement made in the wiki. The wiki states "compacted e.g. with a roller", not "compacted with a roller". It doesn't matter how the compacted surface was made. If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck. |
"Compacted gravel" is probably more important appendum as some used it for compacted earth/dirt (still not sure about adding it and is it actually more clear) |
Probably, yeah. May be difficult for the German translation, because "gravel" translated to German is this: https://duckduckgo.com/?t=ffab&q=kies&iax=images&ia=images I.e. always quite large stones, whilst "compacted" should be a mix of sand, small gravel etc. |
Though "mix of small and larger gravel and loose elements such as sand/clay/dirt that was compacted, typically with a roller" is hard to shorten otherwise and keep clear (unless someone has any great idea?) I though about adding expanded description of surfaces, but sadly Line 33 in f99db3d
and it would require some more dedicated form element When I observed less experienced people using StreetComplete I noticed that many of them were confused by surfaces - and attempts were made to find better images but it was not fully eliminated. Maybe making description of surfaces available in app, as suggested at https://eeee.no/@erik/112894257072009817 would help? |
yeah, you're right, but just "compacted" isn't the best fit either
I don't think it should be a word for word translation, I'd argue it's okay to use a totally different name as long as it carries the same meaning in a different culture/language |
Agreed, hand-operated vibrating plate compactors / rammer compactors are often used instead of roller compactors... But it perhaps could be clarified just by adding that "e.g." (i.e. as "Compacted (e.g. with a roller)", but it any case it looks quite long, and probably would eat up most of the picture (3 lines would eat about half of a picture on my device), which would be annoying/confusing in it itself... And it would not really help, as the core of the problem seems not to be (just) whether it is compacted and how. At least in English - in other languages, it is likely the word for "compacted gravel surface" might not have anything to do with verb "compact(ing)", so that inference might not be taken for granted. How would you say it in Czech, @vfosnar?
In Croatian, we call those compacted gravel surfaces "Makadam" (likely the same source as for Macadam), but I'm not sure if it is well understood in English commonly (and seems it can be confused, as there were apparently things called "tar-bound macadam" which become popular by trade name "tarmac") - Croatian apparently picked it up well before it got to that phase...
Maybe, but (apart from significant extra translator work), there remains the question of how it would be invoked (long press on a picture? separate info button on each picture?) Perhaps easiest might be to add regular |
That one is informative... there is common confusion between several types of gravel, and it is not the first time I've seen it. Perhaps renaming in English:
And giving instruction for translators in POedit how they should translate those (i.e. not literally word-by-word, but by how are those named in their language, to keep it clearly distinguishable from one another).
Giving instructions to translators would hopefully help with that issue. |
Nope, gravel might be translated to this, but actually it's more a false friend. Kies referres more to what you would find in a river bed - pebbles in English. The right term in German is Schotter, which refers to "Bruchstein" - crushed stones with sharp edges, compared to round edges of pebbles. |
Hm, let's rename it to "compacted gravel", then. Adding more "hint" texts and similar would just blow the interface out of proportion and ultimately make it take longer to find the value one is looking for. Regarding translations to other languages - this is rather something to worry about for the translators. E.g. if the current German translation is fine, it stays fine. I find @mnalis suggestion good, although I find it unnecessary to change the wording of "fine gravel" to further distinguish from "compacted gravel". "fine gravel" is gravel that is not compacted. |
even if they would be hidden by default like other hints are nowadays? |
Yeah, it's fine (had to check, I'm using SC in English) 😬 |
this looks like SCEE to me |
Same strings in German StreetComplete |
Good, so the German translation can be "Verdichteter Splitt" |
That's true. SC refused to start for me atm, again. See #5850 ;) |
I think the right technical term for this would be "Splitttragschicht" or "Schottertragschicht" depending on the size. Here's an example how this looks: https://rohstoffgewinner.com/referenz-schotter-waldwegneubau-oberwiesenthal/ But for me your suggestion sounds fine. :) |
Schottertragschicht is the gravel you put below a (for example asphalt or paving stones) topping, you link says that it will get 14 cm of asphalt on top. A Splittragschicht does not exist, the material is completely unsuited for thick layers. Sorry for bumping this, but it is right down my alley. |
Compacted surface can be easily confused with dirt for paths and smaller roads. It should be clearly stated that compacted is only for machine compacted tracks, for example by changing the name to "Compacted (with a roller)"
I can do a quick PR if this gets a pass and add Czech translation too
https://wiki.openstreetmap.org/wiki/Tag:surface%3Dcompacted
https://wiki.openstreetmap.org/wiki/Tag:surface%3Ddirt
The text was updated successfully, but these errors were encountered: