It looks like this and 156219687 are from an import.

Can you please document it on the wiki? Specifically on osm.wiki/Import/Catalogue .

If you didn't go through the import process (see osm.wiki/Import/Guidelines ), please do so ASAP. Otherwise, it is _highly_ likely that this data will be removed.

FTR: note/4147496

`tiger:reviewed=name @ <road name>`: I verified that the name was correct at the indicated intersection with `<road name>` but did not check geometry.
This was done with imagery I captured. I *think* I uploaded it to Mapillary, but I'm not 100% certain.

Yeah, it should _not_ be oneway. I'll fix it in a minute.

Hello again.

I don't know if you want to use a more advanced tool. If you don't, I'm sorry in advance about talking about a more advanced tool.

Assuming you do, JOSM ( https://josm.openstreetmap.de/ ) has a plugin called `utilsplugin2` that adds a `Circle arc` tool. This lets you take three points and generate a _pretty good_ curve for whatever you are mapping. I use it a lot when mapping a sidewalk going around a turning circle.

For reference on the difference to how it looks see:
* No circle arc: node/11241305337
* Circle arc: node/11241332135

Not to pile on here, but I don't think US 50 goes south at Loma. Its been awhile since I did a drive through it using Mapillary (see https://www.mapillary.com/app/?pKey=1491045207904255 ), but I didn't see any US 50 signs.

If you live in the area, I would highly recommend uploading new/fresh imagery so that someone doesn't assume that a malicious actor was messing with the map. I live in Grand Junction, and I don't when I'll be driving through Loma and/or Mack again.

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 2022".

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

Thanks for your contributions,
vorpalblade

P.S. the local GIS office is having what is known as a "mappy hour" on September 27th. See https://www.mesacounty.us/news/gis/gis-mappy-hour for details.

Hi there, I don't know if you are with the city government or not (your username indicates that), but there is better background imagery available.

To see the full background list, open the `Background Settings` menu (default keyboard shortcut `b`) and go through that.

Since you are _probably_ with the city government, you _probably_ want to use the `Mesa County GIS Valleywide 2022` background.

Moving on to what you've been mapping recently (bicycle lanes), many of those have already been mapped as part of the road infrastructure using `cycleway=lane`. You may be interested in reading osm.wiki/Bicycle for the distinction between a cycle path and a cycle lane.

If you are wanting to model the position of the cycle lanes, you might want to use `width` tags. For example, with `North 3rd Street`, I would use `width=33'` (I use edge of gutter to edge of gutter, but most people will say kerb-kerb; I prefer to use lower values since that can matter sometimes). Here are the tags I would use (using meters as the unit, instead of feet/inches):
width:lanes:backward=3|1|2
width:lanes:forward=3|1
width=10

If you don't mind an editor with a larger learning curve, take a look at JOSM ( https://josm.openstreetmap.de ). It has many paintstyles that may help you, one of which is specifically for lane and road attributes.

Anyway, I'm glad to see someone from the city mapping as well. I did most of the footpaths in GJ downtown a few years ago.

As an aside, depending upon how accurate/precise you want to be, I _think_ you might want to look into setting the background offset (`Background Settings` -> `Imagery Offset`). The offset for the 2022 imagery (against one of the survey monuments, IIRC) was `0.40; -0.16`.

Thanks,
vorpalblade (Taylor)

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".

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 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".

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

The tagging scheme itself looks good, assuming the shoulder is a cycle lane -- I don't think I would classify it as such, as it doesn't look wide enough to ride on comfortably, and I'm not seeing any markings on either end of the road (on Mapillary and 2020 aerial). So I'll probably remove the `cycleway=lane`.

Thanks for your contributions,
vorpalblade

Addendum:
I'm not certain how the turn restrictions at node/176212265 are valid (from a legal perspective). I'm not seeing anything in the 2020 aerial imagery that would indicate that vision is obstructed.

Anyway, something else that you can add to discourage routing would be stop signs. Assuming they exist on the ground.

I'll try to remember to do a drive-by to get Mapillary imagery for that intersection some time.

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".

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 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".

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

This is actually kind of important, since Mapbox Satellite shows the pre-2018 building, which you adjusted the outline to. The building was demolished and rebuilt in 2018. I'll be reverting the geometry change.

Thanks for your contributions,
vorpalblade

Would you mind explaining what you were intending to do in your future changeset comments?

I *think* you were just squaring up a diagonal street_side parking area, but I'm not certain.

Since the parking area is a diagonal parking area, it is likely that I will (at some point) get around to redrawing the area to match the on-the-ground reality.

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".

If you ever get into micromapping, I *have* georeferenced all the available imagery using the imagery offset database. There is a plugin for JOSM, but iD does not use it (unfortunately).

Thanks for your contributions,
vorpalblade

Just a heads up, Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap. I am specifically mentioning this as the outlines drawn were poor. I'm going to fix them, using data from Grand Junction (see osm.wiki/Import/City_of_Grand_Junction,_Colorado_Buildings, manual URL for entry into the JOSM MapWithAI plugin is https://services6.arcgis.com/Do88DoK2xjTUCXd1/ArcGIS/rest/services/Grand_Junction_CO_Buildings/FeatureServer/0 -- if you use this in the future, *please remember to remove OBJECTID and addr_state*).

JOSM has access to the 2019 (County wide) and 2020 (Grand Valley) aerial photos with the names starting as "Mesa County GIS". Please use those instead of Maxar inside Mesa County. (Note: I've also aligned those imagery layers and other common imagery layers like Maxar to survey monuments in the area.)

Thanks for your contributions,
vorpalblade

Reverted in changeset/108679380 due to the address change.

I'm probably going to revert this changeset for the following reasons:

1) The new address is wrong (1st street is 7 blocks west)
2) A building geometry was moved (not in and of itself a problem, but you failed to square the geometry after the move). And I'd probably check with an imagery offset (I added one at the intersection of North Avenue and 12th street for most major imagery providers). See the imagery offset database.

A couple of comments:
1) You probably cannot use that map as a source ("© 2020 COLORADO MESA UNIVERSITY") unless you have gotten permission from the college.
2) You modified the geometry of the college so it was in the road. Please don't do that.

Just an FYI, I *have* georeferenced all the major imagery sources in the area 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".

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

Hi there. It is nice to see someone else editing in this area using StreetComplete. It does look like you might have just been visiting, based off of your editing activity.

If you ever to edit using JOSM in the area, I *have* georeferenced all the major imagery providers using survey monuments in the imagery offset database.

And Mesa County GIS has allowed us to use their (much more) up to date imagery for tracing in OpenStreetMap.

Thanks for your contributions,
vorpalblade

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".

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