comparison: docs/faq/faq.rst
docs/faq/faq.rst
- changeset 55
- d4ed2005724f
- parent 54
- 613613bc8872
- child 61
- e3ff7af1d97e
equal
deleted
inserted
replaced
| 54:613613bc8872 | 55:d4ed2005724f |
|---|---|
| 124 A: The following definitions apply: | 124 A: The following definitions apply: |
| 125 | 125 |
| 126 SCC raw lidar data file | 126 SCC raw lidar data file |
| 127 ^^^^^^^^^^^^^^^^^^^^^^^ | 127 ^^^^^^^^^^^^^^^^^^^^^^^ |
| 128 | 128 |
| 129 This file should be named as measID.nc. For example if your measurement had a measurement ID of 20130101cc00 the corresponding NetCDF file should be named 20130101cc00.nc | 129 In the current version of the SCC there is not limit in the name of the raw |
| 130 data file. We suggest, however, that this file is named <measurement_id>.nc. | |
| 131 For example, if your measurement had a measurement ID of 20130101cc00 the | |
| 132 corresponding NetCDF file should be named 20130101cc00.nc | |
| 130 | 133 |
| 131 Sounding file | 134 Sounding file |
| 132 ^^^^^^^^^^^^^ | 135 ^^^^^^^^^^^^^ |
| 133 | 136 |
| 134 The file should be named as rs_measID.nc. Considering the above example the sounding file should be named rs_20130101cc00.nc | 137 The file should be named as rs_measID.nc. Considering the above example the sounding file should be named rs_20130101cc00.nc |
