Jump to content
Sign in to follow this  
boundnorth

2D polys to 3D contours not working

Recommended Posts

I've drawn (traced) the site contours with the polygon

tool, starting with the lowest and moving upslope.

Layer options set to Active Only, set the starting elevation

and the interval. When the dialog box opens to start to

converting the polys to 3D contours, no contours are

selected (usually the lowest contour is selected to start

the process). I've made several site models in other files

at this point so I'm familiar with the basic setup - and

that should be right. Any thoughts?

Share this post


Link to post

When all else fails (or whenever software misbehaves). First, try quitting and restarting the software. Second, try restarting the computer. Also, you might try opening a brand new file into which you can paste all of the poly's from the original file. Try the 2d-3d operation, leaving the poly's in the "none class". If this still does not work, I suggest double checking all the poly's to make sure none doubles back on itself or crosses any other. Also, double check that there is nothing else selected...

Share this post


Link to post

Thanks for your help and quick responses.

I quit & restarted; no change. Shut down the computer; no change.

Copied contours to new file and for a brief moment, 2Dpolys to

3D contours worked.. and then the same problem began again.

Nothing doubles back on itself or crosses, and the polygons (pre-3D contours)

are the only objects on that layer.

Share this post


Link to post

OK, next question: please provide your hardware/software configuration including the exact version of VW's you are running. Perhaps Katie (or someone at NNA) has better answers...

Share this post


Link to post

Did you inadvertently duplicate in place one or more of the polys? Just a thought.

I know this is a bunch of work, but you can use a 3d loci instead of contour polys to make a DTM. Select each poly in turn and use the Dupe Along Path tool to dupe a 3d locus. Assign an appropriate spacing. You can assign z value, color and class/sub class (for instance, class name is z value) for each group you dupe. Then select them all (make sure there are no groups or other kinds of objects) and invoke the Create Terrain command. I keep the 3d loci on their own layer.

One advantage of using 3d loci instead of contours is that you can select a portion of the vertices and create a DTM of a small part of your plan.

-B

Edited by Benson Shaw

Share this post


Link to post

Hey, boundnorth, did you ever figure out what the problem was? I'm having the same trouble here.

I don't have time to screw around with VW (AGAIN) so I converted my 2d polys to 3d and manually moved them into position. Not exactly quick but it worked.

I'd really like to know what went wrong so I can avoid it next time.

Share this post


Link to post

Billtheia, delete the very small polygon that is in the middle of your lot.

After manually converting the 2D polygons to 3D polygons the Validate 3D Data routine revealed that there was a problem. If you select all of your polygons you will find there are 15 of them, but you only have 14 visible contour lines. After deleting that very small polygon element you will be able to proceed.

Share this post


Link to post

Weird. That 15th element is actually a result of trying to run 2d poly's to 3d contours. Deleting it doesn't fix my problem.

If I delete the 15th element and then run 2d poly's to 3d contours, it fails leaving that 15th element behind.

Thanks for pointing out the Validate 3D Data routine, though. I didn't know it was there.

Share this post


Link to post

Works for me. If you tell me what the start contours height is, what the contour intervals are and which end is the lowest I'll do it for you and post it back to the list.

Correction: It won't work for me in your drawing. If I Copy the 14 polygons and then Paste in Place into a new imperial units document it works fine.

Edited by mike m oz

Share this post


Link to post

That was my experience too - if I pasted the polys into a new doc, everything worked. So, what the heck is wrong with the file that it's in? Corruption of some kind?

I've also had weird problems with some files not exporting to dwg properly. If I copy everything to a new doc, export works fine too.

What causes corruption of VW files?

Is there some way to check the validity of a VW file (like ACAD audit?)

Share this post


Link to post

Biilltheia, I don't know the answers to those questions.

Maybe you should bugsubmit some of your problem files with a concise description of what the problem is. If NNA can replicate the problem they might be able to work out what is causing it.

This particular problem may be due to a corrupted object elsewhere in that particular drawing. In earlier versions of VW I've had several experiences of corrupt imported Autocad items causing problems in drawings and as a consequence I always import DWGs into new empty drawings. I then extract the information I need for my drawings. If you need to bring in a whole drawing do it as a DLVP using the 'shuttle file' technique.

Share this post


Link to post

Thanks, Mike.

I'm not so sure that NNA cares to have me submit this because my problem is with VW2008 and, as I understand, they're not doing any more work on that version.

With regard to ACAD files, I'm talking about trouble EXPORTING to ACAD. I recently had trouble with entire sections of a model disappearing. If I copied and pasted everything into a new file, thought, the export worked fine.

When I DO import ACAD files, I ALWAYS use a shuttle file and a DLVP.

Thanks for your help.

Share this post


Link to post

Bill, I just opened your file in VW 2009 and it converts the 2D polygons to 3D contours without any problems at all. I didn't even have to delete the very small polygon segment - the routine just ignored it. Maybe you should consider upgrading to VW 2009.

Share this post


Link to post

Can't say that I'm crazy about the idea of BUYING a bug fix. It doesn't exactly make me happy about NNA's shift to an annual release cycle.

Share this post


Link to post

Bill, there are many improvements and enhancements in VW 2009 that make upgrading worthwhile. Often I find I don't fully appreciate the improvements in a new version until I have to go back and use an earlier version. Then it becomes obvious.

Share this post


Link to post

Bill, VW 2008 was a huge improvement over VW 12 ? the disappointing things were bugs

2009 takes VW into a new direction and although the improvements are not as great as 12 to 2008 it seems to be far less buggy and just better to use

I found my work flows from VW 12 to 2008 were substantially lessened ? just much quicker to do things in 2008

2009 ? the Plant Tool as an example ? I said to our distributor here in Oz ? I think I have died and gone to heaven ? the improvements are that powerful

I update sooner always rather than later and I think what I pay for VW is cheap considering I use it as a tool for my work most days

I like the annual release cycle

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...