You have not replied to any of your changeset comments or fixed any of the issues, but the routing remains broken, so I have reverted your edits. I have previously already asked you to slow down and make sure your edits are correct before uploading. Now these mass edits added so many issues that no other volunteer editor is expected to fix these after you. And you cannot leave such broken data for many days while the changes propagate to navigation apps and other maps.

Please only restore your edits or make new ones if you are going to fix all the errors without any guessing about what is a ford or a bridge or a culvert.

Do not use AI tools / RapID unless you are going to manually check the additions. It always has errors and always needs to be reviewed. It also uses Bing, which is misaligned and possibly out of date.

Do not click the "fix" button in the iD editor unless you understand what it does and are fully intending the change. Not all warnings are errors that can be fixed as offered, nor can you fix many of them without actually surveying on location.

And please use the latest aerial instead of relying on Bing or old data, especially if you see there are newer edits in the area (such as around the airport).

Ideally, split your large edits by what you are doing and don't mix different changes - it is impossible to fix without fully reverting the whole changeset.

Almost all your changeset comments are just "edit, add places", which means nothing and does not explain to other editors what you are doing or what sources exactly you are using. In the future, please start providing an actual description of your mass edits, because there clearly are issues that need to be checked by others.

If you don't know how to fix these issues, then contact the OSM community first for guidance before making so many changes.

This reverts:
181318104 - large number of invalid fords
181319563 - multiple invalid fords
181326370 - couple invalid fords
181328946 - huge number of invalid fords
181329124 - badly-fixed fords
181385638 - multiple invalid fords
181385842 - multiple invalid fords
181431035 - multiple invalid fords
181431135 - couple invalid fords, overlapping/duplicate waterways
181431481 - multiple invalid fords
181472762 - large number of invalid fords, bad waterway layer
181479807 - large number of invalid fords, bad waterway layer
181480373 - multiple invalid fords
181480457 - badly-fixed fords, new issues introduced
181497170 - multiple invalid fords
181497376 - overlapping/duplicate waterway

Yes, a survey would be needed for the exact signage. It's very hard to say otherwise and I am not familiar with the area. We can adjust the values then - I am not yet sure what they should be at the moment.

How do cars access this location - from way/1063716658 direction ? You only tagged one section, so I am unsure which route they have to take.

Please fix your edits. There are many roads that are now blocked by fords/ditches and navigation is broken. You cannot leave such issues for multiple days.

This edit especially has added a huge number of incorrect waterways and invalid fords blocking routing all over the place. Even where you attempted to fix some of it, you left fords all across the parking ways like node/13730335051. Please fix all of these.

This line way/1500109234 has no tags.

Please stop mass-editing waterways like this. You are creating invalid fords, invalid bridges, bad geometry and routing, invalid layers, etc. Please fix all these issues promptly because you are breaking navigation. And fix all your previous recent edits before you make any new ones.

Please fix all the incorrect fords you created.

Why is this ditch layer=1 way/1423368955 ?

Please fix all the incorrect fords you created.

Why is this ditch layer=1 way/155730973 ?

Please fix all the incorrect fords you created. Several remain like node/13738824009.

This cycleway section way/909367317 has motor_vehicle=designated. I assume this was a mistake? Or were you attempting to specify which way is used to access the parking/service road?

This parking way/1063716664 has access=permit. How is this signed on the ground? If it's one of those "tikai ar atļaujām" signs, then the access will be private, because on OSM permit means anyone from public could purchase/acquire it.

Čau, dzīvojamās zonas vajadzētu norādīt ar living_street nevis residential. Es te izlaboju.

Like mentioned before, please stop adding misaligned, overlapping AI building without actually manually checking them.

Please do not disconnect ways from other ways like you did with way/1497946028 and way/1497946029 . There were mapped correctly. If disconnected, these become unroutable deadends in the rest of the path/road network.

I surveyed the location. The west path is basically non-existant - I could not tell it apart from just grass - you would basically be walking through bushes and old fences. Regardless, the westmost fence by the service road is now repaired/closed, so you would have to enter by private gate/driveway and it doesn't look like anyone is seriously using it. North path is accessible and there aren't any barriers except an annoying kerb. Eastmost locked gates signage makes it pretty clear it's private courtyard access. So technically you can get to the east courtyard via the north path, but you are just entering a private courtyard through a roundabout way via some old destroyed gates and fences. I tagged west courtyard features as private and left paths in the meadow as public.

Hello,

This edit broke the geometry of the building, deleted the original way, deleted the tags, deleted all the building parts and misaligned the new shape. I have reverted this edit. Please edit more carefully and only adjust things you are confident are correct and follow correct OSM tagging and geometry for 3D building tagging.

Hello,

Could you please clarify what the real-world access here is - is it private? If so, there should only be access=private on this way and none of the other values. "designated" means that this way is not just public but specially marked as for pedestrians.

access=*

Thanks

Looking at latest aerial (Bing), it seems that this path is gone or very rarely used way/1177100639. May be some of the fences around 160B have been repaired or something. I would probably consider removing this section altogether since it's basically just overgrowing grass indistinguishable from the rest. The original edit suggests this is one of those "hole in fence" paths. OSM doesn't generally map paths like this unless they are clearly identifiable.

Sveiki,

Lūdzu nekartē highway=service + area=yes priekš ceļu ģeometrijas - tas ir domāts tikai vietās, kur ir liela plaša teritorija un navigācija/pārvietošanās ir visos virzienos, piemēram industriālās teritorijās. Uz šādiem maziem celiņiem starp mājām, kur ir vienkārša lineāra kustība, šis nekad nebūs.

Ja tu gribi kartēt precīzu ceļu ģeometriju, tad to norāda ar area:highway=service. Un šie laukumi nevar pārklāties ar gājēju celiņiem vai citām virsmām - tiem jābūt tikai līdz brauktuvju un krustojumu robežām (faktiski pa apmalēm). Arī layer=* un citām birkām jāsakrīt ar pašiem ceļiem.

Jo citādi sanāk iekartēts, ka faktiski mašīnas var braukt pa ietvēm, un piemēram rezultātā var sanākt šādi navigācijas "brīnumi": osm.org/directions?engine=graphhopper_car&route=56.941454%2C24.040272%3B56.941684%2C24.03947

highway=service#Linear_ways_and_areas

area:highway=*#Differentiation_area:highway_vs._area=yes_on_a_highway

Šis ir tas sienas posms, par kuru minēju: https://www.mapillary.com/app/user/hellphoto?&pKey=2151843558688976&focus=photo