Archive for the ‘Help’ Category

New place for our GAP1 files

June 10th, 2013 by Ricardo Píriz

We have now a new ftp address on the GMV server for the RINEX measurement files coming from our GAP1 station. The files can now be downloaded with the following login information:

  • server: ftp.gmv.es
  • user: magicgnssro
  • password: R0gnss06

We are storing hourly files at a 1-second rate and daily files at a 30-second rate. The files can be accessed on a web browser through the following URLs (examples):

ftp://magicgnssro:[email protected]/gap1161j.13d.Z (hourly file)

ftp://magicgnssro:[email protected]/gap11610.13d.Z (daily file)

Files are kept on the server for the last 45 days, older files are also available upon request.

GAP1 station now contributing to IGS’ MGEX

July 30th, 2012 by Ricardo Píriz

Our GAP1 station is now contributing GPS+GLO data to the IGS’ MGEX experiment (RINEX files and real-time stream). RINEX files are available on the following ftp servers: CDDIS (USA), BKG (Germany), IGN (France). Hourly high-rate files are also available at GMV’s ftp server as usual (see below). A new GAP1 station log is also available. Galileo data is not yet ready due to unavailability of the required receiver firmware.

  • Daily files (@ 30 sec):

ftp://cddis.gsfc.nasa.gov/gnss/data/campaign/mgex/daily/rinex2/

ftp://igs.bkg.bund.de/MGEX/obs

ftp://igs.ign.fr/pub/igs/data/campaign/mgex/daily/rinex2

  • Hourly files (@ 30 sec):

ftp://cddis.gsfc.nasa.gov/gnss/data/campaign/mgex/hourly/rinex2/

ftp://igs.bkg.bund.de/MGEX/nrt

ftp://igs.ign.fr/pub/igs/data/campaign/mgex/hourly/rinex2

  • High-rate files (@ 1 sec):

ftp://cddis.gsfc.nasa.gov/gnss/data/campaign/mgex/highrate/rinex2/

ftp://igs.bkg.bund.de/MGEX/highrate

ftp://igs.ign.fr/pub/igs/data/campaign/mgex/highrate/rinex2

  • Hourly high-rate files (@ 1 sec); example:

ftp://ftp.gmv.es/incoming/gap1212m.12d.Z (only available for the last week or so)

Navigation messages have been discontinued, we recommend using daily “brdc” files from IGS:

GPS; example:

ftp://cddis.gsfc.nasa.gov/gps/data/daily/2012/212/12n/brdc2120.12n.Z

ftp://igs.bkg.bund.de/IGS/BRDC/2012/212/brdc2120.12n.Z

GLONASS; example:

ftp://cddis.gsfc.nasa.gov/gps/data/daily/2012/212/12g/brdc2120.12g.Z

ftp://igs.bkg.bund.de/IGS/BRDC/2012/212/brdc2120.12g.Z

Regional PPP

October 25th, 2010 by Ricardo Píriz

Precise Point Positioning (PPP) is normally understood as a global positioning service, since precise satellite orbit and clock products used as input in PPP are best calculated using a network of GNSS reference stations distributed worldwide.

However orbit and clock corrections for PPP can also be provided over a world region in a similar way to WAAS or EGNOS corrections. It is even possible to provide a national PPP service over a single country, using national GNSS stations exclusively.

Satellite orbits and clocks calculated using regional stations do not have of course a high overall accuracy, but they do have a higher accuracy over the service area and, most importantly, orbit and clock errors largely cancel out over the service area. For a static or kinematic PPP user located inside the region, positioning accuracy using global or regional products is very similar.

In magicGNSS version 3.1 it is possible to evaluate the performance of regional PPP in a very simple way. Just process an ODTS scenario to calculate orbits and clocks covering the time period of your interest. On the Stations tab, select stations over your region only. Click on the station icons to select/deselect, you can use core stations and/or your own stations.

In regional ODTS it is better to deselect “Refine Station Coordinates” in Settings. Core stations have already precise coordinates, and for your own stations you are supposed to have processed them beforehand in PPP using the “Update My Station Coordinates” option. Try also to use a longer ODTS scenario duration (3 to 4 days), in order to maximize satellite visibility. It is also important to select a good reference clock in ODTS. The reference clock time should be close enough to UTC (or GPS Time), with an offset of the order of the microsecond or less. You can see the offset of a station clock by processing it in PPP.

When ODTS processing is ready, create a new PPP scenario for that period, and select Products from the ODTS scenario you just processed, instead of the global ones (Operational):

You can use COMP to compare static or kinematic PPP solutions using global and regional products.

Ocean loading

January 18th, 2010 by Álvaro Mozo

Ocean loading is the deformation of the Earth due to the weight of the ocean masses. The water in the ocean moves due to the gravitational pull of the Moon and the Sun (this is the tides), and causes the Earth, which is not completely rigid, to deform according to the varying load of the ocean’s water. The deformation is periodic, following the relative motion of Earth, Moon and Sun, however such relative motion is rather complex and thus periodicity has to be represented with several harmonic terms of different period.

Periodicity of tides around the world (graphic from NOAA)

Periodicity of tides around the world (graphic from NOAA)

Most commonly, the 11 first terms (i.e. those with higher amplitude) are retained to model this effect.

Ocean loading can be perceived as a periodic displacement of the station position (especially in coastal areas), as well as a periodic variation of the Earth’s gravity.

How is ocean loading taken into account in magicGNSS?

(more…)

Automating data processing with the Scheduler

October 21st, 2009 by Ricardo Píriz

With the latest version of magicGNSS (1.4), and if you have a *pro* account, you will be able to automate your station data processing in ODTS or PPP, using the new Scheduler. This is how the Scheduler settings look like:

Scheduler

Just select the algorithm you want to automate (ODTS or PPP). Previously you should have run an ODTS or PPP scenario to be used as template by the Scheduler. Every time it runs, the Scheduler reads the scenario Duration, the list of Stations, and the Settings, from the template scenario. Make sure your template scenario is properly configured! (more…)