Hmm... the BBcode doesn't seem to be working for me today...
----Quote: Alpine Mapping Guild ----
Not necessarily.
NED has lots of problems due to legacy USGS DEMS with all kinds of production artifacts such as scan lines, seams, quilting patterns etc... Sometimes it is useful to regenerate from the original DLG data to get rid of those artifacts, especially if they happen to fall over complex terrain where fudgin it in Photoshop would be difficult and time consumming.
----Quote: Alpine Mapping Guild ----
Good point. There may be cases where the NED is so bad, that a re-interpolation from the DLG contours will give a better result. Even the current NED data can have serious "banding" like errors (for lack of a better word). However, interpolation from contours is tricky, and the results are highly method dependent. Some common methods would include ANUDEM, TAPES-C, Topo-something in Arc, and v.surf.rst .
----Quote: Alpine Mapping Guild ----
Dylan, as you seem to know alot about this would you happen to know which interpolation tools / methods were used to generate USGS DEMs in the first place. I know about how the data was collected (GESTAL Photo Mapper vs, digitizing, vs. Photgrammetry) from the USGS documentation, but have found very little info on how the DEM themselves were interpolated.
----Quote: Alpine Mapping Guild ----
From what I have read, many of the USGS DEM products are created via a work flow like you mentioned: stereo photos -> contours via a mechanical/automated system -> (simple spline-like interpolator) -> an interpolated, gridded final product. The end result is a nice gridded dataset, but with various types of artifacts. As depicted in the attached image, contour heights are over represented in the gridded DEM, and calculated aspect angles seem to suffer from over represented values in the 8 cardinal directions. In addition, the spline interpolator can introduce "waves" or "ripples" in the DEM. I should note that the previously mentioned RST method can do the same thing, however it is possible to account for this in the parameters passed to the algorithm. The book Terrain Analysis (available on Amazon), has some very good discussion on these topics, but little is mentioned about how to fix them. If anyone is interested, I have found that a "terrain rescaling" algorithm in GRASS (and a Java version which I have forgotten the name of) can generalize terrain in a way that filters out the noise, while preserving the overall shape. In GRASS, this command is called
r.param.scale .
----Quote: Alpine Mapping Guild ----
In your opinion, given zero knowledge of GRASS how long and difficult would it be for someone to become familiar with it enought to learn to use to be able to run the RST algorithm on some vector data and export a DEM?
----Quote: Alpine Mapping Guild ----
If you have a MacOS machine, then installing and running GRASS is a simple as any other Mac application. Here is a link to some
pre-packaged downloads. As mentioned before getting started is the hardest part. Once you have your data in GRASS, I would recommend reading the manual pages on the RST method, along with the linked publications in the manual. I would say that a couple hours should be enough. Posting to the mailing list can save lots of time as well. However, there is still much debate over which algorithm will consistantly produce a more
hydrologically correct DEM.
Cheers,
Dylan