de-linting

ruminations/README.md

@@ -4,21 +4,36 @@
 
 - You just need a brief, self contained introduction to Rust Geodesy?
 
-  Jump directly to [Rumination 009](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/009-rumination.md): Teach yourself Geodesy in less than 900 seconds (of arc)
+  Jump directly to
+  [Rumination 009](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/009-rumination.md):
+  Teach yourself Geodesy in less than 900 seconds (of arc)
 
 ## All ruminations
 
-If you have plenty of time, feel free to work your way through, and ruminate over, all the ruminations:
+If you have plenty of time, feel free to work your way through, and ruminate over,
+all the ruminations:
 
-- [Rumination 000](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/000-rumination.md): Overall architecture and philosophy
-- [Rumination 001](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/001-rumination.md): A few words about an often-seen pipeline
-- [Rumination 002](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/002-rumination.md): The missing manual
-- [Rumination 003](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/003-rumination.md): kp - the RG Coordinate Processing program
-- [Rumination 004](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/004-rumination.md): Why Rust Geodesy - some background
-- [Rumination 005](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/005-rumination.md): Divided by a common language
-- [Rumination 006](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/006-rumination.md): Still confused, but at a higher level
-- [Rumination 007](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/007-rumination.md): Operator parameter introspection
-- [Rumination 008](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/008-rumination.md): Geodesy from a PROJ perspective
-- [Rumination 009](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/009-rumination.md): Teach yourself Geodesy in less than 900 seconds (of arc)
-- [Rumination 010](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/010-rumination.md): What's wrong with ISO 19111?
-- [Rumination 011](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/011-rumination.md): Some potential elements of an introduction to a revised version of ISO 19111/OGC topic 2
+- [Rumination 000](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/000-rumination.md):
+  Overall architecture and philosophy
+- [Rumination 001](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/001-rumination.md):
+  A few words about an often-seen pipeline
+- [Rumination 002](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/002-rumination.md):
+  The missing manual
+- [Rumination 003](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/003-rumination.md):
+  kp - the RG Coordinate Processing program
+- [Rumination 004](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/004-rumination.md):
+  Why Rust Geodesy - some background
+- [Rumination 005](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/005-rumination.md):
+  Divided by a common language
+- [Rumination 006](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/006-rumination.md):
+  Still confused, but at a higher level
+- [Rumination 007](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/007-rumination.md):
+  Operator parameter introspection
+- [Rumination 008](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/008-rumination.md):
+  Geodesy from a PROJ perspective
+- [Rumination 009](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/009-rumination.md):
+  Teach yourself Geodesy in less than 900 seconds (of arc)
+- [Rumination 010](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/010-rumination.md):
+  What's wrong with ISO 19111?
+- [Rumination 011](https://github.com/busstoptaktik/geodesy/blob/main/ruminations/011-rumination.md):
+  Some potential elements of an introduction to a revised version of ISO 19111/OGC topic 2

src/coordinate/set.rs

@@ -150,11 +150,11 @@ macro_rules! coordinate_set_impl_3d_subset {
 /// this will usually be what you need:
 ///
 /// - The `0` as the third coordinate will make transformations behave as if the points
-/// are placed immediately on the reference ellipsoid, `h==0`
+///   are placed immediately on the reference ellipsoid, `h==0`
 ///
 /// - The `f64::NAN` as the fourth coordinate will spill into the plane coordinate
-/// values if passing these static coordinates through any dynamic transformations,
-/// requiring a proper time coordinate, hence giving a very noisy debugging signal
+///   values if passing these static coordinates through any dynamic transformations,
+///   requiring a proper time coordinate, hence giving a very noisy debugging signal
 ///
 /// If other fixed values for third and fourth coordinate are needed, the
 /// `CoordinateSet` trait is also blanket-implemented for the tuple

src/token/mod.rs

@@ -199,17 +199,17 @@ where
 ///
 /// ## Ellipsoid definitions
 /// - Geodesy only supports a limited set of builtin ellipsoids OR or definition
-/// via semi-major and reverse-flattening parameters  `ellps=a,rf`.
+///   via semi-major and reverse-flattening parameters  `ellps=a,rf`.
 /// - PROJ has [richer ellipsoid](https://proj.org/en/9.3/usage/ellipsoids.html#ellipsoid-size-parameters)
-/// support which *parse_proj* provides partial support for.
+///   support which *parse_proj* provides partial support for.
 /// - Specifically if an ellipsoid is defined via `a` and `rf` parameters, *parse_proj*
-/// will redefine them as `ellps=a,rf` and remove the `a` and `rf` parameters.
+///   will redefine them as `ellps=a,rf` and remove the `a` and `rf` parameters.
 /// - All other cases supported by PROJ are NOT handled by *parse_proj* and will
-/// fail when instantiating the operator.
+///   fail when instantiating the operator.
 ///
 /// ## Scaling via `k` parameter
 /// - PROJ still supports the deprecated `k` parameter. Most output from `projinfo` will
-/// have the scaling defined as `k` instead of `k_0`.
+///   have the scaling defined as `k` instead of `k_0`.
 /// - *parse_proj* will replace `k` with `k_0` whenever it is encountered.
 ///
 pub fn parse_proj(definition: &str) -> Result<String, Error> {