Here is a couple of screen shots from Mobile Mapper office of the data collected
The first is unprocessed (uncorrected data).




The next image is still in Mobile Mapper but of the processed points.



And here is the link to the spreadsheet after I processed and exported the data.

Very sort occupations

Here was the method of collection. I walked to the fire hydrant, turned on the unit, opened up a file and as soon as the hourglass turned into the triangle, I then began collecting data. 10-20 seconds is all.

Fire hydrant, water valve,curb,curb,light pole,small tree (antenna over tree),Medium tree (house blocked all western sky), Large tree (directly underneath), and then the Survey point, Paulk East.
The only point that got a minutes worth of data was Paulk East.

The curb lines were taken at five second intervals and I was a bit too quick around the radius on one or two trips.

The background map is sorta funny looking. Must have to do with the resolution because all in AutoCAD are very smooth lines. I loaded the shape file I created and it looks smooth also. Again, probably something to do with the scale.


Today's test is multiple session (only using the fire hydrant and the survey point)... Several sets with 2 minute occupations, several sets with 3 minute occupations and a few with 5 minute occupations.

I have been reading through the manual but cannot find any recommended time on point so I'm trying to find 'my' comfort zone.

I would place different degrees of freedom on selected points. Hydrants I want as good as I can get in the shortest amount of time, trees I don't expect to ever really get good solid results.

Deral Paulk, PLS OK

Isn't this supposed to be Saturday? What is with us redneck science guys anyway..

Guess it's study on Saturday, perform on Monday.

And...so far I'm very impressed with this little blue unit.

Modified By Deral_ Paulk on 7/24/2004 at 11:09 AM

What is worse for me is that I am online on Saturday reading about your Saturday redneck science experiments...LOL

And hey, Saturday is when I do most of my experimenting.

BTW... excellent work.

As a yellow box user, I must say that I am also imporessed with the MM. Can't wait to try out my new MM CE when it arrives.

Hey Scott,
Are there rednecks in Canada?
By the way, check your email.

Deral,
That does look good. Very reasonable for submeter work. Glad your keeping us up on it.
Modified By Shawn Billings on 7/24/2004 at 12:16 PM

That is the issue with sub-meter positioning..None of the receivers have super computers, they are just tools.

Proved yet again today..

Phil says let it settle down..What he means is let it compute a new position before logging data.


Use RTK and try and walk to a point. You have to stop before you get to it to actually be close.. The unit needs to catch up with you..

It's not instant...

Same with the MM...You need to let the unit get a new fix, BEFORE, you start logging data..Doesn't take but a few seconds, but if you start logging as soon as you get to the point then you might have an outlier that will skew the entire session..

Deral...

Results tomorrow will be much better..Of that I am sure.

Yesterdays processed much better, but still an outlier or two with 2 and 3 minutes of data. DOP's looked good but maybe something else was going on also.

Here is the latest view of the iono...Not good.

Active Iono

Deral

Looks like sunspot 652 is a really bad one possibly. It is the size of Jupiter..Already listed as a M5 with the chance of producing severe X class peaks.


Might be a good day for the super-latudinals to hang out at the pool or catch up on some office work.
Modified By Deral_ Paulk on 7/25/2004 at 6:41 AM

Deral

I was waiting to see if you had "The Experience" on Friday. We did. Did two Opus sessions, while at the same time running a ProMark2 stop and go session. Shawn tried to run through all the points two times, but on the second go round we were losing lock while the signal strength on 6-7 sv's appeared to be peaked out. The first problem observations were near trees - to the North. But, when we lost lock in the big wide open spaces, knew something was up....as in really up. I knew there had been a (near) X-class flare a short time back, but of all things failed to check the sec.noaa.gov site before we left. Friday night, after checking, it was apparant why we had our problems. Also cleared up the reason even the OPUS sessions looked a bit shakey.

GPS work is a whole lot like boating. You don't (shouldn't) take off on a long distance boat trip without checking on the current as well as forecasted weather and water conditions. Same should be with checking for potential ionospheric problems prior to gps, or at least afterwards to look for possible reasons for problem sessions.

We'd have been much better off doing conventional shots on Friday.


Modified By J.D. Billings on 7/25/2004 at 10:23 AM

Dang..You would have thought that two veterans, such as us, of the long baselines would be on top of this..

As they say in the military..Lessons learned.

I dumped two CORS files and processed in TGO and looked at the statistics...Miserable stuff... Comfirmation I suppose of LOP (lack of planning)..

But, on the bright side, the long line experiments led us both to take a look at the space weather. I wonder how many do not and can't figure out why they have less than stellar (pun intended) data at times.

I think this might be especially true in the GIS field. Many have good training with using GPS, but I'm not aware of any training programs that give more than a cursory comment to space weather.

For emergency stuff, then I will not sweat these details, but for GIS gathering where it will go into basemaps then I do sweat the small stuff.

Deral-Student of the School of Hard Knocks...