Why have you removed junction=circular from the Lucaya roundabout when this is precisely the type of junction it is meant to be used for according to the wiki?

I can't remember the signs on this specific junction. I think one of the 'circles' in this area has unusual priorities, but I'm not sure which. Unfortunately, as IIRC the signs are all physical rather than painted so aerial imagery isn't very useful.

I think [junction=circular](https://wiki.openstreetmap.org/wiki/Tag:junction%3Dcircular) was chosen for [way/26397622](https://www.openstreetmap.org/changeset/65138248) in the end.

I'm pretty sure there is no physical barrier here.

IIRC this is a leftover from the time of the roundabout's construction. The road heading east was to be referred to as the Fishing Hole Road and continued more or less directly east prior to the expansion of the harbour. This was continuous with way/654595434 which still retains this name as loc_name & alt_name. Note both ends are shown blocked in the 'premium' imagery layers you have cited, Bing and in the data itself.
Frankly, while the road heading east from here used to be primary (pre Warren J Lavarity Highway (way/303256235)) it is probably little more than unclassified/service now.

Not really, it's officially Grand Bahama Highway east of Mall Drive. I'm just not sure if the name change is at the roundabout or at Airport road where it becomes a single carriageway.

I think the signage was inconsistent when I was last there, with part of it called Queen's Cove Drive. I'm not entirely sure where the name changes from GB Highway; I know what would be logical, but logic doesn't always play a huge role.

What is your data source for this?

Cool, lets hope the coastline polygon gets updated before someone decides to "fix" the flooding.

This looks suspiciously like man_made=quay

Where was this mechanical edit discussed?

I mostly asked because I'd read this recently: osm.wiki/What%27s_the_problem_with_mechanical_edits%3F

Were these changes manually reviewed?

Yes, as stated in the previously linked Automated Edits code of conduct, discussion is typically held on the relevant mailing list.
Also as a quirk of local governance some establishments may well be nominally open until 23:59 and it would be perfectly reasonable for them to display this instead of 'midnight'.

IIRC traffic on the circle must yield to inbound traffic at nodes 289189608 & 289189063 (probably node/289189616 too). I have modified to junction=circular.

I think your changeset comment might be about a previous edit.

Do you have a source for this address? It seems odd for lot 1 to be on a neighbouring street and in the middle of a neighbourhood.

Also, in ISO 3166-1 alpha-2, The Bahamas is abbreviated BS not BM (Bermuda).

I think what you have traced as an extension of Montgomery Crescent is actually a maintenance track / cutline for a minor power line. I have split the way and updated the tagging of the new portion to reflect this.

Is this quite new? It isn't on the Satellite imagery yet.

That may be somewhat true for a road, but what valid interaction local detail could have with the Bermuda Triangle is beyond me (save at the end points).

I think the utility of this view on OSM Inspector is that many long ways are caused by things like a node being drastically misplaced accidentally (e.g. moved to 0,0) and are not realistic.

In other cases the way needs further legitimate refinement from imagery or survey (as you have done in some of your other recent edits). Artificial division of those ways masks a problem that still exists from people who may be able to resolve it. If no more detailed information is available, then I think the sparse data we have should remain as is rather than being further ingrained by interpolation.

In some cases though these long segments are real and I think should remain as is. In this particular case I think there is far greater danger from the way getting falsely entangled with objects in the Atlantic than there is from accidental duplication etc.