Add Stations and Services

The services currently found within the download utility are supported because they provide public access to data and they are known to us.

If you know of another service which provides public FTP access to GNSS reference data, contact Waypoint support (support.novatel@hexagon.com) as it may be possible to add the service to the software. This has the added benefit of making the service available to all other users as well.

If you prefer to add your own custom service, create a user.xml file within your User directory (C:\NovAtel\WayptGPS880\Resources\User). The first line of the user.xml file must contain <DN1> and the last line must be </DN1>.

Service and station records must conform to the format described below.

You might find it easier to copy a service and station record from the manufact.xml file and paste it into user.xml file for modifying.

Adding a service requires knowledge of the FTP address at which the data is stored. The directory structure and file type must be known.

Service records must conform to the format described below. Refer to the manufact.xml file for examples of service and station records.

Station record format

<station>

 

 

<name></name>

Four-character station name as saved on FTP server. See Note 1.

 

<download>

 

 

 

<appxlat></appxlat>

Latitude in decimal degrees (signed).

 

 

<appxlon></appxlon>

Longitude in decimal degrees (signed).

 

 

<appxht></appxht>

Ellipsoidal height, in meters.

 

 

<serv>

 

 

 

<name></name>

Name of service to which the station belongs. See Note 1 and Note 3.

 

 

</serv>

 

 

</download>

 

</station>

 

 

Service record format

<service>

 

 

<name></name>

Name of service, up to a maximum of 8 characters. See Note 1.

 

<data></data>

 

 

<protocol></protocol>

Type of file transfer protocol used by the service (FTP, HTTP or HTTPS).

 

<encryption></encryption>

The encryption method used (false or explicit). Applies only to FTP connections.

 

<address></address>

Address of the FTP server.

 

<username></username>

Required to log into nonpublic sites. See Note 1 and Note 4.

 

<password></password>

Required to log into nonpublic sites. See Note 1 and Note 4.

 

<ofile></ofile>

Generic path to the observation file containing daily (24-hour) data. If the daily data is unavailable or not provided, download of hourly data will be attempted if defined. See Note 6.

 

<dfile></dfile>

Generic path to the compressed observation file. See Note 4 and Note 6.

 

<nfile></nfile>

Generic path to the GPS navigation file. See Note 6.

 

<gfile></gfile>

Generic path to the GLONASS navigation file. See Note 4 and Note 6.

 

<hofile></hofile>

Generic path to the hourly observation files. See Note 4 and Note 6.

 

<hdfile></hdfile>

Generic path to the compressed hourly observation files. See Note 4 and Note 6.

 

<hnfile></hnfile>

Generic path to the hourly GPS navigation file. See Note 4 and Note 6.

 

<hgfile></hgfile>

Generic path to the hourly GLONASS navigation file. See Note 4 and Note 6.

 

<color></color>

Color to use for symbols in utility’s interface. See Note 4 and Note 5.

</service>

 

Station and Service record notes

  1. This field is case-sensitive.

  2. Only the Z, GZ, and ZIP formats of compression are supported.

  3. The service name must match the ServID field of a service record, as defined in the manufact.xml file or, if the service is user-created, in your user.xml file. If the station is found on more than one service, enter a separate <name> entry for each service.

  4. This field is optional and, thus, does not need to be present.

  5. The color defined here is used in the interface to identify the stations belonging to this service. The following colors are available: red, green, blue, magenta, cyan, gray, wine, black, gold, darkgray, darkgreen, darkblue, lightcyan, and darkmagenta.

  6. This field identifies the format of the directory structure used on the FTP site to organize the data. Any folders in the structure that are common to all data must be hard-coded into this field. The rest, however, must be defined using the following case-sensitive strings:

    [JJJ]

    Julian Day

    [YYYY]

    Year

    [XXXX]

    Station ID

    [week]

    GPS week

    [wkrl]

    GPS week - 1024 - padded with leading zeroes

    [wkrn]

    GPS week -1024 - without padding

    [yy]

    Last two digits of the year

    [d]

    Day of the week (0 – 6)

    [MN]

    Month number

    [DM]

    Day of the month

    [H]

    Hour of the day, in upper case (A-X)

    [II]

    Hour of the day, numeric (00-23)

    [mmm]

    first three letters of month (Jan-Dec)

    [CITY]

    any custom string (such as the name of a city or region) contained within an FTP sites folder structure that varies for individual stations