Move to Site

[AllenJessup]

When trying to move Featurelines to another site the program often freezes. I've found one Featureline that seems to hang Civil 3D. It seems the first time I select it the Move to Site command doesn't work. If I try again. The program freezes. Also. If I select more that one at a time including the problem line. It freezes immediately.

I've audited and recovered the drawing multiple times. Listing the Featurelines doesn't give me a clue. I've also tried selecting the the Featurelines in the Prospector.

The drawing I've attached contains three Featurelines. The bottom 2 that appear yellow are Featurelines that I have moved to the destination site. The top one that appears green is the problem Featureline.

I think the workaround will be to redraw the Featureline in the new site. But I can't think of what would be wrong with this FL.

BTW. If you chose to look at the attached drawing. Expect to freeze Civil. If it doesn't freeze for anyone then I'll need to Repair or Reinstall.

[Todd_Rogers]

Hey Allen. Have you tried the command FINDSITEOVERLAPS?

[jmayo-EE]

Before re-drawing it I would explode it down to lines. If there are no overlapping segments or zero length objects just recreate from objects.

I too get some funky Flines and/or sites on occasion. i just try to recreate as fast as possible.

[cwr-pae · Accepted solution]

I opened your drawing and attempted the move to site, program froze.

I inspected the feature lines and noticed the problem FL was named "N EG Wlk-2 N Lady Godiva]>" which seemed strange. I removed the ']>' from the end of the name and was able to move the line to the <none> site.

']>' are used in text formatting in ACad and C3d label components, etc. I'm guessing they confuse C3d as part of a name field.

[AllenJessup]

Thank you. I never noticed that. It was named a couple of years ago. The must have been some sort of typo or copy/paste error. I'll look for that in other FLs.

[AllenJessup]

FINDSITEOVERLAPS didn't do anything for the issue. But it did point out that as the Move to Site command failed. It may have created duplicate Featurelines.

[Todd_Rogers]

---

@AllenJessup wrote:

It may have created duplicate Featurelines.

That's when you run the DELETEDUPFEATURELINES command 😉

---

[AllenJessup]

@jmayo-EE 

If it had been a complicated line. I would have exploded it. It only had two vertices.

In other cases where the FL wasn't interacting with a Surface. I've had luck deleting the FL, restoring it with the OOPS command and adding it to the Surface again.

[AllenJessup]

Yup. A bit of a Catch 22. There hadn't been duplicated prior to the problem. So I didn't think to search for them before you mentioned it. I did inspect the one I had trouble with for duplication.

90%+ of the duplication is in a group of FLs I tried to move that included the bad one. 

[jmayo-EE]

If you had intermediate elevation points or PIs on the same course, explode will retain the vertices and give you a series of lines not just one.

Good catch by @cwr-pae . The special characters were the issue. Special characters rarely react well with these Apps.

[Neilw_05]

The last time I tried the Delete/Oops workflow, C3D restored the FL to the surface. I concluded they "fixed" the oops command to make it restore the surface. However they have improved the ability to find and select FL graphically.

[AllenJessup]

---

@cwr-pae wrote:

the problem FL was named "N EG Wlk-2 N Lady Godiva]>" which seemed strange.

---

Was it the ] you found strange or the naming in general? We don't have a naming convention for our FL's so I just follow a similar pattern to field shots. North edge of walk 2 North side Lady Godiva. 2 means it's the second N EG Wld on the N side after skipping a paved driveway.

I often don't bother naming FLs. But this job has become painful and I thought it might help.

[cwr-pae]

The specific combination of formatting symbols ]> caught my eye. Because they are used in that pairing (and their reverse) too begin and end formatting strings by dimension text, C3d label style components, etc. If they are separated it probably wouldn't be an issue. { and } are used by mtext and dimension text for the same purposes so be wary of these in naming objects also.

I frequently name FLs for the same reasons.

[AllenJessup]

Yes. The symbols were obviously a mistake. Either a typo or maybe a copy/past error. Thanks for spotting that for me.

[daneiljack]

This can be frustrating, but there are a few troubleshooting steps you can take to resolve the problem:

Purge Unused Objects: Before attempting any other steps, try purging any unused objects in your drawing. Sometimes, these objects can cause conflicts and unexpected behavior.

Isolate the Problem Featureline: Since the freezing seems to be related to a specific Featureline, try isolating it to see if it is indeed the source of the problem. You can try copying the suspected Featureline into a new drawing and see if the issue persists. If the problem is isolated to that particular Featureline, there might be something wrong with its data.

Check Featureline Data: Review the properties and data associated with the problematic Featureline. Make sure there are no erroneous values or inconsistencies. Also, check for any nearby objects or constraints that might be interfering with the movement.

Use the Select Similar Command: Instead of selecting the Featurelines individually, you can use the "Select Similar" command. Select one Featureline, right-click, and then choose "Select Similar" from the context menu. This will select all Featurelines with the same properties. Once selected, try moving them to the new site.

Layer Visibility: [Check] if the problematic Featureline is on a layer with issues, or if there are any layer settings that might be interfering with the move operation. Make sure the necessary layers are turned on and thawed.

Try on Different System: If possible, try the same operation on a different computer with Civil 3D installed. This will help determine if the issue is specific to your system or if it's a problem with the drawing itself.

Update or Reinstall Civil 3D: Ensure you are using the latest updates for Civil 3D. If the issue persists, you might consider reinstalling the software to ensure a fresh installation.

Contact Autodesk Support: If none of the above steps resolve the issue, it might be a bug or a more complex problem with the software. In such cases, contacting Autodesk Support or checking their knowledge base for known issues and solutions can be helpful.

Remember to save a backup of your drawing before attempting any significant changes or troubleshooting steps to avoid data loss.

[salbrechtJHHCV]

Thank you!!!  Just dealt with a pesky feature line in one of my drawings named "(99)" open/close parentheses cost me 10 min. -Would have been more if not for this comment.  I've run into this before and now I finally have the answer!!!