LIDAR - Revision history

Neteler: /* Direct import of LAS as raster DEM */

2024-12-15T12:09:19Z

Direct import of LAS as raster DEM

← Older revision		Revision as of 12:09, 15 December 2024
Line 184:		Line 184:
	==== Direct import of LAS as raster DEM ====		==== Direct import of LAS as raster DEM ====

	This is the same as the above, but use the {{~~Cmd~~\|r.in.lidar}} module (only in GRASS 7). ~~In all cases~~ you should manually decide on a suitable grid resolution and bounds, then set them with ''g.region'', before running the import modules.		This is the same as the above, but use the {{cmd\|r.in.lidar}} module (only in GRASS 7) and the {{cmd\|r.in.pdal}} module (GRASS GIS 8+).
			For the binning of LiDAR points into raster cells, you should manually decide on a suitable grid resolution and bounds, then set them with ''g.region'', before running the import modules. See the examples in the manual page.

	==== Import LAS as vector points in GRASS 6 ====		==== Import LAS as vector points in GRASS 6 ====

Neteler: updated to G8

2024-12-15T12:06:34Z

updated to G8

← Older revision		Revision as of 12:06, 15 December 2024
Line 203:		Line 203:
	* Vector points can be interpolated into raster DEMs with a number of modules, including {{cmd\|v.surf.rst}}, {{cmd\|v.surf.bspline}}, and {{cmd\|v.surf.idw}}.		* Vector points can be interpolated into raster DEMs with a number of modules, including {{cmd\|v.surf.rst}}, {{cmd\|v.surf.bspline}}, and {{cmd\|v.surf.idw}}.

	==== Import LAS in GRASS 7 ====		==== Import LAS in GRASS GIS 7 and later ====

	As vector points		As vector points
	* ~~GRASS 7 offers the~~ {{cmd\|v.in.lidar}} command		* {{cmd\|v.in.lidar}} command

	As raster: map:		As (binned) raster map:
	* {{cmd\|r.in.~~lidar~~}} command		* {{cmd\|r.in.pdal}} command
	* {{AddonSrc\|imagery\|r.in.pdal\|version=7}}

	=== Clean imported raster DEM ===		=== Clean imported raster DEM ===

Neteler: refer to other LiDAR workshops in this Wiki

2020-10-11T22:50:52Z

refer to other LiDAR workshops in this Wiki

