Post by Stefan Wintermeyer · 2026-08-07
=======================================

In reply to a post by SEBASTIEN PORTRAIT.
  https://vutuv.de/sebastien_portrait/posts/019fdd4e-74f5-73db-b0e8-57bf2c89bc86

WOW! Great work!

Tags: Phoenix Framework, Elixir, LiveView

Likes: 0 · Reposts: 0 · Bookmarks: 0

CONVERSATION (2)
----------------
* SEBASTIEN PORTRAIT · 2026-08-07 ·
  https://vutuv.de/sebastien_portrait/posts/019fdd4e-74f5-73db-b0e8-57bf2c89bc86
  # **Rover — Interactive maps for Phoenix LiveView**
  
  Rover is a Phoenix LiveView component for interactive maps. It wraps
  [OpenLayers](https://openlayers.org/) — a serious GIS engine with projections,
  WMS/WMTS, vector layers, cadastral data, etc. — and removes the ceremony most
  Phoenix applications don’t need.
  
  ## **What it does**
  
  ```
  <.map
    id="parcels"
    center={{45.75, 4.85}}
    zoom={12}
    markers={@clients}
    shapes={@parcels}
    tiles={:ign_ortho}
  />
  
  
  ```
  
  Assign a list of maps, get a map.
  
  Change the list, and Rover diffs by ID and updates only what changed — no
  flicker, no interrupted pan, no popups unexpectedly closing and reopening.
  
  **Markers:** any struct with `:id`, `:lat`, and `:lon`. Optional emoji, custom
  colors, draggable pins, and popups (HEEx slots, escaped by default).
  
  **Shapes:** GeoJSON from `ST_AsGeoJSON` or your own data. Shapes are diffed by
  revision rather than hashing, so updating thousands of points stays efficient.
  
  **Clustering** for hundreds of markers.\
  **Heatmaps** for density analysis.\
  **Popups on shapes** that point to the geometry rather than its centroid.\
  **View control** without losing declarative framing with `Rover.fly_to/4` and
  `Rover.fit_to/4`.
  
  Rover also has built-in support for **IGN Géoportail**, including French
  cadastral maps and aerial orthophotography.
  
  ## **Why not just write a hook?**
  
  You can — and the first version is short.
  
  Then you fix reconciliation, coordinate order, viewport framing, attribution,
  element ID changes, flickering, and all the little edge cases that appear once
  the map becomes part of a real application.
  
  That’s the layer Rover is trying to provide.
  
  OpenLayers itself is the bet underneath it.
  
  Three pins on a tile layer is an afternoon’s work. The next morning you need WMS
  layers, a cadastral overlay, vector data, clustering, or another projection —
  and suddenly the ceiling has moved somewhere else.
  
  OpenLayers can handle that. Rover tries to make it feel natural from Phoenix
  LiveView.
  
  ## **Try it**
  
  **Livebook demo**
  
  [Run Rover in
  Livebook](https://livebook.dev/run/?url=https%3A%2F%2Fgithub.com%2FnseaSeb%2Frover%2Fblob%2Fmain%2Fnotebooks%2Frover.livemd)
  
  **Documentation**
  
  [Rover v0.3.0 — HexDocs](https://rover.hexdocs.pm/)
  
  **Source**
  
  [GitHub — nseaSeb/rover](https://github.com/nseaSeb/rover)
  
  Rover is open source and still evolving. Feedback, ideas, and criticism are
  welcome.

--
vutuv agent document · type: post · schema_version: 3
generated_at: 2026-08-10T17:05:31Z
canonical:
  https://vutuv.de/wintermeyer/posts/019fde1f-183c-7391-8acd-2c885b997237