Skip to content

[MeshCore P3] M4 - Neo4j export to PATH_OBSERVED #375

@pskillen

Description

@pskillen

Parent

Part of #267. Milestone M4.

Goal

Graph backend for topology + centrality, isolated from Meshtastic traceroute.

Scope

  • Export MeshCorePathEdgeBucketnew PATH_OBSERVED relationship (separate from ROUTED_TO) with protocol, evidence, weight, resolved, bucket props.
  • Generalized node key (mc:<internal_id> / mc_hash:<size>:<hash>); do not reuse the MT integer node_id.
  • Async + idempotent from rollups only (never per-observation); manage.py bulk export.

Acceptance criteria

  • Re-export is idempotent (MERGE on stable key).
  • MT ROUTED_TO graph + heatmap untouched.

Decisions (locked)

  • New PATH_OBSERVED relationship type.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions