TL Cogo Block
Todor LatevTL Cogo Block
Todor LatevRecover lost Autodesk® Civil 3D® cogo points from static Autodesk® AutoCAD® block instances (exploded cogo points or custom blocks)
$15.00/year
Ever received a file from a consultant or client containing a bunch of static/exploded cogo point blocks instead of native Autodesk® Civil 3D® cogo point objects?
This app will help recreate the lost Civil 3D cogo points. It will recursively scan through the nested block definitions and attempt to extract relevant information to rebuild the original cogo point.
Supported text objects inside the block definition are DBText, MText and Attributes. Additional functionality such as character trimming and coordinate scaling on numerical inputs is also provided.
Any point blocks that fail to generate a cogo point are automatically added to a selection set for easy identification.
This app does not rely on the presence of attribute data inside block definitions in order to determine the cogo point parameters. Instead, it recursively searches the Autodesk® AutoCAD® blocks for objects containing text strings, extracts this information and assigns it to the various cogo point fields according to a format string specified by the user. It then recreates the cogo point Civil 3D object if all input conditions are met.
Refer to the General Usage instructions in the help file for details on the various parameters, supported objects and workflow.
Details
Operating system
Release date
Feb 21, 2020
Last updated
May 30, 2023
Version
2020.02.12.1
Language
Compatible with
CIV3D
2019, 2020, 2021, 2022, 2023, 2024
Capabilities
Blocks
Survey
Tags
Site, land & parcels
Frequently asked questions (FAQs)
What else should I know about this product?
Additional notes:
Attributes found in some blocks may have the "Visible" switch turned off, resulting in some blocks containing much more data than actually shown on screen. The app will process all attribute strings in the order found regardless of the state of the "Visible" switch. Use the TLBlockList command and account for all text strings in the format string parameter for best results. Consider the following example:
Attribute 1: tag: ELEV, attribute text: 3.27, visible: True
Attribute 2: tag: PNTS, attribute text: 20041, visible: True
Attribute 3: tag: CODE, attribute text: 39, visible: True
Attribute 4: tag: DESC, attribute text: pavement, visible: False
Attribute 5: tag: NOTE2, attribute text: , visible: False
Attribute 6: tag: ELEV2, attribute text: , visible: True
Attribute 7: tag: NOTE, attribute text: , visible: False
Attribute 8: tag: NAME, attribute text: , visible: True
Here the block contains two note strings as well as a desc string, which are turned off and may not be visible on the screen. The notes are of little use since they are empty but the desc field can be used to assign the point description field to "pavement" in this instance. Alternatively, the block contains a survey code value (39 in this case) which can be assigned to the description field instead if deemed more important.
Is there additional support information provided?
For questions/comments/suggestions/bug reports etc please send an email to Todor.Latev@gmail.com
Found an issue?