V2.0.0: Introduce Local CRS, Autodetect CRS and Mutators

Introduce Local CRS, Autodetect CRS and Mutators

Author: mfbonfigli

DEVELOPMENT.md

@@ -28,13 +28,13 @@ The Dockerfile is organized as a multi-stage build.
 4. The build artifacts are copied in a final scratch image where they are ready to be copied out to the host.
 
 ## Local Development environment setup
-Two approaches are possible, using docker to run builds in a reproducible environment or building it locally setting up the local machine.
+Two approaches to local development are possible, the first is using docker to run builds in a reproducible environment, the second is building the code locally without docker.
 
 Note that all the options mentioned statically link Proj to the final build executable, this ensures the system builds a single highly portable binary that embeds all required dependencies. 
 
 ### Option 1. Install docker and use `build.sh` or `build.ps1` to build the code and run the tests. 
 
-The pro here is that this should work in any environment and ensures that the final executable build is reproducible. It recommended to always run a "dockerized" build before creating a PR.
+The benefit of using Dockerized builds is enabling reproducible builds. It recommended to always run a "dockerized" build before creating a PR.
 
 To build just run in a powershell console:
 ```
@@ -43,12 +43,13 @@ To build just run in a powershell console:
 
 ### Option 2. Setup the local machine for local development without Docker.
 
-This approach is more challenging and the steps are different depending whether you are development under Windows or Linux. In general the environment needs to be set up mimicking the steps described in the `Dockerfile`. 
+This approach is more challenging and the steps are different depending whether you are developing under Windows or Linux. In general the environment needs to be set up mimicking the steps described in the `Dockerfile`. 
 
-Since the dockerfile has been written designed to run builds in Linux, that is also documenting how to setup a linux dev environment. In the following we will focus mostly instead on the steps to setup a dev environment under Windows.
+The provided Dockerfile has been written to run builds in Linux, and as such it is also documenting how to setup a local Linux dev environment. 
+For this reason, in the following we will focus mostly instead on the steps needed to setup a dev environment under Windows.
 
 ### **Setup a Windows development environment**
-The commands in the following are supposed to be executed from a powershell console.
+The commands that follow are supposed to be executed from a Powershell console.
 
 **1. Install golang**
 

LICENSE-3RD-PARTIES.md

@@ -250,4 +250,51 @@ The TUM-GIS cesium-point-cloud-generator is released under Apache 2.0 license:
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
-limitations under the License.
+limitations under the License.
+
+
+
+##### PDAL [Point Data Abstraction Library](https://github.com/PDAL/PDAL)
+
+This software uses test datasets coming from the PDAL , released under BSD open source license:
+
+Unless otherwise indicated, all files in the PDAL distribution are
+  Copyright (c) 2022, Hobu, Inc. ([email protected])
+and are released under the terms of the BSD open source license.
+
+This file contains the license terms of all files within PDAL.
+
+Overall PDAL license (BSD)
+===========================
+
+ Copyright (c) 2022, Hobu, Inc. ([email protected])
+
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following
+ conditions are met:
+
+     * Redistributions of source code must retain the above copyright
+       notice, this list of conditions and the following disclaimer.
+     * Redistributions in binary form must reproduce the above copyright
+       notice, this list of conditions and the following disclaimer in
+       the documentation and/or other materials provided
+       with the distribution.
+     * Neither the name of Hobu, Inc. or Flaxen Consulting LLC nor the
+       names of its contributors may be used to endorse or promote
+       products derived from this software without specific prior
+       written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+ FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+ BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+ OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
+ AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
+ OF SUCH DAMAGE.