Editing DSP

From BRL-CAD

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 27: Line 27:
 
=== Preparing your height field data ===
 
=== Preparing your height field data ===
  
The DSP takes unsigned short (16-bit) integer data. Our various command-line data converters can help bring data in from pretty much any existing format, including image data, via various processing commands. If the data were in png image format, for example (which is basically 3-channel 8-bit integer data), the data could be prepared with a combination of 'png-pix', 'pix-bw', and 'cv'.  
+
The DSP takes unsigned short (16-bit) integer data. Our various command-line data converters can help bring data in from pretty much any existing format, including image data, via various processing commands. If the data was in png image format, for example (which is basically 3-channel 8-bit integer data), the data could be prepared with a combination of 'png-pix', 'pix-bw', and 'cv'.  
  
If you type the 'in' command, it will prompt you for each parameter individually and that should help some. For the DSP, the main parameters are: the source of the height data, the width (number of points in the X direction) and length (number of points in the Y direction) of the input data, width/length/height scaling factors, and whether to smoothly interpolate between cells (0 = do not interpolate, 1 = interpolate).
+
If you type the 'in' command, it will prompt you for each parameter individually and that should help some. For the DSP, the main parameters are: the source of the height data, the width (number of points in the Y direction) and length (number of points in the X direction) of the input data, width/length/height scaling factors, and whether to smoothly interpolate between cells (0 = do not interpolate, 1 = interpolate).
  
 
See the 'dsp_add' tool for combining two existing DSP data files into one.
 
See the 'dsp_add' tool for combining two existing DSP data files into one.
  
A DSP primitive is an array of cells initially defined by points in the X-Y plane as positive heights from Z = 0.  The DSP can then be transformed to other orientations and positions.  The number of cells is (numX * numY).
+
A DSP primitive is an array of cells initially defined by points in the XY plane as positive heights from Z = 0.  The DSP can then be transformed to other orientations and positions.  The number of cells is (numX * numY).
  
 
The data format for the DSP primitive is network-ordered unsigned short integers (nu16).  BRL-CAD has a couple of dozen tools that you can use for converting existing data into that raw format, such as the 'cv' command or the 'bw-d' and 'd-u' commands among other similar tool chains.  If you use the cv command, the output format is "nus" for network unsigned shorts.
 
The data format for the DSP primitive is network-ordered unsigned short integers (nu16).  BRL-CAD has a couple of dozen tools that you can use for converting existing data into that raw format, such as the 'cv' command or the 'bw-d' and 'd-u' commands among other similar tool chains.  If you use the cv command, the output format is "nus" for network unsigned shorts.
Line 79: Line 79:
 
Example 1.
 
Example 1.
  
In [[mged]] create a dsp object of width 142, length 150, no interpolation, cut direction 'ad', cell size 1 (in current units), and unit elevation 0.005 (in current units):
+
In mged create a dsp object:
  
  mged> in dsp1.s dsp f Ex1.dsp 142 150 0 ad 1 0.005
+
  mged> in dsp.s dsp f Ex1.dsp 142 150 0 ad 1 0.005
mged> r dsp1.r u dsp1.s
 
  
 
Example 2.
 
Example 2.
Line 89: Line 88:
  
 
  mged> in dsp2.s dsp f Ex2.dsp 152 150 0 ad 1 0.005
 
  mged> in dsp2.s dsp f Ex2.dsp 152 150 0 ad 1 0.005
mged> r dsp2.r u dsp2.s
+
 
 +
 
  
 
=== Rendering your DSP ===
 
=== Rendering your DSP ===
Line 95: Line 95:
 
Example 1.
 
Example 1.
  
  mged> B dsp1.r
+
  mged> B dsp.s
  mged> ae 270 90
+
  mged> ae 45 45
 
  mged> rt
 
  mged> rt
  
 
You should see something like this:
 
You should see something like this:
  
[[Image:Ex1rt.png]]
+
[[Image:Dsp.png]]
  
 
You can play around with the scaling factors (the end pair: 1 - cell width, 0.005 - cell height) to improve the looks of the image.
 
You can play around with the scaling factors (the end pair: 1 - cell width, 0.005 - cell height) to improve the looks of the image.
Line 107: Line 107:
 
