Skip to content

meshsat 0.10.0: Zones, offline maps and tracks

Choose a tag to compare

View all tags
@papadopouloskyriakos papadopouloskyriakos released this 29 Sep 04:02
· 9 commits to main since this release
v0.10.0
84ba074

meshsat 0.10.0: Zones, offline maps and tracks

  • Zones (Setup > Safety > Zones), as MeshSat Android's:

    • A long press on the map places a zone, and another long press moves it.
    • The editor has the name, the radius (a slider from 50 m to 5 km, or metres typed, 10 m to 50 km), the choice of entering, leaving or both, and a note. All three errors show at once.
    • The Bridge keeps the zones, checks every position a mesh node sends against them, and lists who entered or left, newest first. An alert goes nowhere but that list, as on Android.

  • Offline maps (Setup > Maps):

    • The built-in world overview, which is Android's own file.
    • Detailed maps added from MBTiles files, used first, and kept when the network is gone. A file is checked before it replaces a map of the same name.
    • The map notices that it is offline after three failed downloads and says which map it shows. Offline with only the world overview, the Map tab zooms out to where that overview still reads.

  • The Map tab:

    • Where each node went in the last 24 hours, as dashed lines.
    • The "Layers and nodes" panel: this phone, the nodes and the tracks as layers; each node can be hidden with its track; Show all and Hide all; this phone's position.
    • The bubbles on markers and tracks, and "Centre on me" and "Show everyone" as on Android.

  • People: the node's sheet in Android's words. Its "Show on map" goes to the node, and is offered only once the node has sent a position.

  • Looks: text inside a row is no longer bold, and sheets are drawn on the card colour, as on Android.

  • The Bridge underneath (MeshSat Bridge 31ae3941): the zones were never checked. The Bridge now creates its zone monitor, checks every mesh position, and keeps the crossings (MESHSAT-1414).

  • Tested: 243 unit tests. On the bench phone, the whole suite ran against the installed package: 95 cases against a scripted Bridge, 8 against a second, real Bridge, and 7 live, all green. The live tier was run a second time after the bench's T-Deck was set back: an earlier run had left its hop limit at 4, so setting 4 in the app changed nothing. After the last map changes, the 31 map and route cases ran again on the final package, all green. Among them:

    • a zone placed on the map and saved as Android's circle; a node crossing it listed; the three errors at once;
    • a detailed map added from a file; the map offline with the tile server cut off, showing the detailed map and saying so;
    • a day of positions drawn as one track per node;
    • live: a zone saved from the app on the phone's own Bridge and deleted again, and the T-Deck hearing the alarm test and a text typed in the app.

    No zone has been placed by a real finger yet: the suite presses the map through a test action of the app.

Install on a Mobian phone: wget https://github.com/meshsat/meshsat-linux/releases/download/v0.10.0/meshsat_0.10.0_arm64.deb && sudo apt install ./meshsat_0.10.0_arm64.deb (docs/INSTALL.md).

Assets 4
Loading