some issues I came accross as I did my first test run in Miami Dade County

I am looking to improve the public transit mapping in Miami Dade County and am hoping to run this over Miami Dade county to update the positions and especially the tags of the bus stops in the county. I created a [YAML file](https://github.com/Udarthegreat/public-sources/blob/main/gtfs%20janitor%20stuff/Miami%20Dade%20County.yaml) for configuration and used it to do a test run of gtfs janitor to see what improvements I would make to the configuration file and came across a few issues and small improvements I would like to see in gtfs janitor while doing this. As a note I have since updated the configuration file so the version that I ran gtfs janitor on is [01fab33](https://github.com/Udarthegreat/public-sources/blob/01fab33ce10c59f328b26c5f82c3e4bfdb358fc4/gtfs%20janitor%20stuff/Miami%20Dade%20County.yaml)). I also uploaded the [`.osc` file](https://github.com/Udarthegreat/public-sources/blob/main/gtfs%20janitor%20stuff/gtfs-janitor-export%20pass_1.osc) generated by the test run to the same GitHub repo as the configuration YAML. While I was doing the test run I wrote down all of the issues I ran into, I put all of these into the readme of the folder the configuration YAML and the `.osc` are in, I have put slightly expanded versions of some of these below (but not necessarily in the same order). the list: - In the generated `.osc` allot of the bus stops ended up without `name=*` or `ref=*`, as in it added the tags without any values even when the existing OSM data had at least one of those present. - Is there a way to tell it to expand road name abbreviations as allot of the gtfs stop names are something like "SW 107 AV & SW 96 ST" so would need to have the stop names expanded before upload. The thing is that it also has some names that are a combination of name expansion and converting to title case, such as "FAIRWAY HEIGHTS BD @ SW 102 PL". - Sometimes the name of the bus stop in OSM is reversed from what it is in the gtfs file (and also, as mentioned above using abbreviations), as an example the osm name was "Southwest 157th Avenue & Southwest 88th Street" and the expected value was "SW 88 ST / SW 157 AV" - I would really like to tell it that the old position is better (for example the old position has a shelter and a bus bay , they are obviously the same bus stop but they placed the bus stop in the gtfs funky (I have attached an example image below and the node I would like to keep the position of [is](https://www.openstreetmap.org/node/1039681177)) <img width="1731" height="738" alt="Image" src="https://github.com/user-attachments/assets/e30c3580-3105-47db-9a3e-e56de3a62bf5" /> - allow in the configuration yaml file to provide some local short codes (like for example in Miami Dade county "UM" is understood to mean "University of Miami") - it failed to match to potentially closer stops that are currently tagged as from a different operator (like Broward transit and the city of miami transit), for example node [9501636482](https://www.openstreetmap.org/node/9501636482). - let me keep the name of a OSM stop as compared to the gtfs name (an example image provided below were I am pretty sure that the OSM nodes name is more correct but the gtfs position is better) <img width="1870" height="497" alt="Image" src="https://github.com/user-attachments/assets/7d5e02d3-c426-4825-9182-254db3515474" /> - it also tried to delete stops that are still part of other routes, as an example, when it came to the stops at [Vizcaya Station](https://www.openstreetmap.org/relation/11259199) it had all of the other non matched stops selected as "Delete" when most of those are part of various bus routes, image of this below: <img width="1900" height="842" alt="Image" src="https://github.com/user-attachments/assets/8113b095-39ed-4b48-9b31-6c0ae41238c2" /> - it would be nice to be able to tell it to replace one tag with another, as some bus stops have a `gtfs_id` tagged which, from my understanding should be replaced by `gtfs:stop_id` - I wish that the matches that need review would be grouped by proximity in the order they are shown to you (for example if there are multiple stops in one area (for example around a single station) all of those bus stops should be shown to the user in sequence) - once all of the matching is done and it has generated the `.osc` file it would be nice to have a visualization of the dif created and maybe some editing tools to touch things up a bit. This would also help to ensure that any stops that it didn't show me for review that are obviously placed incorrectly are found and possibly have their position fixed before the final .osc is downloaded and validated in JOSM. From what I remember node [1039659656](https://www.openstreetmap.org/node/1039659656) is an example were it didn't pop up for review but gtfs janitor matched to it but that is not the correct position and there is an [existing node](https://www.openstreetmap.org/node/11408844900) at the correct position but it did not come up for review so it added tags to it when it should remain as it is, I can confirm that node [11408844900](https://www.openstreetmap.org/node/11408844900) is there as I passed it on the road this week ( the week of 09/25/2025) and that there is no bus stop infra at the incorrect position. - The Busses have specific seats for wheelchairs if they are riding and the doors of the buses have a expandable platform that can be manually expanded by the driver to make it easier for people in wheelchairs to get on, the issue is that gtfs `wheelchair_boarding` is from what I can tell set to 2 for most of them so I don't know if that value is any good, what should I do about that? There are more issues that I am pretty sure are just issues with the config file from what I can tell in the [readme](https://github.com/Udarthegreat/public-sources/blob/main/gtfs%20janitor%20stuff/Readme.md) then what I put here.