*It's like => it's likely

building addresses are mostly managed automatically. It's like housenumber added to Kurmäe hostel will get erased since it's missing in official sources.

Hi, be careful, you've accidentally changed bus station's name

Thank you! Added it to actual school amenity too, so that it won't be just on a building.

and why is this
way/875901109
access=customers?
Customers of what?

Hi, why have you made these
way/307428684
way/307425971
parkings private?

Changed. I've made an area out of it.

Hi, what's the source for English name?

Hi, in such cases when pedestrians and cyclists are on the same path, you shouldn't create two paths. You should add one path which can be used both by cyclists and pedestrians.

In this case, such path already exists!
Only problem is that it's a highway=footway, which isn't very good. But because of bicycle=designated access tag cyclists are allowed to use it.

I'll rollback this change. And change highway value to path.

You can find more info on mapping cycling infrastructure in the wiki
osm.wiki/Bicycle

and here
https://community.openstreetmap.org/t/mapping-cycleways-in-estonia/104894

You can also add a boom barrier / lift gate to the entrance and select appropriate access on the parking lot, if it's private or only for customers, if you want.

Hi, welcome!

highway=service shouldn't stop where parking starts, it should go inside. Routing software does not route through parking lots, so the initial position of this way was correct.

There was also a parking before, but marked not as area, but a node at the tip of the highway. It still exists. You should remove it. You can do it either
1) By clicking on feature type and selecting "Point"
2) Removing it in "Tags" section

I've seen it. I think maybe a narrow area? At least artwork_type supports it by wiki. Or maybe map each sculpture individually? New aerial imagery allows it now. IMO one node is good enough too.

Not sure many consumers will consume artwork as a way :/

Thanks. While I don't completely agree, I've added bicycle and foot designated.

Smoothness could be added, but I don't remember it well enough to add it from memory right now. If I remember correctly, there is a problem of the path being very different depending on going on the right or left side.

Maybe mtb:scale=0 is also applicable.

It's ok. Please don't accept my attacks personally too, they are more directed at Tallinn's road dept. constantly messing up and creating such a sitiuation. I just want to make something better than they have.

What genuinely is unsettling, is us repeating the same things over and over. Doesn't look like our opinions will change.

Let's wait for a different opinion.

BTW, @Tormi, we have a heated discussion here and are in need of third opinion. It would be much appreciated. But also don't feel obliged to get into such details.

changeset/144441885

I don't believe this is a plausible scenario. Incompetent decision is as they do now - cycleway on paper, bad path in reality.

More plausible is that this path is improved and there is no controversy here anymore.

You can keep ignoring my arguments made from practical point of view. But if you trust Tallinn transport dept. that much, then remove cycling possibility from Vana-Kalamaja in North direction - no way those smart people could have put a cycleway markings and a 331 sign together by mistake on a new street. Mark all pedestrian ways around Kristiine junction as designated - they are so blue on Tallinn's map. Oh, and don't forget to personally remove pedestrian sign from Kase street in Maarjamäe - it's not vandalism if it's on Tallinn's map!

We aren't getting anywhere and only useful feedback was from Pikse so far. Maybe this discussion entertains you, but I'm done with it.

@Pikse (or anyone else), if you could invest a bit of your time in this problem, consider arguments, maybe check out the path in question and give a final "vote" at some point, it would be very appreciated as we have a 1 vs 1 stalemate here.

It doesn't prohibit routing through it. I don't see it as a problem. Actually, it's an advantage that for routers this will have a higher cost, because it reflects the truth of this part being harder. No normal router prohibits cycling on paths.

I don't believe every intersection with a path requires signage, but this place is special as I've already pointed out.

>However, I don't think Kitsarööpa tee falls into this category.

It does fall into this category since I'm an individual.

This designed vs designated is actually a good point.

But consider this: they would never install signs here, because it would be seen as a total failure to create bicycle infrastructure, but the signage is intentionally vague to have a cycleway on paper and a bad path with a stream running through it in reality.

There are many instances where Tallinn's map lies about cycleway connectivity and even marks paths explicitly signed as a footway as cycleways.

Since there can be different interpretations of signs,, I removed the tag to reflect my understanding of reality one type of path turn into a different one.

But if multiple people vote to have this as designated on the map, we can change it back.

The downsides I see are:
* It's hard to correctly tag problems with this path, as there is channel made by water along it, but if there are no other people, you can ride on a narrow part not affected by it.
* Many simple routers won't take into account other tags or won't take into account all of them, while a path where cycling is not forbidden and surface isn't ideal is simple enough.
* We are copying maps made for a political benefit to hide problems. It reduces trust in osm and usefulness of osm as an independent source of data for end users. It works against promoting building bicycle infrastructure, as apparently this is good enough.
* Since it's harder to consume data if we put bicycle=designated, less protected and able people are at risk here (and they probably don't have a strava account).

Are you ok with those? I have yet to hear what we gain by it.

And also is it designed as one. It's clearly not designed and clearly isn't remotely as safe for all ages and abilities as actual infrastructure.