I propose the removal of support for the "non-upstream" Potree 1.xCIN format, in our effort to clean the itowns codebase.
Context
The CIN format appears to be a specific format introduced by a fork of PotreeConverter by Oslandia. Upstream Potree 1.x data formats includes BIN (that we also support), LAS and LAZ. Moreover this fork seems more of an experimentation and had no activity in the past seven years.
Note: our potree_25d is the only known use of this format, we should think of a replacement if we do not find the original source of data.
I propose the removal of support for the "non-upstream"
Potree 1.x
CIN
format, in our effort to clean the itowns codebase.Context
The
CIN
format appears to be a specific format introduced by a fork ofPotreeConverter
by Oslandia. UpstreamPotree 1.x
data formats includesBIN
(that we also support),LAS
andLAZ
. Moreover this fork seems more of an experimentation and had no activity in the past seven years.Note: our
potree_25d
is the only known use of this format, we should think of a replacement if we do not find the original source of data.