Good people,
Thought some of you might like to know that there is a new version of Trimble Access (v2022.10) available.
The big new feature is feature coded symbols and linetypes. You can now see in your controller what your job will look like back in Trimble Business Centre.
Access also now supports IFC and BIM files on Android controllers.
And you can export to LandXML
Thanks to the help of some folks here (350RocketMike and JohnHamilton in particular) we have fixed a number of small annoyances.
There is a full list of enhancements here... https://help.trimblegeospatial.com/TrimbleAccessReleaseNotes/en/2022.10.htm
Hope you find them useful
Cheers
Jim
.
?ÿ
?ÿ
BRACE FOR IMPACT!!!
?ÿ
Jk
???? ???? ?????ÿ
Nice to see there's improvement in the F2F coding.
I would like to see an option added for defining a set of parallel lines through measured points as with the inroads TMPL code where each parallel line can have it's own feature code.
?ÿ
That export .csv, by blocks of name range, is helpful.?ÿ
That looks like they are finally getting caught up to this century lol. Awesome S I am just now building a feature code library.
And thanks, Jim for looking into my problem and not giving up!
Waiting out some heavy rain, this is exactly the post I was hoping to find on here. Thanks for the update!?ÿ
This is great. Several items on my wish list have been addressed. (Probably not due to me sending them to my dealer, I've no idea whether anything gets sent on to development, but I'm stoked that so many upgrades and fixes have been added!)
The FXL symbolization and layer colors is fantastic, I'm going to dedicate some time to updating our FXL to reflect our standard blocks. Then on to the much more difficult task of actually getting the crews to use it...
Renaming media files is huge - I will happily put away my custom stylesheets for renaming photos and modifying the JXLs to reflect updated names.
The Station Intervals options is going to be great for our corridor staking crews. I developed a custom stylesheet for generating a pre-made cutsheet from RXLs that largely mimics the interval selection options; paired with this new option we'll save even more time staking roads.
THANK THE LORD the target lock mode is now stored in the JXL! Drove me nuts trying to troubleshoot raw data without knowing what mode the crew was in.
Great to see we have BIM/IFC functions in Android! (Now if only the USA would get with the 21st century and start using more IFC/BIM in design...)
Thanks for all the hard work Jim! Access was already top dog for functionality and versatility, this only makes it better.
Glad to see it shouldn't be switching to passive mode anymore when I check backsight.?ÿ
The big new feature is feature coded symbols and linetypes. You can now see in your controller what your job will look like back in Trimble Business Centre.
I remember I set this up in Carlson SurvCe about 5 years ago.?ÿ It was neat but kind of one of those things you do to kill time on a rainy day.?ÿ I'll have to look into it and see if I can set it up in our styles.
This reminds me of another wishlist item for Access--?ÿ if I remember right in SurvCE I was able to define a line and then offset it in topo mode which helped me walk a nice grid for doing ground shots on large parcels.?ÿ In Access it seems like I can only do this in stakeout mode (after I first create a line and then store it), and people who work in TBC tell me points shot in stakeout mode are difficult to manipulate and very much prefer points shot in measure mode.
It would be nice if I could quickly define and offset a line in measure or measure codes mode and just kind of have that in the background for navigation purposes.?ÿ If this already exists then I'd be curious to hear how to set it up, and if not then it would be cool to have it added sometime.
@bstrand?ÿ
We were told the same thing about storing in staking in fieldgenius, but I was told it should be fine in access. I will make sure to avoid doing this for anything important as I'm sure it would have created a problem eventually.?ÿ
I'm looking forward to being able to draw lines as I go (like we were able to with fieldgenius for 10 years). Normally I spend a lot of time using the key in line function which makes you press a lot of buttons just to get a line between 2 points.?ÿ
Now I get to annoy my project manager by updating access which will force him to update TBC.?ÿ
Yes, your grid is on the ToDo list.
In the meantime you can use 'Stakeout line' to two points and work with the Station and Offset.
Or you can key all the lines and use the Snap toolbar to give you the intersections.
You should also let your TBC guys know there is a function in there that converts stake-out records to ordinary points.
As-staked points aren't difficult to deal with in TBC, it's just mildly annoying if they are not actually stake points. Trimble (reasonably enough) holds as-staked points at their design location and stores the deltas, until they are converted (if they need to be).
So if something is staked out, like a calculated boundary point, and then stored as a stake point, if one just dumps the project into TBC and then exports out the points, what gets exported is that original calc position, because as far as Access and TBC know, the operator intended to set a point at that calc position, not observe a monument.
It takes about 5-10 seconds to select all as-staked points in TBC and run the "convert as-staked points" command, which will then break that link to the design location and place points where they were actually observed. But it can get messy when the operator then has to merge those converted points with others, or if the job was begun on an assumed datum and then is post-processed to bring it to a projection. Again, not terrible, but just a bit tricky and not really in line with the ideal workflow.
Some crews stake out to station/offsets along road corridors in order to get their cross-sections during a topo, but when they do, it's going to hold that design station & offset, plus a zero elevation (2D alignment is being staked) or that profile elevation (3D alignment being staked) until the stake points are converted in TBC.
?ÿ
As far as staking out lines or grids during a topo, Access allows the operator to have "stakeout" and "measure" dialogs open at the same time. Start staking out, then start a Measure Points/Codes routine - just don't exit out of the stakeout beforehand.
Flip back to the stakeout dialog, move to where you need to be for the first point, flip back to Measure Points, observe, flip back to stakeout and keep on truckin'.
This seems like a good opportunity to pose a question. Typically I use the measure points/topo/control/rounds, ect.. Could someone elucidate a bit on the measure codes and where and how this is most applicable? Thx Willy
?ÿ
This seems like a good opportunity to pose a question. Typically I use the measure points/topo/control/rounds, ect.. Could someone elucidate a bit on the measure codes and where and how this is most applicable? Thx Willy
?ÿ
It just lets you create a panel of buttons that basically automatically types the codes for you.?ÿ It can help speed up topo-ing things, especially if it's repetitive coding like cross sections.