Hello,
I would have a request/impulse for enhancement for the
PointSymbol command.
The reason is to simplify graphics works in TBC and - in certain cases - to eliminate the need to
use Feature Definition Manager (fxl) files and Feature Code Processing.
PointSymbol command currently offers by default about 160 different map signs as potential point symbols
in graphical representation of point objects. They are embedded in the TBC system, but - unfortunately - closed
for potential adding of new graphical symbols.
In our cases, we deal with telecommunication/pipeline/waterline/land survey institutions of which every institution
has its own norms/directives for graphical representation of measured point objects in the field.
I have several *.CELL files (used in MicroSTATION) and each of them contains many tens or even hundreds of map signs
for point objects, according to their final use - telecommunication/pipelines/waterlines/land surveying/GIS.
I am able to extract the graphical map signs (symbols) for point object from these .CELL files and create .DWG file format/s.
All these symbols (in .CELL files) conforms to actually valid norms/directives of respective institution mentioned above.
Unfortunately, the default graphical point symbols in TBC system (under
PointSymbol command) have little use for us,
since they are graphically different than we would need to have.
My suggestion:I would suggest to add there (in the
PointSymbol menu) an import option for importing DWG file formats, which would contain
additional graphical symbols for point objects. This would extend the existing graphical symbols, which could be used
for graphical representation of points. Of coarse, there could be added additional functionality like a filter to show/hide imported files/map signs,
delete imported DWG file/s, ...
Then, we would be able to select a graphic sign/s for point/s in compliance with respective directives valid for displaying
point objects according to the end user (telecommunitacions/pipelines/...).
The main goal of this suggestion is to create final end-user deliverables within ONE software package (TBC)
without the need to refine the processed data in TBC additionally in other software package (CAD, Micro, ...). Thanks in advance for considering this suggestion or to inform me about an alternative solution.
Martin Kalafut
------------------------------
Martin Kalafut (Secondary email
------------------------------