On Mon, Oct 24, 2016 at 10:52 AM, Benjamin Kabelik <b.kabelik@ airbornetechnologies.at> wrote:
> Dear mailing list members, > > > > I read the thread about the extra bytes and wrote a pdal translate command > for a ntv2 projection from UTM33n ETRS89 to Austria MGI M34: > > > > For %i in (*.las) do (docker run -v c:/temp/trafo_wien2/:/data > pdal/pdal:1.3 pdal translate reprojection > --filters.reprojection.in_srs="EPSG:25833" > --filters.reprojection.out_srs="+proj=tmerc +lat_0=0 > +lon_0=16.33333333333333 +k=1 +x_0=0 +y_0=-5000000 +ellps=bessel > +towgs84=577.326,90.129,463.919,5.137,1.474,5.297,2.4232 +units=m > +no_defs +nadgrids=/data/AT_GIS_GRID.gsb" --writers.las.forward=vlr > --writers.las.extra_dims="Amplitude=float,Pulse width=float" > --writers.las.minor_version=4 --writers.las.dataformat_id=6 > --writers.las.offset_x=auto --writers.las.offset_y=auto > --writers.las.offset_z=auto -i /data/%i -o /data/%i_gk_gisgrid.las) > > > > > > There are two things that came up: > > 1. I had to switch the data type of amplitude and pulse width from > uint16 to float because with uint16 I get integer values instead of float. > > 2. Is there any option to forward the description and scale of the > extra bytes? > I'm sorry, but there is currently no way to set the scale/offset or description in an extra-bytes VLR/field. I'd be happy to help with a contribution that you may wish to make to remedy the situation. Best, -- Andrew Bell [email protected]
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
