Tanstack Start
General settingsMaps & location

Route fence

List, view, create, and update route corridors between two addresses — production persistence with demo route geometry in the console.

A route fence stores one or more corridors (buffered polygons) between a source and destination address. List, detail, create, update, and delete operations are production-backed via the route-fence API.

Important: The Generate Route step in the console uses demo / mock route geometry to produce candidate polylines on the map. It does not represent a live commercial routing engine. What is production-grade is the saved corridor geometry, source/destination IDs, and status once you call Create Route Fence or Update.

Navigation: Settings → General Settings → Route Fence (/dashboard/setting/general-settings/route-fence).

Permissions

See create_route_fence, view_route_fence, update_route_fence, delete_route_fence in Access and permissions.

List

Purpose: Browse route fences and open detail or delete.

  • New Route Fence appears when create_route_fence is allowed.
  • Row actions typically include View, Edit, and Delete (each permission-gated in the columns).
  • Optional status filtering may be available via URL search parameters in supported builds.

Expected result: Rows load from the API; errors show a recoverable state with Retry when implemented.

Create route fence (/route-fence/new)

Steps

  1. Select New Route Fence.
  2. Choose Source and Destination using the address comboboxes (organization addresses).
  3. Choose Status (object_status lookup).
  4. Select Generate Route. The app produces one or more demo route options for visualization (not production routing).
  5. Select one or more route options, then Apply Route Fence to build corridor polygons from those paths.
  6. Review the map preview, then submit Create Route Fence (requires create_route_fence).

Validation

  • Source and destination must be set with resolvable coordinates.
  • You need at least one applied corridor before create succeeds (No valid corridors to save if polygons are empty).

Expected result: Success toast and return to the list; the new record appears in the table.

View detail

Purpose: Inspect corridors, metadata, and map visualization for one route fence.

Open from the list (View). Use Edit in the header when update_route_fence allows changes (navigates with ?edit=true search in supported flows).

Edit route fence

Purpose: Change source, destination, status, remove existing corridors, or add new corridors from generated options.

Steps

  1. Open the record in edit mode (update_route_fence).
  2. Adjust Source, Destination, and Status as needed.
  3. Optionally run Generate Route again (still demo geometry), select options, and Apply Route Fence to append new corridor polygons.
  4. Mark existing corridors for removal or restore before save as supported by the UI.
  5. Update to persist.

Expected result: Success toast and return to the list; map and list reflect stored corridors.

Delete

From the list, delete with confirmation when delete_route_fence is present.

Troubleshooting

  • Generate Route does nothing: Ensure both addresses are selected and that address detail loads coordinates.
  • Cannot create — no valid corridors: Use Apply Route Fence after selecting at least one generated option, or fix polygons so each corridor has enough points.
  • Understanding “demo” routes: Distance and duration shown for generated options are illustrative; operational routing accuracy is not claimed for this step.
  • Route fence not found: Return to the list and open a valid ID; stale bookmarks may 404 at the API.

Geofence

List, create, view, edit, and delete geofences; assign vehicles with time-bounded rules (production).

Address setting

Create, search, edit, and delete organization addresses with map-backed coordinates (production).

On this page

PermissionsListCreate route fence (/route-fence/new)View detailEdit route fenceDeleteTroubleshootingRelated