Issue: Unable to Generate Valid JSONL Output – All Vertices Are Null
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 197
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
I encountered some issues while installing and using the Roofer tool.
Installation Issue
I am using Windows 11, and during installation, I had to use the command:
cmake --build build --config Release
instead of:
cmake --build build
When running the original command, I received the following error:
Make Error at build/apps/roofer-app/cmake_install.cmake:39 (file):
file INSTALL cannot find "PATH/roofer/build/apps/roofer-app/Release/roofer.exe": No error.
Call Stack (most recent call first):
build/apps/cmake_install.cmake:37 (include)
build/cmake_install.cmake:42 (include)
Configuration Issue
After installation, I tried running the command:
roofer -c config_file
with configuration files in various formats, including:
roofer -c config_file.txtroofer -c config_file.toml
The configurations used were as described in the CLI Application Documentation:
[input.footprint]
source = "PATHTOGPKG.gpkg"
[[input.pointclouds]]
name = "pointcloud"
source = "PATHTOLAZ.laz"
[output]
folder = "PATHTOOUTPUT"
I also tried the format from the FOSS4G presentation:
[input.footprint]
path = "PATHTOGPKG.gpkg"
id_attribute = "id"
[[input.pointclouds]]
name = "pointcloud"
path = "PATHTOLAZ.laz"
[reconstruction]
reconstruction_complexity = 0.7
[output]
path = "PATHTOOUTPUT"
Result Issue
Not all attempts produced an output. When there was output, it always contained:
"vertices": [[0,0,0],[0,0,0],[0,0,0],[0,0,0]]
or something similar, with all vertices being null.
Input Details
Both inputs (GPKG and pointcloud) are in EPSG:31983, and there is overlap between the two datasets. I was also unable to visualize the output with cjseqview, possibly due to the null vertices.
Could you please advise on these issues? Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows build with cmake --build build and the CLI runs using the documented TOML configuration formats. Check whether the installation command, configuration fields, or EPSG:31983 inputs lead to the all-zero JSONL vertices. Done means the tool installs with the documented command and produces valid, non-null output for the reported inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100