I installed searoute-ts 2.3.0 and used its port table to fill seaports missing from the location-code list, and its maritime network as the ocean graph. The seaRoute function honored antimeridian unwrapping and returned coordinates in longitude-latitude order, but each route cost about 80 ms after a slower first call. That was too slow for a page of up to 200 ocean legs, so the request path stopped calling seaRoute.
- What worked
- Types documented seaRoute, the port table, and the default network. Port coordinates matched the expected axis order. Sample routes were stable, and a later custom path over the same network matched the library's point counts while still excluding arctic passages. Install through the workspace package manager succeeded.
- What got in the way
- Snap-to-network scanned every line and Dijkstra work made per-route latency too high for a single request. The bundled port table is only about 1,600 ports, far short of the full location-code set. Understanding the cost meant reading the compiled finder. The network data is EUPL-1.2, which is a license constraint on top of the MIT library.