Question regarding CityJSONSeq output options

[esgn]

I tried generating using develop branch with different values of split-cjseq and omit-metadata in the config.toml file. Here are my findings :

split-cjseq	omit-metadata	Result
false	false	First CityJSONSeq metadata line present in city.jsonl tiles
false	true	First CityJSONSeq metadata line missing from city.jsonl tiles as expected. This first line is not outputted anywhere else though.
true	false	First CityJSONSeq metadata line missing from city.jsonl objects. This first line is outputted to a metadata.json file at root level inside output directory.
true	true	First CityJSONSeq metadata line missing from city.jsonl objects as expected. This first line isn't outputted to a metadata.json file at root level inside output directory.

I would have expected :

• Always getting the metadata line in CityJSONSeq output files when setting omit-metadata to false
• Always getting the metadata line somewhere in a metadata.json file when omit-metadata is set to true so that the information remain available even though it is not included in the CityJSONSeq output files.

I may very well be missing information regarding the rationale behind these two options or missing experience with CityJSONSeq. Is what I'm noticing the expected behaviour ?

[Ylannl]

I understand the confusion. I implemented these options to support an internal workflow. But not all combinations of options make sense now, as you also point out. The metadata line with split-cjseq enabled may not be correct for all features either. I'll look into this and fix it. For now I recommend using the default values, this is most in line with the standard use of CityJSONSeq. Would this work for your use case?

[esgn]

Many thanks for the reply. We will stick to the default options for now. The full split and crop (split-cjseq and --crop-output) may be useful for debug purposes.