Omnigraph
Graph engine for context assembly. Object-storage native. Agents work with graph data the way engineers work with code: branched, typed, reviewed, merged, audited, and governed.
City Data Explorer — open-data digital twin of Weimar (web maps + export to Rhino/Grasshopper)
Translation pending
DataGitHub @Bauhaus-InfAUOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗A browser-based digital twin of Weimar (Thuringia, Germany), built entirely from open geodata. Layers can be inspected on interactive 2D/3D maps and exported for a selected area as GeoJSON or Rhino 3DM for further analysis in Rhino / Grasshopper.
Open it: https://bauhaus-infau.github.io/weimar-city-data-explorer/
Each map has a layer list on the left (eye icon toggles visibility), a 2D/3D switch and tools on the right: export (area selection → GeoJSON zip or 3DM), scale grid, PNG/PDF image export, legend.
The page must be served over HTTP (not opened as file://):
python -m http.server 8000
then open http://localhost:8000/.
index.html, app.js, detailed.js, style.css the web application (no build step)
layers/layers.json layer manifest: sources, layers, sidebar, palettes
layers/base_border*.json standard export areas
layers/data/ prepared vector data (GeoJSON, LoD2 binary)
terrain/weimar-dgm/ terrain tiles (Terrarium PNG) built from DGM1
materials/ counting sheets for the Space Syntax survey
tools/ Python scripts that downloaded and prepared the data
tools/ documents how the data in layers/data/ and terrain/ was produced. The scripts
expect the original working folders (data/raw, data/processed), which are not part of this
repository, so they are a reference rather than a one-click rebuild.
The attribution for each individual layer is stored in layers/layers.json and shown in the
application.