Ah, in that case it goes in `loc_name`, then; see osm.wiki/Names#Local_names_(loc_name)

> loc_name=* is for the name of a feature as it is known locally, but only where this is deemed to be too much of a slang name or otherwise unofficial-sounding.

Also, one observation: I see you renamed the "Orange Building" to "VT Parking Services", and I noticed there was another larger building directly north of it also named "Parking Services". The official VT map: https://campusmap.aws.gis.cloud.vt.edu/ (which I don't use directly for mapping, just citing as a reference here) names the latter as "Parking Services Building" and the former as Residence (Orange House), which it at least appears to be built as (building=detached) per Streetside, etc. To confirm, is former building also explicitly named Parking Services per your survey?
---

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

One thing I needed more info from you on: the new crossing added here was tagged `crossing=uncontrolled` and `crossing:markings=yes`, but the type of markings (most likely `zebra`, as used near-universally elsewhere at VT) was left unspecified, and no markings are visible on any available source of aerial or ground imagery (usable with OSM or otherwise). Could you confirm that zebra markings are present here? Thanks!
---

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

Also, in the same changeset ( https://osmcha.org/changesets/169441727 ) as a further improvement I added surface and foot/bicycle access tags to the sidewalk per local convention, as well as complete crossing tagging in line with standard practice.
---

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

Hey—thanks for adding this! I did notice a few issues, which I fixed where possible in changeset #169441727 along with some further improvements and other nearby fixes.

FYI, the specific things I noticed included:
- The link way between the south terminus of Beamer Way and the Huckleberry trail was removed (and without replacement with a noexit node) which breaks correct routing, despite there being an apparent physical path connecting the two. I added it back, this time properly modeling the path between them.
- The sidewalk crossed two service ways without an intersection node between them (or more properly, a crossing node/way), which I added.
- The sidewalk tags on the corresponding road needed to be updated to match your changes and not contradict them, which I did.
- The sidewalk lacked footway links at either end connecting it to the physically-accessible road junctions, which is important for proper routing. I added them.
---

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

Hey—I noticed the added building wasn't actually given the name "HAE Pods" (or `loc_name`, etc). Was that intentional?
---

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

See changeset #169374037 for the fence, track and landuse improvements to the actual western section of Heth Farm
---

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

*Eastern section, oops
---

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

Quick tip—in Rapid (which has the same datasets as MapWithAI for JOSM that I use), the "Commonweath Virginia Addresses" dataset that you're using here (source=esri/Virginia_address or esri_Virginia) has addr:county instead of the more complete, useful and locally/nationally accepted addr:city and addr:postcode. The "United States Addresses" dataset (source=esri/USA_NAD_Addresses or esri_DOT_addresses), by contrast, has essentially identical coverage (at least locally and likely statewide) but with addr:city and addr:postcode instead of addr:county, so you probably want to use that instead.
---

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

Also, change terrace unit to correct type instead of apartment

*And also add/merge complete address tagging
---

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

Done in changeset #168420335 ! https://osmcha.org/changesets/168420335
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/168325430

Yeah, seems like it was added 7 years ago in changeset #62253586 , alongside numerous other area streets.
---

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

Thanks!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/168375077

Ah great, thanks! One more thing I can check off from my near-term task queue. You planning on doing Turner Street NE too in the immediate future, or want me to take care of that? I wouldn't want to duplicate effort or make conflicting changes. Thanks!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/168325430

Seems like StreetComplete is bugging out here—all the modified ways were *already* tagged with both sidewalk=separate and sidewalk:both=separate, and all SC did was remove the (valid, as a graceful fallback for consumers that don't have full support for the newer/more detailed sidewalk:side) sidewalk=separate tag. I've reported the error to StreetComplete: https://github.com/streetcomplete/StreetComplete/issues/6378
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/166327264

I was really wondering about that one too...just hadn't quite summed up the gumption to do something about it quite yet, though I was planning to in the near future—thanks for taking care of it! Initially I thought they might be trees that some mapper decided were informal bicycle parking spots, but looking at the history looks like a ton of stuff (>1000 objects) were added in the changeset and it was probably just a copy-paste mistake.
---

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

Looks good; thanks for the fix!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/168118926

Hey Jake, thanks for the on the ground survey and updates on the recently reconstructed NE campus areas! Just a quick note—the parking lot perimeter way should be left untagged service=parking_aisle, as aside from a small portion it is not a parking aisle itself, and is rather the perimeter of the lot and main service way for navigating around the lot as a whole, between parking aisles. Per the wiki and the corresponding approved standards ( service=parking_aisle ):

Not every roadway within a parking lot is a parking aisle. Examples are:
* Forms the "trunk" or perimeter of the parking lot, connecting multiple parking aisles – use highway=service without service=* instead. There may be parking spaces on either side, but the roadway's primary purpose is to get drivers to another part of the parking lot.
* Roadway does not have any parking bays itself.

I expect to do another pass through this area in a few days and can fix it then, though feel free to do so before I get to it. Thanks!

No worries, it happens! I make enough mistakes as it is on desktop even with an extensive safety net of JOSM, Osmose, OSMI, KR and custom validator rules that I don't trust myself to edit on mobile, hehe