py3dtiles.convert module

py3dtiles.convert.convert(files: list[str | Path] | str | Path, outfolder: str | Path = './3dtiles', overwrite: bool = False, jobs: int = 8, cache_size: int = 3210, crs_out: CRS | None = None, crs_in: CRS | None = None, force_crs_in: bool = False, pyproj_always_xy: bool = False, benchmark: str | None = None, rgb: bool = True, classification: bool = True, intensity: bool = True, color_scale: float | None = None, use_process_pool: bool = True, verbose: int = False) → None[source]

Convert the input dataset into 3dtiles. For the argument list and their effects, please see Converter.

Parameters:

  • files – Filenames to process. The file must use the .las, .laz, .xyz or .ply format.

  • outfolder – The folder where the resulting tileset will be written.

  • overwrite – Overwrite the ouput folder if it already exists.

  • jobs – The number of parallel jobs to start. Default to the number of cpu.

  • cache_size – Cache size in MB. Default to available memory / 10.

  • crs_out – CRS to convert the output with

  • crs_in – Set a default input CRS

  • force_crs_in – Force every input CRS to be crs_in, even if not null

  • pyproj_always_xy – When converting from a CRS to another, pass the always_xy flag to pyproj. This is useful if your data is in a CRS whose definition specifies an axis order other than easting/northing, but your data still have the easting component in the first field (often named X or longitude). See https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6 for more information.

  • benchmark – Print summary at the end of the process

  • rgb – Export rgb attributes.

  • classification – Export classification attribute.

  • intensity – Export intensity attributes. This support is currently limited to unsigned 8 bits integer for ply files, and to integers for xyz files.

  • color_scale – Scale the color with the specified amount. Useful to lighten or darken black pointclouds with only intensity.

Raises: