Trouble with Rinex Files

Send me an email.

After I respond to you, you can reply to me with an attachment of your RINEX file.

Paul in PA

Email sent! Thanks for the help!

Josh, Start Out By Updating Your RINEX Converter

I used a version of teqc to edit your file, teqc does not like the data for the start time but got past it. Start time is 20:06:30

I then removed the Glonass, seleced only C1, L1, P2, L2 and parsed the file to 30 seconds.

This allowed me to find other RINEX problems, first my teqc edited RINEX stopped at 20:13:00. That is only 6.5 minutes. OPOUS-RS would hve more or less done the same thing, so your error message is correct.

What I found in your original file was;
good RINEX to 20:13:15
next observation set was 2:20:40
next observation set was 2:20:41
next observation set was 20:13:40

What I did was to remove the 2 errant 1 second observation sets from your original RINEX file and sent it through teqc again. It stopped at 20:23:30, similar problem and on the third attempt it stopped at 20:33:30.

I now have a 30 second RINEX file with no observation sets at 20:13:30, 20:24:00 and 20:34:00. I am sending that to OPUS-RS using "none" antenna at zero height. I believe it should accept it, if not I will resubmit adding the missing times with no satellite data. If that does not work I my have to invent the missing data. The last three gap observations also can be submitted as under 15 minute files.

Paul in PA

Josh, Start Out By Updating Your RINEX Converter

Man if you can get this to work I will owe you HUGE!! I am not very familiar with editing of rinex files as I have never had any problems with them before and don't have access to teqc. This is newer unit that I have never used as a static receiver only as RTK. If it works would you be willing to edit 4 additional files? I would be more than willing to pay you through a paypal account your time.

Again thank you so much! You may have saved me in more ways than one. My wife kept telling me this trip was not worth the money and has been as stressed as I have been because we put up money to go out there just so I could get additional work down the road from this client. If I can't get this to work I will lose the client and the money I already don't have....

Josh, Start Out By Updating Your RINEX Converter

If you are willing would it help if I sent the non converted rinex files straight from the receiver?

Josh, Start Out By Updating Your RINEX Converter

Verify your GPS receiver model and antenna type. Is the antenna on the OPUS list?

Does OPUS accept your raw receiver data? If so try that.

The editing I did on your original REINEX was done in "NotePad" since it is merely a text file. You have to use "Open With" the first time in Windows, after that ny file ending in .17o should open in WordPad. Come January it will be necessary to use Open With again to specify .15o file extension.

Even if you do not want to edit use NotePad to get an idea what your RINEX should look like.

Paul in PA

Josh, Start Out By Updating Your RINEX Converter

I will have to check when I get home to verify the antenna type but I don't think its on there. Its a Geomax Zenith 10 receiver if that helps. I tried uploading the *.dat file but it got kicked back by OPUS.

Here Is Your Solution

Below is your results. I will email you the file I submitted, but will change the file name to FARM312u.14O. I selected the hour alpha character from memory and missed it by one character. Anytime I edit a RINEX file I try to use the same letters used in default RINEX files, the letters a to x are used after the day of year number "312" for your file and apply to the UTC hour in which the file begins. If I am splitting a file for OPUS-RS I may have 2 files starting in the same hour, so I add something to the later files. Receivers usually use a number designator instead of a letter, 1 for the first file of the day and so on. If there are more than nine files the last numeral of the day of year is overwritten. Once OPUS receives your file, teqc checks it and renames it with the correct alpha character. If you submit two files 1 and 2 that are in the same hour OPUS-RS will not accept the second one as the renamed alpha character file is still in the processing queue.

Send me your other files. Anything that you think you owe me, submit to Wendell's fund to maintain this board.

Paul in PA

FILE: FARM312v.14O OP1415808854118

1009 WARNING! No antenna type was selected. No antenna offsets or
1009 pattern will be applied. Coordinates with reduced accuracy
1009 will be returned for the antenna phase center.
1009
1008 NOTE: Antenna offsets supplied by the user were zero. Coordinates
1008 returned will be for the antenna reference point (ARP).
1008
NGS OPUS-RS SOLUTION REPORT
========================

All computed coordinate accuracies are listed as 1-sigma RMS values.
For additional information: http://www.ngs.noaa.gov/OPUS/about.jsp#accuracy

USER: lplopresti@enter.net DATE: November 12, 2014
RINEX FILE: farm312u.14o TIME: 16:17:42 UTC

SOFTWARE: rsgps 1.37 RS92.prl 1.99.2 START: 2014/11/08 20:06:30
EPHEMERIS: igr18176.eph [rapid] STOP: 2014/11/08 20:41:00
NAV FILE: brdc3120.14n OBS USED: 2037 / 2240 : 91%
ANT NAME: NONE QUALITY IND. 3.08/ 18.96
ARP HEIGHT: 0.000 NORMALIZED RMS: 0.411

REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2014.85438)

X: -383970.244(m) 0.008(m) -383971.051(m) 0.008(m)
Y: -5146382.384(m) 0.075(m) -5146380.977(m) 0.075(m)
Z: 3736038.625(m) 0.058(m) 3736038.491(m) 0.058(m)

LAT: 36 5 7.25742 0.010(m) 36 5 7.27957 0.010(m)
E LON: 265 43 59.09729 0.007(m) 265 43 59.06094 0.007(m)
W LON: 94 16 0.90271 0.007(m) 94 16 0.93906 0.007(m)
EL HGT: 321.624(m) 0.094(m) 320.460(m) 0.094(m)
ORTHO HGT: 349.768(m) 0.096(m) [NAVD88 (Computed using GEOID12A)]

UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 15) SPC (0301 AR N)
Northing (Y) [meters] 3994157.840 196725.788
Easting (X) [meters] 385936.036 195850.157
Convergence [degrees] -0.74628184 -1.31911727
Point Scale 0.99976031 0.99997409
Combined Factor 0.99970985 0.99992362

US NATIONAL GRID DESIGNATOR: 15SUV8593694157(NAD 83)

BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DN6071 MOA2 MODOT ANDERSON CORS ARP N364103.393 W0942618.245 68221.2
DM3513 MOCS MODOT CASSVILLE CORS ARP N363848.209 W0935420.355 70229.1
DI8422 SAL6 SALLISAW 6 CORS ARP N352202.191 W0944858.797 93910.0
DE7172 OKMU MUSKOGEE CORS ARP N354300.062 W0952405.820 110303.9
DH7105 ARHR HARRISON CORS ARP N361103.236 W0930148.726 111859.8
DL6014 MOCA MODOT CARTHAGE CORS ARP N371039.166 W0942127.243 121476.6
DF7475 OKHV HEAVENER CORS ARP N345447.379 W0943705.092 133902.1

NEAREST NGS PUBLISHED CONTROL POINT
GG0646 FAYETTEVILLE OZARKS ELEC MAST N360349.002 W0941225.704 5897.7

This position and the above vector components were computed without any
knowledge by the National Geodetic Survey regarding the equipment or
field operating procedures used.

If Paul cannot get them to work, where at in Arkansas? Shoot me an email if you have to reobserve. I am much closer

Josh, Start Out By Updating Your RINEX Converter

Sir, I am impressed. You certainly spin some magic.

I was recently told about NotePad++ which I have found to be a bit better than NotePad. It provides line numbers and can open big files quickly. NotePad++

I Don't Consider RINEX Files As Large

My Win 7 would not allow me to install WordPd++. Will try downloading other versions.

Paul in PA

Jimmy they are just outside of Fayetteville. It looks like Paul is going to be able to help me but I may have some more in Arkansas. Email your contact info and maybe we can do some work together. It would save me the drive. I really underestimated the drive and after these files not initially working I was completely stressed that I would have to do them again or lose the potential client.

Josh, Start Out By Updating Your RINEX Converter

He definitely has spun some magic! I can't express how relieved I am for his assistance!!

Josh,

Shoot me an email at jcsurvey@netzero.net

I do not see your email address. I am about 45 minutes from the I40 bridge in Memphis.

I am sure we can work something out.

Glad Paul was able to help you. He is great. He has helped me in the past. This is a great community we have here

Second Solution Good

Josh,

You have multiple problems. The two year old observations were sporadic throughout the file. In a fair number of instances it was only one second of observations. In at least one case two seconds of older observations were included and upon removal your observation progression was intact. In other cases the older data supplanted current data.

After editing I submitted to OPUS-RS and lo and behold OPUS-RS changed the day of year number from 312 to 311. 311 is correct for Friday November 7, 2014 which is the date for each observation. It appears your receiver used a wrong day of year.

My first suggestion is to totally wipe the receiver memory and observe something local with this receiver to see if that solves any problem.

I will properly rename the file I submitted and email it back to you. I believe subsequent file editing will go smoother.

Paul in PA

FILE: FARM3122t.14O OP1415824190459

1009 WARNING! No antenna type was selected. No antenna offsets or
1009 pattern will be applied. Coordinates with reduced accuracy
1009 will be returned for the antenna phase center.
1009
1008 NOTE: Antenna offsets supplied by the user were zero. Coordinates
1008 returned will be for the antenna reference point (ARP).
1008
NGS OPUS-RS SOLUTION REPORT
========================

All computed coordinate accuracies are listed as 1-sigma RMS values.
For additional information: http://www.ngs.noaa.gov/OPUS/about.jsp#accuracy

