Timeline for Using Python to send arguments to LAStools basics
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2017 at 21:52 | comment | added | Michael Stimson | That is a solid workflow for small areas. The areas I was converting were many square kilometres, as 1k x 1k tiles @ 8ppsm. The first part was to calculate the extent, divide (dice) the extent and then find all files with partial or complete overlap. The second part was to count the class 2 and 8 records for a given tile and if more than 2e31 records quarter the extent until all 'boxes' had less than 2e31 ground records. I didn't need to merge and retile the existing tiles which saved some temp space and processing time. | |
| Jul 7, 2017 at 14:20 | comment | added | noah ahles | Interesting, our workflow utilizes lastile before running blast2dem to make the tile inputs a bit smaller. we use the buffer function (roughly half the size of the tile) within lastile so that there are no edge effects upon mosaicking the output. | |
| Jul 6, 2017 at 22:48 | comment | added | Michael Stimson | blast2dem comes later in the script, in exactly the same way, the reason for separating into blocks is that blast2dem has a maximum number of input points groups.google.com/forum/#!topic/lastools/jeo-vtYK58k and that's what makes the script 644 lines instead of < 100. | |
| Jul 6, 2017 at 22:27 | vote | accept | noah ahles | ||
| Jul 6, 2017 at 22:27 | comment | added | noah ahles | Awesome, thanks for putting this up. Seeing all of the various ways that this can be accomplished has been really helpful. I'm excited to expand this script into running lasheight into lasclassify, then blast2dem both on separate drives to maximize efficiency. | |
| Jul 6, 2017 at 22:21 | history | answered | Michael Stimson | CC BY-SA 3.0 |