Hey, for the maintenance facility on the north side of the airport, I noticed you realigned to the imagery without offset. Before retracing the buildings, I had imagery aligned based on a survey marker to the best I can tell. Generally default offset for map imagery is inaccurate, especially in Hawaii.

Hi Andres,

I don't really know what available source can be used to mark the boundaries accurately. The closest I found was through Hawaii's Open GIS which has tax plats/zoning/ownership info which can be linked together to show all these areas to be military use but doesn't state it is necessarily part of the base (specifically the residential areas to the east of the golf course). But I think the best person to ask was the person who originally created and adjusted the relation @nickvet419.

Only section I would consider not part of the base within the airport boundaries the hazardous cargo pad and related taxiways or the airport control tower but looking at zoning https://geoportal.hawaii.gov/datasets/cchnl::zoning-5/about, I'm pretty certain its fine as is. You'd be surprised how much of the area you'd think is part of the airport but is still part of the base.

The rest I believe would still technically be counted as part of the base even though it's separated by H1 and even though it is publicly accessible, it doesn't mean it isn't part of the base either. The Pearl Harbor National Memorial where you visit the Bowfin and the USS Arizona/Missouri is open to the public but still publicly accessible. Using Bing Streetside, the areas you mention have public areas but likely still belong to the base.

By this map from the military site available to the public (https://cnrh.cnic.navy.mil/Installations/JB-Pearl-Harbor-Hickam/About/Map-of-JBPHH-MWR-locations/) the land marked is considered part of Joint Base Pearl Harbor Hickam. And from the Hawaii Statewide GIS Data (if you look up the various tables and cross reference the land usage), the land use is marked as military as well. If not those sites, the map layer on ID called USGS topographical map surrounds the military areas in a thick red highlight as well (though the map might be on the older side)

Even if it is not part of the base, you would split the relation rather than change the entire relation value. No source was mentioned on the changeset either which points to the source which mentions why it would not be considered part of the military base either and even looking at satellite imagery, those areas are fenced off and requires going through a checkpoint to enter those areas which still points it towards being part of a military base and even if not, used for military purposes (recreation or residential land uses dedicated only to military personnel still counts as military landuse)

As mentioned in the other changeset you have done, I would suggest reverting the tag changes since a military base can contain other land usages and doesn't preclude them from being tagged as landuse=military and military=base.

Hi, I know you're new so adding this comment to notify you of the error.

For this changeset and the prior changeset/167596468 the previous tags looked correct. For this changeset specifically, the name is correct to be called the Joint Base Pearl Harbor Hickam since the entire Pearl Harbor military base is called that. Not to mention, in the other changeset, you mentioned it being a golf course and residential area, but that does not preclude them from being part of the military base and the removal of the wikidata tags since a military base can easily contain these features and as long as there are separate areas appropriately tagged representing them within the military base, that is fine.

Because of this, I would suggest reverting these changes back to the original.
changeset/167596468

I believe you accidentally named the retail area/parking lot with bus route info?

That's good you're using Strava Heatmap for reference. Just asking, but are you using the general heatmap or a subset like running or cycling? If you use the general heatmap, it merges everything together making it more difficult to align. If using it separately, like running for example, people tend to stick to sidewalks and crosswalks therefore on bigger roads, the heat trails bracket the roads allowing for better alignment. Similarly, for bikes (rides), they will tend to ride on the side-most lane (unless circumstances differ) and you can rely on that as well. I do tend to use JOSM since layering is easier there but I think there is a plugin for the iD editor to overlay that. Unfortunately, the imagery offset database connection isn't available in iD osm.wiki/Imagery_Offset_Database. I have uploaded some to there but the older ones from when I first started using it (and with older much blurrier imagery than the current Bing), are likely incorrect.

As a separate note, for roads which are straight, you should align/square the nodes since that'll make them not zig zag very slightly.

After finishing this area, I won't head down to Ewa Beach first but Royal Kunia first and maybe realign/redraw buildings which were not done correctly since it was earlier on when I first started editing and with worse imagery. Then I'll head south.

You should fix the error. Also are you simply aligning to imagery or are you using some gps tracks/Strava heatmap to align the roads, if you aren't then you realigned (likely misaligned) roads to a different misalignment.

Within the ID editor (web), there is an option to realign imagery but not possible to overlay something like Strava heatmaps but at least GPS traces is available albeit not being available everywhere since people have to upload it themselves to OSM. Using that you can still align the imagery up close enough (will never be perfect lol). Using a desktop editor like JOSM (with plugins for assistance) would be an alternative allowing for easier editing of big relations like bus routes. Checking the wiki would be better for understanding how to possibly set that up. osm.wiki/JOSM

Hey George, great job on adding all TheBus routes all around Oahu. Definitely would be a pain to do. Just as a note, when aligning roads, you should do it based on GPS traces or on Strava Heatmap if you want. The Bing/Esri satellite imagery isn't aligned correctly.

Just noticed, but when you realigned the waterways, you did not connect Kalauao Stream to Pearl Harbor.

Hey, although buildings did need to be adjusted, it seems you used the possibly default alignment rather than with something more accurate. Within the area (most of the traced buildings in the area), I have used Strava Heatmaps to align roads and in turn the buildings.
Cheers

Hi Tom,
I feel the change in tags from cape to locality might be in err based on definitions provided by OSMWiki. I have linked below two locations of discussion.
https://community.openstreetmap.org/t/possible-error-in-the-mass-retagging-of-natural-cape-to-place-locality-in-hawaii/107959
https://osmus.slack.com/archives/CCJ2P6KCH/p1704946819050559

It seems on the Grandview peak node, you inputted the elevation value in feet rather than in meters.