Doc updates in preparation for 2.9 release (PDAL#4732)

* Fix PDAL#4662

* add include note for the three ways to describe bounds

* spread 'bounds' note option description

* add synonym for layer <-> lyr_name

* add synonym for expression => limits

* sanitize as many usages of filters.range => filters.expression as we can

* unset release date

Author: hobu

doc/apps/translate.md

@@ -81,12 +81,12 @@ $ pdal translate \
 
 Given these tools, we can now construct a custom pipeline on-the-fly. The
 example below uses a simple LAS reader and writer, but stages a voxel
-grid filter, followed by the SMRF filter and a range filter. We can even set
+grid filter, followed by the SMRF filter and a {ref}`filters.expression` filter. We can even set
 stage-specific parameters as shown.
 
 ```
-$ pdal translate input.las output.las voxelcenternearestneighbor smrf range \
-    --filters.range.limits="Classification[2:2]"
+$ pdal translate input.las output.las voxelcenternearestneighbor smrf expression \
+    --filters.expression.expression="Classification == 2"
 ```
 
 ## Example 3:

doc/download.md

@@ -4,7 +4,7 @@
 
 ## Current Release(s)
 
-- **2025-05-22** [PDAL-2.9.0-src.tar.bz2] [Release Notes] ([md5])
+- **2025-XX-XX** [PDAL-2.9.0-src.tar.bz2] [Release Notes] ([md5])
 
 ## Past Releases
 

doc/index.md

@@ -26,7 +26,7 @@ The entire website is available as a single PDF at <http://pdal.io/_/downloads/e
 
 ## News
 
-### **05-22-2025**
+### **XX-XX-2025**
 
 PDAL 2.9.0 was released. Visit {ref}`download` to grab a copy.
 

doc/pipeline.md

@@ -122,8 +122,8 @@ files from a single pipeline.  The crop filter creates two output point views
 
 ### Multiple Writers and Output Types
 
-A pipeline can have multiple writers, but they must operate sequentially. 
-If tags and inputs create seperate end points (multiple leaf nodes), not 
+A pipeline can have multiple writers, but they must operate sequentially.
+If tags and inputs create seperate end points (multiple leaf nodes), not
 all stages will be executed. For example, you can have something like:
 
 `Reader -> Filter -> Writer -> Filter -> Writer`
@@ -136,7 +136,7 @@ But you can not split the pipeline and write to multiple end points:
 
 ```
 Reader -> Filter -> Filter -> Filter -> Writer
-                      |           |         
+                      |           |
                       v           v
                     Writer      Writer
 ```
@@ -337,7 +337,7 @@ this job in more detail.
 A common task is to create a digital terrain model (DTM) from the input point
 cloud. This pipeline infers the reader type, applies an approximate ground
 segmentation filter using {ref}`filters.smrf`, filters out all points but the
-ground returns (classification value of 2) using the {ref}`filters.range`, and
+ground returns (classification value of 2) using the {ref}`filters.expression`, and
 then creates the DTM using the {ref}`writers.gdal`.
 
 ```json
@@ -351,8 +351,8 @@ then creates the DTM using the {ref}`writers.gdal`.
         "cell":1.0
     },
     {
-        "type":"filters.range",
-        "limits":"Classification[2:2]"
+        "type":"filters.expression",
+        "expression":"Classification == 2"
     },
     {
         "type":"writers.gdal",

doc/stages/bounds_opts.md

@@ -0,0 +1,60 @@
+  ```{note}
+
+  Bounds can be expressed in multiple forms:
+
+    * Classical PDAL style
+
+      * 3D – `([xmin, xmax], [ymin, ymax], [zmin, zmax])`
+      * 2D – `([xmin, xmax], [ymin, ymax])`
+
+    * [GeoJSON BBOX](https://datatracker.ietf.org/doc/html/rfc7946#section-5)
+
+      * 3D – `[xmin, ymin, zmin, xmax, ymax, zmax]`
+      * 2D – `[xmin, ymin, xmax, ymax]`
+
+    * JSON Object
+
+      * 3D
+
+      ```
+      {
+        "minx": 1,
+        "miny": 2,
+        "minz": 3,
+        "maxx": 101,
+        "maxy": 102,
+        "maxz": 103
+      }
+      ```
+
+      * 2D
+
+      ```
+      {
+        "minx": 1,
+        "miny": 2,
+        "maxx": 101,
+        "maxy": 102
+      }
+      ```
+
+      * CRS
+
+      The JSON Object style form is the only one that can also include a
+      definition using the `crs` member. It can be any valid PROJ-compatible
+      CRS definition (WKT, WKT2, PROJJSON, PROJ.4 codes).
+
+
+      ```
+      {
+        "minx": 1,
+        "miny": 2,
+        "minz": 3,
+        "maxx": 101,
+        "maxy": 102,
+        "maxz": 103,
+        "crs": "EPSG:4326"
+      }
+      ```
+  ```
+

doc/stages/filters.approximatecoplanar.md

@@ -29,7 +29,7 @@ coplanar (1) or not (0).
 
 The sample pipeline presented below estimates the planarity of a point based on
 its eight nearest neighbors using the approximate coplanar filter. A
-{ref}`filters.range` stage then filters out any points that were not
+{ref}`filters.expression` stage then filters out any points that were not
 deemed to be coplanar before writing the result in compressed LAZ.
 
 ```json
@@ -42,8 +42,8 @@ deemed to be coplanar before writing the result in compressed LAZ.
         "thresh2":6
     },
     {
-        "type":"filters.range",
-        "limits":"Coplanar[1:1]"
+        "type":"filters.expression",
+        "expression":"Coplanar == 1"
     },
     "output.laz"
 ]

doc/stages/filters.crop.md

@@ -65,12 +65,10 @@ This example crops all points more than 500 units in any direction from a point.
 
 bounds
 
-: The extent of the clipping rectangle in the format
-  `"([xmin, xmax], [ymin, ymax])"`.  This option can be specified more than
-  once by placing values in an array.
+: The extent of the clipping rectangle in the format.  This option can be
+  specified more than once by placing values in an array.
 
-  ```{note}
-  3D bounds can be given in the form `([xmin, xmax], [ymin, ymax], [zmin, zmax])`.
+  ```{include} bounds_opts.md
   ```
 
   ```{warning}
@@ -119,4 +117,4 @@ a_srs
 
 ## Notes
 
-1. See {ref}`workshop-clipping`: and {ref}`clipping` for example usage scenarios for {ref}`filters.crop`.
+1. See {ref}`workshop-clipping`: and {ref}`clipping` for example usage scenarios for {ref}`filters.overlay`.

doc/stages/filters.csf.md

@@ -21,8 +21,8 @@ using default options, and writing only the ground returns to the output file.
         "type":"filters.csf"
     },
     {
-        "type":"filters.range",
-        "limits":"Classification[2:2]"
+        "type":"filters.expression",
+        "expression":"Classification == 2"
     },
     "output.laz"
 ]

doc/stages/filters.elm.md

@@ -57,8 +57,8 @@ returns that are not marked as noise.
         "threshold":2.0
     },
     {
-        "type":"filters.range",
-        "limits":"Classification![7:7]"
+        "type":"filters.expression",
+        "expression":"Classification != 7"
     },
     "output.las"
 ]

doc/stages/filters.estimaterank.md

@@ -42,8 +42,8 @@ and then filters out those points where the rank is three using
         "thresh":0.01
     },
     {
-        "type":"filters.range",
-        "limits":"Rank![3:3]"
+        "type":"filters.expression",
+        "expression":"Rank != 3"
     },
     "output.laz"
 ]