chore: Run pint for formatting

src/Database/PostgisFunctions/MagellanBoundingBoxFunctions.php

@@ -150,11 +150,6 @@ public static function zMin($geometry): MagellanNumericExpression
     /**
      * Returns a bounding box expanded from the bounding box of the input, either by specifying a single distance with which the box should be expanded on both axes, or by specifying an expansion distance for each axis. Uses double-precision. Can be used for distance queries, or to add a bounding box filter to a query to take advantage of a spatial index.
      *
-     * @param  float|Expression|\Closure|null  $unitsToExpand
-     * @param  float|Expression|\Closure|null  $dx
-     * @param  float|Expression|\Closure|null  $dy
-     * @param  float|Expression|\Closure|null  $dz
-     * @param  float|Expression|\Closure|null  $dm
      *
      * @see https://postgis.net/docs/ST_Expand.html
      */
@@ -193,8 +188,6 @@ public static function expand($geometry, float|Expression|\Closure $unitsToExpan
     /**
      * Returns the estimated extent of a spatial table as a box2d. The current schema is used if not specified. The estimated extent is taken from the geometry column's statistics. This is usually much faster than computing the exact extent of the table using ST_Extent or ST_3DExtent.
      *
-     * @param  string|Expression|\Closure|null  $schemaName
-     * @param  bool|Expression|\Closure|null  $parentOnly
      *
      * @see https://postgis.net/docs/ST_EstimatedExtent.html
      */

src/Database/PostgisFunctions/MagellanGeometryAccessorFunctions.php

@@ -26,7 +26,6 @@ public static function boundary($geometry): MagellanGeometryExpression
     /**
      * Orders by the diagonal of the supplied geometry's bounding box as a LineString. The diagonal is a 2-point LineString with the minimum values of each dimension in its start point and the maximum values in its end point. If the input geometry is empty, the diagonal line is a LINESTRING EMPTY.
      *
-     * @param  bool|Expression|\Closure|null  $fits
      *
      * @see https://postgis.net/docs/ST_BoundingDiagonal.html
      */

src/Database/PostgisFunctions/MagellanGeometryProcessingFunctions.php

@@ -21,7 +21,6 @@ trait MagellanGeometryProcessingFunctions
      * A negative distance shrinks the geometry rather than expanding it. A negative distance may shrink a polygon completely, in which case POLYGON EMPTY is returned.
      * For points and lines negative distances always return empty results.
      *
-     * @param  float|Expression|\Closure|null  $styleMitreLimit
      *
      * @see https://postgis.net/docs/ST_Buffer.html
      */
@@ -74,7 +73,6 @@ public static function buildArea($geometry): MagellanGeometryExpression
     /**
      * Computes a point which is the geometric center of mass of a geometry. For [MULTI]POINTs, the centroid is the arithmetic mean of the input coordinates. For [MULTI]LINESTRINGs, the centroid is computed using the weighted length of each line segment. For [MULTI]POLYGONs, the centroid is computed in terms of area. If an empty geometry is supplied, an empty GEOMETRYCOLLECTION is returned. If NULL is supplied, NULL is returned. If CIRCULARSTRING or COMPOUNDCURVE are supplied, they are converted to linestring with CurveToLine first, then same than for LINESTRING
      *
-     * @param  bool|Expression|\Closure|null  $useSpheroid
      *
      * @see https://postgis.net/docs/ST_Centroid.html
      */
@@ -93,8 +91,6 @@ public static function centroid($geometry, bool|Expression|\Closure $useSpheroid
     /**
      * Returns a "smoothed" version of the given geometry using the Chaikin algorithm. See Chaikins-Algorithm for an explanation of the process. For each iteration the number of vertex points will double. The function puts new vertex points at 1/4 of the line before and after each point and removes the original point. To reduce the number of points use one of the simplification functions on the result. The new points gets interpolated values for all included dimensions, also z and m.
      *
-     * @param  int|Expression|\Closure|null  $iterations
-     * @param  bool|Expression|\Closure|null  $preserveEndPoints
      *
      * @see https://postgis.net/docs/ST_ChaikinSmoothing.html
      */
@@ -107,7 +103,6 @@ public static function chaikinSmoothing($geometry, int|Expression|\Closure $iter
      * A concave hull of a geometry is a possibly concave geometry that encloses the vertices of the input geometry. In the general case the concave hull is a Polygon. The polygon will not contain holes unless the optional param_allow_holes argument is specified as true. The concave hull of two or more collinear points is a two-point LineString. The concave hull of one or more identical points is a Point.
      *
      * @param  float|Expression|\Closure  $pctconvex controls the concaveness of the computed hull. A value of 1 produces the convex hull. A value of 0 produces a hull of maximum concaveness (but still a single polygon). Values between 1 and 0 produce hulls of increasing concaveness. Choosing a suitable value depends on the nature of the input data, but often values between 0.3 and 0.1 produce reasonable results.
-     * @param  bool|Expression|\Closure|null  $allowHoles
      *
      * @see https://postgis.net/docs/ST_ConcaveHull.html
      */
@@ -131,7 +126,6 @@ public static function convexHull($geometry): MagellanGeometryExpression
     /**
      * Return the Delaunay triangulation of the vertices of the input geometry. Output is a COLLECTION of polygons (for flags=0) or a MULTILINESTRING (for flags=1) or TIN (for flags=2). The tolerance, if any, is used to snap input vertices together.
      *
-     * @param  float|Expression|\Closure|null  $tolerance
      *
      * @see https://postgis.net/docs/ST_DelaunayTriangles.html
      */
@@ -143,8 +137,6 @@ public static function delaunayTriangles($geometry, float|Expression|\Closure $t
     /**
      * Filters out vertex points based on their M-value. Returns a geometry with only vertex points that have a M-value larger or equal to the min value and smaller or equal to the max value. If max-value argument is left out only min value is considered. If fourth argument is left out the m-value will not be in the resulting geometry. If resulting geometry have too few vertex points left for its geometry type an empty geometry will be returned. In a geometry collection geometries without enough points will just be left out silently.
      *
-     * @param  float|Expression|\Closure|null  $max
-     * @param  bool|Expression|\Closure|null  $returnM
      *
      * @see https://postgis.net/docs/ST_FilterByM.html
      */
@@ -168,9 +160,6 @@ public static function generatePoints($geometry, int|Expression|\Closure $number
     /**
      * Computes the approximate geometric median of a MultiPoint geometry using the Weiszfeld algorithm. The geometric median is the point minimizing the sum of distances to the input points. It provides a centrality measure that is less sensitive to outlier points than the centroid (center of mass).
      *
-     * @param  float|Expression|\Closure|null  $tolerance
-     * @param  int|Expression|\Closure|null  $maxIterations
-     * @param  bool|Expression|\Closure|null  $failIfNotConverged
      *
      * @see https://postgis.net/docs/ST_GeometricMedian.html
      */
@@ -182,7 +171,6 @@ public static function geometricMedian($geometry, float|Expression|\Closure $tol
     /**
      * Returns a LineString or MultiLineString formed by joining together the line elements of a MultiLineString. Lines are joined at their endpoints at 2-way intersections. Lines are not joined across intersections of 3-way or greater degree.
      *
-     * @param  bool|Expression|\Closure|null  $directed
      *
      * @see https://postgis.net/docs/ST_LineMerge.html
      */
@@ -221,8 +209,6 @@ public static function orientedEnvelope($geometry): MagellanGeometryExpression
      * All points of the returned geometries are not further than the given distance from the input geometry.
      * Useful for computing parallel lines about a center line.
      *
-     * @param  int|Expression|\Closure|null  $numSegQuarterCircle
-     * @param  float|Expression|\Closure|null  $styleMitreLevel
      *
      * @see https://postgis.net/docs/ST_OffsetCurve.html
      */
@@ -286,7 +272,6 @@ public static function sharedPaths($geometryA, $geometryB): MagellanGeometryExpr
     /**
      * Returns a "simplified" version of the given geometry using the Douglas-Peucker algorithm. Will actually do something only with (multi)lines and (multi)polygons but you can safely call it with any kind of geometry. Since simplification occurs on a object-by-object basis you can also feed a GeometryCollection to this function.
      *
-     * @param  bool|Expression|\Closure|null  $preserveCollapsed
      *
      * @see https://postgis.net/docs/ST_Simplify.html
      */
@@ -299,7 +284,6 @@ public static function simplify($geometry, float|Expression|\Closure $tolerance,
      * Computes a simplified topology-preserving outer or inner hull of a polygonal geometry. An outer hull completely covers the input geometry. An inner hull is completely covered by the input geometry. The result is a polygonal geometry formed by a subset of the input vertices. MultiPolygons and holes are handled and produce a result with the same structure as the input.
      *
      * @param  float|Expression|\Closure  $vertexFraction The reduction in vertex count is controlled by the vertex_fraction parameter, which is a number in the range 0 to 1. Lower values produce simpler results, with smaller vertex count and less concaveness. For both outer and inner hulls a vertex fraction of 1.0 produces the orginal geometry. For outer hulls a value of 0.0 produces the convex hull (for a single polygon); for inner hulls it produces a triangle.
-     * @param  bool|Expression|\Closure|null  $isOuter
      *
      * @see https://postgis.net/docs/ST_SimplifyPolygonHull.html
      */
@@ -338,8 +322,6 @@ public static function simplifyVW($geometry, float|Expression|\Closure $toleranc
      * If the optional "theshold" parameter is used, a simplified geometry will be returned,
      * containing only vertices with an effective area greater than or equal to the threshold value.
      *
-     * @param  float|Expression|\Closure|null  $threshold
-     * @param  int|Expression|\Closure|null  $setArea
      *
      * @see https://postgis.net/docs/ST_SetEffectiveArea.html
      */

src/Database/PostgisFunctions/MagellanMeasurementFunctions.php

@@ -26,7 +26,6 @@ public static function distanceSphere($geometryA, $geometryB): MagellanNumericEx
      * For geometry types returns the minimum 2D Cartesian (planar) distance between two geometries, in projected units (spatial ref units).
      * For geography types defaults to return the minimum geodetic distance between two geographies in meters, compute on the spheroid determined by the SRID. If use_spheroid is false, a faster spherical calculation is used.
      *
-     * @param  bool|Expression|\Closure|null  $useSpheroid
      *
      * @see https://postgis.net/docs/ST_Distance.html
      */
@@ -112,7 +111,6 @@ public static function maxDistance3D($geometryA, $geometryB): MagellanNumericExp
     /**
      * Returns the area of a polygonal geometry. For geometry types a 2D Cartesian (planar) area is computed, with units specified by the SRID. For geography types by default area is determined on a spheroid with units in square meters. To compute the area using the faster but less accurate spherical model use ST_Area(geog,false).
      *
-     * @param  bool|Expression|\Closure|null  $useSpheroid
      *
      * @see https://postgis.net/docs/ST_Area.html
      */
@@ -131,7 +129,6 @@ public static function area($geometry, bool|Expression|\Closure $useSpheroid = n
      * For geometry types: returns the 2D Cartesian length of the geometry if it is a LineString, MultiLineString, ST_Curve, ST_MultiCurve. For areal geometries 0 is returned; use ST_Perimeter instead. The units of length is determined by the spatial reference system of the geometry.
      * For geography types: computation is performed using the inverse geodetic calculation. Units of length are in meters. If PostGIS is compiled with PROJ version 4.8.0 or later, the spheroid is specified by the SRID, otherwise it is exclusive to WGS84. If use_spheroid=false, then the calculation is based on a sphere instead of a spheroid.
      *
-     * @param  bool|Expression|\Closure|null  $useSpheroid
      *
      * @see https://postgis.net/docs/ST_Length.html
      */
@@ -240,7 +237,6 @@ public static function shortestLine3D($geometryA, $geometryB): MagellanGeometryE
      * Returns the 2D perimeter of the geometry/geography if it is a ST_Surface, ST_MultiSurface (Polygon, MultiPolygon). 0 is returned for non-areal geometries. For linear geometries use ST_Length. For geometry types, units for perimeter measures are specified by the spatial reference system of the geometry.
      * For geography types, the calculations are performed using the inverse geodetic problem, where perimeter units are in meters. If PostGIS is compiled with PROJ version 4.8.0 or later, the spheroid is specified by the SRID, otherwise it is exclusive to WGS84. If use_spheroid=false, then calculations will approximate a sphere instead of a spheroid.
      *
-     * @param  bool|Expression|\Closure|null  $useSpheroid
      *
      * @see https://postgis.net/docs/ST_Perimeter.html
      */

src/Database/PostgisFunctions/MagellanOverlayFunctions.php

@@ -101,7 +101,6 @@ public static function split($geometryInput, $geometryBlade): MagellanGeometryEx
      * Point-in-polygon and other spatial operations are normally faster for indexed subdivided datasets. Since the bounding boxes for the parts usually cover a smaller area than the original geometry bbox, index queries produce fewer "hit" cases.
      * The "hit" cases are faster because the spatial operations executed by the index recheck process fewer points.
      *
-     * @param  int|Expression|\Closure|null  $max_vertices
      * @param  float|Expression|\Closure|null  $gridSize If the optional gridSize argument is provided, the inputs are snapped to a grid of the given size, and the result vertices are computed on that same grid. (Requires GEOS-3.9.0 or higher)
      *
      * @see https://postgis.net/docs/ST_Subdivide.html

src/Database/PostgisFunctions/MagellanSpatialReferenceSystemFunctions.php

@@ -42,10 +42,6 @@ public static function srid($geometry): MagellanNumericExpression
      * - geometry ST_Transform(geometry geom, text from_proj, text to_proj);
      * - geometry ST_Transform(geometry geom, text from_proj, integer to_srid);
      *
-     * @param  int|Expression|\Closure|null  $srid
-     * @param  string|Expression|\Closure|null  $fromProjection
-     * @param  string|Expression|\Closure|null  $toProjection
-     * @param  int|Expression|\Closure|null  $toSrid
      *
      * @see https://postgis.net/docs/ST_Transform.html
      */

src/Database/PostgisFunctions/MagellanTopologicalRelationshipFunctions.php

@@ -179,8 +179,6 @@ public static function overlaps($geometryA, $geometryB): MagellanBooleanExpressi
      * For more information refer to Section 5.1, “Determining Spatial Relationships”.
      * Variant 1: Tests if two geometries are spatially related according to the given intersectionMatrixPattern.
      *
-     * @param  string|Expression|\Closure|null  $intersectionMatrixPattern
-     * @param  int|Expression|\Closure|null  $boundaryNodeRule
      *
      * @see https://postgis.net/docs/ST_Relate.html
      */