Code Measurements from RINEX Observation File

Discussion in 'General GPS Discussion' started by harmonicconvergence, Jan 17, 2011.

  1. harmonicconvergence

    harmonicconvergence

    Joined:
    Dec 16, 2010
    Messages:
    1
    Likes Received:
    0
    I have two/three related questions about the code measurements given in the RINEX observation file.

    1) Are the reported pseudoranges already corrected for the receiver's clock bias?

    2) Are they corrected for each satellite's clock bias?

    3) Is it reasonable to estimate a signal's travel time by dividing the reported psuedorange by the speed of light?

    I'm trying to develop my own MATLAB code to calculate a receiver's position using data from RINEX observation and navigation files, but I'm getting position errors upwards of +/-25m (RMS).
     
    harmonicconvergence, Jan 17, 2011
    #1

    1. Advertisements

  2. harmonicconvergence

    Nour

    Joined:
    Sep 28, 2011
    Messages:
    1
    Likes Received:
    0
    Location:
    Lille
    Hey HarmonicConvergence,

    I am very interested by your work, I'm too working on a Matlab code. I have a problem and I would like to discuss about it with you! Maybe we could find the solutions together.

    Regards
     
    Nour, Sep 28, 2011
    #2

    1. Advertisements

  3. harmonicconvergence

    typer

    Joined:
    Nov 28, 2011
    Messages:
    6
    Likes Received:
    0
    GoGPS Project

    Check out the GoGPS MATLAB Project. They started with MATLAB code and are currently porting to java.

    Maybe you can get some help from their code samples?
     
    typer, Nov 28, 2011
    #3

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Creating a seperate satellite file from Rinex file

  2. GPSbabel convert from gpx file to csv file Can't get all elements of waypoints to be converted

  3. absence of p2 code data of most GPS satellites in rinex data

  4. Conversion of Rinex file to leica format

Loading...