Trimble Business Center

Hi all,

I'm preparing to overhaul our Feature Code Library (FXL), which has its roots in our old Geodimeter workflows - back when we were limited to a flat code list and basic line commands. While that setup has served us well, it's long overdue for modernization.

I'm comfortable working in both the Feature Definition Manager and directly editing the FXL in a text editor, and I want to take full advantage of Trimble's feature coding capabilities across both field and office environments.

Here's what I'm hoping to implement:

• Create linestrings for TC, FL, and back of curb by measuring a single alignment (e.g., flow line) and applying offsets - with horizontal offsets to either side and vertical offsets that can vary.

• Use custom block features for utility items like boxes and vaults, supporting 2- to 3-point field methods for orientation and scaling. I plan to create these blocks from scratch in AutoCAD or Symbol Editor, or adapt suitable existing ones.

I've been reviewing Trimble's GlobalFeatures.fxl, which has been very informative but also a bit overwhelming in scope. I know Trimble has published a large collection of documentation and tutorials, though they're spread across different platforms and can be a bit challenging to piece together when diving into advanced topics. I also know there are dealers and individuals in the community who are passionate about sharing best practices - and those contributions are often the most practical and insightful:

• Tutorials or workflow guides for building advanced FXLs using best practices

• Sample FXLs and/or blocks relevant to civil workflows in the U.S., especially in Southern California or similar regions

If you've done something similar or have resources to share, I'd be very grateful. Thanks in advance to anyone willing to offer insights or examples.

Note: I've cross-posted this to both the Trimble Access and TBC communities, as it applies heavily to both field data collection and office setup/workflows.

For utility-related FXL updates, I'd build the library around the field workflow first and CAD symbols second. Boxes, vaults and handholes are good candidates for custom blocks, but I'd also add attributes for locate method, depth, signal quality, transmitter frequency/power, and whether the line was direct connected, clamped, sonded or passive. That extra metadata is very useful once the file gets into TBC or CAD.

For equipment categories and transmitter/locator reference, this page is useful when standardizing those attribute fields: https://ucghdd.com/collections/underground-magnetics