pbf/NavSea_Object_Taxonomy_Manual_Review.md

NavSea Object Taxonomy Manual Review

1 Review Objective

This package is for manual confirmation of the current NavSea object taxonomy derived from the pbf_analysis database snapshot in this workspace.

The review focuses on confirming:

• canonical object type naming
• family grouping
• detection grouping
• geometry unification or splitting
• ambiguous object handling

The current pipeline already separates source-preserved render layers, semantic object layers, and detection-oriented object taxonomy. This review package highlights the places where human confirmation is still needed before treating the taxonomy as stable.

2 Review Priority Groups

Priority A - Immediate navigation safety relevance

Hazards, wrecks, rocks, reefs, dangerous obstacles, navigation marks, route controls, anchorage controls, restricted areas, and fishery hazards that can affect collision, grounding, or entanglement decisions.

Priority B - Navigation context / operational relevance

Boundaries, facilities, subsea cables and pipelines, piers, floating structures, and other contextual objects that matter to operations even when they are not direct collision targets.

Priority C - Background / rendering objects

Labels, bathymetry support layers, clip layers, land masks, and other source-preserved layers that may be rendering support rather than semantic end objects.

3 Manual Review Candidate Table

review_priority	layer_name	class_name	shape_name	vt_layer	observed_geom_types	total_feature_count	suggested_canonical_object_type	suggested_canonical_family	suggested_detection_class	suggested_review_reason	needs_manual_review
A	航行危険障害物	暗岩		p航行危険障害物	Point	10,366	暗岩	hazard	obstacle	Direct grounding hazard; confirm whether rock / reef subtyping should remain separate from generic obstacle handling.	YES
A	航行危険障害物	洗岩		p航行危険障害物	Point	3,323	洗岩	hazard	obstacle	High-salience grounding hazard; confirm stable canonical naming under hazard family.	YES
A	航行危険障害物	干出岩		p航行危険障害物	Point	1,178	干出岩	hazard	obstacle	Intertidal hazard object with clear navigation relevance; confirm whether it stays separate from other rock hazards.	YES
A	投錨注意障害物	険悪物		p投錨注意障害物 / P投錨注意障害物	Point, Polygon, MultiPolygon	26,836	険悪物	hazard	obstacle	Same object appears as point and area; confirm whether symbolic and areal forms should be unified or split.	YES
A	投錨注意障害物	魚礁		p投錨注意障害物 / P投錨注意障害物	Point, Polygon, MultiPolygon	16,608	魚礁	hazard	obstacle	Artificial reef can imply fishery semantics or navigation hazard; family assignment needs human confirmation.	YES
A	航路標識点		灯 (Lt)	p航路標識群	Point	14,936	灯 (Lt)	navigation_aid	navigation_mark	Core navigation mark subtype; confirm whether light subtypes should be normalized under a broader canonical lighthouse / light object.	YES
A	航路標識点		防波堤灯台	p航路標識群	Point	4,679	防波堤灯台	navigation_aid	navigation_mark	Shape-driven subtype may be a naming variant of a broader light / lighthouse family.	YES
A	錨泊地等			p錨泊地等 / P錨泊地等	Point, Polygon	234	錨泊 (指定)地	anchorage	anchorage	Same anchorage concept appears as symbol and area; confirm whether annotation and area extent should remain one object type.	YES
A	施設・境界線等	港則法による境界		L741	LineString, MultiLineString	1,696	港則法による境界	boundary	boundary_control	Regulatory meaning affects route compliance and alerting; boundary family and detection role should be confirmed manually.	YES
A	海岸線等深線等	浅所危険界		P基本線	Polygon, MultiPolygon	31,537	浅所危険界	hazard	obstacle	Shoal hazard boundary may be treated as hazard extent, boundary object, or bathymetry support; requires explicit confirmation.	YES
A	漁具定置箇所	区画漁業		P漁具定置箇所	Polygon, MultiPolygon	19,025	区画漁業	fishery	fishery_area	Fishery extent has entanglement and operational relevance; confirm fishery-area grouping and naming.	YES
A	漁具定置箇所	定置漁業		P漁具定置箇所	Polygon, MultiPolygon	3,570	定置漁業	fishery	fishery_area	Fixed fishery installations should be checked against other fishery-area types for canonical consolidation.	YES
B	海岸線等深線等	浮施設・桟橋		L基本線 / P基本線	LineString, MultiLineString, Polygon, MultiPolygon	30,090	浮施設・桟橋	infrastructure	structure	Strong multi-geometry ambiguity across line and area representations; confirm unify vs split between centerline and footprint semantics.	YES
B	海岸線等深線等	未測海域		L危険界 / P基本線	LineString, Polygon, MultiPolygon	4,554	未測海域	water_area	water_area	Appears both as boundary and area extent; confirm whether unsurveyed-region boundary should be separated from area fill.	YES
B	施設・境界線等	海底線 (電信電話)		L海底線	LineString, MultiLineString	12,817	海底線 (電信電話)	utility	utility_line	Utility line can also imply entanglement / anchor risk; confirm utility vs hazard emphasis.	YES
B	施設・境界線等	海底輸送管 (水)		L海底線	LineString, MultiLineString	655	海底輸送管 (水)	utility	utility_line	Pipeline semantics are operationally important and come from a container layer; confirm naming and grouping.	YES
B	施設・境界線等	養殖場		P施設・境界線等	Polygon	716	養殖場	fishery	fishery_area	Fishery object currently originates from a facilities / boundary container layer; confirm semantic extraction is correct.	YES
B	施設・境界線等	漁網		P施設・境界線等	Polygon	178	漁網	fishery	fishery_area	Net-related entanglement risk should be confirmed as fishery semantics rather than generic facility content.	YES
B	航路	航路 (法律による航路)		L航路 / P航路	LineString, Polygon, MultiPolygon	404	航路 (法律による航路)	route	route_reference	Legal route appears as line and area; confirm whether centerline guidance and regulated area should be split.	YES
C				P基本線ククリ	LineString, MultiLineString	1,080,780	P基本線ククリ	overlay_support	render_support	High-volume clip / outline layer likely acts as rendering support rather than semantic object content.	YES
C				P危険界ククリ	LineString, MultiLineString	51,962	P危険界ククリ	overlay_support	render_support	Source-preserved hazard-outline layer; confirm it should stay container / render-only.	YES
C				P投錨注意障害物ククリ	LineString, MultiLineString	8,743	P投錨注意障害物ククリ	overlay_support	render_support	Outline layer around anchoring hazards may be symbolic support rather than independent semantic object.	YES
C				P航路ククリ	LineString, MultiLineString	864	P航路ククリ	overlay_support	render_support	Route clip / outline layer should likely remain render support; confirm no semantic promotion is needed.	YES
C				L海底地形	LineString, MultiLineString	2,075,172	L海底地形	overlay_support	render_support	Very large source-preserved layer may be bathymetry render support rather than end-user semantic taxonomy.	YES
C				p地名	Point	36,247	p地名	overlay_support	render_support	Label layer behaves as background annotation support, not operational semantic object content.	NO
C				p地名陸	Point	35,388	p地名陸	overlay_support	render_support	Label layer behaves as background annotation support, not operational semantic object content.	NO
C				P穴	Polygon, MultiPolygon	367,217	P穴	overlay_support	render_support	Land-mask support layer appears stable as rendering support and does not currently require semantic taxonomy splitting.	NO

