Hi again :), No problem. If you go here: osm.wiki/OSM_Inspector/Views/Tagging#Name.2Fdescription_without_feature_tags
This link lays out the problem. The node is flagged as an error because the "key" has no "feature" associated with it. A feature could be a building, an amenity, a shop, an entrance, a stop sign, etc. A description of the object is needed. That's why, for example, a stand-alone address node gets flagged as an error. It's not clear what the address node is associated with. An easy fix might be to create a building and physically attach the node to it. Or, the node itself might fixed by adding a building tag to the node. Cheers! :)

Hello, again :) Around these two buildings you created an area named, "du36043702". Can I assist you in finishing your work correctly?

Greetings and welcome to openstreetmap :) Thank you for your additions to the map. I noticed you made some edits, but they aren't finished yet. For example, around Liberty Media in the Denver area you created an area named, "li39558011". If you explain what you are trying to do here, I'm happy to help you finish the work correctly.

Hello again, I see here you created a line around Palazzo Verdi. The line has no tags that describe your meaning. Can I help you finish what you started?

Greetings and welcome to openstreetmap :) Thank you for your additions to the map. I noticed you made some edits, but they aren't finished yet. For example, around the Parker Hannifin Corporation, you created a line, but there are no tags describing what it is for. Are you trying to describe an area that has a name?

I wish I could say I was an expert and I knew what is preferred, but I'm just learning with some aspects of addresses. However, yes, a stand-alone address that isn't a building or isn't physically attached to a building always pops up as an error. If you're ever curious to see, just go to https://tools.geofabrik.de/osmi/ and in the search field type, "Denver". Then in the upper left corner use the drop down list to view, "tagging". You'll see a few blue triangles in southeast Denver which indicate OSM Inspector-tagged errors. You can zoom in and click on a triangle. Then, on the right, under, "Selection" if you click on one of the small magnifying glasses, it will take you directly to the tagged error for editing. Cheers! :)

Greetings. I see you created some lines, or ways, northeast of East 110th Avenue and Landmark Drive in Commerce City. Did you mean to create residential roads here? Can you please add the correct tags? If you need any assistance, please feel free to ask :)

Hello, again. I'll be happy to check with you before making any corrections. No problem. Are you still working on Hampden Village? It looks like the last edit there was 25 days ago. Cheers :)

Greetings, again :) I was chasing down some OSM Inspector-tagged errors and came across the stand-alone address nodes you created (Addison at Cherry Creek Apartment Homes). I didn't quite understand why they were tagged as errors, so I contacted the website's team. Sorry to modify your work, but I just wanted to clean up the error notifications. This is the clarification I received: "These nodes have address tags and a description tag but nothing else. Such description are not useful because they are not bound to a physical feature. If they describe a building, they should be tagged on the building outline. If they describe a residential area, they should be tagged on the landuse polygon.
See also https://blog.geofabrik.de/?p=425 and
osm.wiki/w/index.php?title=OSM_Inspector%2FViews%2FTagging&type=revision&diff=1586002&oldid=1503850
(I just added the section)
Best regards
Michael Reichert
OSM: Nakaner"

Me again :) Since I've been an air traffic controller for 38 years, I took interest in the points you created for emergency landings. Perhaps it would be better to tag these as helipads? I know these are emergency landing sites and not necessarily designed as helipads per se, but the tag description is, "A landing area or platform for helicopters", which would fit if these have been officially designated as landing areas for use in emergencies. Just a thought.

Thanks! Sorry to keep bothering you. I'm just trying to clean up automatically tagged errors ;)

Hi again :) I was looking through some edits that have been tagged automatically as errors and I see your new milestones. I think the addition of the milestones is a great idea, but I don't think the way you've mapped them will work. Are they showing up on any maps you use? I'm certainly no expert on milestones, but I did some research. Here are a couple of links, if you're interested: highway=milestone
https://help.openstreetmap.org/questions/39161/highway-milestones-mile-markers
For sure, the milestone needs to be part of the road, not next to it. I experimented with creating a node. You can look at it at mile 31 on South Saint Vrain Drive. I think this might work better for you and it should render correctly on the map. But again, I'm no expert on milestones.

Greetings and thank you for your additions to openstreetmap. I noticed you created a line that pretty much follows along Longmont's administrative boundary. The line is untagged, that is, it has no tags that describe what it is or what its purpose is. Is this line serving a purpose? Thanks :)

Cheers! :)

Hello, thank you for your reply. While you are trying to decide what went wrong with your import, will you please remove all of the thousands of buildings you have added to the Denver area?

Greetings. I'm no expert on imports and please correct me if I'm wrong, but aren't you required to create a dedicated user account for an import? osm.wiki/Import/Guidelines

I noticed you have imported hundreds, maybe thousands of buildings around the area of West 25th Avenue and Sheridan Boulevard, Denver, Colorado. These buildings do not represent what is on the ground. Perhaps you made this import by mistake? Did you contact local mappers for a community buy-in? Did you create a dedicated user account for the import? way/563532590
osm.wiki/Import/Guidelines

Good to hear. Thanks :)

I should also mention, we don't use all caps. For example, 2850 MAGNOLIA DRIVE, should be Magnolia Drive. Again, the drop-down menu should make it easy to correct

Howdy, and thanks for all your hard work adding to the map. I just wanted to reach out to you and let you know your work is appreciated, but a lot of your work won't actually link to the map. The problem is that if a building is, for example, at 760 Coyote Circle, but it's mapped as 760 Coyote Cir., it pops up as an error and won't link to the map. Another random example would be 228 N Dory Lakes Drive. It won't link because we don't use abbreviations with the names of streets. Fortunately, when entering info into the map there is a drop-down menu, so it's easy to enter, North Dory Lakes Drive. If you go back and correct all your edits, they will link correctly in the database. If you have any questions, feel free to ask :)