We moved from Trimble R6 receivers to Carlson BRx7 with SurvPC on our TSC7 controllers, works great so far. We still use our S6 totalstations with Trimble Access.
I??m looking for detailed info on the RW5 format. Google is my friend, so I found something, mostly older information, and there is some info from Carlson on the latest additions about Headers containing info on Observations with tilt info but I miss a more global overview.
I??m looking in extracting QC reports for certain codes with multiple observations.
I did not find a way in SurvPC to select points based on codes and generate a report for all these points. Reports in SurvPC seems only possible point per point and that takes us too long.
btw Carlson support in Belgium/Holland seems rather slow
thanks in advance
Christof.
Hi Christof,
I can't help you (only old stuff about RW5, no way for code filtering), but if you find some clues, I'll be interested. Could you give some udpates if you got any?
btw Carlson support in Belgium/Holland seems rather slow
I'm afraid that support and growth in Europe is not a priority for Carlson.
Have you looked at the csv export options? I know you can export a csv with pdop, hdop and other similar rtk info for each point. Maybe you can find what you're looking for there.
Considering RW5 is text format, I wouldn't be surprised if the idea solution is a custom transformation/report...if Carlson can export raw data to XML, an XSLT transform could suffice to create a report.
Maybe you can find other data to explore in "Special codes" in feature code list. There's plenty of fields that are absolutely undocumented. I think that some of them doesn't appear in the RW5 file, but i can't see anything about the tilt. The field list may be relative to the instrument, so maybe you should take a look...
Thank’s for the hints. The idea is indeed to make a QC-report for a selection of points.
That may be a selection by feature code(s) or simply the points with multiple observations.
I’ll have a look at it the coming weeks. The RW5 is very descriptive and a good start.
I’ll will post back here once All is clear.
Small update before the site goes down for the big move to rpls.com.
I found that not all data is available in the rw5 file. For 3xample points that were deleted have no such indication in the Rw5 file. Please corr3ct me if l’m wrong.
So I started having a look at the 2 database files now. Will update later on.
grtz,
Small update before the site goes down for the big move to rpls.com.
I found that not all data is available in the rw5 file. For 3xample points that were deleted have no such indication in the Rw5 file. Please corr3ct me if l’m wrong.
So I started having a look at the 2 database files now. Will update later on.
grtz,
Haven't used Carlson for a bit, but in the past, no points are really in the raw data except entered points that are used (control points). Only the observation data is really there. I believe the coordinates are shown, but as a note. Coordinates result from running the data. (Which makes sense.)
And, deleting a point from the CRD file might result in a note in the raw data, but in the past that point would still be calculated when the data was processed. In other words, nothing gets deleted from raw data (which makes sense).
If you observed a new point with the same point number, things got a little strange. I believe that if you changed the descriptor, it would see that...probably just write the point into the raw data?
We never deleted points. We simply renamed them to a null identifier in the description.
If you store as the same point number and run the raw data, I forget what happens then, but I thought it averaged the points.
extracting QC reports for certain codes with multiple observations.
The easiest might be to bring into Star*Net and have it auto match points, which would give you a visual ellipse on those points.
If you observed a new point with the same point number, things got a little strange. I believe that if you changed the descriptor, it would see that...probably just write the point into the raw data?
Wouldn't it ask, store new points of raw data only?
