Tag: DGPS

  • Nationwide Differential GPS Shutdown Proposed, Comments Sought

    oceantides
    Twenty-two NDGPS sites that serve coastal areas would remain operational under the proposal.

    An Aug. 18 Federal Register notice proposes shutting down the Nationwide Differential Global Positioning System (NDGPS) in January 2016 because of a decline in its use, except for sites in coastal areas.

    The notice, issued by the U.S. Coast Guard (USCG), Transportation Department (DOT) and Corps of Engineers (USACE), reads:

    The Nationwide Differential Global Positioning System (NDGPS) service augments GPS by providing increased accuracy and integrity using land-based reference stations to transmit correction messages over radiobeacon frequencies. The service was implemented through agreements between multiple federal agencies including the  USCG, DOT, and Army Corps of Engineers, as well as several states and scientific organizations, all cooperating to provide the combined national DGPS utility.

    However, a number of factors have contributed to declining use of NDGPS and, based on an assessment by the Department of Homeland Security, DOT and USACE. DHS, DOT and USACE are proposing to shut down and decommission 62 DGPS sites, which will leave 22 operational sites available to users in coastal areas.

    A DGPS reference station antenna.
    A DGPS reference station antenna.

    Contributing factors cited in the decision are:

    • USCG changes in policy to allow aids to navigation (ATON) to be positioned with a GPS receiver using Receiver Autonomous Integrity Monitoring (RAIM), which assesses the integrity of a GPS signal within the receiver;
    • increased use of Wide Area Augmentation System (WAAS) in commercial maritime applications, which uses ground-based reference stations and satellite communications to improve accuracy;
    • limited availability of consumer-grade NDGPS receivers;
    • no NDGPS mandatory carriage requirement on any vessel within U.S. territorial waters;
    • the May 1, 2000 Presidential Directive discontinuing GPS Selective Availability
    • continuing GPS modernization; and
    • the DOT Federal Railroad Administration’s determination that NDGPS is not a requirement for the successful implementation of Positive Train Control (PTC), which provides the railway system the capability to positively enforce movement authorities along railroad systems.

    US_NDGPS_Coverage_APR29_SmIn April 2013, announced that DHS and DOT were in the process of analyzing the need for NDGPS. “The response to the 2013 notice was limited, but the responses received were well informed on the NDGPS system, its use, and current and potential applications,” the notice reads. “While a limited number of responders found the broadcast of corrections to be beneficial, no respondents reported the discontinuance of DGPS broadcast to be detrimental or harmful. Ship pilots in particular noted that DGPS can be critical in confined waterways for precise ship-handling maneuvers.”

    Public comments on the proposed shutdown and decommissioning of 62 DGPS sites are being accepted until Nov. 16. Termination of the NDGPS broadcast at these sites is planned to occur on Jan. 15, 2016.

    Full details on how to submit public comments can be found on the Federal Register page.

  • Webinar Follow-up Q&A: SBAS, DGPS or Post-Processing? Which Should You Use?

    Last week, I conducted a webinar along with Dr. Michael Whitehead titled “SBAS, DGPS or Post-processing? Which Should You Use?” It was one of the best webinars I’ve conducted to date. More than 600 people registered. We barely squeezed it into 65 minutes and could have kept going for the better part of two to three hours, given the subject matter to cover and the number of questions we received before and during the webinar. Thank you for attending, if you did. If you weren’t able to you, can download it by registering here. After registering, you’ll be provided a link to download it.

    I knew that only having 65 minutes would be a serious issue for the webinar because the discussion could take many worthwhile tangents. And it was. But alas, we stuck to the presentation agenda, stayed on schedule, and were able to address several audience questions.

    We had a lot of questions before and during the webinar. As customary, I’d like to address some of those as well as present the poll results here. First, the poll questions and results with accompanying pie charts to illustrate the results.

     

    Poll #1: For those of you who use post-processing, what are the reasons you use it?

    Total votes: 117

    Gakstatter comment: This is an interesting spread with no clear dominating reason. Based on data I’ve seen and data we collected, I’m not convinced that post-processing is more accurate. If it is, is it worth the extra 10%, 20%, or ??% accuracy? I understand the votes for more reliable corrections. There’s something to say for reverse processing (forwards and backwards).

     

    Poll #2: For those of you using post-processing, from where do you access GPS base station data?

    Total votes: 129

     

    Gakstatter comment: These answers don’t surprise me. National and regional CORS have become very prolific in the past 10 years.

     

    Poll #3: For those of you who use real-time DGPS/SBAS, what is the reason you use it?

     

    Total votes: 110

    Gakstatter comment: These answers surprised me a little. I thought more people would vote for “less complicated.” Does that percentage of users really need corrected coordinates in the field? Why? E-mail me a quick answer if you have a chance.

    Poll #4: For those of you using real-time DGPS/SBAS, from where do you access DGPS/SBAS corrections?

    Total votes: 129

    Gakstatter comment: This answer doesn’t surprise me at all. I suspect RTK networks will increase due to their continued proliferation and different levels of accuracy offered.

    Poll #5: When I purchase GPS/GNSS equipment in the future, I will likely select equipment that utilizes the following correction method (select all that apply):

    Total votes: 144

    Gakstatter comment: This was the only multi-answer poll. People could select more than one answer. These answers were surprisingly close. That surprised me. It didn’t surprise me that SBAS was the leader. It surprised me that post-processing is still as predominant as it is. If you have a chance, e-mail me a quick explanation as to why you will use post-processing in the future.

    Before diving into some audience questions, I’d like to clarify the slide illustrating the post-processing plot shown below.

    During the webinar, we were discussing PPP (precise-point positioning) when this slide was displayed. This data was not corrected via PPP, but rather post-processing the pseudorange data, which is the equivalent of L1 SBAS and L1 DGPS. The point was to show how SBAS/DGPS accuracy compares to post-processing. In the real world, you won’t post-process 24 hours of data. Some of you will post-process only a few minutes of data per session in cases where you need to turn off the receiver and travel between points. In other cases, users will keep the receiver tracking between points, allowing reverse processing to work more effectively.

    On to the Questions

     

    Question #1: Will there ever be a way in which the position of a rover can become fixed by using two fixed base stations?

    Gakstatter comment: SBAS does this already. SBAS’s consist of a number of base stations within the coverage area (e.g., WAAS has 38). Data from many base stations is used to compute the correction information sent to an SBAS-enabled GPS receiver.

    I’m assuming your reasoning is to improve position integrity.

    Another method of accomplishing this is by post-processing against more than one base station or switching between DGPS beacon stations. If they differ significantly, then you might want to compare against a third base station.
    Question #2: At what point in time will the strength of the GPS signal be increased? To what strength will this occur? 500 times more powerful? What improvements in signal reception will be experienced? Indoor my house reception?
    Gakstatter comment: The GPS broadcast strength is increased with new GPS satellite model. For example, the current Block IIF satellite broadcasts the new L5 signal about four times stronger than L2C. While no one can be sure yet as to how much this will improve indoor positioning, there will be some marginal improvement in conditions where GPS doesn’t operate very well today. Also helping will be the improved code and error-correcting techniques that should make operating in difficult conditions a bit better, especially where there are a mixture of satellites with strong and weak signals.
    Also, it raises the issue of a viable L5 single frequency receiver, which should outperform the L1 C/A single frequency receivers of today.
    Question #3: NAD83, WGS84, ITRF differences, how to make the best choice?
    &nbsp
    ;
    Gakstatter Comment: I don’t think there is an incorrect choice, except maybe that NAD83 is a 2D system and will eventually give way to a 3D system, but that won’t happen in the U.S. for many years.
    Otherwise, it’s a question of matching disparate data sets. Probably the #1 question I hear from users is “why doesn’t my GPS data line up with my basemap?” The answer is almost always a difference in datums. Many papers have been written on this. Click here for a good PowerPoint presentation created by Dave Doyle of the National Geodetic Survey.
    Question #4: Are there any open source post-processing software programs available?
    Gakstatter Comment: Mike suggested looking here….http://gpspp.sakura.ne.jp/rtklib/rtklib.htm
    Question #5: If a person uses real-time correction satellites, is there a need to post-process?
    Gakstatter Comment: It’s rare that someone would do both, but not out of the question. For example, one might rely primarily on real-time corrections and record raw data for post-processing in case there is a problem receiving the real-time corrections. The opposite is true, too. One might rely primarily on post-processing and use real-time corrections as a back-up in case there is a problem with post-processing.
    Caveat emptor: There are probably datum differences between the sources of real-time and post-processing corrections. This needs to be reconciled when combining data that has used the two sources.
    Question #6: Is it possible to post-process data without using a DGPS?
    Gakstatter Comment: Yes, all that is required for post-processing is the ability to record raw observation data.
    Question #7: Are there geographic areas in the U.S. that are not covered by NGS CORS stations?
    Gakstatter Comment: No, not for pseudorange (L1) differential corrections. The distance to the base station will vary depending on where you are located and thus may affect your accuracy to some degree, but the density of CORS in the U.S. is such that you will never be more than a couple of hundred kilometers from a base station and likely much closer.
    A side note: Back in the mid-1990s, I remember experimenting with post-processing software we were developing. At that time, I tried post-processing data collected in Oregon with a base station located in Atlanta, Georgia. This was a 2,500 km baseline. It produced a result, albeit not one I would necessarily trust. The only limitation is that the two units must track common GPS satellites. With that length of baseline, it’s possible that only half of the satellites tracked may be in common.
    Question #8: What is the ideal distance range from a CORS station to your site to use post-processing?
    Gakstatter Comment: Ideally, as close as possible. The further you are from a base station, the more potential error will be introduced due to atmospheric differences between the two locations. As stated above, the density of CORS (at least in the U.S. and many parts of the world) are such that the nearest base station is quite near and likely no more than a couple of hundred kilometers away.
    Question #9: What is the trade-off between short observation time (couple of minutes) to position accuracy when using post-processing?
    Gakstatter Comment: Ok, remember we are talking about pseudorange corrections (as opposed to carrier phase). Given that the receiver has been tracking satellites for a period of time (let’s say two minutes), the observation times only need to be a few seconds for each feature to be mapped.
    For example, if you are mapping utility poles and don’t turn off the receiver between poles, you only need a few seconds (5-10 seconds) of data for each pole and average it for the final coordinate. Think about if you’re mapping a road centerline. You’ll likely record data while moving, so each second you are recording a new position.
    Question #10: What about the vertical correction? I see in the slide an antenna carried in a backpack. Is the antenna placed at ground level for point? Is there a constant correction required?
    Gakstatter Comment: Vertical accuracy is typically worse than horizontal accuracy by a factor of 1.5-2.0 due to the inferior satellite geometry, especially in areas of hilly terrain and/or trees/buildings where the horizon is blocked. Good geometry for vertical positioning requires tracking a number of GPS satellites that are low on the horizon.
    Question #11: What is the future of DGPS? I heard Coast Guard beacons were going away?
    Gakstatter Comment: The beacon stations operated by the U.S. Coast Guard are not in jeopardy and never have been. Neither have the marine beacons in the other 40+ countries that broadcast GPS corrections. However, the U.S. Department of Transportation operates 29 inland stations in the U.S. which have faced budget challenges the past few years. In April 2008, the U.S. DOT issued a policy decision to continue operating the 29 inland sites. Construction of seven sites remains that would allow the Nationwide DGPS to reach Initial Operating Capability (IOC), which would provide coverage to 99% of the continental U.S. No budget has been approved for the construction of those seven sites.

     

    Question #12: Can you briefly explain the difference between DGPS & RTK?
    Gakstatter comment: Here are a couple of good websites that explain each of these techniques. Essentially, DGPS is a real-time GPS positioning technique accurate to about 30 centimeters at the very best. RTK is a real-time GPS positioning technique accurate to about 1 centimeter.
    Question #13: How much time do you need to get the position from the base station for real-time DGPS?
    Gakstatter comment: Assuming both receivers are already tracking satellites, your receivers will begin using the base-station corrections as soon as the data link is made between the two.
    Question #14: Can you comment on advantages (if any) of using corrections from a network RTK service for DGPS corrections. Any advantages on eliminating base separation?
    Gakstatter comment: I’ve heard that DGPS corrections are optimized within an RTK Network. However, I need to research this a bit further to better understand the true advantages, if any.
    Whitehead Comment: A virtual base station (VBS) solution could be formed using the network. Thus differential GPS could exhibit the same advantages using such a network that RTK does (cancellation of atmosphere errors). The software would have to support this.
    Note though that if close to one of the Reference Stations in the network, it is probably best to just use the nearest Reference station as this will best cancel the atmosphere errors. When in the middle the network, the VBS solution would use surrounding reference stations to provide a good approximation of atmospheric errors and then output a correction that looked like it originated from a reference station (virtual station ) near to the users receiver.
    Question #15: What is up with PRN 135? Still on station?
    Gakstatter comment: Communication has be re-established with WAAS PRN 135 and is being tested by its owner, Intelsat, as well as the Federal Aviation Administration (FAA). See a detailed article by clicking here. The latest information I heard is that it’s currently at 93°W longitude undergoing testing. If the testing is successful, it will be re-located back to 133°W longitude and brought back into WAAS service. A timeline has not been published, but I’m guessing within the next 30-60 days.
    Question #16: We used to hear that your point accuracy degraded as the distance from the base station increased. One reason we used to post process. Is this still a factor?
    Gakstatter Comment: Due to advancements in GPS technology, it’s not as much of an issue as it used to be. I think this is illustrated in the results we achieved in our 24 hr test data.
    Ten years ago, it would be hard to find a GPS L1 receiver that would receive DGPS corrections from a beacon station 184km away and still achieve sub-meter horizontal accuracy at the 95% confidence level.
    I’m not saying the distance is negligible. There still the issue of tropospheric, ionospheric and satellite orbit errors as you move farther away from the base station. But, it’s certainly less of a factor than it was before.
    Whitehead Comment:
    Question #17: If we use WAAS correction, does it really help to try to use a post-processing type of software afterward? So far we just use WAAS correction.
    Gakstatter Comment: One of the reasons we collected data using several sources of real-time corrections and also showed the results of post-processing was to illustrate the differences between the two.
    If you follow proper procedures, there’s no reason to think that accuracy obtained using WAAS will differ significantly from accuracy obtained using post-processing. This is assuming that you’re using a single-frequency GPS receiver and post-processing using pseudorange corrections and not carrier-phase processing. Some receivers like the Trimble GeoXH are actually dual-frequency receivers and so data from it will likely surpass the accuracy of WAAS if you’re using its dual-frequency antenna and equivalent post-processing software.
    By proper WAAS procedures, I mean letting it track for five minutes upon initial start-up to allow it to download a current ionospheric map.
    Question #18: Does SBAS use 1 receiver and no base station? Expensive?
    Gakstatter Comment: SBAS uses 1 receiver and a lot of base stations. You just don’t have to pay for the SBAS base stations (or to use them.) The signal, like GPS, is provided free of charge.
    SBAS consists of a network of base stations (WAAS has 38) and communications satellites that broadcast corrections to users on the ground (or aviation users in the air).
    Question #19: How far north in Alberta is WAAS coverage available and useful?
    Gakstatter Comment: The primary concern would be visibility of the WAAS GEO satellite that broadcasts the correction data. Following is a map that illustrates the coverage. The contour lines are degrees above the horizon for which the two WAAS GEO satellites are visible.
    Solid line = PRN 138, Dashed line = PRN 133
    Question #20: Do you have any comments about CDGPS in Canada/US?
    Gakstatter comment: Sadly, the CDGPS service is being decommissioned March 31. You can read about it here. 
    Question #21: I am hearing from my state specialists (NRCS) regarding the LightSquared issue. We are advising working through the PNT ExComm and our cooperating partners.
    Gakstatter comment: This is a potentially serious issue for GPS users. Click here for the latest news as of February 1.
    Question #22: Where do you find the DGPS beacon station list and what is available to you?
    Gakstatter comment: I’m not sure if this is 100% complete, but it’s the most complete list I’ve seen. Click here.
    Question #23: Are most mapping-grade GPS receivers (for example Trimble GeoXh) equipped off the shelf to receive beacon signals?
    Gakstatter comment: Some receivers are equipped off-the-shelf, others are not (such as the GeoXH) and require additional hardware.
    Question #24: In which areas is it possible to use corrections from OmniSTAR?
    Gakstatter comment: Click here to view worldwide maps of OmniSTAR coverage.
    Question #25: Was the Garmin set to WAAS?
    Gakstatter comment: Yes, during the 24-hour data collection session, the Garmin unit was receiving WAAS 100% of the time as far as we could tell. The purpose of the 24-hour test period was to able to randomly sample data during that period to arrive at the accuracy statistics we presented. I randomly sampled the dataset several time
    s (averaging 10 seconds worth of positions 200 times) and the results were consistent with what we presented.
    Question #26: How does post processing account for ionosphere or troposphere errors if receiver is geographically far away from the base station? If not, does DGPS and WAAS provide better accuracy and integrity?
    Whitehead comment: Post Processing using a CORS station would take the nearest station and do differential GPS which cancels common errors in ionosphere and troposphere (ionosphere and troposphere are both temporally and spatially correlated) so if the CORS station is close, there will be good cancellation. If the receiver is far, the algorithms could use a troposphere model to account for the differential troposphere (as was done in the Presentation for BeaconT) and this would probably cancel troposphere so that remaining errors were sub-decimeter level. Differential Ionosphere errors could also be easily modeled with good results. It is likely that the performance could be made to easily surpass SBAS.
    DGPS would suffer from the same effects as does post processing, and maybe even more so since a model of differential atmosphere errors is rarely used. SBAS will likely provide better accuracy in situations where you are far from a base station.
    Question #27: What is Beacon T?
    Gakstatter Comment: While collecting data to present at the webinar, Mike noticed there was a bias in the beacon measurements. The beacon station is located ~184km away at about 7,000 ft elevation while the test site was at about 1,000 ft elevation. Initially, Mike wasn’t modeling the troposphere difference between the base and rover.
    To model the troposphere, Mike said he used a troposphere model to figure out troposphere in both locations, and then subtract the two. Although the models are not necessarily that accurate in an absolute sense, the differential tropo between the two locations is fairly accurate using the models. This differential tropo allows the receiver to correct the tropo in the base station differential to make it appear as if it originated in the rover location. Mike said he could’ve done the same for the ionosphere, but he didn’t since that is it usually less of a factor. After using the modified tropo model (Beacon T), the height bias was around 1/2 meter, which could be attributable the ionosphere. The horizontal bias is small, as you can see in the results.
    Using this troposphere model resulted in a significant improvement over the original solution.
    Question #28: Why is VBS better than WAAS?
    Gakstatter Comment: It surprised me too. The receiver used was the same that was used for beacon and WAAS. I contacted OmniSTAR for their opinion.
    John Pointon of OmniSTAR responds: “There have been incremental improvements in the VBS service over the years, mostly improvements in modeling and processing. We have added two or three extra reference stations but that hasn’t been the most critical improvement, just helped in some specific areas. These, combined with the relatively benign solar environment, result in VBS accuracy which, although not equivalent to our dual-frequency and multi-system solutions, is consistently better than either Beacon or WAAS.”
    Whitehead Comment: In the past, we’ve seen similar performance from both OmniStar VBS and WAAS.  Different atmosphere conditions and different locations can affect the performance of both. We’ve seen situations where WAAS is better.  It is probably fair to say that OmniStar is more focused on accuracy, whereas WAAS is focused on integrity.  It may be wise to do a comparison in the particular area where you operate.  Note, however, that in the US, OmniStar is referenced to NAD83 whereas WAAS is references to ITRF so positions reports between the two can differ by several meters.
    Question #29: When I look at your scatter plot, I have to ask if short-term point averaging is really effective at achieving more accurate positions?
    Gakstatter Comment: I think it’s well accepted that you are wasting time by occupying a point for 180 seconds. That said, there’s something to be said for letting the receiver track satellites for a period of time (1-2 minutes) before storing 5-10 seconds of data. Of course, if the receiver is already tracking satellites, then it’s not necessary to wait. The idea is to let the measurements settle down and take advantage of carrier-phase smoothing if the receiver uses that technique.

    Question #30: Could you go into PPP a bit more? How does it work?

    Gakstatter Comment: We opened a can of worms by discussing PPP. It’s an entirely different subject that I will cover in a future article. In the meantime, you can read Dr. Richard Langley’s article on PPP here.

    Question #31: How do you test the accuracy of SBAS collected data?

    Gakstatter Comment: In the U.S., it’s easy. Find a local survey mark using the National Geodetic Survey website. Printout the ITRF coordinates of the survey mark. If they aren’t on the datasheet, you can convert from NAD83/CORS96 to ITRF using the HTDP program. Compare the coordinates output by your GPS receiver to the coordinates of the survey mark.
    If you’re located outside of the U.S., look for a similar government agency in your country that maintains a record of survey marks. It’s vital that you are comparing coordinates referenced to the same datums.

     

    Question #32: Will there be any disadvantage if we use a EGNOS corrections in Kuwait, if we receive EGNOS?

    Whitehead Comment: Kuwait is outside the EGNOS coverage zone, so satellites to the south may not even have Clock and Orbit correctors available, which means the Receiver could not compute a correction for these satellites.  Unless the receiver can mix differentially cor
    rected ranges with non-differentially corrected ranges, it would likely drop the satellites in the south that had no corrections. This would then reduce PDOP and thus accuracy. Mixing differentially corrected ranges with non-differentially corrected ranges may give worse accuracy than no corrections at all since the SBAS system may have clock or other biases relative to GPS.
    By the way, I wish the SBAS providers would get together and share data so that they each could provide world-wide orbits and clocks. Then it would matter less if you were outside the coverage area.
    Gakstatter Comment: I’ve heard that EGNOS is planning an expansion to the south and east, so Kuwai may eventually be within the EGNOS coverage footprint. Also, you’ll want to monitor the progress of India’s GAGAN system, which is a similar SBAS. It’s possible you might fall within the GAGAN extrapolated footprint for non-aviation users.

    We covered most of the questions posed by the audience. If we didn’t address yours or didn’t provide a complete enough answer for you, please e-mail me and I’ll do my best to answer you.
    As I mentioned above, we had quite a few questions about PPP. It’s a technology that’s worthy of further coverage and discussion. Look for a future article on it.
    Thanks, and see you next time.
    Follow me on Twitter at http://twitter.com/GPSGIS_Eric

     

  • SBAS (WAAS) and NDGPS Accuracy and Statistics

    There’s something I’ve been wanting to write about since the ION-GNSS conference a few weeks ago. However, a nasty cold, a 10-day trip to Europe (INTERGEO conference), and some jet lag have kept me from it until now.

    Here goes.

    First of all, most of the presentations from the CGSIC meeting are available on the USCG Navigation Center website. You can view them by clicking here. There’s some very good reading and most of it is pretty light-weight and in PDF format.

    One of the presentations at the CGSIC (Civil GPS Service Interface Committee) meeting during the ION-GNSS conference was “Integrating NDGPS and SBAS —
    An Optimal Real-time GPS Mapping Solution,” presented by Jean-Yves Lauture of Geneq, Inc.

    I’m publishing two of the slides from his presentation in order to:

    1. Show the accuracy potential of WAAS and NDGPS given a high performance L1 receiver.
    2. Discuss the statistical names/values used to express GPS accuracy.

    First of all, each of the slides below are at the same scale. Each ellipse is 20 cm with the outside limit (radius) being one meter.

    I’ve known for quite sometime that SBAS (WAAS in this case) is capable of sub-meter precision with a single-frequency GPS receiver. These results are a bit better than what I’ve seen personally, and keep in mind it’s a limited data set of 1,800 continuous epochs, but impressive none the less. Also, keep in mind that the WAAS Performance Analysis Report published quarterly by the FAA’s National Satellite Test Bed shows the 95% horizontal accuracy value for Denver, Colorado, (near where this data was collected) being .547 meters for the quarter ending June 30, 2010 (7,856,354 samples collected over three months).

     

    30 minutes of WAAS-corrected data (each ellipse represents 20cm)

     

    The results I didn’t expect were the slide below, which shows NDGPS-corrected results using the same receiver/antenna. Keep in mind this is a GPS L1 receiver using phase-smoothed pseudorange measurements, not a GPS L1/L2 receiver using a carrier-phase float solution. If you look closely, you’ll see it states the baseline distance is 200 km. Granted, this is a limited data set, and I’ll be interested in seeing further results. If this was a dataset presented by a manufacturer or other party with some sort of interest, I wouldn’t publish it, but this is data collected by an objective entity (a credible U.S. government agency) so that earns, in my mind, a level of credibility.

    The results are pretty impressive. All data points fall within ~20 cm.

    30 minutes of NDGPS-corrected data (each ellipse represents 20cm)

    Keep in mind that this data was collected recently, and we are currently in a period of low ionospheric activity. In other words, data was collected under near-ideal conditions. At the end of the day, my point is that GPS L1 accuracy using SBAS and NDGPS has gotten pretty darned good.

    Accuracy Statistics

    The second reason I’m publishing the slides is to discuss accuracy statistics.

    Look at the small box inside each slide showing 99%, 95%, 68%, and 50% accuracies.

    If you look at the data points, it might not be immediately apparent how those values were arrived at. For example, how could a group of data points all within ~20 cm have a 95% confidence of 37 cm?

    To explain this, there was a good article published in GPS World in 2007 titled “GNSS Accuracy: Lies, Damn Lies, and Statistics” by Frank van Diggelen. It does a good job explaining statistical expressions (RMS, 2DRMS, etc.).

    Keep in mind that most manufacturers express horizontal GPS accuracy specifications based on 68% confidence. When the specification sheet states “sub-meter” HRMS (horizontal RMS) precision, that means 68% of the time; the horizontal accuracy will be less than a meter. In reality, that “sub-meter” receiver won’t consistently deliver sub-meter precision. If you convert the 68% HRMS value and express it with 95% confidence (2D HRMS), the actual horizontal precision for that same receiver will be well over one meter. That’s the precision you can expect from the receiver, not the 68% confidence value.

    Thanks, and see you next time.

    Follow me on Twitter at http://twitter.com/GPSGIS_Eric

  • As Loran Fades, Attention Shifts to DGPS and SBAS

    Few precise-positioning users have employed Loran in a professional sense, although maybe you have in your personal life if you’re a airplane pilot or a mariner. Then again, if you’ve flown as an airline passenger or cruised onboard a ship, you’ve benefited from the back-up to GPS that Loran provides. Similarly, if you’ve used a mobile phone recently; you don’t see it, but the wireless carriers all use Loran as a back-up. That back-up is about to go away.

    Loran was developed initially for marine navigation and then adopted for aviation navigation. I used Loran-C for aviation navigation in the early 90’s after I earned my private pilot’s license. It was much easier than triangulating off of VORs and NDBs. Yes, GPS receivers for aviation were starting to emerge at that time but flying is expensive so a hand-held GPS was an out-of-reach luxury for a newlywed who just bought his first house and was preparing to start a family.

    Loran is a terrestrial (ground-based) system of broadcasting towers, somewhat synonymous with NDGPS. You can read details about the system in the link I provided, but essentially it’s a line-of-sight system in which the Loran receiver antenna needs a direct path to the tower to utilize the signal. Coverage depends on the density of the broadcasting towers. Some regions are covered better than others and when I was using it, there were many areas that were not covered. Accuracy is always an ambiguous subject with respect to navigation technologies, so I’ll go out on a limb and say that Loran-C accuracy is repeatable to about 20 meters. A proposal was floated to upgrade Loran to a system called e-Loran which is reportedly accurate to about 9 meters.

    Anyway, over the past several years there’s been a discussion about what to do with the Loran system because it’s clear that GPS has supplanted Loran as the primary navigation system for marine and aviation. Several articles have been published in GPS World by industry experts with most being in favor of maintaining Loran. The primary argument is that we need a back-up system for GPS, not only for navigation, but for the many invisible ways that GPS supports the national infrastructure (financial networks, wireless communications, transportation).

    Here are several relevant articles, from most recent to further back:

    New Backward-Compatible Technique to Develop GPS+eLORAN User Base

    Coast Guard Jettisons Loran

    LORAN: What the President Meant to Say Was…

    Loran Study Finally Unleashed: Says Keep It, Best Option

    eLoran, Superhero Sidekick

    Loran Gets a Witness

    The Case for eLoran

    In addition to these articles , the U.S. government publishes the Federal Radionavigation Plan (FRP) roughly on a biennial basis. There was one published in 2001, then 2005 and the last one was published in 2008/early 2009. It is the official policy document in which all US navigation systems are planned. According to the FRP, it is prepared jointly by the Department of Defense, Department of Homeland Security, the Department of Transportation and a number of other contributing government agencies.

    If you don’t have time to read the 2008 FRP, following is a telling statement from the document:

    “In March 2007, the DOT Pos/Nav Executive Committee and the DHS Geospatial/PNT Executive Committee accepted the findings of the Institute for Defense Analysis’ Independent Assessment Team and approved to pursue the designation of Enhanced-Loran, commonly referred as eLoran, as a national PNT backup for the U.S. homeland.

    At its March 2007 meeting, the National Space-based PNT ExComm supported this approach and tasked DOT and DHS to complete an action plan that includes identifying an executive agent, developing a transition plan to address funding and operations and requesting the approval by the DOT and DHS Secretaries resulting in a final decision. DoD has not approved eLoran as a GPS backup for military applications.

    In March 2008, the National Space-based PNT ExComm endorsed the DOT/DHS decision to transition the LORAN system to eLoran.

    With respect to transportation to include aviation, commercial maritime, rail, and highway, the DOT has determined that sufficient alternative navigation aids currently exist in the event of a loss of GPS-based services, and therefore Loran currently is not needed as a back-up navigation aid for transportation safety-of-life users. However, many transportation safety-of-life applications depend on commercial communication systems and DOT recognizes the importance of the Loran system as a backup to GPS for critical infrastructure applications requiring precise time and frequency.

    Currently, DHS is determining whether alternative backups or contingency plans exist across the critical infrastructure and key resource sectors identified in the National Infrastructure Protection Plan in the event of a loss of GPS-based services. An initial survey of the Federal critical infrastructure partners indicates wide variance in backup system requirements. Therefore, DHS is working with Federal partners to clarify the operational requirements.”

    By the way, that Independent Assessment Team mentioned in the first paragraph was led by Brad Parkinson, who knows someting about GPS. Further, the government read the report behind closed doors but refused to release it, until forced to do so nearly two years later, by public information access filings.

    There still aren’t any answers to the question about a real back-up to GPS. No doubt it’s a vulnerable system. But that’s a subject for another day.

    What’s Loran got to do with us?

    The reason I’m writing about this is because as support for Loran wanes, attention (resources and focus) shifts away from Loran, it comes to bear more intensely on GPS navigation and its augmentations for marine and aviation; specifically DGPS and SBAS (WAAS/EGNOS/MSAS).

    With a significant policy shift such as this (albeit it has been in the cards), manufacturers stop allocating engineering development resources to the products/technologies with a dim future and shift those resources to products/technologies with a bright future. True, DGPS has been around for better than a decade and SBAS for about half that time so there’s been plenty of time for manufacturer’s to exploit those technologies, but there is still a lot that can be done.

    Engineers are experimenting with and implementing technologies in some interesting areas.

    HA-NDGPS. High accuracy NDGPS. Currently with a high performance DGPS receive
    r, one can attain about meter-level accuracy. Testing with HA-NDGPS, using a dual frequency GPS receiver shows that accuracies in the 10cm (95%) horizontal and 20cm (95%) vertical range are achievable within a 100 mile baseline according to the US DOT Federal Highway Administration Turner-Fairbank Research Center. Test broadcasts are being sent from a site in Hagerstown, MD.

    Broadcasting DGPS/SBAS corrections via NTRIP. The emergence of RTK Networks has spurred the popularity of using the internet to deliver GPS corrections. NTRIP has become a commonly used method of accomplishing this. One of the weak points of DGPS technology has been the reliability and expense of broadcasting DGPS corrections via the 283-325kHz band. Of course, with NTRIP one must have internet access somehow and that typically happens via WiFi or GSM/CDMA mobile phone network. But it’s not that complicated. I’ve been with a GPS user who has pulled the SIM card from their iPhone, plugged it into a GPS receiver, and begin receiving DGPS corrections immediately.

    During my last webinar, someone had posed the question if receiving SBAS corrections is possible via the internet in order to bypass the requirement to maintain visibility of the SBAS geostationary satellite. Streaming SBAS corrections via the internet is already happening in Europe. Users can access EGNOS corrections and bypass the EGNOS geostationary satellites by using SISNeT. A similar type of system could be implemented for any SBAS and not necessarily by the SBAS service provider. It could be a commercial entity.

    I think the internet and GSM/CDMA mobile phone networks are really going to transform the way we transport data from reference stations to our receivers in the field. We’ve been fighting this battle of delivering GPS corrections for better than a decade. In the past, we’ve experimented with FM pagers and landline modems and now we’ve settled on low frequency radiobeacon, VHF/UHF/Spread spectrum and geostationary satellites but none are close to the perfect solution. GSM/CDMA mobile phone networks may be the final solution as the networks continue to build-out towards complete geographic coverage. Of course, we are helped immensely by the mobile phone industry whose focus on data for the many new social networking applications will drive the price of data plans downward.

    By the way, almost all wireless carriers use Loran as a back-up technology; highly precise timing is a key aspect of how wireless communication works. The carriers use GPS for that, but if GPS goes down — as it did in San Diego during a memorable jamming episode a few years ago — so do all cell phones, if the carriers don’t have a timing back-up. In San Diego, they didn’t. Just something to think about, if you are using your mobile phone network to transport data or receive corrections.

  • Spain’s GMV Wins Malaysian DGPS Contract

    The Marine Department of Malaysia’s Ministry of Transportation has chosen Spain’s GMV and Astronautic Technology Sdn. Bhd. (ATSB) to establish the country’s coastal differential (DGPS) network.

    This contract is partly a result of GMV’s close relationship with ATSB, a Malaysian company, forged more than three years ago in a business cooperation forum organized by the Spanish Overseas Trade Institute in Malaysia, according to the companies. The network established by GMV and ATSB will include four transmitting stations, two remote monitoring centers, and a control center. Along with coordinating the installation of the systems, GMV also will set up the necessary communications software, reference stations and integrity monitors at each site and track the specific remote-monitoring and control-center software.

    “The system we have developed for this project provides dynamic support and flexibility for markets in the maritime sector,” said Luis Mayo, GMV CEO. The project validates Madrid-based GMV’s international expansion and strengthens its position in Malaysia, where it now boasts a portfolio of signature clients, the company said.