Skip to content

Zer0pa/ZPE-Geo

Repository files navigation

ZPE-Geo

Install / Developer Commands

Package Install

Installable package: python3.11 -m pip install zpe-geo. Current release: 0.1.1 on PyPI. Source: Zer0pa/ZPE-Geo.

python3.11 -m pip install zpe-geo

Import smoke:

python3.11 - <<'PY'
import importlib.metadata as md
import zpe_geo

print("zpe-geo", md.version("zpe-geo"))
PY

Install success only proves package acquisition/import. Product scope, stale PyPI state, platform limits, and blockers remain in the front-door sections below.

  • PyPI copy is stale; the repo keeps a root plus code/ package layout for source verification.

Quick Start

git clone https://github.com/Zer0pa/ZPE-Geo.git zpe-geo
cd zpe-geo
python -m venv .venv
source .venv/bin/activate
python -m pip install -e ".[dev,h3]"
python -m pytest code/tests -q
python -m build
00 · ZPE-GEO · TRAJECTORY ARCHIVE DEVELOPER-READY · B3 OPEN

Journeys Seen as Paths, Not Points.

A trajectory archive for the shape of the route · ZPE-Geo · PyPI zpe-geo v0.1.1 · github.com/Zer0pa/ZPE-Geo

GPS records where you were. It cannot show what the journey looked like. ZPE-Geo keeps the path itself — the curve of the road, the arc of the vessel, the sweep of the turn — as a compact archive packet. Movement compresses 13.78× on a 34,668-way OpenStreetMap extract; a maneuver query returns P@10 = 1.0 on 210 trajectories. Scope is bounded: archive and search only, not navigation, not lossless geometry.

ZPE-Geo approved scientific square mechanics diagram showing trajectory codec with GEO_DELTA_V1 and H3 indexing.
Scope: archive and search only. Not navigation, not lossless geometry; B3/full-corpus checks remain open.
01 · THE GAP ARCHIVE/SEARCH GAP

GPS captures where you were. It cannot tell you what the journey looked like.

02 · MARKETS ADJACENT FORECASTS
Maritime analytics ’31 $2.6 B
Maritime analytics ’35 $7.6 B
Maritime information ’30 $23.2 B
Fleet telematics ’30 $36.2 B
Autonomous vehicle data ’30 $11.5 B
Mordor Intelligence, MRFR, ResearchAndMarkets · external trajectory-adjacent forecasts, not a ZPE-Geo revenue claim.
03 · VALUE OF MARKET
$36.2B
Fleet telematics by 2030; ZPE-Geo addresses the archive-and-search slice, not navigation or fleet intelligence.
04 · INSIGHT

A route is not its waypoints — it is its arc.

05.1 · CURRENT TECH COORDINATES, NOT PATHS

GPS logs, GeoJSON files, parquet tables: a journey today becomes a list of timestamped coordinates. The shape between them — its curve, its arc — is inferred later, or lost.

05.2 · OUR TECH KEEP THE PATH

ZPE-Geo encodes movement as delta packets that hold the shape of the journey, not just its points. Compression reaches 13.78× on a 34,668-way OpenStreetMap extract, 27.3× on real GeoLife GPS, 21.0× on real NOAA AIS. A maneuver index finds routes by the movement inside them.

05.3 · BENCHMARKS DECLARED FIXTURES
OSM13.78×34,668 ways
GeoLife GPS27.3×real extract
NOAA AIS21.0×real extract
P@101.0maneuver search
ZPE OSM 13.78×
DP OSM 6.45×
max-wave 0/2 MISS
Status: two larger corpora (Argoverse2, NOAA) not yet passing · full-set extension pending.
06 · MEASUREMENT OSM · REAL EXTRACTS · BLOCKERS

Every metric stays tied to declared OSM, AIS, and GPS surfaces.

