Custom Query (419 matches)


Show under each result:

Results (70 - 72 of 419)

Ticket Resolution Summary Owner Reporter
#250 invalid Create program to rescale dark file benj benj

We need a program that will read in a dark frame file, rescale it to mimic that for a different integration time and then output the new file.

Basic level: Read in data file, multiply by a user-specified scaling factor (except pixels 1 & 2 on band 1 for each line), output new data file.

What we really want: Same, but calculate scaling factor from differential of integration times - check relative data values for existing dark files to try and work out if the result of changing the integration time is just a linear scaling (hopefully) or something more complicated, then implement appropriate algorithm. The user should also be able to specify a scaling factor as above if they prefer.

Gold-plated: Same, but also account for changes in framerate and in spectral/spatial binning. May be worth spending half an hour to check whether the effects of altering these are also just linear scaling, but if they're not then don't include them (assume constant).

Related tickets: #218 #249

#347 fixed DEM generation script fails on long lines iopa benj

The script used to generate DEMs for UK flightlines ( currently only takes into account the start and end position of the aircraft on each line (because it reads these from the header files). This means that on long lines where there is an entire BNG tile between the start and the end it may not include DEM data for the whole flightline.

Possible solutions:

  1. (Preferred): Read SBET file in (using, unless you've got a pressing reason to do it another way), track position of aircraft and do maths on swath width to work out which BNG tile the aircraft is over (ensuring it's in the UK as well).
  2. (Possibly easier): Adapt existing script to be more intelligent about what tiles might be in the middle. May be easier but might be complicated by corner case and/or case where rolls over tile edge (9->0).
#545 fixed DEM Scripts Rewrite/Restructure dac dac

There are currently a large number of scripts and libraries for DEM related tasks, most commonly used to:

  • Create DEMs for use in APL
  • Create DEMs from LiDAR data
  • Perform general tasks on DEMs (e.g., reprojection)

These scripts are a complicated mix of bash and Python which are very difficult to debug. Previous attempts to simplify them have only increased the complexity.

There are problems with the existing scripts which are proving difficult to fix given the current state of the code, the biggest one is that the DEMs produced are often much larger than needed.

A rewrite/restructure of the existing DEM scripts is therefore proposed with the following aims:

  • Use Python instead of bash where possible
  • Store common functions within a Python library
  • Make use of existing libraries both external (e.g., GDAL, Proj, GRASS Python bindings) and internal where possible.

Given these aims the following is proposed:

New DEM Scripts Create DEM subset to navigation data for use in APL. Locations of existing DEMs (ASTER and NMB) will be hardcoded but will allow any DEM mosaic (real or virtual raster) to be provided.

  -o Out DEM, --outdem Out DEM
                        Output name for DEM
  -n Nav file, --nav Nav file
                        Navigation data (.sol / .sbet file)
  -p Main project directory, --project Main project directory
                        Main project directory (default=".")
  --aster               Use ASTER data
  --nextmap             Use Nextmap data (/users/rsg/arsf/nextmap/neodc/nextma
  --srtm                Use SRTM data (/local1/data/basedata/srtm/srtm_global_
  --demmosaic Input DEM mosaic
                        Input DEM mosaic. For non-standard DEM. Use "--aster"
                        or "--nextmap" for standard DEMs.
  --separation_file Seperation file
                        File with Height offset to add if "--demmosaic" is
                        used and DEM heights are not relative to WGS-84
                        elepsoid. Not required if using "--aster", "--nextmap"
                        or "--srtm" for standard DEMs.
  -b BIL Navigation Files, --bil_navigation BIL Navigation Files
                        Directory containing post-processed navigation files
                        in BIL format. By default raw navigation data will be
                        used for "--project". If this is not available (e.g.,
                        for ARSF delivered data use this option and point to
                        "flightlines/navigation" within delivery directory
  --keepgrassdb         Keep GRASS database (default=False) Create DEM from lidar data

  -o Out DEM, --outdem Out DEM
                        Output name for DEM
  -s Out Screenshot File or Directory, --screenshot Out Screenshot File or Directory
                        Output directory for screenshots or single file for
                        screenshot of mosaic, in JPEG format.
  --las                 Input LiDAR data are in LAS format (default=True)
  --ascii               Input LiDAR data are in ASCII format (default=False)
  -r Resolution, --resolution Resolution
                        Resolution for output DEM (default=2)
  --in_projection In Projection
                        Input projection (e.g., UTM30N; default=UKBNG)
  --out_projection Out Projection
                        Out projection. Default is same as input
  -n Nav file, --nav Nav file
                        Navigation data (.sbet / .sol file) used if patching
                        with another DEM
  -p Main project directory, --project Main project directory
                        Main project directory, used if patching with another
  --demmosaic Input DEM mosaic
                        Input DEM mosaic to patch with in GDAL compatible
                        format. Vertical datum needs to be the same as output
                        projection. Only required for non-standard DEM. Use "
                        --aster" or "--nextmap" for standard DEMs.
  --aster               Patch with ASTER data
  --nextmap             Patch with Nextmap data (/users/rsg/arsf/nextmap/neodc
                        If patching with another DEM, get extent from
                        hyperspectral navigation data, recommended if DEM is
                        to be used with APL and navigation data are available.
  --lidar_bounds        If patching with another DEM, get extent from lidar
                        data plus default buffer of 2000 m. If DEM is not
                        required to be used with APL this option is

New DEM Library Putting all the DEM functions in a separate module (arsf_dem) is proposed rather than multiple libraries.

|-- arsf_dem
|   |-- arsf_dem.cfg
|   |--
|   |--
|   |-- dem_lidar
|   |   |--
|   |   |--
|   |   |--
|   |   |--
|   |   |--
|   |   |--
|   |   |--
|   |--
|   |--
|   |--
Note: See TracQuery for help on using queries.