[postgis-tickets] [SCM] postgis.net branch website updated. clarity-final-7-g3a3fce3
git at osgeo.org
git at osgeo.org
Sat May 13 23:14:28 PDT 2023
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "postgis.net".
The branch, website has been updated
via 3a3fce3efca2b9c3e08255e1eb822c7fa9cee502 (commit)
from 79e3aa493520c1c8959fe560cd00db0e983732b1 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 3a3fce3efca2b9c3e08255e1eb822c7fa9cee502
Author: Regina Obe <lr at pcorp.us>
Date: Sun May 14 02:14:21 2023 -0400
Add weights and missing geekDoc setting to tips
diff --git a/content/documentation/tips/lon-lat-or-lat-lon.md b/content/documentation/tips/lon-lat-or-lat-lon.md
index 79dcad7..32fef8b 100644
--- a/content/documentation/tips/lon-lat-or-lat-lon.md
+++ b/content/documentation/tips/lon-lat-or-lat-lon.md
@@ -5,11 +5,12 @@ category: tips
tags: [newbie, geometry, geography, ST_FlipCoordinates]
author: "Regina Obe"
date: "2013-08-18"
+weight: 20
geekdocHidden: true
geekdocHiddenTocTree: false
---
-In web mapping APIs like Google Maps, spatial coordinates are often in order of latitude then longitude.
+In web mapping APIs like Google Maps, spatial coordinates are often in order of latitude then longitude.
In spatial databases like PostGIS and SQL Server, spatial coordinates are in longitude and then latitude. Mixing the two up can lead to questions like "why is this European city showing up in Africa on my map?"
@@ -20,7 +21,7 @@ An example use for geometry:
```postgres
ALTER TABLE sometable
- ALTER COLUMN geom
+ ALTER COLUMN geom
TYPE geometry(LineString,4326)
USING ST_FlipCoordinates(geom);
```
@@ -32,4 +33,4 @@ ALTER TABLE sometable
ALTER COLUMN geog
TYPE geography(LineString,4326)
USING geography(ST_FlipCoordinates(geometry(geom)));
-```
\ No newline at end of file
+```
diff --git a/content/documentation/tips/postgis-backend-is-already-set.md b/content/documentation/tips/postgis-backend-is-already-set.md
index e0ebce1..ab93229 100644
--- a/content/documentation/tips/postgis-backend-is-already-set.md
+++ b/content/documentation/tips/postgis-backend-is-already-set.md
@@ -5,12 +5,13 @@ category: tips
tags: [newbie, upgrade]
author: Regina Obe
date: "2017-06-05"
+weight: 100
geekdocHidden: true
geekdocHiddenTocTree: false
---
The error `'postgis.backend' is already set` comes up every so often in PostGIS mailing list.
-The issue arises often during or after an upgrade.
+The issue arises often during or after an upgrade.
The question goes something like this
@@ -23,7 +24,7 @@ If you installed the `legacy.sql` file, particularly before the PostGIS version
The fix for this is to run the old `legacy_uninstall.sql` and then reinstall the new `legacy.sql` file..
-The `legacy.sql` scripts are generally located in your PostgreSQL `share\contrib\postgis` directory. For example, with a 9.4 PostgreSQL and 2.1 PostGIS:
+The `legacy.sql` scripts are generally located in your PostgreSQL `share\contrib\postgis` directory. For example, with a 9.4 PostgreSQL and 2.1 PostGIS:
```sh
# Remove the old functions
diff --git a/content/documentation/tips/st-dwithin.md b/content/documentation/tips/st-dwithin.md
index 1a755a0..274ca5d 100644
--- a/content/documentation/tips/st-dwithin.md
+++ b/content/documentation/tips/st-dwithin.md
@@ -8,6 +8,7 @@ date: "2013-08-26"
thumbnail:
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 10
---
If you have a problem that involves finding the things within X distance of other things or finding what things "have nothing within X distance" do not use `ST_Distance` for filtering and also do not try to use [ST_Intersects](/docs/ST_Intersects.html) with [ST_Buffer](/docs/ST_Buffer.html).
diff --git a/content/documentation/tips/st-set-or-transform.md b/content/documentation/tips/st-set-or-transform.md
index 872cf28..4f84bb1 100644
--- a/content/documentation/tips/st-set-or-transform.md
+++ b/content/documentation/tips/st-set-or-transform.md
@@ -8,6 +8,7 @@ date: "2013-08-30"
thumbnail:
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 20
---
People often get confused between the [ST_Transform](/docs/ST_Transform.html) and [ST_SetSRID](/docs/ST_SetSRID.html) functions.
@@ -33,7 +34,7 @@ Your data is WGS 84 long lat, and you tagged it correctly but you want it in US
```postgres
ALTER TABLE mytable
- ALTER COLUMN geom
+ ALTER COLUMN geom
TYPE geometry(MultiPolygon, 2163)
USING ST_Transform(geom, 2163);
```
@@ -43,7 +44,7 @@ You brought your data in as unknown, you know its wgs 84 lon lat, but you want t
```postgres
ALTER TABLE mytable
- ALTER COLUMN geom
+ ALTER COLUMN geom
TYPE geometry(MultiPolygon, 2163)
USING ST_Transform(ST_SetSRID(geom, 4326), 2163);
```
diff --git a/content/documentation/tips/tip-move-postgis-schema.md b/content/documentation/tips/tip-move-postgis-schema.md
index f52f6e3..e64703d 100644
--- a/content/documentation/tips/tip-move-postgis-schema.md
+++ b/content/documentation/tips/tip-move-postgis-schema.md
@@ -9,6 +9,7 @@ date: "2017-11-07"
thumbnail:
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 100
---
As of PostGIS 2.3, the postgis extension was changed to no longer allow relocation. All function calls within the extension are now schema qualified.
diff --git a/content/documentation/tips/tip-removing-raster-from-2-3.md b/content/documentation/tips/tip-removing-raster-from-2-3.md
index 199f114..72d912a 100644
--- a/content/documentation/tips/tip-removing-raster-from-2-3.md
+++ b/content/documentation/tips/tip-removing-raster-from-2-3.md
@@ -9,6 +9,7 @@ thumbnail:
date: "2023-02-03"
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 30
---
As of PostGIS 3.0, the PostGIS raster support is no longer part of the
diff --git a/content/documentation/tips/tip-upgrading-postgis-sfcgal.md b/content/documentation/tips/tip-upgrading-postgis-sfcgal.md
index 0295148..eb882d6 100644
--- a/content/documentation/tips/tip-upgrading-postgis-sfcgal.md
+++ b/content/documentation/tips/tip-upgrading-postgis-sfcgal.md
@@ -9,6 +9,7 @@ thumbnail:
date: "2022-08-25"
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 100
---
As of PostGIS 3.1, the PostGIS sfcgal support library is no longer part of the
@@ -72,4 +73,4 @@ ALTER EXTENSION postgis UPDATE;
SELECT postgis_extensions_upgrade();
```
-Then run `pg_upgrade` as usual.
\ No newline at end of file
+Then run `pg_upgrade` as usual.
diff --git a/content/documentation/tips/tip-upgrading-raster-from-2-3.md b/content/documentation/tips/tip-upgrading-raster-from-2-3.md
index cee76d5..d2fe5f9 100644
--- a/content/documentation/tips/tip-upgrading-raster-from-2-3.md
+++ b/content/documentation/tips/tip-upgrading-raster-from-2-3.md
@@ -9,6 +9,7 @@ thumbnail:
date: "2022-01-14"
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 30
---
As of PostGIS 3.0, the PostGIS raster support is no longer part of the
diff --git a/content/documentation/tips/tip_count_of_pixel_values.md b/content/documentation/tips/tip_count_of_pixel_values.md
index c18c5f2..8b0090b 100644
--- a/content/documentation/tips/tip_count_of_pixel_values.md
+++ b/content/documentation/tips/tip_count_of_pixel_values.md
@@ -9,6 +9,7 @@ thumbnail:
date: "2014-09-26"
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 50
---
PostGIS raster has so so many functions and probably at least 10 ways of doing something some much much slower than others. Suppose
diff --git a/content/documentation/tips/tip_enable_raster_drivers.md b/content/documentation/tips/tip_enable_raster_drivers.md
index d885313..71962c2 100644
--- a/content/documentation/tips/tip_enable_raster_drivers.md
+++ b/content/documentation/tips/tip_enable_raster_drivers.md
@@ -9,6 +9,7 @@ date: "2015-05-02"
thumbnail:
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 50
---
I've been asked this question in some shape or form at least 3 times, mostly from people puzzled why they get this error.
diff --git a/content/documentation/tips/tip_intersection_faster.md b/content/documentation/tips/tip_intersection_faster.md
index 9130339..e814296 100644
--- a/content/documentation/tips/tip_intersection_faster.md
+++ b/content/documentation/tips/tip_intersection_faster.md
@@ -9,6 +9,7 @@ thumbnail:
date: "2014-03-14"
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 25
---
Doing an <a href="/docs/manual-dev/ST_Intersection.html" target="_blank">```ST_Intersection```</a> is much slower than relation checks such as
diff --git a/content/documentation/tips/tip_pgadmin_shows_no_data.md b/content/documentation/tips/tip_pgadmin_shows_no_data.md
index 9c997b1..2cb0df4 100644
--- a/content/documentation/tips/tip_pgadmin_shows_no_data.md
+++ b/content/documentation/tips/tip_pgadmin_shows_no_data.md
@@ -9,6 +9,7 @@ date: "2013-10-05"
thumbnail:
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 90
---
Every one or two months, someone asks on the PostGIS users list usually somewhat panicked, *My geometry is missing when I look in pgAdmin III*
diff --git a/content/documentation/tips/tip_pixels_of_range_value.md b/content/documentation/tips/tip_pixels_of_range_value.md
index 5fc5b84..d7477f7 100644
--- a/content/documentation/tips/tip_pixels_of_range_value.md
+++ b/content/documentation/tips/tip_pixels_of_range_value.md
@@ -9,6 +9,7 @@ date: "2016-03-13"
thumbnail:
geekdocHidden: true
geekdocHiddenTocTree: false
+weight: 40
---
This raster question comes up quite a bit on PostGIS mailing lists and stack overflow and the best answer often involves
-----------------------------------------------------------------------
Summary of changes:
content/documentation/tips/lon-lat-or-lat-lon.md | 7 ++++---
content/documentation/tips/postgis-backend-is-already-set.md | 5 +++--
content/documentation/tips/st-dwithin.md | 1 +
content/documentation/tips/st-set-or-transform.md | 5 +++--
content/documentation/tips/tip-move-postgis-schema.md | 1 +
content/documentation/tips/tip-removing-raster-from-2-3.md | 1 +
content/documentation/tips/tip-upgrading-postgis-sfcgal.md | 3 ++-
content/documentation/tips/tip-upgrading-raster-from-2-3.md | 1 +
content/documentation/tips/tip_count_of_pixel_values.md | 1 +
content/documentation/tips/tip_enable_raster_drivers.md | 1 +
content/documentation/tips/tip_intersection_faster.md | 1 +
content/documentation/tips/tip_pgadmin_shows_no_data.md | 1 +
content/documentation/tips/tip_pixels_of_range_value.md | 1 +
13 files changed, 21 insertions(+), 8 deletions(-)
hooks/post-receive
--
postgis.net
More information about the postgis-tickets
mailing list