# how to get the location long and lat out of the raw measurements?

I'am making a research about GNSS I used GNSS logger to collect measurements but couldn't understand how these measurements turn into location of long and lat? the picture below of the measurements attributes.

I only know the vastly simplified form: all satellite nav systems work by the satellites telling you where they are and what time it is. In GPS terms, that time is the "pseudorange", and it's all you need (in theory) to locate yourself.

With no satellites in view, you have no clue where or when you are. With one satellite in view, you can place yourself on a 3-sphere* in time and space**. With two satellites you can place yourself on a 2-sphere, etc. When you have four satellites in view you can locate yourself to a point, and you're done***.

I suggest you look around and get a book on satellite navigation. I'd love to recommend one, but first, I'm not current, and second, StackExchange discourages product recommendations. But they're out there, and these days there should be one that covers GPS, GNSS and Galileo.

* I'm using the mathematical terminology here: a 3-sphere is the locus of points equidistant from a point in 4-dimensional space, a 2-sphere is the surface of a ball in 3-D space, a circle on a plane is a 1-sphere, and a point is a 0-sphere.

** I.e., you know that if it's the same time as the satellite's time you're at the satellite's position, if it's 1ms of a second after the satellite's time you're on a 2-sphere 300,000 meters in diameter around the satellite's position, etc.

*** Except for noise, of course, and I can't recall if, even in the perfect case, you end up with just one possible location or a finite number of them.

• thank you yes i want to know which of these i need to locate my locations in this case as i understand the pseudorange ? in my data there is "pseudorange rate meter per second" – Mustafa Azzurri Mar 8 '20 at 9:05
• You need more information. 'TimeNanos', if it's the satellite's time, could be used for the pseudorange, but that's not something you can tell just by looking at a name in a header file. This is a book length subject, which is why I'm suggesting that you find a book and buy it. – TimWescott Mar 8 '20 at 21:42
• thanks for explaining I'll try to find a book about it – Mustafa Azzurri Mar 9 '20 at 11:46