4 Ambiguity Categories

Multi-Geometry Ambiguity

Current high-value multi-geometry objects include:

• 浮施設・桟橋: 30,090 features across LineString, MultiLineString, Polygon, MultiPolygon
• 険悪物: 26,836 features across Point, Polygon, MultiPolygon
• 魚礁: 16,608 features across Point, Polygon, MultiPolygon
• 未測海域: 4,554 features across LineString, Polygon, MultiPolygon
• 航路 (法律による航路): 404 features across LineString, Polygon, MultiPolygon
• 錨泊 (指定)地: 234 features across Point, Polygon

Primary review question: should these remain one canonical object with mixed geometry support, or should point-symbol, line-boundary, and area-extent variants be split into separate semantic objects?

Navigation Meaning Ambiguity

The following objects directly affect collision, grounding, anchor, or entanglement reasoning and should be reviewed first:

• 暗岩
• 洗岩
• 干出岩
• 険悪物
• 魚礁
• 浅所危険界
• 漁網
• 養殖場
• 海底線 / 海底輸送管

Primary review question: does each object belong in hazard, fishery, utility, or another family when detection behavior is considered?

Source Layer Container Ambiguity

The current layer rules identify several likely container layers:

• P基本線: container_layer, 34 semantic object types, 701,625 features
• P施設・境界線等: container_layer, 16 semantic object types, 6,425 features
• L海底線: container_layer, 5 semantic object types, 14,391 features
• L基本線: container_layer, 5 semantic object types, 53,615 features

Primary review question: should these layers remain source-preserved render containers while downstream products use extracted semantic objects instead?

Regulatory / Boundary Ambiguity

Objects with strong legal or control semantics include:

• 港則法による境界
• 航路 (法律による航路)
• 錨泊 (指定)地
• 浅所危険界
• 未測海域

Primary review question: should regulatory boundary geometry and filled-area geometry be modeled as the same object type or as separate rule / extent objects?

5 First-Pass Recommended Review Scope

Focus first on classes and layers most similar to the task brief:

• 航行危険障害物
• 投錨注意障害物
• 航路標識点
• 航路境界等 / 航路 (法律による航路)
• 錨泊地等
• 施設・境界線等
• 海岸線等深線等 / 海岸線等深線等小縮尺版
• 漁具定置箇所

Recommended first-pass order:

1. Confirm hazard objects and shoal / reef / wreck naming
2. Confirm navigation-mark subtype normalization
3. Confirm anchorage, route, and regulatory boundary grouping
4. Confirm fishery and utility objects extracted from container layers
5. Confirm which clip / support layers remain render-only

6 Proposed Review Decisions

