GPS Toolkit (GPSTk) 1.0 Released 197
rmach writes "Based on many years of work performed at ARL:UT, we have release GPSTk under the GNU LGPL. GPSTk is a cross platform library and set of applications that provides both fundamental and advanced GPS processing algorithms to the GPS and open source community. A wide array of functions are provided by the GPSTk library, including: RINEX I/O, ephemeris calculation, P-code generation, atmospheric refraction models, and positioning algorithms. GPSTk applications provided more concrete benefits to the user, including: cycle slip detection and removal, calculation of the Total Electron Content (TEC) of the ionosphere, position residual computation, and RINEX file manipulation. The library is about 41,000 SLOC with a COCOMO estimated cost to develop of about $1.3 million. You can also read more about it in the current issue (September '04) of Linux Journal."
Re:Not sure how this is useful... (Score:5, Interesting)
Track editing? (Score:5, Interesting)
The other featuer I've always wanted is to do profile slices of my rides to see climbing and descending rates, especially during races.
All in all this toolkit sounds hugely promising, as the last time I looked at SF.net/Freshmeat the capabilities were nearly nil. All I want is a simple import module, track overlay over free downloadable maps, and a track editor...
I'm going to be spending the evening trying to get this stuff working, hopefully it will provide a replacement to my current Garmin/Microsoft solution!
Re:Track editing? (Score:2, Interesting)
I also have an (alpha-quality) script that actually automates making maps from gps data (using kismet)... maybe someday I'll get off my ass and finish it..
Re:Not sure how this is useful... (Score:3, Interesting)
Uh, No.
More precise != faster in fact precise generally == slower. You have to take more measurements to get the data needed for input into the more precise modeling algorithms, but it allows you to calculate location VERY precisely (down to mm if you can get measurements over a day or two).
Re:This is just a bunch of (Score:2, Interesting)
Great! But.... (Score:2, Interesting)
Wasn't the Precision code classified? (Score:2, Interesting)
Now last I checked the Precision (P) code was considered classified. Details about how this code was generated and how to decrypt it were considered military secrets.
I don't believe the P-code has anything to do with selective availability either, I think that the P-code is used for the militaries PPS, which is "precise positioning system".
Anyway, so how is that included in this suite? and further, what purpose does it serve to even have access to the p-code, as standard gps gear isn't even supposed to work with it?
You know the reason... (Score:2, Interesting)
Anyway, don't be shocked by his misguided ego - it's old and getting more so. Hell, his little "gnutella-still-free-for-all dept" on the Real story is evidence of his nature and was pointed out in this [slashdot.org] post. Michael is a liability and tired.
What this is (Score:5, Interesting)
It seems to me that this is first time that code like this has ever been published under an open license.
Re:um, no. (Score:3, Interesting)
GPS and GnuRadio [comsec.com]
and
OpenSourceGPS [earthlink.net]
The latter claims:
"The receiver requires at a minimum a 100 MHz 486 IBM PC with 640k RAM."
So it seems to be possible. Someone posted the GPSTk link to the GnuRadio mailing list with the hope of eventually getting GnuRadio the ability to do advanced processing of GPS signals.
I'm not a GPS expert... am I missing something here?
Dude, where's my phone? (Score:3, Interesting)
Re:LGPL! (Score:2, Interesting)
moron: An inferior olive size having a woody pulp and a large clingstone pit, growing in the mountainous and high-valley districts around the city of Moron, in Spain.
Re:Huh? (Score:3, Interesting)
What I get from my array of GPS receivers is a set of observables, including the pseudorange from the code phase measurements, and carrier phase information. When I get done processing, I have a set of baselines, a set of potential delays in the troposphere and ionosphere, doppler shifts for the satellites in view, timing deltas, and information on signal multipath propagation.
When I report something out, I can give horizontal positions with respect to a known coordinate system to about 1 cm (2sigma RMS) and vertical estimates (referenced to the WGS84 ellipsoid) on the order of 2 cm (2sigma RMS). Given a good gravity model, I can estimate geoid height differences to about 3 cm.
Given code phase observables from a satellite-borne receiver, I can make reasonable estimates of the satellite's ephemerides and state vector, provided 3 sets with a temporal spread of about 20 minutes. Given code and carrier data I can derive the state vector in less time and with better accuracy.
I can estimate the amount of precipitable water in a vertical column of atmosphere above a GPS receiver site.
I can make estimates of the ionosphere's total electron count.
There's more.
For the record, I've been doing all of the above, for several years.