Hi there, it looks like Forest Friday Cheers is an event that takes place at Apocalypse Ale Works, not a permanent physical space. You can add the bitcoin related tags to the main Apocalypse Ale Works if you would like as well as adding information about the events space, but please do not create nodes specifically for events like this. Thanks.

Hey there,

Your improvements are welcome, though everything on this property should be marked as access=private as it is a derelict site and closed to the public. Just a heads up if you come back to this area, I've added the tags so no need to do anything.

Makes sense. If we were to re-add these with the proper geometry, could we still add them, using a non-administrative boundary tag and no admin_level? Or would you suggest leaving them as nodes with no established boundaries?

I'll admit this was something I did early on in my mapping career- so the topology of them was probably bad. I take responsibility for any mistakes there.

I'd be happy to import them the right way as I think it's useful information, unless there are other objections than just the geometry.

Sounds good. I'll forward this on to the local group and we can talk about the best practice for this redevelopment project. Thanks!

I need to resurvey but it was my understanding that this section of Main Street would be closed for redevelopment for a significant period of time - see https://www.lynchburgva.gov/875/Downtown-Renewal-Construction-Project.

Like I said, I need to get out there and update the check date but last time I was down there a couple weeks ago it was still closed.

More nonsensical parks. way/1300227263

Additionally, please stop tagging landuse parcels with business details, tag the building itself, not the landuse. What sources are you using to get the ownership for the parcel data? "Virginia Property Lines" is just an imagery overlay, clearly you are obtaining ownership information from somewhere and you are not sourcing the data. I would like to verify if it is licensed for use in OSM.

Why have you created recreation grounds that are literally just the street areas? relation/17827478 way/1300805998

Please stop importing parcels with nonsensical tags. They are unhelpful to map and do not exist on the ground. You have been blocked multiple times for this.

I see. I'm looking right now on water=*, and for pond it says " A pond: a body of standing water, man-made in most cases, that is usually smaller than a lake." This is the definition I'm using and agree with. I know for reservoir it adds that it is held back by a dam, and while the ponds in this area *are* usually impounded by a small earthen dam, I think the small size takes priority in the definition here. Ivy Lake itself I would probably consider the smallest "reservoir" I would tag.

Hi, regarding the traffic signals at Timberlake and Candlewood Court/West Edge Way (node/220982062) in this area we (local mappers myself, partytax, and blendergeek) have agreed to use the "Tag all incoming ways" style (highway=traffic_signals#Tag_all_incoming_ways) for handling complex stoplights involving dual carriageways. The signal lights are placed at the stop bars for each incoming way. The benefit of this is that a car only passes through one traffic signal node when making a turn and it is slightly more precise. Please do not simplify intersections that are mapped this way in the Lynchburg area. Thanks.

hey! great work updating the geometry of Ivy Lake and a bunch of the ponds around the area- I just wanted to suggest using water=pond instead of water=reservoir for the small bodies of water. The wiki is a little ambiguous but seems to suggest that pond is better for small water bodies, even if man-made with earthen dams. Reservoirs tend to be larger and serve a specific purpose (like for drinking water or hydroelectric generator) whereas I feel like the wiki page for pond more accurately describes these small bodies of water. It's personal preference, but I want things to be consistent in this area. I'd love to hear your thoughts about it and make the case for water=reservoir though.

*edit: I see you're already using that way of tagging, I just saw these when investigating uses of traffic_sign=* in the area for QA work

just FYI: when adding a stop sign as a node on the way, it should be tagged as highway=stop. traffic_sign=stop is for describing the actual sign itself, off the street.

Valid point.

When I did the first pass to specify crossing:markings type (lines, ladder, zebra) I did a query on all the existing crossing=marked in the city. I wanted to leave the existing data alone as much as possible and only add the :markings tag on top- this worked for the most part, until I came across this one node which looked like the markings had been removed. I didn't want to remove the crossing= tag as that would be removing existing data.

Really the main issue here is that it is a data conflict that can only be resolved by a ground survey, which is what my fixme note is for and was added to explain the situation. I just haven't had a chance to make a trip around town to survey fixme's I've added yet, I usually do those in batches.

Hey, just so you know, I intentionally left off crossing:markings from this crossing (node/9241020432) as from aerial imagery it looks like the road got repaved sometime between Bing's image capture and the Virginia state imagery capture. I put a fixme on the node and way to make sure someone knew about this.

I haven't had a chance to survey it yet, but please do not re-add crossing:markings unless you can verify with a ground survey whether or not the crossing got repainted. I know iD likes to yell and makes it easy to add, but there was a reason it was missing from this crossing.

I've also been trying to specify what type of markings there are in crossing:markings, so if you come across one feel free to add that extra detail from imagery instead of just adding "crossing:markings=yes"

This changeset looks pretty good too, the only thing I would advise is that "closed=" is not really a key that's in use. To indicate a shop is closed and a building is vacant, you can change the "shop=" to a "disused:shop=". This allows you to still specify what kind of shop it was, but also makes sure that any of the third parties who use OSM data know it's not currently open, because they may not know about the tag "closed=permanently."

If it's more run down and fully abandoned, you can also use "abandoned:shop" and "abandoned:building", but if it's still in good shape and the building could be re-opened with only some cleanup work then disused is the best tag.
---

Published using OSMCha: https://osmcha.org/changesets/142790174

These edits look good- though it looks like you removed the wikidata tag. Could you add it back? Its value was Q21028360.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/142692244

Hi there- I saw you requested a review on this edit. highway=pedestrian might be more appropriate here than highway=footway. highway=pedestrian

Hey there! After asking around (because I wasn't sure what to tag it as either) it looks like man_made=cooling (man_made=cooling) is the best tag for a large HVAC unit. I don't think it will render on the map, so just be aware of this. I also don't think iD has a preset for it, so if you come across more, you'll have to manually add the tag at the bottom. However, we always strive for adding accurate tags even if they aren't rendered or preset.

Thanks for your work around E. C. Glass!

Hey there! I addressed your fixme request- the tagging for a pedestrian area is

highway=pedestrian
area=yes

instead of
area:highway=footway

That's why it wasn't rendering. It should appear on the map now!