Merge pull request #183 from ldgeo/master

doc: fix README&NEWS, pc_boundingdiagonal doesn't exists
This commit is contained in:
Éric Lemoine 2017-05-31 13:02:39 +02:00 committed by GitHub
commit b9ecf07606
2 changed files with 3 additions and 4 deletions

2
NEWS
View File

@ -11,7 +11,7 @@
- PC_Sort(pcpatch,text[]) (#106)
- PC_IsSorted(pcpatch,text[],boolean) (#106)
- PC_Range(pcpatch, int, int) returns pcpatch (#152)
- PC_BoundingDiagonalAsBinary(pcpatch) and PC_BoundingDiagonal(pcpach) (#158)
- PC_BoundingDiagonalAsBinary(pcpatch) and PC_BoundingDiagonalGeometry(pcpach) (#158)
- PC_SetPCId(pcpatch, int, float8 default 0.0) (#163)
- PC_Transform(pcpatch, int, float8 default 0.0) (#165)
- Enhancements

View File

@ -581,7 +581,7 @@ The `pointcloud_postgis` extension adds functions that allow you to use PostgreS
>
> SELECT ST_AsText(PC_BoundingDiagonalGeometry(pa)) FROM patches;
> st_astext
> ------------------------------------------------
> ------------------------------------------------
> LINESTRING Z (-126.99 45.01 1,-126.91 45.09 9)
> LINESTRING Z (-126 46 100,-126 46 100)
> LINESTRING Z (-126.2 45.8 80,-126.11 45.89 89)
@ -593,11 +593,10 @@ The `pointcloud_postgis` extension adds functions that allow you to use PostgreS
> LINESTRING Z (-126.9 45.1 10,-126.81 45.19 19)
> LINESTRING Z (-126.7 45.3 30,-126.61 45.39 39)
> LINESTRING Z (-126.1 45.9 90,-126.01 45.99 99)
> (11 rows)gq
>
> For example, this is how one may want to create an index:
>
> CREATE INDEX ON patches USING GIST(PC_BoundingDiagonal(patch) gist_geometry_ops_nd);
> CREATE INDEX ON patches USING GIST(PC_BoundingDiagonalGeometry(patch) gist_geometry_ops_nd);
## Compressions ##