But now let's invert the file so we get its negative:
 
But now let's invert the file so we get its negative:
  
  $ bwmod -m-1 -a255 < Ex1.bw > Ex1n.bw
+
  $ bwmod -m-1 -a255 < Ex1.bw > Ex1neg.bw
  
And make another dsp in the same manner as before:
+
And make another dsp:
 
 
$ cv huc nu16 Ex1n.bw Ex1n.dsp
 
$ ...
 
 
 
And see the results:
 
 
 
[[Image:Ex1nrt.png]]
 
  
 +
 
Example 2.
 
Example 2.
  
  mged> B dsp2.r
+
  mged> B dsp2.s
  mged> ae 270 90
+
  mged> ae 45 45
 
  mged> rt
 
  mged> rt
  
 
You should see something like this:
 
You should see something like this:
  
[[Image:Ex2rt.png]]
+
[[Image:Dsp2.png]]
  
Again, you could play with various parameters to get the desired look. You could also create the negative as we did with example 1 and see the results:
+
Again, you could play with various parameters to get the desired look.
 
 
[[Image:Ex2nrt.png]]
 
  
 
== Creating a DSP object from manual or programmatic generation of data ==
 
== Creating a DSP object from manual or programmatic generation of data ==
  
A DSP object can be created manually or programmatically by creating an ASCII data file as input using the BRL-CAD utility asc2dsp to convert it directly to the DSP binary formatAn easy way to create the input file for asc2dsp is to first create it row by row in natural form with the top row being the desired top row and so on in desired viewing orderThen take the finished file and filter it through the Unix utility tac which will reverse the order of the rows (lines).   
+
Now let's consider a more practical example and a real test of BRL-CAD.  We can import topological data and produce a realistic ground surfaceThere are many free sources of such dataSee this site for a start:
  
=== A simple example ===
+
http://www.naturalgfx.com/free_topo_gis.htm
  
For example, let's create the letter "T" for viewing in the X-Y plane.
+
We started with shape file data for the US from:
  
$ cat t-normal.asc
+
http://seamless.usgs.gov/data_availability.php?serviceid=Dataset_19
1 1 1 1 1
 
0 0 1 0 0
 
0 0 1 0 0
 
0 0 1 0 0
 
0 0 1 0 0
 
0 0 1 0 0
 
  
Now reverse the file:
+
We downloaded the zip archive 'ned_19_arc.zip' and unzipped in its own directory:
  
  $ tac t-normal.asc > t-reversed.asc
+
  $ mkdir ned_19_usa_arcgis_shapefile
 +
$ mv ned_19_arc.zip ned_19_usa_arcgis_shapefile
 +
$ cd ned_19_usa_arcgis_shapefile
 +
$ unzip ned_19_arc.zip
 +
Archive:  ned_19_arc.zip
 +
  inflating: ned_19_arc.dbf         
 +
  inflating: ned_19_arc.pdf         
 +
  inflating: ned_19_arc.prj         
 +
  inflating: ned_19_arc.sbn         
 +
  inflating: ned_19_arc.sbx         
 +
  inflating: ned_19_arc.shp         
 +
  inflating: ned_19_arc.shp.xml     
 +
  inflating: ned_19_arc.shx         
 +
  inflating: ned_19_arc.txt         
 +
  inflating: ned_19_arc.xml         
 +
  inflating: NED_DataDictionary2006.pdf 
  
and see the result in perfect form for asc2dsp:
+
See these pages for details of the [ESRI] shape file format:
  
$ cat t-reversed.asc
+
http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf
0 0 1 0 0
 
0 0 1 0 0
 
0 0 1 0 0
 
0 0 1 0 0
 
0 0 1 0 0
 
1 1 1 1 1
 
  
Finally, create the dsp file:
+
http://en.wikipedia.org/wiki/Shapefile
  
  $ asc2dsp t-reversed.asc t.dsp
+
We will use one of two Perl modules, Geo::Shapelib or Geo::ShapeFile, and write a Perl program to manipulate the shapefile data to produce the desired dsp object. The Perl modules are available on CPAN here:
  
