AI Assistant
Notifications
Clear all

TS16/Captivate to Carlson/Infinity/ACAD2018 total data flow

4 Posts
4 Users
0 Reactions
517 Views
Seth Bishop PLS
(@seth-bishop-pls)
Posts: 23
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Good Morning from the State of Confusion/Frustration

So like many we have a TS16 with a CS20, running Captivate and Infinity...Well trying to run Infinity....We had coding issues, line work issues ect ect.. Everyones feedback was super helpful. Yet I need some advice as to what we should be using for total data work flow...Infinity is just too difficult and cumbersome to get the linework out of... My thoughts were captivate to Carlson/ACAD2018 and using starnet for adjustments.

We do lots of control work, monitoring, topo/asbuilts....my boss likes to adjust everything. We use GPS,Static, RTK, network RTK, TPS measurements..ect..ect...

We are looking for a more streamlined process...

Any thoughts would be helpful


 
Posted : October 12, 2017 2:51 pm
totalsurv
(@totalsurv)
Posts: 810
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

You could just bring everything into Survnet in Carlson. It would probably take a while to figure out how to manipulate the raw data etc. but if you are not happy with Infinity and already use Carlson it may be the way to go. You will still need a software to post-process GPS data.


 
Posted : October 13, 2017 3:41 am
squowse
(@squowse)
Posts: 998
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I have given up (for now at least) on writing an XSLT stylesheet to convert Leica XML to Starnet in a format I am happy with.
Instead I am writing it in Python. It seems so far to be a lot more intuitive and powerful.


 
Posted : October 15, 2017 5:01 am
james-w-johnston
(@james-w-johnston)
Posts: 18
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Seth,

James from MicroSurvey support here.

If you already like working with STAR*NET you might like to try using MicroSurvey CAD, MicroSurvey inCAD or MicroSurvey embeddedCAD as your CAD solution. You can read the points, linework and traverse file directly from Captivate and all CAD standards can be controlled from the field codes. You can work with all the sensors you mentioned above.

STAR*NET can be used to handle any traverse adjustment requirements.

It's a streamlined process that doesn't require Infinity.


 
Posted : December 3, 2017 3:28 pm