Trimble Business Center

 View Only
Expand all | Collapse all

Export of Hatching from TBC 5.70 to DWG

  • 1.  Export of Hatching from TBC 5.70 to DWG

    Posted 06-18-2022 11:11
    Hello,

    I have a some hatched objects in my TBC 5.70 project as can be seen here:




    I selected all (including hatching) to export into a DWG file.

    When I imported the DWG file into MicroSTATION V8i, the situation looks like this:


    As can be seen in the picture above, the hatching itself is lost.

    Q:
    Is there a way to save the hatching created in TBC 5.70 for subsequent use in MicroSTATION/AutoCAD software packages?
    (I tested it with DWG ver. 14, ver. 2000, ver. 2007 and ver. 2018, but always got the results as illustrated above (hatching is always lost).

    Martin Kalafut








    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------


  • 2.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-18-2022 19:49
    This is the case of micro and CAD not having that hatch pattern in their system.  You could explode the hatch and then when imported used that exploded hatch to recreate the hatch in micro and CAD.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 3.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 02:27
    Francisco - maybe I do not understand it correctly but
    I tried it, however it does not work. When I select the hatching itself to be exploded and explode it, then Number of objects exploded = 0.
    (I used here the BLOCK pattern for hatching).

    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------



  • 4.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 09:45
    Edited by Francisco Guerrero 06-20-2022 09:47
    I was able to use the Explode command and explode the "hatch" into polyline segments.



    I even exploded the block hatch


    here I have selected some random segments after the explode.


    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 5.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 12:28
      |   view attached
    Look at my video attached:

    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------



  • 6.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 13:42
    thats odd.  I tried again on another project using 5.7 and  I still am able to explode the hatch.  mind sharing your work?

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 7.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 14:09
    Yes, no problem. What would you need - just vce file or also original GNSS RTK measurements?
    Should I email it to you or post it here?

    Just remember - I use a refined slovak coordinate system in my project as follows (which is NOT standard part of TBC installation):


    But for this purpose, you can switch it to the standard part of the csd database - JTSK03 Krovak EN:






    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------



  • 8.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 14:14
    VCE.  just the linework would work.  upload on here.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 9.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 14:26
      |   view attached
    Here is my zipped vce file.

    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------

    Attachment(s)



  • 10.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-20-2022 14:36
    Hatch must be in a closed shape so it allows for explode to work.  I connected the linework to create a boundary and then exploded the hatch which now works.  either copy the linework or use those existing linestring to connect and close.




    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 11.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-21-2022 01:05
    Edited by Martin Kalafut 06-21-2022 02:08
    Many thanks Francisco! I joined the corresponding lines and after hatching the required area I am able to explode it.

    Still a question:

    When I joined all corresponding lines to form a closed shape of the area for hatching, within joined
    lines were different graphic types of lines (solid lines, fence line, gate line, etc. where some of them were graphically represented
    with another than solid lines).

    After such joining - the resulting one (joined) line is graphically represented as unified solid line. However, this is not 
    required result. I need to have some parts of the joined line to be graphically represented as they were before joining.
    It means - part of the joined line would graphically represented by solid line, parts by a another types of lines (fence, gate, ...)

    Is it possible to achieve it?

    Martin

    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------



  • 12.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-21-2022 03:51
    if you still have those original lines or have not saved that work.  Just do a copy and paste of all those lines and save them on another layer such as "reference hatch lines". This way you keep the original lines as their specified line type.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 13.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-21-2022 04:39
    I am not quite sure, what do you mean.

    In fact, I defined for all different types of lines their specific layers and after that I did the line works.
    So, every type of line has assigned its own specific layer.
    When I joined them in one joined line, the joining procedure created one joined solid line.

    When I select (for example) the part of the joined line where the gate is (before joining) and change the line
    on the type of line designed for gate - of coarse - all joined line changes from solid line for gate line type. When I break the joined
    line in the place where the gate is, I lose the possibility for exploding, since there is no more closed shape.

    By the way, why joining procedure selected the solid type of line for the joining and not - for example - line type
    for fence or gate which are also parts of the segments to be joined?

    Put into another words, I want to have a closed shape of the line for hatching in order to have the possibility to explode it,
    whereas all its line parts should graphically retain their specific types of lines as designated before joining.

    This is what I meant and what I wanted to achieve. So I do not understand what do you mean by using COPY/PASTE.
    What should I copy and where should I paste it?


    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------



  • 14.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-21-2022 04:59
    copy all linestrings that you will use to have a closed line.  Relayer those copied lines into another layer so you do not disrupt the linestring properties.  With the copied linestring you will join those and create the hatch out of that closed line.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 15.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-21-2022 14:10
    OK - thanks!

    Nevertheless, I would like to know the basic logic used in joining of several line segments with different line types
    (solid line, fence line,  line for gate, dashed line, etc. - they graphically differ each other).

    Which line type will be used for graphical representation of the final (joined) line?
    The line type of the first selected line segment for joining?

    Thanks!

    Martin

    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------



  • 16.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-22-2022 05:45
    when you copy the lines to be used for hatching those are just for reference of the hatch and that new layer created to save them to will be turned off.  so when you export the data you need be sure to turn off the copied linestrings.  The image below shows my copied linestring and the original linestring which are not modified keeping their original proprieties.  When you create the hatch, place that hatch in a layer you want to export.



    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 17.  RE: Export of Hatching from TBC 5.70 to DWG

    Posted 06-22-2022 13:28
    Thanks Francisco!

    I also used slightly modified approach.

    First, before joining the line to have a closed shape for hatching, I copied all separate
    line segments (with no moving, it means - they remained at the same places/coordinates)
    into their new separate layers with all their properties regarding the types of line segments, colors etc.

    I switched off the newly created layers.

    Then, I created a new layer for planned joined line and selected all line segments for joining. A joined line
    with unified line type was created.

    I selected the lines bordering the area for hatching and created the hatching (which can be exploded).ň

    Finally, I switched off the layer containing the joined line with unified line type and switched on back
    the layers with individual line segments which have different line types/colors.

    Everything is fine and the result is as expected and the hatched area (which can be exploded now problem free) is bordered
    by line segments (which are NOT joined to the one unified line) with different line types/colors.

    Many thanks again for your valuable help!

    Martin 


    ------------------------------
    Martin Kalafut (Secondary email
    ------------------------------