Edits to reference name to more clearly and consistently describe the TEXpress, Express, and HOV lane system


As a part of regional transportation agency, we’re currently engaged in a project that involves updating certain attributes of road network data (managed lanes) within OpenStreetMap (OSM). Our goal is to ensure the most accurate and useful representation of our roadways, which benefits both the community and enhances the quality of the datasets we rely on.

We’re setting out to enhance the details of roadways without changing their geometry. Our focus is on areas where the reference names currently lack uniformity. We aim to standardize reference names and update tags for HOV lanes and tollways for better consistency. Our method involves making bulk edits through the OSM API to ensure these attributes are clear and uniform across the board.

Before we begin, we’re keen to ensure that our approach is fully aligned with the community’s guidelines. We’ve done some research on the best practices for bulk updates but haven’t found clear instructions. If there are specific guidelines or considerations for this type of update, we’d be grateful if you could point us in the right direction.

Thank you.

Automated Edits code of conduct - OpenStreetMap Wiki and Organised Editing Guidelines - OpenStreetMap Foundation seem relevant here.

Feel free to ask for clarification if anything seems unclear!

1 Like

Already reminded in original https://www.reddit.com/r/openstreetmap/comments/1bd1w7r/edits_to_reference_name_to_more_clearly_and/

The problem with your project lies in several factors. In Dallas, the roads are owned by the North Texas Transit Authority, while the ones in Austin are owned by someone else, while the ones in Houston are by someone else. They’re gonna call them whatever the higher up of each company decide to call them.

The second thing is going to be how locals refer to something as. I may call a TeXpress lane HOV and all other lanes like the as such. Those from other parts of the country (or even world) may just refer to them as whatever they’re used to.

For a better understanding of the debate, you need to look at the debate about the naming of service roads throughout the state.

Hi, it’s great to see regional transportation agencies like yours take an interest in OSM!

Would you mind elaborating? What are some examples of inconsistencies you’ve found so far? We currently identify routes in a couple ways, so it’s possible that what you’re seeing is a legacy encoding for backwards compatibility rather than what we’d prefer data consumers to use at this point.

I believe they have started the edits:

I asked them to respond to the questions asked here in a changeset comment