Hi Ted, The Topo to Raster tool has not been updated for 9.4. Its still the same version of ANUDEM as it is in prior releases. Have you considered processing your data in several pieces utilizing the Margin in Cells option and then mosaicking the adjacent rasters? You might also want to consider creating a Terrain from your large contour dataset. Many of the surface analysis tools have been enhanced in 9.4 to directly analyze Terrains. You can always convert the terrain to a raster later if necessary. Regards,
Ted, In 9.3 you can generate a Terrain/TIN from contour data. For SF_Type choose mass points or softline. The same applies to 9.4. If you already have a Terrain and want to include the contours make sure the feature classes reside in the same feature dataset as the terrain otherwise you will not have access to them when executing Add Feature Class to Terrain. Check out this page to learn more about surface feature types. http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?id=3393&pid=3388&topicname=Representing_terrain_source_data_in_feature_classes In 9.4 there is also some new renderers for Terrains; Terrain Contour and Terrain Point renderers. On a side note, contours are generally a derivative of a surface so you should try to avoid a situation where contours are the only input to creating a surface. Photogrammetrically derived mass points is probably one of the best sources of data to build a terrain with, but really you want a combination of SF Types to fully represent the surface. Here are some common types of data used to build terrains. http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Types_of_source_data_supported_in_terrain_datasets Thanks for the feedback.
"The Topo to Raster tool has not been updated for 9.4. Its still the same version of ANUDEM as it is in prior releases." ie 4.5What a pity, I was hoping for an updated version of ANUDEM, say 5.2, that now uses breaklines and has improved the model in other areas.I find I have to tile up my topo data to build a good DEM but unfortunately there are a lot of artifacts when that is done. 1. You have to handle split lakes separately to find the level and mask them afterwards.2. Islands in lakes are not handled, so these have to be put back in.3. Large features on the edge do not get modelled properly unless you have an enormous cell buffer.4. Floodplains are very hard to get looking plausible especially if you add stream lines that meander.5. Every now and again there is a spike in the model caused by some unknown issue in the data.6. Using a file based parameter list does not cut it because the parameters need to be dynamic to handle a series of tiles.7. There is a limit to the number of tiles that can be merged, so it has to be done in a series of ever larger builds. Replacing a faulty tile is very difficult because of the complicated merge.8. The limit command does not work to limit the data processed so I have to clip all participating layers for each tile.9. Hillshade grids will be one pixel short all around the tile, so they cannot be merged later unless you build oversize tiles and then clip again.10. Some tiles are too sparse to build, for example small islands off the coast, so the tiles have to be combined into a single non-standard tile, processed and then clipped out.The process is extremely complex so I have reverted to a series of AML and Workstation that run to completion.
Retrieving data ...