Oh I see, you handled that well in https://www.openhistoricalmap.org/changeset/190245. Thank you!

Plot twist: the old border did follow the Colorado River, but the Colorado River was closer to where the border is now than where the river is now. It was just curvier than the current border.

https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~338868~90107091:No--3--Baja-California

Ah, this happened in 1944:

https://www.inegi.org.mx/contenidos/productos/prod_serv/contenidos/espanol/bvinegi/productos/nueva_estruc/889463909262.pdf#page=65

As far as I can tell, the border between Baja California and Sonora used to follow the Colorado River entirely but changed to the present-day boundary sometime in the 20th century. A 1988 federal source [1] still has the old boundary, though that could just be outdated. The Caltopo (“USGS Topographic Maps”) layer has the new boundary and is likely older than that. It definitely moved to follow the railroad by 2001. [2] Maybe the railroad’s completion had something to do with it?

[1] https://web.archive.org/web/20220709203239/http://www.inafed.gob.mx/work/enciclopedia/EMM26sonora/municipios/26055a.html
[2] https://web.archive.org/web/20180206073522/http://www.bajacalifornia.gob.mx/portal/gobierno/legislacion/periodico/indice_261001.pdf#page=28

Ah, makes sense. Thanks for clarifying. Yes, if we can determine the religion/denomination, those tags would be helpful too. I’m also starting to use border_type=* to clarify the form of ecclesiastical unit more specifically than admin_level=*.

If these are civil parishes, they should be boundary=administrative rather than boundary=religious_administration, right?

https://www.openhistoricalmap.org/changeset/187686 replaces much of this changeset with the roads that actually existed and exist along the never-built La Honda Expressway and Willow Freeway.

https://forum.openhistoricalmap.org/t/new-york-city-streets/501/3?u=minh_nguyen

https://www.openhistoricalmap.org/changeset/182057 fixes the boundaries.

Hi, instead of setting note=<1580, you can set start_date:edtf=/1580 by clicking the + button next to the Start Date field. This is a standard syntax that software using OHM data will find it easier to support than unstructured note tags. For more information, see https://wiki.openstreetmap.org/wiki/Key:start_date:edtf

Also, “Area Incorporated into the City of Menlo Park” [1] doesn’t sound like something that should be mapped as a place=city. It sounds like an annexation area. We’d normally create a new version of the overall city’s boundary (Menlo Park, in this case) that encompasses the annexation area.

[1] https://www.openhistoricalmap.org/way/199900541

Thanks for this extensive research! Unfortunately, somehow this changeset ended up repurposing some member ways of Michigan township boundary relations as Interstate highways. For example, https://www.openhistoricalmap.org/relation/2744824 contains bits and pieces of I-64, I-65, and I-74 throughout Indiana. Can you restore the township boundaries and also double-check that other things didn’t get damaged?

Also, please don’t hesitate to cite the sources you used in source tags on individual features, especially if it’s something you had to use exclusively for OHM. Unlike OSM, OHM prefers to keep the sources near the features like that, akin to the practice of maintaining text–source integrity on Wikipedia and AARW (WP:TSI). It doesn’t have to be a full citation, just anything that helps us sort things out in the event of contradicting information. Hopefully that’ll help you organize your research for AARW too.

Remember to add a start_date to even the alleys. Otherwise they’ll show up from the beginning of time. Thanks!

Hi, the main name key is ideally intended for the name of the feature in the language spoken or written locally at the time, which would’ve been Akkadian or Sumerian cuneiform. Greek wasn’t correct but neither is English. Changeset 172797 substitutes the cuneiform name. That said, we just launched an improvement to the site so you won’t notice any change: now every feature is labeled in the language in your account preferences (that is, English), as long as this language is explicitly tagged alongside the primary name.

It looks like you deleted several streets that were originally added from a 1936 aerial image in changeset 62724 and other changesets. While ideally the features would have individual source=* tags, it used to be very common for mappers to tag this information only in the changeset, following the OSM convention. So before deleting something on the basis of lacking a source, you need to look at the feature’s version 1 to see whether a source was given.

What’s your source for the 1926 start date on Verona Columns?

It looks like you deleted a roundabout at Kauffman Avenue and Colonel Glenn Highway in this changeset. What is your reasoning for the deletion? It appears in aerial imagery, and the start date was added in changeset 122229 apparently based on a comparison of Esri Wayback imagery from two years.

By the way, you don’t need to tag individual ways if they’re already part of a boundary relation. In that case, source=* is just about the only key that’s relevant to the ways, in case one part of the boundary comes from a different source than another.

Much of this changeset deleted streets and other features that exist or existed at one time, in favor of features that definitely no longer exist. You should’ve avoided deletion and added end_date=* and/or end_date:edtf=* tags to any features from the Olmstead plan that are gone. Instead, the map is currently a bit of a mix of incomplete Olmstead plan and incomplete later construction projects.

What is your source for these changes, particularly the deletions? This changeset deletes several named streams that were accurate. They were imported from a dataset of the present day, but as natural streams, they likely existed long before any of the maps you’re consulting.

You also added two streets citing a 1956 map but providing no evidence for a claimed start_date=1925. Is 1925 your general placeholder for a start date you don’t know? Instead of relying on magic numbers that can be confused with real dates, please set start_date=* to the date of your source, and https://wiki.openstreetmap.org/wiki/Key:start_date:edtf to a range that includes known upper and/or lower bounds.

I’ll be going through some of your recent changes soon and attempting to find better sources for them, but if I’m unable to, I’m afraid I’ll have to revert your changes wholesale in favor of the better-sourced data that was there before.