Hi,

got here thru a global 'first use' report after correcting some coding tags which all have e.g. Golf when OSM requires them all in small i.e. golf. Got slapped as the paths do not connect other then to themselves ('island car' it's called) which I will ignore most of the times.

Noticed all holes carry the full name of the club. Everywhere else they use tags such as hole 1 or just #1 as name which then actually renders nicely when looking at the map with the carto.fr layer selected. Link https://osmose.openstreetmap.fr/en/map/#item=&zoom=16 then select layers at right. There's so much hidden from view in the standard ID editor.
Just curious how mappers around the world do things differently.
ciao

area:highway has 170,000 uses
https://taginfo.openstreetmap.org/keys/area:highway

Tag info, 10,000 uses of area:highway= traffic_island
https://taginfo.openstreetmap.org/tags/area:highway=traffic_island

I've fixed them back to how they were. If something is awry I'll take care.

To be precise, you turned them into untagged areas with your changes.

Why did you mess up all these traffic islands, here and station area? Don't change if QA does not flag.
Thanks

Change in Madagascar, yet everyone gets to see that in the quadrant Paris-Toamasina. Thank you for splitting up your change sets.

Street lighting up from Frankfurt am main al the way to Bhutan.Kindly split up your change sets, set your StreetComplete to autoupload and you dont have to worry about this annoying OSM changeset display problem.
TIA

Hi, the situation is actually pretty nuts in signing there.. When approaching the crossing the 'recommended' sign says when snow, > 3.5 tons should go straight, but whence you take the turn and are 20 meters in, the sign says you're not allowed to go uphill with a truck over 7.5, at which point no room to make a u-turn. I'll add your recommended tag to the lane.

Note that some of these new traffic light are bi-directional , which is why 'both' was coded and for each pedestrian way work independently. Kindly check again.

Agreed, BUT, the 'bosses' do it all the time momentarily I see an avalanche from everywhere.

Top of the wish list, only see change sets that affect MY geographical area in ID view by being able to enter a top left, right bottom longitude/latitude in a profile screen.

Hi there brother in arms, your QA error warning has disappeared on Sabini 86-108 (really 82, Pronta Moda) also belongs to that block :O). Minor, I just added a height estimated to both the main and 1 level back part as latter in 3D shows flat as a pancake (You can see the quasi 3D in StreetComplete. Then it takes weeks before the models get updated in that program.

ciao ciao.

Yes we know it is ;O). It is in the planning to update the whole relation to include making it rendering properly in 3D. The multipolygon is entirely wrong for this complex structure.

cheers

The roundabouts are being messed with on Marconi... they have laid asphalt straight across and at the same they have installed many refuge islands to stop the Jackie Icks that roam the town. Who knows will they be painting cycle tracks and ASL's like on D'Annunzio next months. ;O)
Happy mapping, in isolation.
(To be continued.)

Please do your edit comments in English or the language of the country where you're editing, We dont speak krakowiak here.

thank you.

OK

So you need to draw a line around the whole thing. With that line selected go directly to relation and select new relation. type=building and give it the role=outer or outline (I've used outer only so far). Then you attach the 2 parts and tag them both with the role 'part', so that you end up with a relation that is 3 parts, 1 outer, 2 parts. (Not seen any sample where building:part was entered in the role field)
I don't use the building:part=* , just building=* as building:part wont render in OSM 2D standard.
The base wiki is osm.wiki/Relation:building
If stuck, let me know. In the meantime I've done the adjacent building with parking deck which is an identical arrangement, called the relation Sabini 70-80 (when there are many in the area it's easy to identify who's who). Then you can flip flop between the 2.
ciao e bonne chance

Hi, several QA warnings near Ripa: suspicious tag combination power=plant together with generator:source

You specified twice the source is solar, plant and generator.

Was about to get in the car and drive 600 km south as it started to feel as forgotten. Anyway the Castri part in the name was correct... 25% score. :o)
Thanks for fixing.

Seke Rob

Hi Finixfighter.

May I do a suggestion ;? Don't merge building parts that have different levels into a multipolygon. You get building:levels 1;2 or 2:4 or whatever combo and the tags from the individual parts are lost and 3D drawing programs wont know who's who and QA throws this out with "{0.key}} should have numbers only with optional .5 increments
" i.e. the building :levels can have only 1 value.

There's 2 approaches, draw as in past and create a relation type=building then add the parts to that relation, or, if you have different heights and levels on 1 building, draw the lowest levels for the whole building, then put the highest part on top and tag that with layer=1. If bottom is 6 meter high and top is 9 meters high tag the highest part with minheight=6, height=9. If you like use the relation type=building and tag the building parts to that relation. 2D fine, 3D fine. Make sure all nodes turn grey for the top section, same as with side by side. Boths ways the individual building parts retain their tag details and can be easily augmented in more tags, colour, material etc..

If you want to see an example, just did Beate Vergine behind Piazza Duca, then added the parrocchia in a separate multipart drawing and relation as well.

Don't hesitate to ask if you get stuck.

happy mapping.
ciao

You've been keeping the OSM world in suspense for days now, or should we say hostage... décevant.

Pretty pretty please, save 1 country at a time.