Note that there are some explanatory texts on larger screens.

plurals
  1. PODGPS corrections on Android
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIt seems like it's totally chip set dependent and requires native access (at a minimum) there is a European initiative to get better gps accuracy via their system. They have a toolkit for their system on supported hardware. Not exactly what you are looking for but you could probably contact them and get some ideas on how to proceed since they are using similar techniques. http://egnos-portal.gsa.europa.eu/developer-platform/egnos-toolkits/egnos-sdk. Of course they require add on hardware as well but it's still worth talking to them (domain experts and all)
      singulars
    2. COAlso, the GPS on Android platforms is ususally enhanced by cellphone or WiFi location support. The GPS bootstrapping is usually aided by the cellular network if this feature is supported by the carrier, and the location API is additionally aided by WiFi location services if enabled. Also, WAAS or EGNOS should be handled transparently by the GPS stack, but they seem not to be available despite in short testing periods / areas in europe.
      singulars
    3. COIt sounds like they just had two devices kind of near each other. If you are using the same receiver(both Droid Xs in this case), most of the error sources should be very similar. For identical devices the ionospheric, ephemeris, and clock errors should be very similar(http://en.wikipedia.org/wiki/Error_analysis_for_the_Global_Positioning_System).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload