Topcon Office Ideas

Portal indented for new ideas or requests for the Topcon Office Software.

Select

  • Topcon Office Product for Survey, Site Prep/Construction or Layout

  • Topcon Tools for Tools ideas

Any issues or bugs need to be directed to Topcon Support <support@topcon.com>

Simplify coding and command requirements for scaled and multi-scaled Symbols

Example: we want to show a tree's foliage spread and a scaled tree trunk. Currently the process is you have two scaled codes (one for the tree and one for the tree trunk). Applying the Code Settings commands (* being the delimiter) and (S for scale command). In this example TR code = the scalable tree and TRNK code = the scalable tree trunk. The code required would be say: TR*S4*TRNK*S1 - which means that the tree spread is 4m and the trunk girth is 1m. This is dependant on Project Settings "scalable symbols" which is 1.000 for diameter and 2.000 for radius. What would be simpler and less complex is to apply "Attributes > POINTS" with the names TR and TRNK with the appropriate "Value Type" setting so if the client in the field entered the attribute name and value eg. TR 4 and TRNK 1 - those entered values would be applied to the codes. NOTE: as Magnet Field has Attributes, it would seem to be the appropriate way to go by applying MField attributes to Magnet Office attributes and apply scaling for spread, trunk and height.

  • Guest
  • Aug 26 2019
Topcon Office
  • Attach files
  • Guest commented
    April 04, 2023 10:56

    Still no solution for trees to be coded by entering all attribute and smooth

    transfer to magnet office?

    Attachments Open full size
  • Admin
    Barkley Hensley commented
    June 10, 2020 23:40

    This is planned to be implemented in both field and office at the same time.

    Attachments Open full size
  • Guest commented
    October 31, 2019 01:42

    I see a few votes for this request to use point Attributes to scale tree symbols during import/reduction, so looking for some user feedback to get some ideas.
    Since each company may apply this slightly differently some kind of standard may be the best way for implementation, therefore could someone please provide some suggestions for using attributes to cater for the not only the trunk but also additional details. 

    For example I have a point with code TREE, and recorded for the point attributes: 

    SPREAD 14
    HEIGHT 18
    TYPE Spotted Gum
    TRUNK*S 0.5

     

    Where SPREAD will assume for the primary symbol/code TREE. 

    HEIGHT (of tree, not ground height/elevation) and TYPE would just be additional info

    TRUNK*S would apply to an additional symbol using TRUNK code.

     

    It would also be necessary to choose whether survey code or attributes would be used as they may contradict each other. 

    NB. MO cannot "apply" the height and type to a symbol, but this may be useful in future to further extend options for MAGNET Modeler.

     

    Thank you!

    Manami

    Attachments Open full size
  • Guest commented
    August 27, 2019 05:22

    I agree there is some work to do on processing for trees.

    In Australia the usual requirement for trees in to record the attributes  of Spread, Trunk, Height and Species, which usual is coded in the field as, "T14/0.5/18/SpottedGum" which is T=Tree, 14m spread (diametre), 0.5m trunk diametre, 18m high and it is a Spotted Gum.

    Every company does it slightly different but the same information is usually requried, a macro is usual applied in AutoCAD or MicroStation to dress the data with a symbol and text streamlining the process.

    It would be great not having to use AutoCAD but it is not feasible in Magnet if there are a million trees. A solution would be great. Thanks.

    Attachments Open full size

Related ideas