Explorer#
The explorer at / shows one continuous CesiumJS globe. A simulation builds the region
around the scene centre and returns the result in WGS84 coordinates on the same globe.

Compiled scenes#
The explorer follows the Python workflow: define a scene, compile it, place transmitters
inside it, solve. The page opens with no scene and no transmitter. A scene centre comes
from one of three actions: drawing an area on the map, choosing a search result, or loading
an example from the Scene section. Compile scene then calls POST /api/scenes with
that centre and the geometry controls. The service runs the same compile_cached_scene
call that owrt.load_scene uses, so the scene lands in the shared cache under the same
directory name, and a scene compiled from Python with the default cache_dir appears in the
explorer as a cache hit.
Inside the square the globe is clipped away and replaced by the compiled scene: the terrain grid with its levelled water, draped with the base map, the building meshes at their solver positions, and a dashed boundary line; Surface classes tints the ground by class. Outside the square the display globe continues. The inset is anchored to the display terrain at the scene origin, so the two meet along the boundary up to the differences between the scene’s elevation source, with its levelled water, and the display tiles. A scene without an environment grid, buildings on flat ground with uniform concrete, keeps the display globe: no clipping and no boundary line.

A compiled Bergen scene in the explorer with Surface classes switched on: the scene terrain and buildings replace the globe inside the dashed boundary, and the coverage layer follows it.
Draw area enters a drawing mode: drag a diagonal on the globe and the outline snaps to the square that will be compiled, with its side length shown. On release the centre and radius are taken from the square and the scene compiles at once. Esc or the banner’s close button cancels. Transmitters that fall outside a newly compiled square are removed.
The status line under the button names the building count and provider, the ground source and whether the scene came from the cache. Changing the radius, buildings, terrain or material profile after compiling marks the status as stale, and Run simulation compiles the changed scene before it solves; changing the building source clears the compiled scene.
Transmitters#
Transmitters are added after a scene is compiled and must lie inside its square, as
scene.add follows load_scene in Python. Place on map enters a placement mode in
which a click inside the dashed boundary creates the first transmitter or moves the
selected one; a click outside is refused. Add transmitter appends an entry at the scene
centre, east of any transmitter already there, and enters placement mode. Each transmitter
has its own latitude, longitude, height above ground, frequency, power,
antenna pattern (Sector or Isotropic), azimuth and downtilt. The scene origin is the
compiled centre, not a transmitter. The number of transmitters is limited by the solver
budgets: transmitters times receiver cells, and for Sionna transmitters times rays per
transmitter (Resolution and ray budget).
Antennas#
The Antennas section loads the antennas an antenna source records
(Antennas). Antenna source lists the installed sources;
Automatic selects the national register in France, the Netherlands and Poland and
OpenCelliD elsewhere when it is configured, and a
source that is not configured is listed, disabled, with the setting it needs. Load
antennas works at any time. Before a scene is compiled it shows the antennas around the
scene centre, or around the map view, at their height above the display terrain. In a
compiled scene it places them with the same code as rt.antennas, so each marker stands
where its Sionna transmitter would; compiling a scene around antennas already shown places
them. Markers are coloured by operator, with a line along the registered azimuth.
Hovering a marker shows its operator, bands, height and where the height comes from, the
registered azimuth and the record ID. The notes
under the section list the source, release, licence, and how many values are defaults.
Operator lists the operators in the area and filters the antennas. Channel lists the downlink channels the antennas register, with their systems, operators and antenna count (Antennas); choosing one keeps every antenna that transmits on it. Under Sionna RT, channels outside 1 to 10 GHz are disabled. Use as transmitters replaces the transmitters with the antennas on the channel and sets the frequency to the channel’s centre and the bandwidth to its width. It needs a compiled scene and a channel; a source without frequencies, such as OpenCelliD, uses the frequency and bandwidth entered. Each transmitter keeps the antenna’s identity and the origin of its values, which travel into the result and the downloaded bundle. When no selected antenna registers a direction, the pattern becomes isotropic. Editing a value marks it as set by the user; moving a transmitter detaches it from its antenna. Load example → Paris compiles a scene and loads its ANFR antennas.
Simulation panel#
Control |
Effect |
|---|---|
Engine |
CPU preview, Sionna RT or another engine of the engine registry ( |
Bandwidth |
Receiver noise bandwidth in MHz; 1 MHz, Sionna’s default, until a channel sets it |
Solver parameters |
For Sionna RT: device, geometry switches, reflection depth, ray samples and propagation switches |
Radius |
Scene half-width, 250 m to 5 km |
Resolution |
Receiver cell size in metres |
Building source |
Automatic, Global, or a specific source (Building sources) |
Buildings |
Include building geometry |
Terrain and Terrain mesh |
DEM-following ground or a flat plane, and its mesh spacing |
Material profile |
ITU semantic classes or Uniform concrete |
Receiver plane height |
Height above ground of the measurement surface |
Run simulation is enabled once a compiled scene holds at least one transmitter. It
posts the request with the scene centre to POST /api/simulations; the service compiles or
reuses the scene, runs the solve on the persisted scene assets, and returns the coverage
layer, the scene payload, warnings, solver details and provenance.
Coverage layers#
Switch between Path gain, RSS, SINR and Association with the metric buttons.
The layer is fetched from GET /api/simulations/{id}/raster.png and draped at the receiver
height above the scene terrain, or laid on the display terrain when the scene has no
environment grid. While a layer is shown, the base map turns grey on the globe and in the
scene so that colour carries only the metric, and the dashed scene boundary is drawn above
the layer. Smooth coverage interpolates the display between cell centres; the exact
mode shows one pixel per solver cell. Mask buildings leaves out the receiver points that
lie inside a building, as whole cells in the exact mode. In the smoothed mode, cells coarser
than 2 m are drawn on finer samples, at most 2 m apart unless the image would exceed 2048
pixels per side, and only the samples inside a building are left out, so the gaps follow
the buildings; the rest of a cell whose receiver point lies inside a building takes the
colour of the cells around it. Grids of more than 1024 cells per side keep whole cells.
Surface classes shows the class tint
on the scene ground; it is off by default. Vertical exaggeration scales displayed relief on the globe and in the scene
alike; at zero everything is flat, which shows what a scene compiled without terrain would
look like. These controls change only the display, not the exported arrays. The legend
shows which solver produced the result and, for the continuous metrics, the display range.
For association it shows a swatch in the colour of each transmitter’s marker and cells,
shared by every eighth transmitter, and a hatched swatch for unserved cells, which are not
drawn. With Mask buildings on, a hatched key marks the receiver points inside buildings,
which are not drawn either. Removing or replacing transmitters clears the shown result.
Downloads#
Download result bundle fetches GET /api/simulations/{id}/artifacts.zip, the bundle described
in Exports. Results are kept in memory for the most recent simulations only;
a download after the result has expired returns a 404.