note: one thing that i HATE right now in Smartworx is that in order to see the curve drawn in the map screen you have to shoot the curve's BC, POC, then EC in a row...you cant skip around like in Carlson. If you try to skip around and come back to the POC and EC the result will be straight lines instead of a smooth curve. I refuse to put this software into real production until this is fixed.
:pissed:
> I refuse to put this software into real production until this is fixed.
You might as well send it back to the vendor. When it comes to DC programs, third party programs give you the most flexibility.
> note: one thing that i HATE right now in Smartworx is that in order to see the curve drawn in the map screen you have to shoot the curve's BC, POC, then EC in a row...you cant skip around like in Carlson. If you try to skip around and come back to the POC and EC the result will be straight lines instead of a smooth curve. I refuse to put this software into real production until this is fixed.
>
> :pissed:
I wish the biggest problem I had with logger software was curves drawing as straight lines! jealous.
From my experience, LisCAD is one of the best field collection and processing systems on the market. But but then I've been using it since the mid 90's. You can draw up to 99 strings per feature at a time (if you can keep track of them) and a plethora of neat tasks to simplify data collection.
The strings in Smartworks are very similar to LisCAD. Smartwork's downfall is the lack of complexity of curves and recalling points and LGO blows for processing mapping data. I simply set my feature codes with strings in attribute one and add the LisCAD modifier codes via free codes. I can see the line work on the data collector, just not the special LisCAD code operations. LisCAD has translator to work with numerous platforms. Once I process the data through LisCAD I output a nice DWG and ASCII file.
Leica and LisTech had a strong working relation with Leica being sole North American distributor until sometime in the 2000's. Now the Leica's parent company owns LisTech. I anxious to see if they incorporate more of the LisTech data collection and mapping features into Viva and the replacement for LGO.
I get it...it's just funny how the swiss can have such brilliant hardware, then drop the ball on the software.
If smartworx dev team incorporated some key features like:
1. Drawing Curves in non - sequential point order.
2. Adding a way to draw rectangles based on 2 points shot; then allow an attribute string that will draw the rectangle (I.e. "RECT2" which will draw a box 2 feet off of the 2 coded points. Use "-" for left of line upstation.)
3. Add a CAD "osnap" pull down menu or toolbar in map view that will allow the user to inverse and draw in the map screen.
Smartworx would dominate the data collection software market and put many other third party developers out of business.
I hope someone from smartworx is reading this....
Although many people may think that users don't need these CAD features in the field software, because they can do the calcs in the office, by allowing the user to do so will make many third party software users happy enough to make the switch to smartworx and in turn will boost hardware sales do to smartworx imaging and scanning capabilities.
LisCAD does 1 & 2. Well at least 1 if you are doing more than a three point line. Like I said, it will be interesting to see if Leica integrate LisCAD into their operations.
two points do not define a rectangle. It takes at least one other parameter such as length or azimuth of a line. And that may still leave ambiguities.
> two points do not define a rectangle. It takes at least one other parameter such as length or azimuth of a line. And that may still leave ambiguities.
?Huh? Last i checked it takes two points to make a straight line...
Hence, The two points will define the length and azimuth/direction and the command "RECT#" would tell the software the distance left or right of the line to square up to...
Carlson does it this way and it works perfectly.
I get it now. I hadn't figured out the relationship of the 2 ft in your example. You are entering enough parameters.