How do I get a .tin file import created from a GeoPak SS4 terrain model
to not look like this in ConceptStation?
I use the Import feature to import a .tin and a .tiff into CS. It creates a .3sm mesh wherein the road network looks like a bunch of wet noodles over meatballs. What trick am I missing to make the roads look like they are on fills and in cuts?
Hi Geoffrey,
Your image is draped over the terrain. Since the image is not a 3D image, it will not look perfect. Some stretching and warping is expected, especially with a terrain that has quite a bit of elevation variation. The better the image quality and geolocation of the image, will result is a more "life-like" draping over the terrain.
Holly
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
I guess don't fully understand how a .3sm file is created. I thought that importing an accurate .tin model would take care of the terrain issues that I have had with CS at this location (rural Missouri, USA). Do I need an accurate 3D image as well? Does a 2D image somehow override the .tin model import?
I'm trying to develop several options for an interchange on an existing 4-lane highway, and I can't really do it with CS if it can't represent the highway profile reasonably accurate. CS gives me a roller coaster for a highway profile.
Did you try using GeoCoordination services to download a terrain and image file? If you tell me the location of the image, I can try as well with my ConceptStation to see what result I get.
If the draped roads are looking bad is likely because the .tin and the tiff files are not aligned correctly. If you attach the raster and the .tin in Geopak, would both file aligned correctly?
Thanks,
Mathieu