civil3d.wishlist1941
2007-10-01, 06:24 PM
Summary: The ability to use DEM files in the current SDTS format, or in ESRI's grid format, to define the grid surface.
And the ability to set the precision prior to import
Description: I would like to see grid surfaces reworked.
The grid surface is the red-headed stepchild of C3D - all the development work is going into improved TIN performance. Meanwhile, technology seems to be heading the other way - I'm seeing more and more data (LIDAR, multi-beam bathymetry, etc.) provided in grid form. Many of these datasets are also too large for a C3D TIN surface to handle. By definition, a grid needs about 1/3 the memory footprint of a TIN created with the same data points.
And we can't use that data without a lot of translation steps, because the only definition option for grid surfaces is to import a DEM file formatted to the *old* USGS standard. So here's really the first part of my wish - the ability to use DEM files in the current SDTS format, or in ESRI's grid format, to define the grid surface.
It should also be possible to increase grid surface performance & reduce memory footprint by reducing the elevation values from double precision to single. There is no elevation on the surface of the earth that needs 16-place accuracy. Grids can represent concepts other than topography, too - in some cases, the values could even be integer.
How Used: I have a LIDAR surface in ESRI's grid format that covers 120 square kilometers with a 1-meter point density. That's right, 120 million points.
If I need a portion of that surface in C3D, I currently start in ArcView, and export the grid to a point shapefile, clip the point shapefile to just the bare minimum area I need, add X & Y data columns, and export the shapefile to a .csv point file. Then I fire up C3D and create a TIN, using the .csv point file as part of the surface definition. Great, I've got a surface - unless there's more than about a million points in the .csv, in which case C3D will crash.
What I should be able to do is create a grid surface and select the ESRI grid file as a definition item, apply a boundary, and be ready to roll with profiles, grading, corridors - the works.
Feature Affinity: Surface Modeling
Submitted By: Earl Kubaskie on August 23, 2007
And the ability to set the precision prior to import
Description: I would like to see grid surfaces reworked.
The grid surface is the red-headed stepchild of C3D - all the development work is going into improved TIN performance. Meanwhile, technology seems to be heading the other way - I'm seeing more and more data (LIDAR, multi-beam bathymetry, etc.) provided in grid form. Many of these datasets are also too large for a C3D TIN surface to handle. By definition, a grid needs about 1/3 the memory footprint of a TIN created with the same data points.
And we can't use that data without a lot of translation steps, because the only definition option for grid surfaces is to import a DEM file formatted to the *old* USGS standard. So here's really the first part of my wish - the ability to use DEM files in the current SDTS format, or in ESRI's grid format, to define the grid surface.
It should also be possible to increase grid surface performance & reduce memory footprint by reducing the elevation values from double precision to single. There is no elevation on the surface of the earth that needs 16-place accuracy. Grids can represent concepts other than topography, too - in some cases, the values could even be integer.
How Used: I have a LIDAR surface in ESRI's grid format that covers 120 square kilometers with a 1-meter point density. That's right, 120 million points.
If I need a portion of that surface in C3D, I currently start in ArcView, and export the grid to a point shapefile, clip the point shapefile to just the bare minimum area I need, add X & Y data columns, and export the shapefile to a .csv point file. Then I fire up C3D and create a TIN, using the .csv point file as part of the surface definition. Great, I've got a surface - unless there's more than about a million points in the .csv, in which case C3D will crash.
What I should be able to do is create a grid surface and select the ESRI grid file as a definition item, apply a boundary, and be ready to roll with profiles, grading, corridors - the works.
Feature Affinity: Surface Modeling
Submitted By: Earl Kubaskie on August 23, 2007