One of the most time-consuming processes when developing with Hexagon G/Technology is creating custom commands. The usual development approach consists of the following iterative process: During testing, only limited changes to the source code are allowed by the Visual Studio Edit and Continue function, effectively requiring multiple iterations of this sequence. The process of starting… Read More »
Consider a requirement where the centroid of a set of points needs to be retrieved within a custom command. This can be achieved using the ‘GTDataProvider.DataContext.Execute‘-method:
Whenever a user is digitizing a polygon, he expects feedback when moving the cursor before actually adding a point, the system should ‘rubberband’ the position under the cursor and only add it to a collection of points after the user left-mouse clicks in the Window. Key to rubberbending in G/Technology is responding to three events… Read More »
Consider a requirement where an unsorted set of geometries needs to be merged into a single geometry. Take for instance the following set of geometries where: a Red dot indicates the startpoint The arrow indicates the drawing direction The label “1-50” indicates the order of drawing and an identifier for the geometry Both of these… Read More »
Fiber Couplers are used to connect Fiber Inner Ducts in a Fiber Branch Enclosure. You can connect Fiber Inner Ducts using the Fiber Feature Editor by selecting the two Fiber Inner Ducts and choosing the ‘Couple’-icon : This will connect the 2 selected Fiber Inner ducts using a Fiber Coupler. After coupling the Fiber Inner… Read More »
Introduction G/Technology provides functionality to run dynamic queries, the so called ‘Ad-Hoc queries’. A Large telecom provider in the Netherlands is moving Fiber Cables from CRAMER to FOW and AdHoc-queries provide a great tool to analyze and visualize migrated data At this provider Fiber Cables are contained by Fiber Inner Ducts who themselves are contained… Read More »
If you publish metadata, G/Technology creates a set of .raw- and .ddc files, the metadata to be stored in these tables/ddc-files is read from table G3E_METADATAKEYS. This gets truncated and filled during the metadata-publishing process by procedure MG3EPopulateMetadataKeys. This blog-entry describes how to extend the G/Technology metadata system with your own tables. Key to extending… Read More »
Suppose we have a Cable feature with CABLE_TYPE, TOTAL_SIZE and FIBER_SIZE attributes. Whenever the CABLE_TYPE attribute is set, attributes TOTAL_SIZE and FIBER_SIZE need to be set as well. We need to implement the following list : ID Cable type Total size Fiber Size 1 Corning 12F 12 4 2 BICC 16F 16 4 3 BICC… Read More »
Fieldvalue filters are used to limit possible choices for a picklist, you can define them by setting column G3E_FIELDVALUEFILTER on table G3E_TABATTRIBUTE. Suppose you have the following table REF_FSHELF : ID MANUFAC MODEL_NAME SLOTS POSITIONS 1 KPE KP-CWDM/2 2 1 2 KPE KP-CWDM/2 2 2 3 KPE KP-CWDM/2 3 6 4 KPE KP-CWDM/2 3 7… Read More »
If you select a feature, GTech shows the selected feature in Feature Explorer. The right area of feature explorer shows attributes of the selected feature, the left area shows the identification of the selected feature. This will show something like ‘Feature name – Fid’ (G3E_FEATURENAME – G3E_FID), in the picture below you can read ‘Point… Read More »