As a variety of low-cost GNSS receivers come to the market, it's pretty obvious that eventually it will be hard not to buy some equipment newer than my vintage Trimble receivers that still perform as well as they ever did. In the sort of work that I do, that means being able to get PPK and Static vector solutions. It looks as if RTK costs next to nothing, so wouldn't be a bad option for topographic mapping and roughing things in as long as the real-time link from base to rover uses a radio rather than a cellular network that would be non-existent in many rural areas where I survey.
Right now, I'm supposing that the key element will be GNSS post-processing software that will export vectors in a format that Star*Net recognizes. That, and relative simplicity, and a professional-grade product that isn't perpetually stuck in beta-test mode.
Subject to being shown otherwise, the CHS X91+ receivers look to be a good hardware choice with GNSS Solutions the first guess as to a reasonable choice for post processing. I haven't demoed GNSS Solutions yet, which is why I'm asking for feedback from Star*Net users.
Here's the question: Is anyone using this specific combination and exporting the vector solutions to Star*Net for adjustment in combination with conventional measurements? Star*Net is almost certainly going to continue to be the essential ingredient in my practice for combining GPS/GNSS vectors with conventional measurements and it looks as if that will pretty much always be needed at some point on a typical project. Stable processing software that works without the sort of complexity that mainly seems to generate bugs to be endlessly fixed via "maintenance agreements" would be also pretty much a necessity.
following this. Kent-where are you finding RTK that cost next to nothing?
TXSurveyor, post: 384854, member: 6719 wrote: following this. Kent-where are you finding RTK that cost next to nothing?
Well, "next to nothing" is a relative concept, of course, but a pair of CHS X91+ receivers looks like a deal to me when you consider that back in 1997 just a pair of L1-only receivers with a controller and software was about $24k in 2016 dollars.
Kent McMillan, post: 384844, member: 3 wrote: with GNSS Solutions the first guess as to a reasonable choice for post processing.
I'm under the impression that GNSS Solutions is already EOL, with no plans to revive it. Am I mistaken?
I'm under the impression that GNSS Solutions is already EOL, with no plans to revive it. Am I mistaken?
I am still using the 3.80 version. Sometimes, a RINEX file would refuse to be imported but other than that it still gives good static/PPK results.
Jim Frame, post: 384880, member: 10 wrote: I'm under the impression that GNSS Solutions is already EOL, with no plans to revive it. Am I mistaken?
I haven't gotten the idea that it is EOL in the sense that it is still functioning software, if unsupported. Mark Silver has described what is basically a hack to bring Geoid 2012a in as well as the NGS file with the current absolute antenna models.
Although, since Star*Net handles a standard NGS geoid model perfectly well, I don't see much value in applying the geoid model in the vector processing software. I'm interested in bringing vectors, not coordinates, into Star*Net.
Star*Net uses plain ascii text files as input. I write my own translators to get data (processed vectors and reduced conventional observations) into both Star*net and Geolab. Not hard to do.
John Hamilton, post: 384913, member: 640 wrote: Star*Net uses plain ascii text files as input. I write my own translators to get data (processed vectors and reduced conventional observations) into both Star*net and Geolab. Not hard to do.
Star*Net will import vectors in various formats, including a binary "O" file format used by Ashtech. If GNSS Solutions also uses that same format, that would be easy enough.
CHC have a very low cost post process software. If you are using their receivers anyway it might be the best solution. I think Mark Silver sells it also.
http://chcnav.com/index.php/Home/article/detailPage/parentID/1462/cat_id/1477/artID/767
If you do end up using it i would be interested to see how good it is. I downloaded a demo before but didn't get a chance to have a good look.
Totalsurv, post: 384928, member: 8202 wrote: If you do end up using it i would be interested to see how good it is.
Hmm. That might be worth trying, although what is attractive about GNSS Solutions is that it apparently is long past the beta test phase of development and it can export vectors in a format that Star*Net can import without any tinkering.
My previous employer tried several manistream packages. These are likely not what you are looking for. My preference for static was LGO, followed by TBC. I've beat the dead horse of Topcon enough this week.
thebionicman, post: 384961, member: 8136 wrote: My preference for static was LGO, followed by TBC. I've beat the dead horse of Topcon enough this week.
What I'm looking for is fairly unbuggy software that will, at a minimum, process Static and PPK vectors GPS vectors using current NGS antenna models as well as export the vectors to Star*Net for adjustment in combination with conventional measurements. Any network adjustment functions in the processing software would be more for Q/A purposes than to generate coordinates for use right out of the box.
I'm not sure how the Q/A processing of RTK vectors would best be done, but those ultimately would need to be imported into Stat*Net for error analysis and adjustment.
I know that TBC (and it's clone, SPSO) will export static vectors to the Trimble Data Exchange format, which is a StarNet option. Not super cheap.
I just ran a couple of files through GNSS Solutions, which I haven't used in many years. After using TGO and TBC for a long time, GNSS Solutions seems pretty light on vector manipulation and reporting. Part of that may be lack of familiarity, but there aren't many options jumping out at me.
I was able to easily export the vectors to Ashtech O** format and import them to Star*Net, though.
Mark Mayer, post: 384966, member: 424 wrote: Not super cheap.
Not cheap at all, unless you're comparing to Bernese or GAMIT/GLOBK.
Jim Frame, post: 384967, member: 10 wrote: GNSS Solutions seems pretty light on vector manipulation and reporting. Part of that may be lack of familiarity, but there aren't many options jumping out at me.
I haven't installed GNSS Solutions yet, but aside from time windowing, selectively disabling SVs, and raising elevation masks, what sort of vector manipulation would one need or want?
Mark Mayer, post: 384966, member: 424 wrote: I know that TBC (and it's clone, SPSO) will export static vectors to the Trimble Data Exchange format, which is a StarNet option. Not super cheap.
I believe that you've mentioned before that you also export RTK vectors for adjustment in Star*Net. Do you bring them into TBC or SPSO first for inspection and Q/A review and then export them to Star*Net along with the Static and PPK vectors in the same project?
Kent McMillan, post: 384996, member: 3 wrote: I believe that you've mentioned before that you also export RTK vectors for adjustment in Star*Net. Do you bring them into TBC or SPSO first for inspection and Q/A review and then export them to Star*Net along with the Static and PPK vectors in the same project?
I do not. The vectors, with covariance data, are in the raw data file. I convert the raw data file to the StarNet gps format.
Since going to Oklahoma in 2011 I have used RTK vectors almost exclusively. I became satisfied their that there was more to be gained from duplicating RTK vectors than from tweaking static resolutions.
At the current time I have no direct access to static vector resolution software at all, although I expect to eventually rectify that.
Kent McMillan, post: 384996, member: 3 wrote: I believe that you've mentioned before that you also export RTK vectors for adjustment in Star*Net. Do you bring them into TBC or SPSO first for inspection and Q/A review and then export them to Star*Net along with the Static and PPK vectors in the same project?
I don't either, I export them from the receiver as an NGS g-file and import that into Star*Net.
