GPS World contributing editor Eric Gakstatter gave a talk on predicted ephemeris at the Civil GPS Service Interface Committee (CGSIC) on Tuesday. The talk was invited and the topic was suggested by CGSIC coordinators. The 53rd meeting of the CGSIC was held Monday and Tuesday before the Institute of Navigation GNSS+ 2013 Conference. Here is Eric’s talk:
Whenever I point a critical finger at the GPS folks, I apologize before I do so because it’s really a wonderful system.
What I try to offer the community in general is a link between the GPS system operators and the civil community. It’s amazing when you think about it, two huge user bases of civil and military users, and a little strip called CGSIC that communicates between them. Rick [Hamilton of CGSIC] introduced me to this concept a couple months ago and asked me to investigate it and think about it. This is what I researched and talked to some folks and came up with.
First, I want to introduce you to some folks doing fascinating things with GPS.
Here’s a young company, Geoloqi, doing really interesting things in Portland. They don’t have any clue where GPS came from; they just have it on their smartphones. One of the founders collected GPS data everywhere he went for the last three and a half years. This map shows 2.5 million data points, and I think it’s fascinating.
These folks interface between the GPS chipset in the mobile device and the apps that run on it. They sold their company to Esri last year.
“Geolocation has the potential to become an indispensable part of our lives. But to be a valuable service, the technology needs to be invisible yet opted into, private, and secure.” — Amber Case, Geoloqi founder
These kids just want to get things done, create ideas and create products: things like, check into a hotel when you get within 100 yards of the door; get your prescription prepared and ready for you when you come within a certain distance of a pharmacy. All these kinds of things are based on the geotrigger or geofence concept.
Now, talking about my work, primarily in surveying and mapping, with companies like utilities with 15 million customers and a lot of infrastructure. To put that at the fingertips of a maintenance person, that’s pretty amazing. I’ve been swimming in this soup for a long time, and I hadn’t heard of this concept — the predicted ephemeris (PRED) produced by GPSOC.
Take a PRED state vector data file, which is currently generated every 15 minutes by the GPS Operations Center under For Official Use Only (FOUO), currently designated unclassified, but not accessible to the general public. If it were made available for public use, it could decrease time to first fix from 40 seconds when you turn on your mobile device, to 5 to 10 seconds.
In the high-precision field like mine, surveying, it really doesn’t make too much difference because by the time you get out of your truck and set up your gear, 30 seconds has already gone by and it doesn’t make much difference.
Now it could be more of an issue with mobile devices in GPS-impaired environments such as urban canyons or indoor environments, where 30 seconds could make the difference between getting a fix or not.
If predicted ephemeris were available, developers could distribute it terrestrially via a wireless network to mobile devices.
Problem: How to transfer PRED from a U.S. government FOUO environment to make it available to application developers?
To me as a product developer or a product manager, interested in pushing products out to the community, that’s a really small speed bump. But when I talk to colleagues who operate in that (government) space, that’s a significant undertaking, a real obstacle. We’re talking about a big change, and a big process to go through to effect that change.
PRED from the horse’s mouth, so to speak, from the U.S. Air Force, really builds credibility. I can build it into a product, because I know it’s going to be there three or four or more years from now.
PRED can be made available, but Civil GPS app developers need to speak up — because civil users won’t. They don’t know about it. They don’t know what is possible.
“How does somebody know what they want if they haven’t even seen it?” — Steve Jobs
I’m trying to raise awareness here. I’ll probably write about soon in the magazine or in my [Survey Scene] email newsletter.
Frank van Diggelen, Broadcom. We’ve been doing this in the commercial world for over a decade. You all have it in your cellphones, with about 90% likelihood provided by Broadcom or someone who’s licensed our patents. It doesn’t work properly unless you have the source of the data and the client side working very cooperatively. The issue is the . . . gap between prediction and use. If the satellite is moved (in orbit or clock) then the prediction is wrong, and you need client-side software that is design cooperatively with the predictions. Our predictions are available in 2-, 4-, 7- or 30- day intervals. Think of a use case where you get a seven-day prediction, and then go away from network coverage for several days, meanwhile, say on Day 4, a satellite is moved or has its clock adjusted, on Day 5 it is set healthy, on Day 6 you turn on your handset and use the prediction from six days ago — it will be wrong and your client-side software has to catch that and know know how to invalidate the predictions.
We deliver these orbital predictions at about the rate of a billion per month. It’s been there for 10 years, and its been working so well most people aren’t even aware that it’s there. If the Air Force puts these out, that sounds great, but if you don’t have client-side software looking for erroneous predicitions — when a satellite is adjusted or moved — then things would be a lot worse for the user community than they have for the last 10 years.
Eric Gakstatter: I understand that, but that’s true for any technology. If a company implements it incorrectly, the market will reject it. Let the market decide.
There may be a need for a non-proprietary solution (PRED) that is publicly available so it could be implemented by other developers, and level the playing field to increase market adoption of GPS.