Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Rework CLI options for KML/COLLADA/glTF export
See original GitHub issueIssue Description
The following points have been raised in the discussion of #147:
- merge
--display-modeand--visible-frominto one option - add options for the elevation settings for KML/COLLADA/glTF exports
- add explicit CLI options for the collada2gltf converter and skip
-Owas:clarify how to pass parameters to the collada2gltf converter
Check out the export-vis-cli branch to follow and test the changes.
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
3.6.3. KML/COLLADA/glTF export preferences - 3dcitydb-docs
The preferences tab contains four subnodes – General, Rendering, Balloon, and Altitude/Terrain – make customization of these exports possible. These settings ...
Read more >Seeking input on the redesign of the command-line interface
The current CLI just offers command-line parameters for the operation to be executed ... Rework CLI options for KML/COLLADA/glTF export #150.
Read more >lastrelease – 3DCityDB Database
Extended ADE export API to support the export of ADE data in KML/COLLADA/glTF. Enhanced LoD export filter with the option to only export...
Read more >Agisoft Metashape Change Log
Updated Build Model and Build Tiled Model commands to combine data from ... Added DJI Pilot KML format support for camera track export....
Read more >Models | Keyhole Markup Language
In KML, you can import 3D models—such as buildings, bridges, monuments, and statues—in the COLLADA interchange file format.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I merged the
--visible-fromoption into the--display-modeoption.I removed the
-Ooption and added--gltf-version,--gltf-embed-textures,--gltf-binaryand--gltf-draco-compressionas explicit options to control the behaviour of the collada2gltf converter. Note that the CLI supports abbreviated option names as explained in the picocli online documentation. Thus, for example, you don’t have to type the full option name--gltf-draco-compressionbut can also use--gDC. Much simpler 😃 This works for all options of all commands.I also added options to control the elevation and mainly followed the proposal of @Son-HNguyen in #139 for this.
The
export-visis now a monster command (just print out the help). But, well, the feedback shows we obviously need all those options. So, I am thinking to also add the COLLADA rendering options as proposed by @Son-HNguyen in #139 (see[rendering_options]).The changes are availble in the
export-vis-clibranch. @yaozhihang, @BWibo, @Son-HNguyen: would be great if you could do some testing.I like your proposal of dropping the
-Ooption and introducing three options--gltf-version,--gltf-binary, and--gltf-draco-compressioninstead. This makes the CLI interface clearer and easier to understand.