mirror/weewx
1
0
Fork 0
mirror of https://github.com/weewx/weewx.git synced 2026-07-30 18:17:56 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix multiple broken links unearthed by Zensical v0.0.41 and later.

Browse Source
This commit is contained in:
Tom Keffer
2026-06-10 12:14:26 -07:00
parent 387dfe3809
commit 68d79ebe2d
10 changed files with 27 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs_src/custom/database.md
View File

@@ -240,7 +240,7 @@ Here is the general strategy to do this.
3. Make sure you have the necessary permissions to create the new database.
4. Use the action
[`weectl database reconfigure`](../utilities/weectl-database.md/#reconfigure-a-database)
[`weectl database reconfigure`](../utilities/weectl-database/#reconfigure-a-database)
to create the new database and populate it with data from the old
database.
@@ -314,7 +314,7 @@ Here are the details:
rebuilding the daily summaries inside the new database. This will be
done automatically by `weewxd` at the next startup. Alternatively, it
can be done manually using the
[`weectl database rebuild-daily`](../utilities/weectl-database.md/) action:
[`weectl database rebuild-daily`](../utilities/weectl-database/) action:
``` shell
weectl database rebuild-daily
@@ -325,7 +325,7 @@ Here are the details:
Normally, data are stored in the databases using US Customary units, and you
shouldn't care; it is an "implementation detail". Data can always be displayed
using any set of units you want — the section [*Changing unit
systems*](custom-reports.md#changing-unit-systems) explains how to change
systems*](custom-reports#changing-unit-systems) explains how to change
the reporting units. Nevertheless, there may be special situations where you
wish to store the data in Metric units. For example, you may need to allow
direct programmatic access to the database from another piece of software that
@@ -334,7 +334,7 @@ expects metric units.
You should not change the database unit system midstream. That is, do
not start with one unit system then, some time later, switch to another.
WeeWX cannot handle databases with mixed unit systems — see the
section [`[StdConvert]`](../reference/weewx-options/stdconvert.md) in the
section [`[StdConvert]`](../reference/weewx-options/stdconvert) in the
WeeWX User's Guide. However, you can reconfigure the database by
copying it to a new database, performing the unit conversion along the
way. You then use this new database.
@@ -344,7 +344,7 @@ The general strategy is identical to the strategy outlined above in the section
only difference is that instead of specifying a new starting schema, you specify
a different database unit system. This means that instead of steps 1 and 2
above, you edit the configuration file and change option `target_unit` in
section [`[StdConvert]`](../reference/weewx-options/stdconvert.md) to reflect
section [`[StdConvert]`](../reference/weewx-options/stdconvert) to reflect
your choice. For example, if you are switching to metric units, the option will
look like:

6
docs_src/custom/image-generator.md
View File

@@ -131,7 +131,7 @@ includes a line plot of both outside temperature and dewpoint:
![Monthly temperature and dewpoint](../images/sample_monthtempdew.png)
### Including a type more than once in a plot {#inclue-same-sql-type-2x}
### Including a type more than once in a plot {#include-same-sql-type-2x}
Another example. Suppose that you want a plot of the day's temperature,
overlaid with hourly averages. Here, you are using the same data type
@@ -242,7 +242,7 @@ for details.
However, supposed you'd like to offer both Metric and US Customary
versions of the same plot? You can do this by using option
[`unit`](../reference/skin-options/imagegenerator.md/#unit)
[`unit`](../reference/skin-options/imagegenerator/#unit)
to override the unit used for individual plots:
``` ini hl_lines="4 9"
@@ -266,7 +266,7 @@ degrees Celsius.
## Line gaps {#line-gaps}
If there is a time gap in the data, the option
[`line_gap_fraction`](../reference/skin-options/imagegenerator.md/#line_gap_fraction) controls how line plots will be drawn.
[`line_gap_fraction`](../reference/skin-options/imagegenerator/#line_gap_fraction) controls how line plots will be drawn.
Here's what a plot looks like without and with this option being specified:
<figure markdown>

2
docs_src/custom/multiple-bindings.md
View File

@@ -129,7 +129,7 @@ binding, `wx_binding`, and will be labeled `Vantage inTemp`. The second line
explicitly uses the `wmr100_binding`. Because it uses the same variable name
(`inTemp`) as the first line, we had to explicitly specify it using option
`data_type`, in order to avoid using the same subsection name twice (see
the section *[Including a type more than once in a plot](image-generator.md#include-same-sql-type-2x)*
the section *[Including a type more than once in a plot](image-generator#include-same-sql-type-2x)*
for details). It will be labeled `WMR100 inTemp`. The results look like this:
![Comparing temperatures](../images/daycompare.png)

16
docs_src/reference/aggtypes.md
View File

@@ -15,14 +15,14 @@
<td class="first_col code">avg_ge(val)</td>
<td>The number of days when the average value is greater than or equal to <em>val</em>. Aggregation
period must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
<td class="first_col code">avg_le(val)</td>
<td>The number of days when the average value is less than or equal to <em>val</em>. Aggregation period
must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
@@ -99,14 +99,14 @@
<td class="first_col code">max_ge(val)</td>
<td>The number of days when the maximum value is greater than or equal to <em>val</em>. Aggregation
period must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
<td class="first_col code">max_le(val)</td>
<td>The number of days when the maximum value is less than or equal to <em>val</em>. Aggregation period
must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
@@ -149,14 +149,14 @@
<td class="first_col code">min_ge(val)</td>
<td>The number of days when the minimum value is greater than or equal to <em>val</em>. Aggregation
period must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
<td class="first_col code">min_le(val)</td>
<td>The number of days when the minimum value is less than or equal to <em>val</em>. Aggregation period
must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
@@ -178,14 +178,14 @@
<td class="first_col code">sum_ge(val)</td>
<td>The number of days when the sum of value is greater than or equal to <em>val</em>. Aggregation
period must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>
<td class="first_col code">sum_le(val)</td>
<td>The number of days when the sum of value is less than or equal to <em>val</em>. Aggregation period
must be one day or longer. The argument <span class="code">val</span> is a
<a href="#ValueTuple"><span class="code">ValueTuple</span></a>.
<a href="./valuetuple/"><span class="code">ValueTuple</span></a>.
</td>
</tr>
<tr>

2
docs_src/reference/skin-options/imagegenerator.md
View File

@@ -301,7 +301,7 @@ Default is to use the color in [`chart_line_colors`](#chart_line_colors).
The SQL data type to be used for this plot line. For more information,
see the section *[Including a type more than once in a
plot](../../custom/image-generator.md#include-same-sql-type-2x)*.
plot](../../custom/image-generator#include-same-sql-type-2x)*.
Optional. The default is to use the section name.
#### fill_color

2
docs_src/usersguide/where.md
View File

@@ -72,7 +72,7 @@ facility. On some systems, the log messages end up in files that you can
browse as you would any other file. On other systems you will have to use
tools provided by the operating system to see the log messages.
See the section [_Monitoring WeeWX_](monitoring.md/#log-messages).
See the section [_Monitoring WeeWX_](monitoring).
## Location of executables in a pip install

2
docs_src/utilities/weectl-import-config-opt.md
View File

@@ -1756,7 +1756,7 @@ temperature to WeeWX field `outTemp`, outside humidity to WeeWX field
!!! Note
Any WeeWX archive fields that are derived (e.g., `dewpoint`) and for
which there is no field mapping may be calculated during import by use of
the [`calc_missing`](#wc_calc_missing) option in the `[WeatherCat]`
the [`calc_missing`](#calc_missing_4) option in the `[WeatherCat]`
section of the import configuration file.
!!! Note

5
docs_src/utilities/weectl-import-csv.md
View File

@@ -146,9 +146,8 @@ name of the file containing the CSV formatted data to be imported.
* [raw_datetime_format](weectl-import-config-opt.md#csv_raw_datetime_format).
The format of the imported date time field.
* [rain](weectl-import-config-opt.md#csv_rain). Determines how the
WeeWX rain
field is derived.
* [rain](weectl-import-config-opt#csv_rain). Determines how the
WeeWX rain field is derived.
* [wind_direction](weectl-import-config-opt.md#csv_wind_direction).
Determines how imported wind direction fields are interpreted.

2
docs_src/utilities/weectl-station.md
View File

@@ -5,7 +5,7 @@ station, including its configuration file.
Specify `--help` to see the actions and options.
See the section [_Options_](#options) below for details of the various options.
See the section [_Optional arguments_](#optional-arguments) below for details of the various options.
## Create a new station data directory

4
zensical.toml
View File

@@ -131,6 +131,10 @@ nav = [
{ "Change log" = "changes.md" },
]
# Do not report things like `[StdReport]` as a missing link!
[project.validation]
unresolved_references = false
[project.theme]
name = "zensical"
variant = "classic"