As I believe I have mentioned, I have not been able to use 1/3 arc-sec. DEMs in DEMEX even if preprocessed by Virtual Terrain Builder (VTB) which is reqired to use 1 arc-sec DEMs before DEMEX can handle them. This leads to an interesting situation on the Kentucky Div. route I am laying track for. At coordinates -84.2754/37.3747 there is a very short tunnel through a small ridge that lies in a bend of Roundstone Creek. This tunnel is barely 150 feet in length with a bridge over the creek on both ends. However, with 1 arc-sec data, the ridge ends east of the tunnel and the route of the track (which is nearly level anyway) is across a flat area. Then further north there is Tunnel #14 which is much longer and through a well defined ridge. So beware, those of you that are creating routes, some elevation areas may not be true to what is really there. I will place a tunnel section where the tunnel is supposed to be and then someone can manually shape the rest of the ridge when the route is released.
I would hope that someone could come up with a version of DEMEX or something like that which would use the higher resolution data but it must be realized that it would be a somewhat futile effort. USGS tends to change the format of DEM data at will and for example, the higher resolution data worked fine until about 5 years ago and then there was a format change. A file processed by VTB is about 1K smaller than the raw file, so there is something causing an error?
Jerry
I would hope that someone could come up with a version of DEMEX or something like that which would use the higher resolution data but it must be realized that it would be a somewhat futile effort. USGS tends to change the format of DEM data at will and for example, the higher resolution data worked fine until about 5 years ago and then there was a format change. A file processed by VTB is about 1K smaller than the raw file, so there is something causing an error?
Jerry






Comment