A map showing the carriers used by Easybell for their VDSL products
Open map, click to select area, wait, done.
Clone this repository, run npm install, run npm run serve to start the local development server or npm run build to build for production.
- Get the bounding box from the selected area
- Query Overpass for all addresses within the bounding box
- Create hexagon grid inside bounding box
- Assign addresses to corresponding hexagons
- Sort addresses within each hexagon based on their distance to the hexagon's center (ascending distance)
- Query Easybell availability API for every address in hexagon until a carrier has been found
- Color hexagons on map based on carrier
- Not every address, especially in more rural areas, is available in OpenStreetMap. This can result in Overpass not returning any addresses for a hexagon, even though there are buildings in there.
- The Easybell API doesn't set CORS HTTP headers so that your browser can query it directly. Therefore, a CORS proxy is used. This is not needed when running locally.
Actually, I didn't build this to map Easybells carriers at all, but to visualize where 1&1 Versatel Layer 2 bitstream access is available. While playing around with Easybells availability API, I noticed that it also returns the carrier used, e.g. 1&1 Versatel.
My assumption is that in regions where 1&1 Versatel provides service to Easybell, they have L2-BSA available, which is in turn used for their own products (e.g. 1&1 DSL for consumers). I was able to confirm this assumption in multiple regions using e.g. RIPE Atlas nodes.
Because picking addresses at random and running e.g. curl -s "https://www.easybell.de/api/provider-availabilities/TAL?exact_address=false&zip_code=49074&city=Osnabrück&street=Domhof&house_number=10" | jq -r ".results[0].carrier" was a bit boring and lacked visualization, I built this project.