Or perhaps make the station have the role=station for the relation, I'm not sure exactly what the bug is here. Check other valid subway networks on the validator for working examples. Thanks again!

Thank you for these improvements! One remaining step is to add the stop_position nodes to the stop_area relation so that each stop is associated with a station (or platform) https://maps.vk.com/osm/tools/subways/latest/singapore.html

No biggie! If there was indeed a reduction in the number of lines then all could be well! Just check the subway validator (I think the one at vk.com runs often) after making rapid transit changes. CoMaps' runs a few times a month.

Hi there! This cleanup seems to have tweaked the subway validator a tad: it's expecting 12 light rail lines but is only seeing 10, and has likewise lost a few dozen stations https://mapgen-fi-1.comaps.app/subway/validator/usa.html -- I can't tell if this is due to reclassification of light rail as train or if something else is going on, but please reply via comment or on this issue so local OSM users have working transit instructions: https://codeberg.org/comaps/subways/issues/23

FYI I've taken to referring to food cart pods as "food courts" since they basically are just outdoor slightly ad hoc food courts. I'll leave the landuse=retail areas you started but I want to make them more obvious and searchable for food, moreso than the name of i.e. a business plaza and landuse that often won't show up in maps or searches.

Whatever you do, 小智智, please check the Subway Validator after making changes to light_rail, subway, monorail, etc. https://maps.vk.com/osm/tools/subways/latest/index.html

Hi there! This and other similar changes are breaking public transit map generation for London: https://maps.vk.com/osm/tools/subways/latest/uk.html -- it seems network:metro needs to be consistent between route relations and route master relations, was there a reason you removed network:metro=Crossrail ?

Thank you for your contributions!
---

Published using OSMCha: https://osmcha.org/changesets/157641383

Thanks for your contributions!
---

Published using OSMCha: https://osmcha.org/changesets/157647869

Thanks! FYI all US speed limits except for maaaaybe ones very close to Canada/Mexico will be in mph. Any maxspeed tag in the US without "mph" is suspicious.
---

Published using OSMCha: https://osmcha.org/changesets/157592070

Thanks for your contributions! Please use descriptive changeset messages to make reviewing (and your own history!) easier.
---

Published using OSMCha: https://osmcha.org/changesets/157597378

Thanks so much for your work making Dallas accessible to all residents and visitors!
---

Published using OSMCha: https://osmcha.org/changesets/154989184

Thanks for helping make the map better!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/153126805

Thanks for improving this location on the map! FYI parking aisles are only for service roads that serve no purpose beyond finding a parking space. The main route in/out/through a parking lot (say if you were a taxi dropping someone off) is just a plain service road. I've made the appropriate changes, though I didn't know what the rules on parking were for the parking lot (paid, access, etc)

Thanks again!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/152255802

Hi there, thanks for helping make OSM accurate!

Please be extra careful when editing around city limits and other big boundaries. It looks like you tried editing this bridge way/5496981 but ended up editing the Lebanon City Limits at way/38414288

I've gone ahead and updated the bridge to what I think you intended. It's good to finally have names for these roads after so many years! Thanks again and happy mapping.

Thanks for improving this area! Feel free to join the North edge of the park to the hospital boundary if indeed they share a boundary. Otherwise if they're separated by i.e. a pathway or river then no need
---

Published using OSMCha: https://osmcha.org/changesets/151749178

Close! Make sure that each type of navigation can navigate across the things you're mapping. Driveways are for cars, bikes, and pedestrians, so this should connect to the sidewalk (as you've done) but also the street, so that if someone wants to navigate to the house at 2830 they're directed appropriately.

Looks good! You can always mark it as a garage or shed as well, but otherwise looks fine.

Hi! Thank you for adding your business to the map. Please avoid promotional details in changeset messages, descriptions, etc: it clutters up the map if every business makes its name "McDonalds Burgers Portland The Best Burger You'll Ever Eat" (the description field exists for crucial neutral details like "A plaque about the battle that was fought here in 1848" or "Only accessible if it hasn't rained lately" -- info that travelers and customers need to have popped up in their face, and definitely not SEO stuff.)

Also beauty shops are a really vague category, given that you're an RN performing "med spa" type procedures and not really the same category as Sally's or Ulta I've modified your listing to be more like a dermatology clinic. We can modify as needed for the best fit but nothing's ever perfect (Rex Burger and McDonalds probably don't want to be in the same category yet here we are!)

Finally I've added your Salem location and cleaned up your opening hours to follow OSM syntax so it shows properly in apps: changeset/151379938

Some things that might be helpful to add to both locations are the level tag (0 is ground or first level, 1 is the first level above ground aka second floor, 2 is the what we'd call the third floor, etc), wheelchair access tags, etc, since I know the Commercial location looks a little complex.

Cheers and thanks again!

You mapped! Thanks for your contributions. Is this grass runway marked or made official in any way, or is it just a grass area that happens to be suitable for landing?
---

Published using OSMCha: https://osmcha.org/changesets/151375705