vector-datasource VS django-rest-framework-gis

Nextzen has freely available DEM tile data to zoom level 15, so about 5 meters/pixel. You need a free API key [1]

Mapbox has paid DEM data to zoom level 20, but I think it's just zoom level 15 scaled up (but the data is cleaner and more recent) [2]

Nextzen also open-sourced their elevation tile generator, but I haven't tried to generate my own tiles [3]

[1] https://www.nextzen.org/#terrain-tiles

I found the Nextzen version but have some issues for now to run it properly https://github.com/tilezen/vector-datasource

Is this something similar to OpenWISP? It all sounds cool, but might be an overkill for small installations…

[0] https://openwisp.org/

Haven't tried it yet, but I think OpenWISP is what you want.

or https://openwisp.org/

All my searches are pointing to OpenWISP

The only "single pane of glass" open source solution I've found like this is OpenWISP. It works along with OpenWR based devices.

I guess if you want to see what is out there, take a look and openwrt and openwisp

OpenWRT is missing a big piece of the puzzle: configuration management and the ability to work with a "controller". OpenWRT is currently great at running stand-alone but has essentially zero support for being part of a "fleet" of devices managed centrally.

This means something as simple as changing the network name or password requires changing it on every single access point manually, and even worse if your mesh system relies on sharing frequently-changing state between devices.

OpenWISP tries to address this problem: https://openwisp.org - I suggest you check it out and solve the configuration management problem first.

The actual "mesh" part is actually relatively easy. Most commercial systems use basic Linux networking tools, HostAPd (sometimes with custom improvements, but this all ends up upstreamed or reimplemented upstream given enough time) and custom glue code to tie them together. A "mesh" system is typically a user-facing network being broadcast by all APs (with shared settings such as name and password) and an invisible, "backhaul" network each AP hosts (either on a separate interface or on the same interface as the AP - I believe some wireless cards can act both as AP and station as long as the channel is the same) and the other in the path connects to, and the glue code handles configuring all of that. 802.11s is also an option that can be used, and I'm pretty sure all of this is already possible to configure manually in Linux - what's lacking is the "glue code" to set up & manage all of this automatically.

In your project did you end up deploying something like django-rest-framework-gis? I have found great results with it. Mainly using PSQL as the backend. I found that the built in Django GeoJSON Serializer can become a little slow with polys like land parcels but it will get the job done and if you can get way without deploying DRF then it maybe worth the trade off.