Provide tiler computation-footprint and resulting tileset feature-characterics

[clementcolin]

It would be interesting, when computing a tileset, to display some data about the tiling process itself as well as the created tileset characteristics. We distinguish two sub-sets:

• What concerns the process (what is lost when only given the result of process: tracability):
  • [x] Type of input data (filename of input files)
  • [ ] Compression mode and characteristics/indicators
  • [ ] Computation time
  • [ ] Number of lods
• What concerns the result of the process (what can be retrieved when given the result). This part should be implemented in Py3DTiles by enhancing the info command (see this issue):
  • [ ] Number of tiles
  • [ ] Size of each tile, along with the number of object per tile
  • [ ] Number of features (e.g. buildings, trees...)

[jailln]

That would be great! An inspiration can be the las to pnts converter of py3dtiles which has a timer and displays information about the transformation.

[EricBoix]

Maybe this information could end-up in the TileSet itself ? The CityTiler already does add an origin property. Maybe such statistics/characteristics could be added to all Tilers and triggerd by a CLI flag ? (e.g. when --write-statistics is set then the tileset includes the statistics and when it is not set then statistics get writtent ot stdout)

[LorenzoMarnat]

Py3DTilers should write in the tilesets it creates information such as:

• Date
• Source/computation process (already done by CityTiler)
• Projection
• Licence
• City/Country/...

This information could be in tileset.json extras