I work at an ISP that offers fixed wireless Internet.

For marketing purposes I generate viewsheds around each of our ~500 towers, so we can get an idea which suburbs to market to.

At the time of sale, my system will calculate the line of site from the access point on the tower to the customer rooftop to determine the height of the pole (is any) needed to get service.

Like the OP, we re-sampled (gdalwarp, raster2pgsql) some of the 15cm lidar data to ~1m to get it down to a manageable size (7TB) and run it on a single bare-metal PostgGIS instance (500GB ram, 64 cores)

Radio waves at 5GHz are quite 'fat' so we need to allow for that on LOS calculations as per [0].

The GIS magic mostly sits in PostGIS and we use a number of data sets to solve problems: * Shuttle Radar Topography Mission - Digital Elevation Model and Digital Surface Model, 30m grid [1] * Building footprints for all of Australia [2] * National Roads [3] * property boundaries (cadastre) [4] * All Australian addresses [5] * Australian suburbs [6]

For the front end we use a VueJS app (quasar.dev) using DeckGL on Google Maps to visualise the LOS path. Back end is Rust (axum/sqlx).

GIS is a very interesting are to work in - if I had more fun they might start charging me admission to come to work!

[0] https://s.campbellsci.com/documents/au/technical-papers/line... [1] https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/me... [2] https://github.com/microsoft/AustraliaBuildingFootprints [3] https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/me... [4] https://www.data.qld.gov.au/dataset/cadastral-data-queenslan... [5] https://www.industry.gov.au/publications/geocoded-national-a... [6] https://www.abs.gov.au/statistics/standards/australian-stati...