Route along a street or duct graph instead of a straight-line factor #7

Closed
opened 2026-11-17 09:16:06 +00:00 by jaylouisw · 0 comments
Owner

Auto-design measures every run as straight-line distance x routeFactor (default 1.2), and says so
in routeMethod. That is honest, but it is not a route: a cable follows a street, a duct bank or a
pole line, and the difference is not a constant factor at the scale of a real deployment.

Ask

Route along real geometry instead of a multiplier, still offline.

  • import a network of streets or ducts (KML LineStrings, or an OSM extract) into the project;
  • snap demand points and splitter sites to the nearest edge;
  • measure each run as the shortest path along that graph, not the straight line;
  • fall back to the straight-line factor, and say which method was used per run, when no graph is loaded.

Acceptance

  • design.synthesise accepts a network (edges with coordinates) and reports routeMethod per run:
    street-graph or straight-line xN;
  • a graph that does not connect two points yields an infeasible candidate with that reason, not a
    straight-line guess;
  • the same determinism guarantee as today: same input, same output;
  • a test with a hand-built 4-edge graph where the graph route is deliberately longer than the straight
    line, asserting the longer number is used.

Not in this issue

Choosing the graph for the user (a tile/OSM downloader), and turn-by-turn directions.

Auto-design measures every run as straight-line distance x `routeFactor` (default 1.2), and says so in `routeMethod`. That is honest, but it is not a route: a cable follows a street, a duct bank or a pole line, and the difference is not a constant factor at the scale of a real deployment. ## Ask Route along real geometry instead of a multiplier, still offline. - import a network of streets or ducts (KML LineStrings, or an OSM extract) into the project; - snap demand points and splitter sites to the nearest edge; - measure each run as the shortest path along that graph, not the straight line; - fall back to the straight-line factor, and say which method was used per run, when no graph is loaded. ## Acceptance - `design.synthesise` accepts a `network` (edges with coordinates) and reports `routeMethod` per run: `street-graph` or `straight-line xN`; - a graph that does not connect two points yields an infeasible candidate with that reason, not a straight-line guess; - the same determinism guarantee as today: same input, same output; - a test with a hand-built 4-edge graph where the graph route is deliberately longer than the straight line, asserting the longer number is used. ## Not in this issue Choosing the graph for the user (a tile/OSM downloader), and turn-by-turn directions.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/glassforge#7
No description provided.