*** FOR FINAL GLONASS SOLUTION ***
    ==========================

Questionnaire concerning GLONASS biases:
----------------------------------------

Your institution: Natural Resources Canada
Contact email address(es): ymireaul@nrcan.gc.ca

The GLONASS clock corrections you generate are consistent to:
[X] pseudorange
[X] carrier phase
Please mark both fields if indicated.

Clock corrections are generated at intervals of:
300s then interpolated at 30s


Handling of GLONASS interfrequency code biases (for ionosphere-free LC):
[ ] one bias parameter for each station and satellite combination/pair
[ ] one bias parameter for each station and frequency channel
combination/pair
[X] other configuration: 
No bias estimation/correction.

Time resolution:


Description of datum definition (or reference) for GLONASS code biases:
NONE!

How many conditions/constraints are imposed for the bias datum
definition?
NONE!


How do you select GLONASS code observable types (to be used for a
specific
station) if P1 and C1, or P2 and C2 are available?
P1 first then C1. No C2.
GLONASS C1 observations are *NOT* "converted" to P1 using the 
CC2NONCC tool as it is the case for GPS.


Do you generate GLONASS clock corrections on a regular/operational
basis?
[X] Yes
[ } No, but test results (in clock-RINEX) would be available for:


Recommendations for PPP users of your GLONASS clock product:

For GPS and GLONASS combined PPP estimation, GLONASS data should be
deweighted with respect to the GPS data.  
In addition the PPP solution should model two independent clocks, 
one from the GPS data and one from the GLONASS data in order to help
contain possible GLONASS biases.


Do you have corresponding GLONASS bias results available (in ASCII
form)?
[ ] Yes
[X] No

Are there any specialties concerning your GLONASS clock product?
None!

Extra question: Do you have experience with GLONASS ambiguity
resolution?
[X] No
[ ] Yes, please specify:

========================================================================
=======