@Kayo_33 please note that not every StreetComplete quest is correct and requires an answer.

Hi, there is no concrete rule. You could either decide that you want the default as maxspeed and since the sign is conditional to have conditional:maxspeed. Or you could put maxspeed as 70 and add a conditional for 90 - at least this won't suggest to break the law for consumers which don't support conditionals.

If it was a condition which is applied rarely, I'd definitely put it in conditional:maxspeed.

You should at least add the default speed (90?) as maxspeed if you leave the conditional as 70.

I also suggest removing ;Sa off;Su off - I think these are not required.

Some context if someone stumbles upon these comments:

https://www.mapillary.com/app/?lat=58.18305939999698&lng=25.50511080000001&z=18.531688264196713&pKey=293992547065552&focus=photo&x=0.5808639655721334&y=0.47141229429312625&zoom=2.0930232558139537

landuse=winter_sports should be used instead of landuse=commercial

I don't think OSM carto cares about layers unless it's roads. I think it has internal layers by which drawing order is determined and if they are on the same layer, smaller things are drawn on top of bigger. Seems that it's not the case here.

You could use multipolygon to carve out that flowerbed from the pedestrian area.
1) Make a multipolygon for pedestrian area, with outer role
2) Move pedestrian area tags to multipolygon
3) add flowerbed as inner part of the multipolygon

osm.wiki/Relation:multipolygon

This will make a hole in the pedestrian area, flower bed will be seen through it.

Hi, please use commonly known tag values where possible. Otherwise consumers won't know what to do with them. Most routers will likely avoid routing through unknown highway type.

For parking lot, use highway=service where cars can drive, then you can connect footpaths to them for routing.

I've updated the parking lot, check it out.

Looks like it's fixed

You probably wanted to connect this to another path way/1340855959

I'd avoid using
access=employees. Not a popular tag unlikely to be understood by consumers. IMO access=private covers the usage good enough.

Nice, @dgmapping!

The problem which I've fixed would cause that. Wait a bit until routing service updates it's graph.

Hi, currently this road is marked as motor_vehicle=destination which means that it's not accessible to motor vehicles unless they intend to park somewhere there.

I think it was intended for a small part near the school. I'll remove it for the most of the street.

Estonia has no motorways (kiirtee) where specific traffic law rules apply (no cycling, no walking, no driving under 40km/h, no stopping, etc.). We do have traffic rules for them if some day we'll get one.

Routers may apply such defaults to this road which would be incorrect.

I vote for reverting this change.

Hi and welcome!
You've made a hole in the building at shop's location.

Shops don't require multipolygons with a buliding and you shouldn't change the building in any way if you want to add shop separately. It's also better to map such shop as just a node.

I've fixed it, you can check it out.

access=private

may be also appropriate if there is a gate.

Hi, you need to add a highway**=* tag to actually turn this line into a road.
As I understand it's behind the fence so

highway=service
service=driveway

would be appropriate.

You can either add it in Tags section when you select the line or by clicking on it under "Feature type" and searching for "driveway"

also consider using landuse=grass instead of a grassland, if the land is cared for (mown)

Hi,
way/1338952157
this grassland shouldn't have a name.

https://www.mapillary.com/app/?lat=58.05724330000001&lng=25.36766130000001&z=17&pKey=6600907689965680&focus=photo

Hi, I can't see any signs which would make the road private. If there are no signs you can't really claim that or stop someone from making a u-turn there.

Hi, addresses can exist without a building. Please don't remove them without checking with Maa-amet

https://xgis.maaamet.ee/adsavalik/CU00445385