USER: lplopresti@enter.net DATE: November 12, 2014
RINEX FILE: farm311t.14o TIME: 20:31:23 UTC

SOFTWARE: rsgps 1.37 RS91.prl 1.99.2 START: 2014/11/07 19:06:30
EPHEMERIS: igr18175.eph [rapid] STOP: 2014/11/07 19:44:00
NAV FILE: brdc3110.14n OBS USED: 2772 / 3303 : 84%
ANT NAME: NONE QUALITY IND. 18.53/ 9.81
ARP HEIGHT: 0.000 NORMALIZED RMS: 0.298

REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2014.85153)

X: 500198.765(m) 0.008(m) 500197.970(m) 0.008(m)
Y: -5275586.027(m) 0.021(m) -5275584.549(m) 0.021(m)
Z: 3538048.094(m) 0.016(m) 3538047.958(m) 0.016(m)

LAT: 33 54 25.37253 0.006(m) 33 54 25.39687 0.006(m)
E LON: 275 24 58.47709 0.007(m) 275 24 58.45172 0.007(m)
W LON: 84 35 1.52291 0.007(m) 84 35 1.54828 0.007(m)
EL HGT: 275.886(m) 0.026(m) 274.527(m) 0.026(m)
ORTHO HGT: 305.386(m) 0.030(m) [NAVD88 (Computed using GEOID12A)]

UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 16) SPC (1002 GA W)
Northing (Y) [meters] 3754478.447 433272.650
Easting (X) [meters] 723402.817 661429.065
Convergence [degrees] 1.34845304 -0.23267519
Point Scale 1.00021529 0.99991833
Combined Factor 1.00017197 0.99987503

US NATIONAL GRID DESIGNATOR: 16SGC2340254478(NAD 83)

BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DE9144 ZTL4 ATLANTA WAAS 4 CORS ARP N332246.854 W0841748.189 64271.5
DM7831 GABN EGPS BRASELTON CORS ARP N340807.083 W0834638.499 78668.5
DM3491 ALCN CENTRE HIGH SCH CORS ARP N340946.956 W0853931.020 103243.6
DM4625 ALHC PLEASANT GRVE SCH CORS ARP N333125.423 W0853805.472 106303.4
DH4146 GABR BLUE RIDGE CORS ARP N345151.920 W0841937.609 108797.6
DO2378 P806 THEROCKMSTGA2012 CORS ARP N325747.899 W0841333.030 109839.4
DH3580 GAAT ATHENS CORS ARP N335708.800 W0831930.965 116471.9
DM3485 ALAS CALHOUN CO AD BLG CORS ARP N334001.184 W0854950.462 118515.5
DM5373 ALLA COUNTY ENG OFFICE CORS ARP N325502.640 W0852401.777 133491.2

NEAREST NGS PUBLISHED CONTROL POINT
DG3187 BV 033 206 GAHD 1973 N335419.308 W0843622.918 2097.3

This position and the above vector components were computed without any
knowledge by the National Geodetic Survey regarding the equipment or
field operating procedures used.

Two More Processed

Two aborted for other reasons.

Paul in PA

Second Solution Good

I am wiping the receiver and starting over tonight. I am going to run a few test observations tomorrow and hope for better results. If not I am guessing I have a bad receiver and am going to go back to the dealer.

Again thank you so much for your help and I am eternally in your debt.

Need Help Or Opinion On Odd Glonass, R-37

I fixed and got 5 out of 6 solutions for Josh.

The last file is perplexing. It is listing one out of 9 Glonass as R-37. None of the other Glonass include a dash between the R and their numbers. I am using WINteqc build 3.3.2014 and it cannot get past or edit that data out.

I tried to correct it by using "find and replace" in WordPad. I changed all the R-37 to R37, but teqc still did not like it. I did not notice R-37 or R37 in any other file. BTW Josh had an OK file just before and just after this file.

Has anyone seen this before? Has anyone fixed it?

One of the earlier files that aborted was for Tuesday 11/11 and went 1 minute past UTC midnite. It processed at 11/12 UTC 23:39:11. I'm going to resubmit that later to see if it trimmed that last minute off. It used 97% of 21 minutes of observations.

I've learned a few things today, such as OPUS-RS will give a solution even if there are epochs with no data, I mean 3 diverse epochs missing in a short file.

Paul in PA

Brute Force Editing Fixed The Last RINEX File

I had to manually remove all R satellites from the observation line and remove the observations. About halfway through the file R-37 disappeared and teqc would work.

Just to let you know if half a file (in time) is GPS only and 30 second intervals and the second half includes Glonass and 5 second data, teqc still does its job and will parse the last part of the file.

Paul in PA