Export a block diagram as a 3D model (glTF/GLB): ground with the map draped on it, walls and base
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 30/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- rust
- Ambito
- computer-graphics
Direzione di ricerca
Start by reading the existing block implementation in #1914, the mesh work in #2017 and #2084, and the glTF writer used by share.webScene; compare these with imagery.mesh. Define how the command reuses those paths to export the settled block view, then implement and validate geometry, textures, and the no-block error. Done means the four listed tests pass and the result reports the file size and omitted view elements.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Today: a block diagram (map.terrain with "block", #1914) can only be exported as a picture (PNG, PDF) or an orbit (#1916). imagery.mesh writes a DEM as an uncoloured OBJ, and share.webScene writes extruded polygons as glTF, but neither gives the block as it's drawn. A 3D file of the block would open in Blender, PowerPoint, a web viewer or a 3D printer's slicer, and could be turned in class.
Proposal
A new command, map.exportBlock, for a map whose terrain has a block:
map.exportBlock={"path": "pedra_azul.glb", "texture": 4096}
- Geometry: the ground as the settled view draws it (the same mesh, #2017/#2084, cut to the block), the walls along the block's sides with their top meeting the ground, and the base as a flat quad. The terrain's exaggeration applies; units are metres from the block's south-west corner, with y up as glTF defines.
- Ground colour: the map drawn top-down over the block's box, at
"texture"pixels on the long side (default 4096, at most 8192), as the ground's texture: the same layers, symbology, water (#1915) and labels the map shows, without the relief's light (the 3D viewer lights it). - Walls: vertex colours for plain walls; a texture strip per wall when the walls carry a polygon layer's classes and hatches (#1914), drawn as the wall draws them in the map.
- Format:
.glb(binary glTF, one file);.gltfwrites the JSON with the buffers and textures embedded. Reuse the glTF writer ofshare.webScene. - Size: the ground's triangles are those of the mesh, at most what the export mesh has; the file's size is given in the result.
- Notices: what isn't in the model: fog and sky, the relief's shading, labels standing up in screen space (they're in the texture flat instead), the legend and other layout elements.
Tests
- A block over a small DEM exports a
.glbthat a glTF validator accepts, with three meshes (ground, walls, base) and a texture. - The ground's vertex heights at the corners match the DEM's heights × exaggeration.
- The walls' top vertices are the ground's edge vertices (no gap).
- A map with no block is refused with a message.
Choices in this proposal
- glTF/GLB, not OBJ: one file with textures, read by Blender, PowerPoint, Windows' 3D Viewer and web viewers. OBJ needs a material file and a texture beside it.
- The map as a texture, unlit: the viewer lights the model, so baking the hillshade in would light it twice.
- A command of its own: the block is a view setting, not a layer, so it doesn't fit
share.webScene's per-layer extrusions; the writer is shared. - Related: #1914, #1916, #2017, #2084,
imagery.mesh,share.webScene.
- Lingua principale
- Rust
- Stelle
- 1.9k
- Fork
- 268
- Merge medio
- 11h 1m
- PR unite (30g)
- 942
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di opengeos/RustGIS
-
[Bug]: layer.move to the place a layer already has fails and stops a script; with several layers it leaves an empty undo stepForse già presa @jgregoriorincon l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
opengeos/RustGIS#2621 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 61/100
opengeos/RustGIS#1446 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di opengeos/RustGIS
Issue simili
-
文件夹重大BUG:不支持重命名Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
I maintainer di solito rispondono entro 1 giorno
-
postgresql-rules / queue-rules: implicit KEY SHARE before a parent key update, and job self-overlapAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
jonathanong/no-mistakes#3879 ·
I maintainer di solito rispondono entro 1 giorno
-
area:index v0.35.0
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
pbakaus/impeccable#1653 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
nautechsystems/nautilus_trader#5741 ·
I maintainer di solito rispondono entro 1 giorno