Just an FYI, but please do *not* align geometry to any of the global imageries (ESRI, Maxar, etc.) in this local area _without_ getting an offset. I have a few offsets in the imagery offset db ~15 miles away set to a survey monument.

There are also local imageries available (Mesa County GIS NAIP 2019) which is (a) clearer and (b) more accurate.

For traffic signals on oneways, you really don't need to add `traffic_signals:direction`. (See the traffic signals at the intersection of West Aspen Avenue and South Cherry Street).

Anyway, just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Please pay attention to your warnings. Specifically, the crossing highway warning. I fixed this issue in changeset/110536485 .

Just an FYI, I *have* georeferenced all the available imagery using the imagery offset database.

As you are a professional editor (based off of the iD host), you should try to use the best available imagery in each area you edit, with the appropriate offsets. The nearest survey monument I've aligned the standard imagery to is ~1 mile north of this edit location.

Unfortunately, the editor you are using doesn't pull from that database, and JOSM requires a plugin for that.

Anyway, just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Comment should be "Add minspeeds"

See https://josm.openstreetmap.de/ticket/21203

I didn't see anything off -- I just saw `iD 2.19.6` which doesn't integrate with the layer offset db, and I figured I'd point it out due to the use of `improve alignment` in the comment. That and "Bing" as an imagery source.

I do have some aerial imagery in Palisade I need to process so that I can add some offset points there, but aligning to Strava traces should help a lot (compared to non-aligned imagery).

Just an FYI, I *have* georeferenced all the available imagery using the imagery offset database.

Unfortunately, the editor you are using doesn't pull from that database, and JOSM requires a plugin for that.

Anyway, just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Just so you know, different imagery's have different real-world offsets.

I *have* georeferenced all the available imagery using the imagery offset database. I don't know if you used the plugin for JOSM.

Anyway, just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Quick question for you: which image did you use to verify the road signs?
All the street level imagery I have access to indicates that the speed limit is 65 mph, not 75 mph.

No worries -- I just did not want you to spend a lot of time realigning stuff to later discover that it was pointless.

The Mesa County imagery is pretty good (<2m to reality), so if something is wildly off from that, you can probably move it. Or if it is a road imported from TIGER (look for the `tiger:reviewed=no` tag).

Also, if you (a) have an android phone and (b) like walking, you can take a look at StreetComplete.

The iD editor (what you used for this changeset) is pretty friendly for new editors, so don't worry about messing things up too badly. Just don't do mass edits (e.g., convert all `building=house` into `building=yes`).

If it helps, I do watch Mesa County for changesets not my own, and often comment.

Just so you know, different imagery's have different real-world offsets, so absent an imagery with a known-good offset, don't bother moving buildings like this.

I *have* georeferenced all the available imagery using the imagery offset database. Unfortunately, the editor you are using doesn't pull from that database, and JOSM requires a plugin for that.

Anyway, just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Hello, I dropped the description you added to 1911 North 10th Street (generally speaking, `description` and `name` aren't on `building=residential`, and this does not look like an exception).

If you want to add the unit numbers, feel free. :)

Thanks for this update -- I moved the name over to a pitch that enclosed the pitch you edited, and deleted the pitch you modified. I did reference this changeset so that someone can follow the history back.

A few notes on this change:
`addr:street=Norrth Avenue` is probably wrong. For starters `North` is spelled wrong (probably a typo -- everyone makes them), and the address is likely for the entire CMU campus, not specifically for the Health Sciences building (which you added a point inside -- why?). I've gone ahead and copied the singular bit of additional information onto the building (`internet_access=yes`), and I've modified the building tag to be `building=university` -- the `amenity` for the university already exists on way/423652248 .

Also, just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

No problem. It was your first edit, after all. :)

iD can square buildings with `Q`, so they are better/more accurate. It also looks like these should be tagged as `building=static_caravan` (mobile homes) instead of `building=house`.

Just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite". Unfortunately, the previous year that covers this area of the county is kind of bad in this location. (IIRC, it was for the National Agriculture Imagery Program.)

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

OK. Can you please do useful edits in the future?

Thanks.

Why did you move the road *slightly*? Bing does not have the resolution for the move you made, and it is kind of outdated downtown anyway.

Just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. I don't know what years Go Map/Go Kaart has access to. You may also want to take a look at "Mapbox Satellite".

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Just so you know, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. You can see it by clicking on the "Background Settings" button in iD (keyboard shortcut "b") and select "Mesa County GIS Valleywide 2018". You may also want to take a look at "Mapbox Satellite". Unfortunately, the previous year that covers this area of the county is kind of bad in this location. (IIRC, it was for the National Agriculture Imagery Program.)

JOSM also has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS".

Thanks for your contributions,
vorpalblade

Please fix the golf course simulation software instead of modifying OpenStreetMap data to "work" in it.

The map data is used for other purposes, including:
* Routing (which is what you are breaking here)
* 3D rendering
* 2D rendering

The bad thing is that a data cut is coming up for most popular routing software (OsmAnd specifically), so I am unwilling to leave bad routing data in OpenStreetMap that *I* know about. I assume that *most* software will do a data cut around the end of/beginning of a month.

If the data is left in, OsmAnd (for example) will have a month where there is bad routing data for this area.