Stake out error
- Thread starter Adam
- Start date
Sean Joyce
Well-Known Member
I had this error a few days ago on one previously staked point I was checking into but not collecting, chalked it up to possibly incorrectly going between State Plane and localized coordinate pages for stakeout and collection of a staked point and maybe confusing the L.S.
It staked the point correctly but then displayed the error message. Nothing else happened after that.
One thing I appreciate about this equipment are built in safeguards that prevent the operator from doing what it perceives as the wrong thing to do.
Don't know if that was the case in this instance.
I have found that there are glitches from time to time such as sound issues, sometimes after updates, sometimes not.
My L.S. sound is fine now.
Another example, leveling seems sensitive to temperature changes and carrying the unit going from horizontal to vertical and so I adjust the level offsets multiple times during the day.
It staked the point correctly but then displayed the error message. Nothing else happened after that.
One thing I appreciate about this equipment are built in safeguards that prevent the operator from doing what it perceives as the wrong thing to do.
Don't know if that was the case in this instance.
I have found that there are glitches from time to time such as sound issues, sometimes after updates, sometimes not.
My L.S. sound is fine now.
Another example, leveling seems sensitive to temperature changes and carrying the unit going from horizontal to vertical and so I adjust the level offsets multiple times during the day.
Mikhail Drakin
Developer
Adam, Sean, please upload the projects where you got these "invalid coordinate" errors with "Send Project to Support" command in Project screen (if they are not secret, of course), and write here names of points you were staking. Thank you.
Sean Joyce
Well-Known Member
Mikhail, sorry I cannot remember the point I was on. After that passing glitch I had no other problems.
If it happens again I will take note.
If it happens again I will take note.
Mikhail, I am sending it now. The point I was checking in on was LS1. On another issue, I am working on a project and imported a drawing file. It is large but not gigantic. The LS will read about 20000 objects then crash. I am going to send it along to. I have a real need to be able to fit large drawings into my LS, but I dont need to have extra points created taking up even more memory. Basically I need to see the lines and be able to pick segments and end points only when needed. I dont understand the concept of creating points automatically at every end point. Some drawings I get are from others so I cant control what I am putting in the LS.
Lines are defined in the database as a connection between points so to have the lines, the points must be created. When importing dwg files there are options to select which layers are imported. Have you tried doing this so the you only import the linework that you need? The other option would be to delete lines that you don't need with your CAD software before importing it.
Matt that's a lot of work. The same drawings will load into Survce no problem. I have loaded huge drawings into SurvCe. I dont want to delete or spend time prepping in the office. I need to be able to load up a drawing as provided to me and work from it. I need all layers in the field.
Mikhail Drakin
Developer
Crash after importing the 20000 objects was caused by math error inside, not data volume. Working with such data volumes is painfully slow, but possible. The crash will be fixed in the next build.
Error message staking a surveyed points also will be fixed in the next build.
Error message staking a surveyed points also will be fixed in the next build.
Mikhail, is there still more that can be done to reduce the loading time for projects with many points?
Mikhail Drakin
Developer
Matt, sure there is, but it requires significant time (weeks/months).
Is it possible to import a cad file as a background map? Sometimes, really most of the time I just want to see the lines. One thing I try to do on each job is load up a drawing and walk thru with my reciever in hand and check over my survey drawing and what not. Quality Control. Some of these jobs have a lot going on. Some jobs are construction staking jobs. Construction jobs are a little different, there is a need to stake a line from the drawing, say a contour line or back curb, whatever it is, for rough grading. When the job progresses most all the stake out points are computed in the office and reviewed before staking, so at this point I only need to see the lines again. So a background type map would work. And sometimes I dont want my crew to be able to select any linework. Depends on who it is. A newbie, nope. My top hand, yes. The LS spends a lot of time loading objects that I will never need. Just some thoughts.
Personally, I like construction staking from CAD, if I have carefully checked the drawing. Too many times the designer doesn't know how to use CAD and the line work doesn't match the dimensions or endpoints don't meet or perpendicular intersections aren't.
Once I get that checked out, then I'll take the CAD file in the field, but even then I prefer to only have the line work I intend to stake. Too easy in the field to grab the wrong line while staking a complex site. I prefer to simplify the drawing as much as possible.
Ultimately, we do need to feed more speed to the database. But I haven't encountered much problem from the long load time because I tend to thin the drawing or points list in the office. I know that isn't how everyone works.
Eventually it would be good to have colors attached to codes instead of Pages too, then the LS screen would resemble cad more and make distinguishing lines easier.
Once I get that checked out, then I'll take the CAD file in the field, but even then I prefer to only have the line work I intend to stake. Too easy in the field to grab the wrong line while staking a complex site. I prefer to simplify the drawing as much as possible.
Ultimately, we do need to feed more speed to the database. But I haven't encountered much problem from the long load time because I tend to thin the drawing or points list in the office. I know that isn't how everyone works.
Eventually it would be good to have colors attached to codes instead of Pages too, then the LS screen would resemble cad more and make distinguishing lines easier.
I'm not aware of any method or program to convert a dwg file to a sqlitedb.
You can open a DWG file in Global Mapper then save it as a SQLitedb file. I have done it a couple of times.
I will check this out Matt. How did it work out?
It worked well. I don't do it often. I don't know that I would do it on a very large site. The ones I have done it on were only about 10 acres. On sites that size it works well. Background maps can slow it down if they are very large.
Mattew, if you mean J-Field, background maps should not slow it down. If it so then we need an example of the background map to improve performance.
I . Just sent another project to support. It was a smaller drawing and it gave an error when loading it up. Previous run of app finished unexpectantly, crash dump. It reads 6000 objects. Then it crashed to the Windows screen.
Mikhail Drakin
Developer
Adam, this is the same bug. It has been fixed, but only in test version. We will update the release version (1.11.8) also.
Thanks Mikhail.