Djinious
Access and service coverage
Answer “what is within twenty minutes of here” for every site in a layer, and keep the answer current as the source moves.
DjiniousMap
Coverage questions are asked once and then quietly go stale. An isochrone run over a whole layer produces travel-time polygons as a dataset of their own, which means it can be styled, filtered, shared and — crucially — rebuilt.
An automation bound to dataset.refreshed re-runs the whole thing when the underlying sites are re-harvested, so the coverage layer is never older than the data it describes.
How it runs
Run over the layer
Run isochrones over every feature in a site layer, not one point at a time.
IsochronesLand in the catalogue
The result lands in the catalogue as a dataset, profiled and mappable.
Job queueBind the trigger
Bind an automation to dataset.refreshed on the source layer.
AutomationsStay current
Every re-harvest rebuilds the coverage without anyone remembering to.
Sharing
Keep exploring
Related use cases
Reality captureOpen data in, graded replicas out: airborne LiDAR, real photographs and a laser scanDjiniousWorld was validated end to end on public datasets — the Autzen airborne LiDAR cloud, the Middlebury temple photographs and the ETH3D “pipes” scene — every step driven through the API, every result carrying the accuracy grade it earned.
DjiniousWorldProperty · DVF and cadastreProperty and land valueReconcile transaction records against cadastral boundaries and publish the result as a layer the whole team reads the same way.DjiniousMap
Municipal open data · trees, cycle networks, sports facilitiesMunicipal asset inventoriesBring the small, messy, locally-published datasets together — and find out which of them can be trusted before you draw them.DjiniousMap