← Older revision		Revision as of 22:50, 11 October 2020
Line 533:		Line 533:
	== See also ==		== See also ==

			* [[Lidar Analysis of Vegetation Structure]]
			* [[Processing lidar and UAV point clouds in GRASS GIS (workshop at FOSS4G Boston 2017)]]
			* [[Introduction to GRASS GIS with terrain analysis examples]]
			* [[From GRASS GIS novice to power user (workshop at FOSS4G Boston 2017)]]
	* [http://web.archive.org/web/20120324184538/http://knol.google.com/k/aerial-extraction-of-roof-surfaces-for-solar-analysis Aerial Extraction of Roof Surfaces for Solar Analysis]		* [http://web.archive.org/web/20120324184538/http://knol.google.com/k/aerial-extraction-of-roof-surfaces-for-solar-analysis Aerial Extraction of Roof Surfaces for Solar Analysis]

Neteler: +def lidar multiple returns

2019-08-02T14:26:52Z

+def lidar multiple returns

← Older revision		Revision as of 14:26, 2 August 2019
Line 349:		Line 349:

	==== DEM/DSM separation the simple way by selection of Lidar returns ====		==== DEM/DSM separation the simple way by selection of Lidar returns ====

			Background on lidar multiple returns: "''Lidar returns are discrete observations* recorded when a laser pulse is intercepted and reflected by targets. Multiple returns derive from one laser pulse intercepting multiple targets (e.g. a top of a tree, its branches, and the ground)''." ([https://gis.stackexchange.com/a/143000/687 source: stackexchange]).

	Find out where we have multiple returns:		Find out where we have multiple returns:
Line 372:		Line 374:
	v.surf.rst elev_lidrural_mrpts_first layer=0 elev=elev_lidrural_mrpts_DSM		v.surf.rst elev_lidrural_mrpts_first layer=0 elev=elev_lidrural_mrpts_DSM
	nviz elev_lidrural_mrpts_DSM col=ortho_2001_t792_1m		nviz elev_lidrural_mrpts_DSM col=ortho_2001_t792_1m


	==== DEM/DSM separation the more complex way ====		==== DEM/DSM separation the more complex way ====

⚠️Pvb: correct url

2019-01-02T11:27:54Z

correct url

← Older revision		Revision as of 11:27, 2 January 2019
Line 89:		Line 89:
	* [http://www.cs.unc.edu/~isenburg/software/ LAStools] are a set of simple command line tools for converting to/from ASCII, viewing, comparing, and compressing LIDAR data. ''While free to use source code is available for older verions, newer versions are not open source, only work on MS Windows, and are no longer free for commercial or government use.''		* [http://www.cs.unc.edu/~isenburg/software/ LAStools] are a set of simple command line tools for converting to/from ASCII, viewing, comparing, and compressing LIDAR data. ''While free to use source code is available for older verions, newer versions are not open source, only work on MS Windows, and are no longer free for commercial or government use.''

	* [~~http~~://~~www.~~liblas.org libLAS] ASPRS LiDAR data translation tools		* [https://liblas.org/ libLAS] ASPRS LiDAR data translation tools

	* See also [[LIDAR#Analysis\|LIDAR Analysis]]		* See also [[LIDAR#Analysis\|LIDAR Analysis]]

Neteler: {{AddonSrc|imagery|i.landsat8.swlst|version=7}}

2018-12-04T10:25:04Z

← Older revision		Revision as of 10:25, 4 December 2018
Line 13:		Line 13:
	* {{cmd\|r.in.xyz}} - Create a raster map from an assemblage of many coordinates using univariate statistics. ([http://hamish.bowman.googlepages.com/grassfiles#xyz example])		* {{cmd\|r.in.xyz}} - Create a raster map from an assemblage of many coordinates using univariate statistics. ([http://hamish.bowman.googlepages.com/grassfiles#xyz example])

	* {{cmd\|r.in.lidar~~\|version=70~~}} - (GRASS 7 only; GRASS must be compiled with libLAS support) Create a raster map from a binary LAS format LiDAR file (*.las) using univariate statistics and filtering. r.in.lidar is based on r.in.xyz. In addition to the options of r.in.xyz, r.in.lidar provides some basic lidar point filter options.		* {{cmd\|r.in.lidar}} - (GRASS 7 only; GRASS must be compiled with libLAS support) Create a raster map from a binary LAS format LiDAR file (*.las) using univariate statistics and filtering. r.in.lidar is based on r.in.xyz. In addition to the options of r.in.xyz, r.in.lidar provides some basic lidar point filter options.

	* {{cmd\|v.in.ascii}} - Import data from an ASCII file to GRASS vector format.		* {{cmd\|v.in.ascii}} - Import data from an ASCII file to GRASS vector format.
	: ''Due to memory overhead vector point imports will be limited to a few million data points unless topology and database creation is skipped with the '''-bt''' flags''. It may also be useful to clip the import file to only accept points falling within the current region by using the '''-r''' flag. See {{cmd\|g.region}} for details on specifying the region bounds.		: ''Due to memory overhead vector point imports will be limited to a few million data points unless topology and database creation is skipped with the '''-bt''' flags''. It may also be useful to clip the import file to only accept points falling within the current region by using the '''-r''' flag. See {{cmd\|g.region}} for details on specifying the region bounds.

	* {{cmd\|v.in.lidar~~\|version=70~~}} - (GRASS 7 only; GRASS must be compiled with libLAS support). Creates a vector points file from a binary LAS format LiDAR file (.las or .laz). r.in.lidar also can create a new location based on the LAS file, and can filter the input points by return and subregion.		* {{cmd\|v.in.lidar}} - (GRASS 7 only; GRASS must be compiled with libLAS support). Creates a vector points file from a binary LAS format LiDAR file (.las or .laz). r.in.lidar also can create a new location based on the LAS file, and can filter the input points by return and subregion.

	=== Analysis ===		=== Analysis ===
Line 184:		Line 184:
	==== Direct import of LAS as raster DEM ====		==== Direct import of LAS as raster DEM ====

	This is the same as the above, but use the {{Cmd\|r.in.lidar~~\|version=70~~}} module (only in GRASS 7). In all cases you should manually decide on a suitable grid resolution and bounds, then set them with ''g.region'', before running the import modules.		This is the same as the above, but use the {{Cmd\|r.in.lidar}} module (only in GRASS 7). In all cases you should manually decide on a suitable grid resolution and bounds, then set them with ''g.region'', before running the import modules.

	==== Import LAS as vector points in GRASS 6 ====		==== Import LAS as vector points in GRASS 6 ====
Line 206:		Line 206:

	As vector points		As vector points
	* GRASS 7 offers the {{cmd\|v.in.lidar~~\|version=70~~}} command		* GRASS 7 offers the {{cmd\|v.in.lidar}} command

	As raster: map:		As raster: map:
	* {{cmd\|r.in.lidar\|version=70}} ~~command~~		* {{cmd\|r.in.lidar}} command
			* {{AddonSrc\|imagery\|r.in.pdal\|version=7}}

	=== Clean imported raster DEM ===		=== Clean imported raster DEM ===
Line 450:		Line 451:

	As vector points		As vector points
	* {{cmd\|v.reclass~~\|version=70~~}} command		* {{cmd\|v.reclass}} command

	As raster map:		As raster map:
	* {{cmd\|r.reclass~~\|version=70~~}} command		* {{cmd\|r.reclass}} command

	== Sample LIDAR data ==		== Sample LIDAR data ==

Neteler: /* Tutorials */

2018-03-08T09:13:52Z

Tutorials

← Older revision		Revision as of 09:13, 8 March 2018
Line 496:		Line 496:
	== Tutorials ==		== Tutorials ==
	* [[Lidar Analysis of Vegetation Structure]]		* [[Lidar Analysis of Vegetation Structure]]
	* [[Processing lidar and UAV point clouds in GRASS GIS]]		* [[Processing_lidar_and_UAV_point_clouds_in_GRASS_GIS_(workshop_at_FOSS4G_Boston_2017)\|Processing lidar and UAV point clouds in GRASS GIS]]
	* [http://ncsu-geoforall-lab.github.io/geospatial-modeling-course/topics/geomorphometry_basics.html Lectures and assignments from NCSU partially dealing with lidar]		* [http://ncsu-geoforall-lab.github.io/geospatial-modeling-course/topics/geomorphometry_basics.html Lectures and assignments from NCSU partially dealing with lidar]
	* [https://wenzeslaus.github.com/grass-lidar-talks Some basic and some new (7.2-7.4) GRASS GIS features related to lidar]		* [https://wenzeslaus.github.com/grass-lidar-talks Some basic and some new (7.2-7.4) GRASS GIS features related to lidar]

Neteler: + more tutorial crosslinks

2018-03-08T09:12:13Z

+ more tutorial crosslinks

← Older revision		Revision as of 09:12, 8 March 2018
Line 494:		Line 494:
	:https://lvis.gsfc.nasa.gov		:https://lvis.gsfc.nasa.gov

	== ~~Links~~ ==		== Tutorials ==
			* [[Lidar Analysis of Vegetation Structure]]
	* [[~~Contour lines to DEM~~]] ~~interpolation module trials~~		* [[Processing lidar and UAV point clouds in GRASS GIS]]
	* [~~http://liblas.org/ libLAS] - LAS 1.0/1.1 ASPRS LiDAR data translation toolset~~		* [http://ncsu-geoforall-lab.github.io/geospatial-modeling-course/topics/geomorphometry_basics.html Lectures and assignments from NCSU partially dealing with lidar]
	* [~~http://pdal.io/ PDAL~~] ~~- Point Data Abstraction Library~~
	* [http://code.google.com/p/fullanalyze/ Fullanalyze] ~~software based on MATIS~~

	~~;Tutorials~~
	* [http://ncsu-geoforall-lab.github.io/geospatial-modeling-course/topics/geomorphometry_basics.html Lectures and assignments from NCSU partially dealing with
	lidar]
	* [https://wenzeslaus.github.com/grass-lidar-talks Some basic and some new (7.2-7.4) GRASS GIS features related to lidar]		* [https://wenzeslaus.github.com/grass-lidar-talks Some basic and some new (7.2-7.4) GRASS GIS features related to lidar]

Line 513:		Line 507:
	* [http://grasswiki.osgeo.org/wiki/TIN_with_breaklines v.triangle] add-on module for construction TIN with breaklines.		* [http://grasswiki.osgeo.org/wiki/TIN_with_breaklines v.triangle] add-on module for construction TIN with breaklines.
	: ''see above [[Contour lines to DEM]] page for further discussion of the (in)appropriateness of using TINs to generate raster surfaces. It is hoped that in future GRASS's more advanced spline interpolation modules will get breakline support.''		: ''see above [[Contour lines to DEM]] page for further discussion of the (in)appropriateness of using TINs to generate raster surfaces. It is hoped that in future GRASS's more advanced spline interpolation modules will get breakline support.''

			== Links ==

			* [[Contour lines to DEM]] interpolation module trials
			* [http://liblas.org/ libLAS] - LAS 1.0/1.1 ASPRS LiDAR data translation toolset
			* [http://pdal.io/ PDAL] - Point Data Abstraction Library
			* [http://code.google.com/p/fullanalyze/ Fullanalyze] software based on MATIS

	== Related publications ==		== Related publications ==

⚠️Wenzeslaus: /* Links */

2016-08-31T13:54:12Z

Links

← Older revision		Revision as of 13:54, 31 August 2016
Line 500:		Line 500:
	* [http://pdal.io/ PDAL] - Point Data Abstraction Library		* [http://pdal.io/ PDAL] - Point Data Abstraction Library
	* [http://code.google.com/p/fullanalyze/ Fullanalyze] software based on MATIS		* [http://code.google.com/p/fullanalyze/ Fullanalyze] software based on MATIS

			;Tutorials
			* [http://ncsu-geoforall-lab.github.io/geospatial-modeling-course/topics/geomorphometry_basics.html Lectures and assignments from NCSU partially dealing with
			lidar]
			* [https://wenzeslaus.github.com/grass-lidar-talks Some basic and some new (7.2-7.4) GRASS GIS features related to lidar]

	;Breaklines		;Breaklines
	* Not very well developed in GRASS so far, but we'd like to change that		* Not very well developed in GRASS so far, but we'd like to change that (you can volunteer)
	* {{AddonCmd\|v.surf.icw}} (only suitable for ~ 200 input points)		* {{AddonCmd\|v.surf.icw}} (only suitable for ~ 200 input points)
	* [http://surfit.sourceforge.net/ SurfIt] (GPL, Tck/Tk)		* [http://surfit.sourceforge.net/ SurfIt] (GPL, Tck/Tk)

⚠️Wenzeslaus: /* Links */ add PDAL

2016-08-31T13:49:10Z

Links: add PDAL

← Older revision		Revision as of 13:49, 31 August 2016
Line 498:		Line 498:
	* [[Contour lines to DEM]] interpolation module trials		* [[Contour lines to DEM]] interpolation module trials
	* [http://liblas.org/ libLAS] - LAS 1.0/1.1 ASPRS LiDAR data translation toolset		* [http://liblas.org/ libLAS] - LAS 1.0/1.1 ASPRS LiDAR data translation toolset
			* [http://pdal.io/ PDAL] - Point Data Abstraction Library
	* [http://code.google.com/p/fullanalyze/ Fullanalyze] software based on MATIS		* [http://code.google.com/p/fullanalyze/ Fullanalyze] software based on MATIS