Lewati ke konten
drawtonomy drawtonomy

Offline usage

Konten ini belum tersedia dalam bahasa Anda.

drawtonomy is designed so that you can sketch lanes, edit OpenDRIVE / OpenSCENARIO files, and play scenarios through esmini without sending any edit data over the network. This page shows how to reach a true zero-egress workflow with the current release, and what we are adding next to make it a single toggle.

What “zero egress” means here

Section titled “What “zero egress” means here”

After the editor finishes loading, no outbound network request is made unless you trigger a feature that explicitly fetches something. The features that trigger a fetch are listed in Data flow and privacy. Avoiding them gives you a fully offline session, which you can verify in the browser’s Network tab.

Checklist for a zero-egress session

Section titled “Checklist for a zero-egress session”
  1. Set the map background to “Off.” This disables the road and satellite tile providers.
  2. Do not use “Generate Lanes from OSM.” That tool is the only built-in feature that queries the Overpass API. Hand-draw lanes or import an existing .xodr instead.
  3. Do not use the map search box. It calls a place-name search service with the text you type.
  4. Do not enable the AI Scene Generator extension. It is disabled by default. As long as you do not open it from the Extensions panel, it never reaches out to an LLM.
  5. Stick to the bundled font for export. Drawtonomy ships Excalifont with the editor. Exports that use this font do not contact Google Fonts.

After those four steps, drawtonomy makes no outbound requests for the rest of the session. You can verify this in the browser developer tools: open the Network tab, filter to “Fetch / XHR”, and confirm the list stays empty as you draw, import, play scenarios, and export.

Workflows that work fully offline

Section titled “Workflows that work fully offline”
  • Hand-draw a road network, set per-lane attributes, export to OpenDRIVE.
  • Import an existing .xodr, edit lane geometry and connectivity, export it back out.
  • Import an .xosc (with its catalog references), edit, and press Play to run it through esmini-WASM right in the editor.
  • Export an esmini-ready .zip containing .xodr + .xosc for downstream simulation.

All of these stay in your browser. Only the optional “Generate Lanes from OSM” feature requires Overpass access.

Workflows that require a network

Section titled “Workflows that require a network”
  • OSM lane import. Requires the Overpass API.
  • Place-name search. Requires a public Nominatim instance.
  • AI Scene Generator extension. Disabled by default; only active when you open the Extensions panel and pick it. Prompts are sent directly from your browser to the LLM provider you configure (Anthropic Claude, OpenAI GPT, or Google Gemini); your existing canvas is not included in the request. See the Security FAQ for the full breakdown.

Roadmap: a single “Offline mode” toggle

Section titled “Roadmap: a single “Offline mode” toggle”

We are adding a top-level Offline mode (network 0) toggle to the hamburger menu. When enabled it will:

  • Block every outbound request from the editor, including the map tile providers, Overpass, place-name search, Google Fonts, and Google Analytics.
  • Show a small badge in the UI so operators can see at a glance that egress is disabled.
  • Be verified in automated tests so that future changes do not silently reintroduce traffic.

If you want this sooner, please open an issue — OEM use cases are exactly what this work is prioritised for.

Section titled “Related”