If both of you have check what min_height=* applies to is mapping of 3D objects in OSM. It applies to the lowest height a building/wall is placed in the render. We should not get this tag mixed up with a tag I use that is meant for attraction=* ways. If you want to see what I am referring to take a look at: osm.wiki/wiki/3D_tagging. And for the the actual tag min_height =* : osm.wiki/Key:min_height.

I'll do you one better and finish it today. I have the day off from work.

Location of trace layover: osm.org/changeset/85516740#map=19/28.35416/-81.56224

Original location of trace data from: osm.org/query?lat=33.81461&lon=-117.92071#map=19/33.81460/-117.92071

Sorry. This is a direct copy of Disneyland's Galaxy's Edge. I have physically mapped that one out in person so I copied the ways in a single trace. I was intending on dropping it over the FL duplicated version and trace new ways in. This trace is supposed to sit in the area between First Order Cargo and Olga's Cantina. The problem arose in it appears that the two projects do not scale properly between the two versions (either because the actual area is a different scale or because map projection, but I think its the first option) I am planning on checking out public imagery more closely to see if I'm still able to trace ways with minor adjustments. I am trying to still decide on what route to take but other edits have distracted me from finish that project.

So I made two types of changes.
1. Corrected the Brand name from Disney Resorts to Disney Parks as that's how this division of company is refers to itself. (https://disneyparks.disney.go.com/)
2. Removed the landuse=commercial use as doesn't feel that it applies to theme parks resorts. Commercial tag seem to indicates point of sales location for businesses. Theme parks and their surrounding property fall under leisure=resort tags.
3. Since you have sent me another notification on a different resort: place=locality seems to be a acceptable tag for theme park resorts as it is defined as A named place that has no population.

There are many issues with the set of edits you have submitted for MK.
1. The adding of pedestrian ways on top of pedestrian Areas is unnecessary. Yes I know it messes with the in browser navigation tool but its not needed.
2. It messes with the design. The use of highway=living_street has been approved for use in theme parks as special type of roadway like Main Street and for way accents. The edits you made messed with previous edits I have made in the past.
3. Setting up for upcoming features. In the next few day I will start going through the entire WDW property and add manmade=bridge, area=yes to all bridgeways and those edits make bridges are unnecessary. I have already converted my home park, DL, and will finishing the updates to WDW resorts hotels before getting started on the Bridgeway upgrades across property.

Speaking of using JOSM, I last tried JOSM several years and did not like the user interface compared to Potlatch. But with both Google and Microsoft abandoning Flash player support in the coming months I might need to start using it with Potlatch relying on Flash.

The original purpose to this edit is to update the area with new data not yet visible yet on Ariel imagery as I live in the area and visit this parking lot every couple of weeks. New Parking toll booths have been installed on the North-East portion of the lot. I was dividing the original tagged “wooded” area where the likely driveway entrance will be. I did not realize at the time that the way is currently tagged as natural=wood as I probably tagged the definition several years ago when I was new to the OSM project. A better tag will be landuse=forest but I am going to hold any updates to foliage until have done a proper inspection to this corner of the lot.

Speaking of using a more powerful editor...I currently have been using Potlatch for a majority of my edits but I have found with Go Map to be able to get more accurate node placement as well it easier to correct overlapping way issues with the app. Potlatch is great with big picture edits and Relationship tags but if you want to make a smooth curve kerb you need to have better control over node placement.

I find it fascinating actually...I'll hit this one but you are welcome to grab any others created. Also you might take a look at EPCOT since its even more complicated than the other parks.

I fixed it...but I did that over 7 years ago. The main area I edit is Disneyland and someone went through and found about 40 signal node polygons that Potlatch created by accident

No need I have been able to rebuild most of them and will finish the rest tomorrow night

PLEASE STOP EDITING WALT DISNEY WORLD! From reviewing you edits you are currently destroying hours of editing work and processes are currently under way to fixing your edits. Please review wiki.openstreetmap.org for any features in the map editor before changing map design and use the discussion tools and DMs to editors of areas before dismantling their work.

What construction is going on here? Are they already prepping for N-19 transfer

Sorry, My map did not render the area when I scrolled over it and mapped it over again. I have removed the duplicate ways and it appears that I'm not the only one as other lakes in the area have multiple map overs too.

tram line is incorrect as that tag relates to train vehicles, not road vehicles [trailway=tram]. This way has been corrected

Would it be better to use the full tag for operator= and also use the tag alt_name=USPS so when it's searched for it will still pop up?

I have already fixed it

I caught it

Your now mi spelling is knot the bets. You donut half to bee a dike abut it.

In what way? There is survey markings starting to map out the new route spray painted onto the cement