search

NOAA-PMEL / LAS

Live Access Server
https://ferret.pmel.noaa.gov/LAS/
The Unlicense
13 stars 5 forks source link

New Product: Coordinate system description/ striding info and control #648

Open karlmsmith opened 6 years ago

karlmsmith commented 6 years ago

Reported by @AnsleyManke on 31 Oct 2008 16:55 UTC How can we make it clearer on the outputs what all of the underlying resolution issues are? This came up for me (as a user) when I was testing Google Earth just yesterday. There was no way from LAS to see even an estimate of what the underlying resolution of the data is. Can only make guesses by looking at plots. (Actually a SHADE plot in RASTER mode would provide strong clues, but then there is the auto-striding to consider.)

Here's a suggestion for how to solve this (for discussion) -- both seem relatively easy to do:

  1. create a new LAS gridded product called "Coordinate System Description" This product could be sensitive to what the currently selected region is. It could use the same striding algorithm as the color plots use. Then it could summarize the coordinate information for the full data set, and display detailed coordinates for the selected region.
  2. I think we should offer a striding controls for color plots in the LAS Options. "auto (fast)" and "off (slow)".

Migrated-From: http://dunkel.pmel.noaa.gov/trac/las/ticket/642

karlmsmith commented 6 years ago

Comment by @AnsleyManke on 31 Oct 2008 17:01 UTC A couple of ways to get an idea about the grid: Do a "show grid points" on plots to get an idea of the resolution of what's being plotted - after any striding. Or you could list a small amount of data to see the grid.

If we allow users to turn off striding, there will be the potential of out-of-memory errors. For plots, I suppose the job could be done in chunks, as it is for listings.

We'll have to think how to do the grid description for irregular grids and for curvilinear grids.

karlmsmith commented 6 years ago

Modified by @AnsleyManke on 5 Jan 2011 23:22 UTC