osm_parse — DRIVE `japan` op

• Data kinds: any → table

• Call: import fullseye as fs; fs.ledger.osm_parse(source, *, origin=None) -> 'Dict[str, object]' (to call the implementation directly, import drivejapan; drivejapan.osm_parse(source, *, origin=None) -> 'Dict[str, object]'; from the registry, opsdrive.get("osm_parse"))

Usage

Reads OSM XML (a string or a file path) and projects the nodes to local planar coordinates [m].

> The detailed description below is the original text — the summary and the headings are translated.

返り値 {"origin": (lat0, lon0), "nodes": {id: {"xy": (x, y), "lat", "lon", "tags": {}}}, "ways": [{"id", "nodes": [id], "tags": {}}], "bbox": (xmin, xmax, ymin, ymax)(<bounds> があればそれ、無ければ節点の範囲), "n_nodes", "n_ways"}。origin が None なら <bounds> の中心(無ければ節点の平均)。<nd ref> が未知の節点を指す way はその節点を落とす(件数を n_dangling に)。Raises ValueError: XML でない、<osm> でない、節点が 1 つも無い。

References (sample data, literature)

• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).

• Operator provenance and references — the sources of the research/methods this op family came from.

• The canonical algorithm (author, year) and its uses are named in the family usage guide above.

Runnable examples (verified samples that actually call this op)

• poc_driving_japan_town — py -3.11 examples/poc_driving_japan_town.py

Ops the type connects to (they accept `table` as input)

course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same

Same category (`japan`)

osm_synthetic · osm_road_graph · osm_road_mask · osm_road_loops · osm_route · japan_world · japan_stats · latlon_to_local

*Provenance: drivejapan.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

osm_parse — DRIVE japan op