Custom Query (419 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (118 - 120 of 419)

Ticket Resolution Summary Owner Reporter
#163 fixed Cloud Test, flight day 031/2008, ethiopia knpa mark1
Description

Data location: ~arsf/arsf_data/in_progress/2008/flight_data/arsf_internal_projects/cloud_test-2008_031_ethiopia

Data arrived from ARSF via initial SATA disk transfer in March

Scientific details: (details of application not available at PML)

PI: Internal project

Sensors:

  • Eagle
  • Hawk

Quicklook

TBD.

#164 fixed pre_lidar_cal, flight day 016/2008 knpa mark1
Description

Data location: ~arsf/arsf_data/in_progress/2008/flight_data/arsf_internal_projects/pre_lidar_cal-2008_016

Data arrived from ARSF via initial SATA disk transfer in March.

Scientific details:

PI: Internal project

Sensors:

  • ATM

Quicklook

TBD.

#166 fixed Support: 13/Jun/08, John Stevenson, IPY07/02, Lidar interpolation issue benj benj
Description

Query relating to Thingvallavatn (#98) lidar data - overlapping flight lines in opposite directions causing interpolation artefacts (see attached image).

We believe these are caused by the lidar being aimed down a steep slope flying one way and up it flying the other coupled to a slight boresight offset, causing a difference in exactly where it hits the slope in each case being calculated as the same location (hence why it only happens on steep slopes, and only on slopes that are either roughly parallel to or perpendicular to the plane, depending on which boresight angle is off).

Suggested solution is to average the lines using r.mapcalc in Grass prior to interpolation of null areas. If the slope is of a fairly constant gradient and the problem is caused by the above, this should hopefully produce reasonable results. Also asked Gabriel Amable at ULM for any suggestions. Given example data in ~arsf/support/20080813-JohnStevenson

Original email as below:

Hi,

I am working on the 203_Thingvallavatn dataset.  I am processing the LiDAR to generate a 1 m DEM.  I have combined the xyz points from each of the .all files into one big file for processing.  When the data are plotted (via nearneigbor and grdview in GMT, or via v.in.ascii and v.surf.rst in GRASS, or r.in.xyz and r.resamp.rst in GRASS), I find that some areas contain ESE-trending stripes.  These have a spacing of 3-5 m and an amplitude of a few 10s of centimetres.  The lines are perpendicular to the flightlines and I imagine that they are due to disagreement between data of different flights.

How do you recommend that I treat the data to remove these?  The stripes are only present on steeper slopes with a NNW to ENE aspect, so I am currently applying a filter to these areas (with the smooth=map parameter in r.resamp.rst).  Do you have any other suggestions?

I have attached some sample data points and a plot of the problem.

Thanks,

John
Note: See TracQuery for help on using queries.