Thomas BrochardDevelopment · Data · AI
Let’s talk
Back to selected work

Geospatial systems & interface design

Case study / 02

Fly Drone Tool

Mission planning with context, and edits you can follow.

A geospatial design connecting route constraints, terrain coverage, weather provenance and versioned edits across multiple views.

Technologies & concepts

  • Python
  • TypeScript
  • SQLite
  • Pydantic
  • HTTP integration
  • Cesium terrain concepts

Technical demonstration / selected source

Private repository

Illustration of the geospatial interface design for Fly Drone Tool.
Design illustration · no operational results represented

01 / The context

The problem behind the design.

A route on a map is only part of a mission plan. Ground elevation, spatial zones, stale observations and changes from another editor all affect how the information can be interpreted. This source showcase explores domain contracts and interface state that preserve those distinctions.

02 / Engineering decisions

Choices made explicit.

Unknown stays unknown

Model altitude units and observation provenance explicitly. Missing or stale weather and incomplete terrain coverage remain distinguishable from confirmed values.

Edits have an order

A per-mission save queue retains pending changes and serializes requests. Mission revisions make conflicting edits visible before accepting an update.

Control has an owner

Window sessions distinguish monitoring from exclusive editing ownership. Mission archives and summaries are stored independently of the current view.

03 / System view

Follow the flow.

Mission-planning design connecting mission models, terrain and weather context, constraint checks and versioned views.

Illustrative architecture from the project presentation. It describes the selected design; it does not imply a deployed service or a measured operational result.

View the full-size diagram
  1. Mission model

  2. Terrain context

  3. Weather context

  4. Constraint checks

  5. Versioned views

04 / Selected artifacts

What the repository contains.

  • Python domain, geometry, weather and SQLite persistence modules
  • TypeScript save queue, window session and terrain modules
  • Selected tests documenting geometry and state-handling cases
  • Architecture visual and static technical presentation

05 / Scope & limitations

How to read this project.

Curated source and design showcase. The selected modules are not a packaged flight-control application. Hardware adapters, simulator binaries, local databases and deployment scripts are excluded. Mission-state examples are illustrative and do not establish flight clearance, obstacle detection or operational validation.

Explore the source with access.

The GitHub repository is private. Its link works for authorized collaborators; other visitors can contact me to discuss the project.

Next case study / 03

Weather ELT Pipeline

Data engineering

Explore the collection

The next conversation

Let’s talk about your project.

↗
A need, an idea, a technical question.
LinkedIn ↗GitHub ↗