Presets for popular Seamark tags

[k-yle]

This issue tracks the progress of creating presets for popular Seamark tags.

Numbers indicate tag usage as of December 2022.

Buoys and Beacons

Currently being discussed in #512

• Buoys
  • Cardinal Buoy 10k
  • Isolated Danger Buoy 600
  • Lateral Buoy (a.k.a. Channel Buoy) 56k iD#5297
  • Safe Water Buoy 1k
  • Special Purpose Buoy (a.k.a. Generic Buoy) 12k
  • Mooring - see below
  • Visitor Mooring - see below
• Beacons
  • Cardinal Mark 1k
  • Isolated Danger Mark 14k iD#5297
  • Lateral Mark (a.k.a. Channel Beacon) 27k iD#5297
  • Safe Water Mark 98¹
  • Special Purpose Mark (a.k.a. Generic Mark) 14k

Other feasible presets

• Piers/Jettys/Pontoons 572k
• Mooring 58k iD#5297
• Slipway 49k
• Ferry routes 29k iD#5416
• Ferry terminal 29k iD#2883
• Marina 27k
• Lock Gate 22k
• Navigation Line & Recommended Track 20k + 3k
• Pile 19k
• Distance Mark 13k
• Bridge height/width restriction 10k
• Wreck 5k iD#5302
• Berth & Anchor Berth 4k + 0.6k
• Anchorage Area 4k
• Restricted Area 3k
• Offshore Platform 3k
• Fairway 1.6k
• Lifeboat Station 600 #76
• VHF calling-in point 400
• Pilot boarding point 500
• Virtual Aid to Navigation (AtoN) 300
• Seaplane Landing Area 100 - #569
• "Small Craft Facilities"
  • Marine Fuel 600 iD#2589
  • Marine Toilet Disposal 500 iD#2623
  • Visitor Berth 900
  • Visitor Mooring 76 too rare?

Obscure features

Probaby not appropriate to create presets for these

• Marine Dumping Ground 200
• Hulk 200
• Traffic Separation Schemes (lane, line, zone, roundabout, crossing, boundary, inshore) 800
  • usually miles away from the shore, and will never need to be editted

Too complex

It may be too complicated to add some of these features due to their tagging system:

• Simple Lights 50k
• Sectored Lights 11k
• Notice Marks 23k
  • Regional presets are supported so this could be possible for just Europe
• Marine Rock 120k and Marine Obstruction 5k
  • May be confusing since these two are similar, and there are already presets for Rock, Boulder, and Bare Rock
• Fog Signal 1k
  • nearly always combined with another feature, so this would just be fields.
• Signal Station 1.6k + 1.3k
  • two different top-level tags ('traffic' vs 'warning'), might be confusing what the differece is. Ideally this would be one preset.

Things to consider

• 7 different presets for buoys and 4 for beacons will be very confusing. Ideally it would be 1 preset for buoys, but this isn't possible since they all have different top-level tags.
• Would 21 new presets overwhelm mappers? Should they be hidden except unless you turn a special mode?
• OpenSeaMap background imagery enable the openseamap overlay iD#8824

Footnotes

1. Much less common than the others because the water (usually) can't be safe if it's shallow enough for a beacon ↩

[matkoniecz]

seamark:type=fairway seems to duplicate waterway=fairway without a good reason, see https://wiki.openstreetmap.org/wiki/Tag:seamark:type%3Dfairway and https://wiki.openstreetmap.org/wiki/Tag:waterway%3Dfairway

[k-yle]

seamark:type=fairway is for the area, waterway=fairway is for the linear centreline.

The tags have two totally separate purposes, but the wiki doesn't explain it well.

• waterway=fairway (line) is used by routers along with waterway=stream/canal/river. It exists purely for routing.
• seamark:type=fairway (area) denotes the geographical limit of the fairway & its assosiated restrictions (like no_anchoring, no_fishing etc.)

[jsavage]

seamark:type=fairway seems to duplicate waterway=fairway without a good reason, see https://wiki.openstreetmap.org/wiki/Tag:seamark:type%3Dfairway and https://wiki.openstreetmap.org/wiki/Tag:waterway%3Dfairway

As a skipper of a yacht, it seems rather pointless to mark a fairway on a chart or OSM. We talk loosely about 'fairways' but I am not convinced that the term is that useful or that there is any useful purpose in marking them - after all, they are usually defined (Bordered) by other navigation aids such as buoyage and in some cases geography.
Unless someone can come up with a use case my recommendation would be to consider dropping both definitions.