If you mean the ones on North Avenue, the dedicated busway there was installed too recently to be seen on aerial imagery. They started in November 2021: https://northavenuerising.com/dedicated-bus-lanes

Sorry, but where in particular do you see the busway tags? I don't remember using the busway tag for anything that wasn't a dedicated bus lane.

Is this not valid? The wiki page for Key:taxon suggests similar tagging. I can change it though since I see that genus and species are more common

Thanks for the heads up, I hadn't realized the distinction - I don't remember if I had a specific reason for using railway=station but the logic of the building=railway_station tag does make more sense

I didn't realize there was new construction there - this was some unplanned exploring on the way back from getting a hair cut. I'll make a note to take a look on my next trip out that way

Thank you I appreciate it, even if you did not intend it that way people will likely take it that way. There are some contexts in which it is not used in a derogatory way (such as in historical contexts) but it is considered a derogatory way to refer to an area in America

Mondawmin is not the "ghetto" it would be better if you didn't use inflammatory changeset summaries like this.

I had tagged it as being for foot and not motor vehicles, but I didn't realize turning circles couldn't be mapped as pedestrian ways, my bad

As for what I had in mind for using this information, local mapper Eli Pousson makes these intersection analysis maps to compare the how the spatial/positional characteristics of the junction relate to crashes which occur at them: https://twitter.com/elipousson/status/1366584359894069248

These are based off of the public Edge of Pavement data from the city which was released in 2017 and is mostly accurate. I don't think there is much reason to transfer every curb outline and junction area from there to OSM. However, the Penn-North intersection has been treated with curb extensions and street resurfacing more recently than 2017, so it's current shape can't be pulled from the edge of pavement data. (The "North Avenue Rising" project - I have not got around to adding the bus lanes yet.) Once I've revised this more I might try deriving an intersection map for Penn-North like the ones linked using Eli Pousson's R functions to test how that could work.

In theory there is analogous information that could be mapped in a similar way at pedestrian surfaces adjacent to a complex junction like this, but I am still thinking about what a good way to do that would be.

This has made me realize I should document what I'm doing here so it's more clear - it's something that I've been working on and revising as I learn more.

I am working off of a schema devised by German mappers for micromapping intersections. There are some concepts related to crossings on the German version of the OSM wiki that may be worth adopting on the English one at some point, but the junction mapping in particular is a more experimental one which is intended to include positional information at intersections that cannot be rendered with nodes and ways alone.

Stop lines for cars are mappable, but at complex intersections with differing angles and close proximities, stop lines can't be rendered without additional information. The explanation for this is here: https://supaplexosm.github.io/strassenraumkarte-neukoelln/posts/2021-12-31-micromap-update#junctions-rendering-stop-lines-right-

The authors of the above post were able to derive the information necessary to accurately map the stop lines based on the junction area, with the signals placed at the stop positions for cars in the direction they control. The purpose of retaining the intersecting node was that I did not want to break anything with routers that can do something with it. [...]

alright, I've gone back over the relevant wiki articles for lifecycle concepts and I see what you're saying. I've retagged accordingly. I think when I tagged this I was thinking of the historic:<date range>:feature scheme which is common. It also looks like in this context no date or lifecycle prefix is necessary on name, just the amenity.

for what it's worth, I try to avoid end_date, as the wiki page for it makes a convincing and strongly worded case for not using it, even in combination with disused:

Alright, that's what I've done now. cheers

Hello,
It's a row of spaced apart shrubs planted along the side of the pavement - I was trying to tag it in a similar way to a 'tree row' as it seems tedious to map each individually. They are to short to be described as bushes or hedges. It's possible there is a better way to tag this that I have not been able to find

Source here is the MD iMAP/Open Baltimore Street Centerline data.

(Fixed now)

That was an accident yes, didn't realize I had done that. Thanks for catching it

Glad it was helpful!

You're right about Dovecote, my mistake. I changed that one back. I have tried to make that distinction where possible (for example the Penn-North Subway location in this changeset) but I was hasty with that change. Let me know if there are any others that look incorrect

Thank you, yes I am new-ish. I have been trying to be more mindful of sidewalk crossings

I have reverted the changesets which broke this relation I think - let me know if this looks better, sorry about the mistake