06.1 · COMPARATIVE PERFORMANCE OSM EXTRACT VS BASELINE
ZPE-Geo OSM 13.78× smaller
DP baseline 6.45×
Argoverse2 max-wave MISS
NOAA max-wave MISS
OpenStreetMap full extract (34,668 ways) · Douglas-Peucker ε=0.5 m baseline for comparison · Argoverse2 and NOAA larger corpora not yet passing · parity with the ACM-2025 reference still open. GeoLife real GPS 27.3× · real NOAA AIS 21.0×.
07 · KEY METRICS OSM EXTRACT · REAL GPS/AIS
07.1 · OSM EXTRACT
13.78×
vs DP 6.45× · 34,668-way OSM extract
07.2 · GEOLIFE REAL
27.3×
Real GPS extract · 5 trajectories
07.3 · QUERY P95
0.064ms
Spatial-range query · mean 0.040 ms
07.4 · WAYS EVALUATED
34,668
OSM full extract · real OpenStreetMap ways
07.5 · RELEASE
v0.1.1
PyPI live but stale · 0.1.2 pending
08 · DETERMINISM DECLARED-FIXTURE REPLAY

Same trajectory bytes,
same query results on fixtures.

08.1 · WHAT DETERMINISTIC MEANS REPEATABLE ON DECLARED SURFACES

On declared repo fixtures, the delta-stream codec produces repeatable compressed bytes under local replay; maneuver queries return stable match sets. Full-corpus extracts — Argoverse2 and NOAA — missed the max-wave check and remain open.

AV fidelity reports p95 1.86 m and max 2.17 m against a 1.0 m threshold; that surface is unresolved. ACM-2025 parity stays inconclusive. The archive-and-search claim is bounded: declared OSM and trajectory fixtures only.

08.2 · THE FIDELITY GAP
Honest Blocker ·

Bound to OSM ways and declared fixtures. AV fidelity p95/max exceed the 1.0 m threshold; OSM DTW p95 trails Douglas-Peucker. Argoverse2 / NOAA max-wave and full-corpus closure remain open. PyPI v0.1.1 is stale; 0.1.2 pending. No lossless-geometry, navigation-system, or road-graph claim.

09

EVERY JOURNEY BECOMES A QUERYABLE PATH.

09.1 · THE AMBITION

The aim is not a better mapping system. It is the archive beneath one. When a trajectory keeps its shape, a route can be stored compact and retrieved by the path it traces — searched by behavior, not by timestamp. Reaching it depends on closing max-wave, full-corpus, and blind-clone gaps.

09.2 · WHAT WORKS NOW

Working today: 13.78× archive compression and P@10 = 1.0 maneuver search on declared OpenStreetMap fixtures.

09.3 · WHAT'S STILL OPEN

Still open: max-wave on Argoverse2 and NOAA, full-corpus closure, blind-clone replay, a current PyPI release.

09.4 · AIS ARCHIVES · NEAR-TERM (12–24 MO)
Vessel histories searched by route shape
A maritime analyst holding decades of AIS feeds can keep them compact and ask the archive “show every approach into this harbor that arced like this one.” Search by behavior, not by ship name or date.
09.5 · FLEET AUDIT · NEAR-TERM (12–24 MO)
A compliance question becomes a search
For a fleet operator answering a regulator, the incident becomes a query against the route library, not a reconstruction from raw logs. The answer returns before the auditor finishes the question, because retrieval beats reassembly.
09.6 · TRAJECTORY IDENTITY · MID-TERM (24–48 MO)
A route gets a durable name
When the same journey produces the same compact packet on two captures, a route stops being a list of points and becomes a citable thing. A mapping engineer can refer to a specific maneuver the way archivists refer to a specific document — by name, not by reconstruction.
09.7 · AV ROUTE LIBRARIES · MID-TERM (24–48 MO)
Self-driving fleets keep every test mile
A mean 123.1× on synthetic AV XY means autonomous-vehicle teams stop choosing which test routes to delete. The full library — every edge case, every odd intersection, every demonstration drive — stays affordable to retain and ready to retrieve.
09.8 · MOVEMENT CUSTODY · PARADIGM (48 MO+)
Movement history acquires provenance
If the open checks close, a specific route at a specific time can be pointed to, retrieved, and compared against an external record. That is the substrate beneath maritime liability, autonomous-vehicle accountability, and continental-scale fleet governance.

About

Deterministic trajectory codec on OSM ways and AIS surfaces — v0.1.1 — 13.78× OSM / 27.3× AIS / p95 0.064 ms

Topics

Resources

License

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages