Update documentation

NorDataNet · Apr 19, 2024 · 2e2d9a8 · 2e2d9a8
1 parent 0e0a1f0
commit 2e2d9a8
Show file tree

Hide file tree

Showing 18 changed files with 564 additions and 1,016 deletions.
diff --git a/01_opening_and_understanding.html b/01_opening_and_understanding.html
diff --git a/02_creating_plots.html b/02_creating_plots.html
diff --git a/03_extracting_data_to_different_formats.html b/03_extracting_data_to_different_formats.html
diff --git a/04_creating_a_cfnetcdf_file.html b/04_creating_a_cfnetcdf_file.html
diff --git a/05_how_to_structure_your_NetCDF_file_or_files.html b/05_how_to_structure_your_NetCDF_file_or_files.html
diff --git a/06_creating_multiple_cfnetcdf_files_in_one_go.html b/06_creating_multiple_cfnetcdf_files_in_one_go.html
diff --git a/07_combing_data_from_multiple_netcdf_files.html b/07_combing_data_from_multiple_netcdf_files.html
diff --git a/08_ancillary_variables.html b/08_ancillary_variables.html
diff --git a/09_cells_and_cell_methods.html b/09_cells_and_cell_methods.html
diff --git a/_sources/03_extracting_data_to_different_formats.ipynb b/_sources/03_extracting_data_to_different_formats.ipynb
@@ -4394,7 +4394,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.4"
+   "version": "3.11.5"
   }
  },
  "nbformat": 4,

diff --git a/_sources/04_creating_a_cfnetcdf_file.ipynb b/_sources/04_creating_a_cfnetcdf_file.ipynb
@@ -5281,7 +5281,7 @@
     "And remember we might want to select additional applicable global attributes from this section of the CF conventions:\n",
     "https://cfconventions.org/Data/cf-conventions/cf-conventions-1.11/cf-conventions.html#attribute-appendix\n",
     "\n",
-    "Go through and add each required attribute and any others you wish to. You are also welcome to add any global attributes from the CF conventions as well as any custom attributes on top of these requirements. Similarly to variable attributes, this can either be done one by one or all in one in a dictionary. "
+    "Go through and add each required attribute and any others you wish to. You are also welcome to add any custom attributes on top of these requirements. Similarly to variable attributes, this can either be done one by one or all in one in a dictionary. "
    ]
   },
   {
@@ -5323,7 +5323,7 @@
    "id": "3d9fd5f0",
    "metadata": {},
    "source": [
-    "In this case, it makes sense to some attributes based on information we have already provided."
+    "In this case, it makes sense to add some attributes based on information we have already provided."
    ]
   },
   {
@@ -5486,7 +5486,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.4"
+   "version": "3.11.5"
   }
  },
  "nbformat": 4,

diff --git a/_sources/08_ancillary_variables.ipynb b/_sources/08_ancillary_variables.ipynb
@@ -458,12 +458,12 @@
     "\n",
     "We need to create a new variable for the flags.\n",
     "\n",
-    "Flags are stored as numbers, and with the meanings for the numbers stored as a variable attribute. The `flag_meanings` should be separated by spaces - so don't include spaces in any of the terms you use! The length of the `flag values` and `flag_meanings` should be the same. "
+    "Flags are stored as numbers, and with the meanings for the numbers stored as a variable attribute. The *flag_meanings* should be separated by spaces - so don't include spaces in any of the terms you use! The length of the *flag values* and *flag_meanings* should be the same. "
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
+   "execution_count": 1,
    "id": "a942a457",
    "metadata": {},
    "outputs": [],
@@ -477,7 +477,7 @@
    "id": "96a656ec",
    "metadata": {},
    "source": [
-    "So for example, a value of 2 means 'probably_good_data'\n",
+    "So for example, a value of 2 means *probably_good_data*.\n",
     "\n",
     "You might wonder which conventions these quality flag values and meanings adhere to. In this case, we are following the OceanSITES Manual v 1.4.\n",
     "http://www.oceansites.org/docs/oceansites_data_format_reference_manual.pdf\n",
@@ -895,7 +895,7 @@
    "id": "ad00e25c",
    "metadata": {},
    "source": [
-    "Now we need to state that the new 'Chlorophyll_A_quality_flags' variable is related to the 'Chlorophyll A' variable."
+    "Now we need to state that the new *Chlorophyll_A_quality_flags* variable is related to the *Chlorophyll A* variable."
    ]
   },
   {
@@ -913,10 +913,10 @@
    "id": "3ba86208",
    "metadata": {},
    "source": [
-    "Finally we need to add our metadata to the ancillary variable to describe it. There are a lot of standard names for different types of flags. Search for 'flag' here to find a suitable `standard_name` for you. \n",
+    "Finally we need to add our metadata to the ancillary variable to describe it. There are a lot of standard names for different types of flags. Search for *flag* here to find a suitable *standard_name* for you. \n",
     "https://cfconventions.org/Data/cf-standard-names/current/build/cf-standard-name-table.html\n",
     "\n",
-    "The CF conventions also has standardised variable attributes you can use for `flag_values`and `flag_meanings`. You often see the `valid_range` attribute used here too to explicitely show that any values outside of that range are invalid. You could use `valid_min` and `valid_max` used instead."
+    "The CF conventions also has standardised variable attributes you can use for *flag_values* and *flag_meanings*. You often see the *valid_range* attribute used here too to explicitely show that any values outside of that range are invalid. You could use *valid_min* and *valid_max* used instead."
    ]
   },
   {
@@ -1342,7 +1342,7 @@
    "id": "667e8976",
    "metadata": {},
    "source": [
-    "Make sure you refer to the conventions you are following for your quality flags in your `Conventions` global attribute, for example"
+    "Make sure you refer to the conventions you are following for your quality flags in your *Conventions* global attribute, for example"
    ]
   },
   {
@@ -1755,7 +1755,7 @@
    "metadata": {},
    "source": [
     "## Retrieving only good_quality data\n",
-    "Suppose we want to retrieve only the good_quality `Chlorophyll_A` data, where `Chlorophyll_A_quality_flags = 1`"
+    "Suppose we want to retrieve only the good_quality *Chlorophyll_A* data, where *Chlorophyll_A_quality_flags = 1*"
    ]
   },
   {
@@ -3011,7 +3011,7 @@
    "id": "8e994299",
    "metadata": {},
    "source": [
-    "More work needs to be done to expand the CF conventions to standardise ancillary data. At the time of writing, a `standard_name` for the volume of sea water filtered does not exist. \n",
+    "More work needs to be done to expand the CF conventions to standardise ancillary data. At the time of writing, a *standard_name* for the volume of sea water filtered does not exist. \n",
     "\n",
     "This is where the scientific community can help! \n",
     "\n",