Candidate Object	Suggested canonical_object_type	Suggested canonical_family	Suggested detection_class	Reason	Manual confirmation required
険悪物	険悪物	hazard	obstacle	Large mixed point / area hazard set; important to decide whether symbol and extent remain unified.	YES
魚礁	魚礁	hazard	obstacle	Could be treated as hazard, fishery, or hybrid operational object depending on downstream use.	YES
暗岩 / 洗岩 / 干出岩	Keep as separate named hazard objects	hazard	obstacle	Distinct rock-hazard names are meaningful for chart interpretation and should not be collapsed without explicit approval.	YES
浅所危険界	浅所危険界	hazard	obstacle	Current suggestion treats it as hazard extent, but it may need a boundary-style subtype.	YES
灯 (Lt) and light subtypes	Normalize under light / navigation mark family while preserving subtype label	navigation_aid	navigation_mark	Many shape-driven names likely belong to a common aid-to-navigation family with subtype metadata.	YES
錨泊 (指定)地	錨泊 (指定)地	anchorage	anchorage	Point annotation and polygon extent probably represent the same concept, but a split between label and area remains plausible.	YES
港則法による境界	港則法による境界	boundary	boundary_control	Legal boundary semantics justify keeping a distinct boundary object if user confirms.	YES
航路 (法律による航路)	航路 (法律による航路)	route	route_reference	Line and polygon forms may need separate centerline and regulated-area objects.	YES
浮施設・桟橋	浮施設・桟橋	infrastructure	structure	Strong line / area dual representation suggests a possible split into linear and areal facility objects.	YES
未測海域	未測海域	water_area	water_area	Boundary plus filled-area modeling should be reviewed before finalizing canonical geometry rules.	YES
海底線 / 海底輸送管	Keep separate utility object types by infrastructure kind	utility	utility_line	Operationally relevant and extracted from a container layer; keep distinct unless user prefers a broader subsea-utility object.	YES
区画漁業 / 定置漁業 / 養殖場 / 漁網	Keep as fishery-area objects with subtype distinction	fishery	fishery_area	These support entanglement-aware review and likely should stay distinct within one fishery family.	YES
P基本線ククリ and similar ククリ layers	Keep as source-preserved render support	overlay_support	render_support	Current evidence suggests these are clip / outline / render-control layers rather than semantic end objects.	YES
p地名 / p地名陸 / P穴	Keep as render-support / background objects	overlay_support	render_support	These appear stable and low-risk as non-semantic support layers.	NO

7 Layer Review Appendix

source_layer	semantic_granularity	current_rule_guess	review_reason	needs_manual_review
P基本線	container_layer	Container surface layer feeding bathymetry, hazard, water-area, and facility objects	Very high semantic fan-out: 34 object types across 701,625 features.	YES
P施設・境界線等	container_layer	Container surface layer for facilities, boundaries, fishery, and place objects	Mixed semantic content suggests it should remain a container layer rather than a single semantic layer.	YES
L海底線	container_layer	Container linear layer for cable and pipeline objects	Contains multiple subsea utility types with shared rendering source.	YES
L基本線	container_layer	Container linear layer for piers, berths, removed objects, and linear marine structures	Same source layer mixes several operationally different linear object types.	YES
p航路標識群	semantic_layer	Stable semantic point layer with shape-driven navigation-mark subtypes	Semantic layer is good, but subtype normalization still needs manual confirmation.	YES
p投錨注意障害物	semantic_layer	Stable semantic hazard layer with mixed object meanings	Contains hazards, reefs, current phenomena, and seabed-related points that may need family confirmation.	YES
p航行危険障害物	semantic_layer	Stable semantic hazard layer	High-priority safety layer; naming and family assignments should be checked even if the layer itself stays semantic.	YES
P錨泊地等	semantic_layer	Semantic area layer for anchorage and restriction objects	Needs confirmation that point and area anchorage variants are modeled consistently.	YES
L等深線	semantic_layer	Stable contour layer	Geometry behavior looks expected for contour lines; low ambiguity.	NO
p地名	style_or_source_layer	Source-preserved label layer	Background label support; not currently a semantic review focus.	NO
p地名陸	style_or_source_layer	Source-preserved land label layer	Background label support; not currently a semantic review focus.	NO
P穴	style_or_source_layer	Source-preserved area support layer	Stable render-support role; no strong evidence for semantic promotion.	NO

8 Review Outcome Guidance

Please confirm the following decisions after manual review:

1. Confirm canonical object naming for hazards, aids to navigation, route controls, anchorage objects, fishery objects, and utility objects.
2. Confirm family grouping for ambiguous objects such as 魚礁, 浅所危険界, 未測海域, and subsea infrastructure.
3. Confirm detection grouping, especially where the current suggestion uses obstacle, navigation_mark, anchorage, boundary_control, utility_line, or fishery_area.
4. Confirm geometry unification rules for mixed point / line / area objects such as 浮施設・桟橋, 険悪物, 魚礁, 未測海域, 航路 (法律による航路), and 錨泊 (指定)地.
5. Confirm which source layers remain container or render-support layers, especially P基本線, P施設・境界線等, L海底線, L基本線, and the ククリ layers.