(The TGM creation is left as an exercise for the reader.)
+
http://search.cpan.org/dist/Geo-Shapelib/Shapelib.pm
  
=== A practical example  ===
+
http://search.cpan.org/~jasonk/Geo-ShapeFile-2.51/ShapeFile.pm
  
Now let's consider a more practical example and a real test of BRL-CAD. We can import topological (topo) data and produce a realistic ground surface.  There are many free sources of such data, but these, for US topo data, seem to be the most likely:
+
Our program (tentatively named 'manip-shapefile.pl') will be made available in the BRL-CAD package.  
 
+
   
http://nationalmap.gov/viewer.html/
+
[TO BE CONTINUED]
http://earthexplorer.usgs.gov/
 
 
 
Trying to find suitable topo data, in a desired format for a specific area, is not so easy there, so we located another source of topological data (digital elevation models [DEM]) in [http://mcmcweb.er.usgs.gov/sdts/ SDTS] format:
 
 
 
http://data.geocomm.com/dem/demdownload.html
 
 
 
We selected [http://data.geocomm.com/catalog/US/61076/sublist.html Colorado],
 
[http://data.geocomm.com/catalog/US/61076/1231/index.html El Paso County], and [http://data.geocomm.com/catalog/US/61076/1231/group4-3.html Digital Elevation Models].
 
 
 
On that page we downloaded all six 10-meter data archive files for complete coverage of the county.  We also downloaded the six *TXT files which contain metadata about each archive. [Note that you are required to have a Geo Community account for any downloads (membership is free).] 
 
 
 
The six archive files are:
 
 
 
3818122.DEM.SDTS.TAR.GZ
 
4055020.DEM.SDTS.TAR.GZ
 
4055026.DEM.SDTS.TAR.GZ
 
4055028.DEM.SDTS.TAR.GZ
 
4055034.DEM.SDTS.TAR.GZ
 
4057865.DEM.SDTS.TAR.GZ
 
 
 
Taking the first archive as an example:
 
 
 
$ tar -tvzf 3818122.DEM.SDTS.TAR.GZ
 
 
 
we see that the archive files are not in a directory (but they are a set with possibly redundant file names found in other sets), so we create a directory for each:
 
 
 
$ mkdir 3818122.dem
 
...
 
 
 
Now move each archive into its own directory and unpack it:
 
 
 
$ mv 3818122.DEM.SDTS.TAR.GZ 3818122.dem
 
$ cd 3818122.dem
 
$ tar -xvzf 3818122.DEM.SDTS.TAR.GZ
 
3814CATD.DDF
 
3814CATS.DDF
 
3814CEL0.DDF
 
3814DDDF.DDF
 
3814DDOM.DDF
 
3814DDSH.DDF
 
3814DQAA.DDF
 
3814DQCG.DDF
 
3814DQHL.DDF
 
3814DQLC.DDF
 
3814DQPA.DDF
 
3814IDEN.DDF
 
3814IREF.DDF
 
3814LDEF.DDF
 
3814RSDF.DDF
 
3814SPDM.DDF
 
3814STAT.DDF
 
3814XREF.DDF
 
README
 
 
 
We can view the SDTS data files with a free viewer (for Windows only) available here:
 
 
 
http://www.visualizationsoftware.com/3dem
 
 
 
In order to manipulate the data in SDTS files we used the [http://gdal.org/ GDAL library] and then created a C++ program called 'sdtsdem2asc' which can be found here:
 
 
 
https://github.com/tbrowder/brlcad-usgs-topo-tools
 
 
 
After building and installing that program, we can change directory to the desired data set and create the dsp. We enter the desired base name of the image (we choose the unique data set base name)  and use the '--chop' option to minimize the dsp's vertical height to the default one meter below the lowest height in the data set.  Note the program will do all the work for us with the options shown:
 
 
 
  $ cd /path/to/3818122.dem
 
$ sdtsdem2asc 3814CATD.DDF --base=3818122 --chop
 
 
 
The resulting default png file (but cropped) is shown below.
 
 
 
[[Image:381822-az35-el25.png]]
 

Please note that all contributions to BRL-CAD may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BRL-CAD:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)
Retrieved from "https://brlcad.org/wiki/DSP"