Coming from…
Coming from QGIS or ArcGIS Pro
If you build models in QGIS or ArcGIS Pro, Daedalus works like a Model Builder that is also
a data-prep tool. Each geoprocessing step is a node, attribute work and spatial work sit in
the same workflow, and everything runs on your machine, offline if you need it to.
What feels familiar
- Your file formats. A Geo Reader opens GeoJSON, Shapefile, GeoPackage, GML and KML/KMZ, and GeoParquet comes in through the Parquet reader. A GeoPackage with several layers lists each layer in the Drones panel. Write Geo File writes GeoJSON, GeoPackage, Shapefile or GeoParquet.
- Projections. The Metadata tab shows a layer's CRS. Reproject transforms geometry to another CRS, and the Geo Reader can reproject as it reads.
- Overlay and proximity. Spatial join, buffer, clip, intersect, dissolve and Voronoi each have a node.
- Hex grids. H3 Aggregate bins features into H3 hexagons.
- A map for every step. Select a node and open the Map tab under the canvas. It draws features, choropleths, heatmaps, proportional symbols, bivariate choropleths, 3D extrusions, clusters and flow lines.
What's different
- Vector and tables only. There is no raster or mesh data, and geometries are 2D.
- Geocoding and routing run offline. Geocode matches place names against a bundled gazetteer, and street addresses against an address index you build for your region. Route, Isochrone and Matrix use road tile sets you build the same way. Both are managed on one settings page.
- Offline basemaps. The Map tab's basemap can come from a file on your machine. Its selector offers Auto, Off, Offline and Online, and Offline never touches the network.
- No layer styling panel. You style a node's map in its Map tab. To keep a map for a report, add a Map node.
- Sources are never edited. Nodes read from a layer and write new outputs. To drop features, filter them on the way through.
No equivalent yet
Some QGIS or ArcGIS tools have no Daedalus node yet. Searching for them shows a hint instead of
an empty list. These are the ones you are most likely to miss:
| GIS name | What to do instead |
| Aspect | Raster data isn't supported; vector and tables only |
| Export mesh faces | Mesh layers aren't supported |
| Set Z value | Z/M values aren't supported; geometries are handled as 2D |
| Create Routes | Linear referencing isn't supported |
| Sliver polygons | Topology checks aren't supported yet |
| DBSCAN clustering | Spatial clustering isn't supported yet |
| Hot Spot Analysis (Getis-Ord Gi*) | Hot spot statistics aren't supported yet; H3 Aggregate shows density |
| Spatial Autocorrelation (Global Moran's I) | Spatial autocorrelation isn't supported yet |
| Create Random Points | Random point generation isn't supported yet |
| Densify by interval | No vertex densify; write it in a DuckDB Query |
| Location-Allocation | Not supported yet; Matrix gives the travel costs to start from |
| Layer To KML | KML export isn't supported; Write Geo File writes GeoJSON/GPKG |
| Feature Class To Geodatabase | File geodatabase isn't written; Write Geo File to GeoPackage |
| Export To CAD | CAD/DXF export isn't supported; Write Geo File for GIS formats |
| Write vector tiles (MBTiles) | Vector tile export isn't supported |
| Geographically Weighted Regression (GWR) | Only global OLS: Linear Regression; no GWR yet |
| Delaunay triangulation | No triangulation node; Voronoi builds the dual polygons |
| Single sided buffer | One-sided buffers aren't supported; Buffer grows both sides |
Tips
- Search with your tool names. Pairwise Clip, Join attributes by location and Create Thiessen Polygons all find their Daedalus node.
- Check the CRS early. Select a reader and look at the Metadata tab. If layers don't line up, add Reproject before the join, or set Reproject to on a Geo Reader.
- Install offline data before you go offline. Street-level geocoding and road routing need an address index and a road tile set for your region. Build them on the offline map data settings page while you have a connection.
- Write SQL for the long tail. Many vertex and geometry tools, such as centroids, simplify or extract vertices, map to a DuckDB Query node, where DuckDB's spatial functions do the work.
- Pull in context data. Overture Maps, OSM Overpass and Population (Kontur) add places, roads, buildings and population to your study area.