Is there an alternative workflow for creating contours from a raster tif?
I have a 12km2 tiff. When I generate contours from the whole thing, it's seems to be conservative with it's weeding procedure. The end product is not accurate.
If I zoom into an area (say 0.05km2), select resample raster, then create contours, the accuracy is much better. Obviously not feasible to do separate areas and stitch them all together.
Is there a better method? Maybe style the raster to display contours and then export that somehow?
Ultimately, we're trying to get a civil 3d surface from the raster that is manageable and we're trying to do this without the help of an ESRI GIS tech.
Any tips? thanks!
If you are trying to build a tinn surface using Civil 3D, then use C3D. You don’t necessarily have to use Map3D if you’re starting with a DEM.
In C3D, create a surface in Toolspace. This entails establishing a name for a NEW surface. The newly named surface will merely be a ‘placeholder’ for a surface to-be-created.
For your surface, you’ll need to give it ingredients, or raw materials, so civil can build it. The materials are known as the surface definition. This is where you can ‘add’ your DEM as that surface definition.
Chicagolooper
Thanks, yeah we've been down that road before. Civil 3D isn't capable of handling most tifs/dems efficiently.
I should have mentioned, this is not for detailed design... it's for our hydrological team to complete their analysis. We're taking the contours from the raster, creating a shp file and bringing them into Civil 3D via the Surface from GIS tool. It's creates a much more efficient surface.
Hi Randy,
"Civil 3D isn't capable of handling most tifs/dems efficiently."
Just curious, what sort of problems have you uncovered in Civil 3D surface creation?
Dave
Dave Stoll
Las Vegas, Nevada
I don't think it's anything new... maybe you work very small dems for your projects but we aren't able to use dem's larger than a few hundred m2. We would only be asked to use dems for larger studies so more than a couple km2 which is not managable without refining the data first.
For example a 1km2 geotiff is 5.5mb but the resultant civil 3d file is 2mb with a 100mb external mms file as civil 3d automatically recongizes the performance issues.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.