Edit O(100) nodes ~simulataneously

Hello,

I have been adding bicycle racks in my area (San Diego) to OSM using StreetComplete. These bicycle racks are typically these individual hoops, which I considered to fit a single bike typically, so I added capacity=1 to all the stations (except in one or 2 locations which had 2 racks right next to one another).

However they are spec’d for 2 bikes, and while traveling recently I saw them typically hosting 2 or even 3 bikes in certain circumstances. Here’s an example below.

Is there a simple way to fetch all the racks I’ve uploaded and multiply their capacities by 2? I am looking to survey more bike racks in the area using a more comprehensive mapper with GPS track/waypoint support such as Vespucci, and am holding off until fixing this.

Here’s the general area I’ve been recording in and I’m hoping to cover some of the major thoroughfares here more extensively.

https://www.openstreetmap.org/#map=16/32.73168/-117.16449&layers=C

Thank you!

If you do this with Vespucci or JOSM doesn’t really matter the procedure is essentially the same:

  • construct a query to find just the loops in question (see Object search - Vespucci and JosmFilterDoc/filter.md at master · simonpoole/JosmFilterDoc · GitHub don’t forget to suitably limit the area of the query)
  • run it against an Overpass server to download just the loops in question
  • select the results (the current version of Vespucci doesn’t have an option to automatic select the results of an Overpass query, but you can simply run the original non-overpass query again to achieve that, the oversight is fixed in 20.2)
  • change the capacity value to 2
  • upload
2 Likes

This should show you your desired bike racks: Searching for all amenity=bicycle_parking with bicycle_parking=stands and capacity=1 last touched by your own user account in San Diego: overpass turbo

Note that last touched only takes into account the points that you edited last. If someone has made a change after you, the point will not be displayed.

1 Like

You can just use (user_touched:"XYZ") instead of (user:"XYZ") and you’ll get all elements that user XYZ ever touched, instead of just those that were last touched by that user.

7 Likes

Some are already at 2, as has been said above. As multiplication is not available, I’d suggest starting with the higher numbers (filter for value=2), make them 4; Then filter for value 1 and make it 2.

1 Like

I was assuming, just as, nearly, everybody else, that the OP just wanted to fix the stands that they added with capacity=1 (for glaringly obvious reasons).

2 Likes

Thanks for the help, ended up doing with this JOSM as it was much easier to write a query on a laptop than a cell phone.

Was unclear with the original post and yes, aimed to fix all the 2’s. There were a couple of locations with 2-3 loops I incorrectly marked with capacity=N for N loops instead of 2N, but edited those out by hand.