Implement FlatCityBuf output
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 197
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
FlatCityBuf (FCB) output is in my opinion a must for cloud native ops. Not only does the format allow stuffing everything in one file -- compared to a number of per feature CityJSONSeq text files plus a separate metadata.city.json file -- but I have also tested how much more efficient it is to create 3DTiles from FCB compared to CityJSONSeq
Roofer outputting FCB would directly pipe into Tyler, resulting in a complete pipeline to generate 3DTiles 1.1 from reconstructed buildings.
Are there plans for FCB output already ? We can help.
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
Review Roofer's existing output entry points and the Tyler context linked in the issue to understand how CityJSONSeq and metadata are currently produced. Completion would mean Roofer emits a single FlatCityBuf output that can feed Tyler; no specific file or test is named, so confirm implementation and validation points with maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100