On Wed, May 08, 2024 at 05:53:48PM -0400, Regina Obe wrote:
> On Wed, May 08, 2024 at 03:01:47PM -0500, Daryl Herzmann wrote:
> >
> > I stumbled into this issue today. The lack of 9311 in spatial_ref_sys. Is
> > a fix
> > for this coming or is the spatial_ref_sys just known to be stale and not
On Wed, Feb 14, 2024 at 05:09:44PM +0400, Arnaud Vandecasteele wrote:
> The default_version is still 3.2.3 and I suppose this is why postgis
> doesn't really upgrade. It only keeps the same version.
>
> Do you know how I could resolve this issue ?
Whichever version is installed last determines
On Thu, Jan 11, 2024 at 07:15:02PM +0100, Sandro Santilli via postgis-users
wrote:
> We've changed the configuration of this mailing list to respect the
> recomendations from the SysAdmin team:
>
> https://wiki.osgeo.org/wiki/SAC:Mailing_Lists#Configuring_the_mailing_list
H
We've changed the configuration of this mailing list to respect the
recomendations from the SysAdmin team:
https://wiki.osgeo.org/wiki/SAC:Mailing_Lists#Configuring_the_mailing_list
Notable changes are:
1. No more [postgis-users] prefix in email subjects
2. No more added footer
3.
On Wed, Nov 08, 2023 at 10:05:39AM +, Alexandre Neto wrote:
> Thanks Sandro, I will. And I will try to PR on the documentation.
>
> One extra question. When I add a topoGeometry column to a table with a
> geometry column, in QGIS, I now fail to be able to edit the table. It seems
> that the
iginal geometry is changed.
>
>Thanks,
>
>Alexandre Neto
>
>On Tue Nov 7, 2023, 11:33 AM GMT, Sandro Santilli <mailto:s...@kbt.io> wrote:
>> On Thu, Nov 02, 2023 at 03:26:22PM +, Alexandre Neto via postgis-users
>> wrote:
>>> UPDATE te
On Thu, Nov 02, 2023 at 03:26:22PM +, Alexandre Neto via postgis-users
wrote:
> UPDATE temp.troco SET
> topo = totopogeom(geom, 'master_topology',1)
[..]
> Now I decided to remove one of the linestrings that splited two polygons.
>
> And I rerun the updated on the topo columns:
>
>
On Fri, Sep 01, 2023 at 12:04:12AM -0400, Regina Obe wrote:
> Weblate.osgeo.org requires an osgeo account.
> Which you can get here:
> https://id.osgeo.org/ldap/create
>
> You can use it to:
> 1.File bug reports in PostGIS bug tracker https://trac.osgeo.org/postgis
Also file or comment on
On Thu, Aug 31, 2023 at 11:14:21AM +, atanga MARCELIUS via postgis-users
wrote:
> As mentioned earlier I tried the soft upgrade and it failed.
Did you also mention how it failed ?
The failure below is NOT what you'd get with Regina's instructions
> > x=# ALTER EXTENSION postgis UPDATE
On Thu, Aug 24, 2023 at 10:13:39AM +0200, Sandro Santilli wrote:
> On Thu, Aug 24, 2023 at 10:01:56AM +0200, Sandro Santilli wrote:
> > On Wed, Aug 23, 2023 at 08:38:54PM -0400, Greg Troxel wrote:
> > > Sandro Santilli writes:
> > >
> > > > On Wed,
On Thu, Aug 24, 2023 at 10:01:56AM +0200, Sandro Santilli wrote:
> On Wed, Aug 23, 2023 at 08:38:54PM -0400, Greg Troxel wrote:
> > Sandro Santilli writes:
> >
> > > On Wed, Aug 16, 2023 at 08:46:08AM +0200, Paolo Cavallini wrote:
> > >> Dear admin,
On Wed, Aug 23, 2023 at 08:38:54PM -0400, Greg Troxel wrote:
> Sandro Santilli writes:
>
> > On Wed, Aug 16, 2023 at 08:46:08AM +0200, Paolo Cavallini wrote:
> >> Dear admin,
> >> the list, as many @osgeo were, is misconfigured for its DMARC. I suggest to
&
On Wed, Aug 23, 2023 at 10:08:23AM +, atanga MARCELIUS wrote:
> x=# ALTER EXTENSION postgis UPDATE TO '2.5.5';
> ERROR: extension "postgis" does not exist
The above message means that database "x" does not contain
the "postgis extension". This does not necessarely mean it doesn't
Hi WangDapeng,
On Wed, Aug 23, 2023 at 02:00:31PM +0800, Light wrote:
> I see that the Chinese translation of the documentation is missing and I
> want to contribute. We submit 3-4 files per week.
There's some simplified chinese translation on weblate:
On Wed, Aug 23, 2023 at 12:36:58PM +0200, Nicolas Ribot wrote:
> (OpenJump is a GIS software that can display such views/tables
> containing heterogeneous geometry types, as QGIS does not like them)
I believe recent QGIS versions do support views with heterogeneous
geometries, not in the same
On Wed, Aug 16, 2023 at 08:46:08AM +0200, Paolo Cavallini wrote:
> Dear admin,
> the list, as many @osgeo were, is misconfigured for its DMARC. I suggest to
> change one of the settings.
Hi Paolo, thanks for the heads up.
I've followed Markus Neteler's recipe here:
Patch release 3.3.4 is now available.
Details and download links can be found at:
http://postgis.net/2023/07/PostGIS-3.3.4-Patch-Release/
Thanks,
The PostGIS Development Team
___
postgis-users mailing list
postgis-users@lists.osgeo.org
On Wed, May 17, 2023 at 01:14:27PM +0200, Michal Seidl wrote:
> this SQL puts my Postgre into recovery mode for some seconds?
> The rason seems to be when nprefix parametr is set to ''.
Thanks, confirmed and filed as a ticket:
https://trac.osgeo.org/postgis/ticket/5384
--strk;
On Fri, May 12, 2023 at 12:13:29PM +0200, Sandro Santilli wrote:
> On Tue, May 09, 2023 at 03:59:13PM +0530, Nikhil Shetty wrote:
>
> > I installed 3.1.5 but we are still having the same issue when upgrading
> >
> > dbname=# alter extension postgis update ;
> [
On Tue, May 09, 2023 at 03:59:13PM +0530, Nikhil Shetty wrote:
> I installed 3.1.5 but we are still having the same issue when upgrading
>
> dbname=# alter extension postgis update ;
[...]
> ERROR: cannot drop function st_distance(geography,geography) because other
> objects depend on it
>
hip at extension packaging
time (Sandro Santilli)
Thanks to Sven Klemm (Timescale) for the report
- #5241, Crash on ST_SnapToGrid with empty multis (Regina Obe)
- #5234, Fix 2.5d topology building regression (Sandro Santilli)
- #5280, Handle load of dbase character fie
On Mon, Apr 17, 2023 at 04:56:06PM +0200, Sandro Santilli wrote:
> On Mon, Apr 17, 2023 at 03:18:50PM +0530, Nikhil Shetty wrote:
>
> > DETAIL: view x depends on function st_buffer(geometry,double precision)
> > DETAIL: function x depends on function
> >
On Mon, Apr 17, 2023 at 03:18:50PM +0530, Nikhil Shetty wrote:
> DETAIL: view x depends on function st_buffer(geometry,double precision)
> DETAIL: function x depends on function st_intersection(geometry,geometry)
> DETAIL: view x depends on function
On Fri, Apr 14, 2023 at 01:29:02PM +0530, Nikhil Shetty wrote:
> geo=# alter extension postgis update to '3.1.2';
> ERROR: could not access file "$libdir/postgis-2.5": No such file or directory
[...]
> We removed the old 2.5.4 packages and installed 3.1.2
>
> ls -l /usr/pgsql-10/lib | grep
On Wed, Feb 08, 2023 at 02:44:54PM -0500, Regina Obe wrote:
> Your topo should be a collection of topo elements, not the collection of
> primitives that make up the topo.
I suggest to use different wording, as "topo" is too vague :)
So I'd reword as:
Your TopoGeometry should be defined by a
On Tue, Jan 24, 2023 at 01:55:44AM -0500, Regina Obe wrote:
> Strk, remind me why we have these notices, I think it just confuses people
> more than being helpful.
Debugging left over, I've changed that in commit 0e97ae29e to:
- RAISE NOTICE 'Extension % is not available or not packagable for
On Tue, Dec 20, 2022 at 12:02:03PM -0500, Regina Obe wrote:
> Sandro and Paul, is there any way we can expose the compiled version of GEOS
> and Proj?
I don't think there's a speicific function but some functions
do include the compiled-in version in the error message, like
ST_FrechetDistance
On Tue, Dec 13, 2022 at 11:31:05AM -0800, Paul Ramsey wrote:
> Just to put a nail in this one: the last time our selectivity estimates for
> Contains/Within were good was version 2.1, which used the && operator instead
> of hte ~/@ operators in the SQL wrapper functions.
I think I was the one
On Wed, Dec 07, 2022 at 11:13:08AM +0100, Douglas Fan wrote:
> I am trying to build topology on PostGIS with 4000+ polygons. The input are
> not clean, with overlaps and gaps. I have created a procedure to commit
> each update statement for each polygon so that I can catch the exception
> and
On Tue, Sep 06, 2022 at 09:50:04AM +, Alexandre Silva wrote:
> Hey Sandro,
>
> Thanks for your help.
> Here's the ticket in case anyone wants to follow this bug:
> https://trac.osgeo.org/postgis/ticket/5234
Thank you for your report.
The regression should now be fixed in all branches
(was
On Tue, Nov 01, 2022 at 10:07:34AM +0100, Chris Mair wrote:
> So the problem here was an optimization introduced in Postgres 12, in your
> case it did more harm than good:
> https://www.postgresql.org/docs/12/release-12.html#id-1.11.6.17.5.3.4
>
> Quote:
>
> Specifically, CTEs are
Sandro Santilli wrote (please quote with appropriate attribution):
> > This means that your current "default" PostGIS version is 2.4.9,
> > so "postgis_extensions_upgrade()" tries to upgrade to that version,
> > but it's actually a DOWNGRADE instead.
On
On Fri, Sep 30, 2022 at 09:25:38AM +0200, Giuseppe Naponiello wrote:
>
> POSTGIS="3.3.1 3786b21" [EXTENSION] PGSQL="130" GEOS="3.9.0-CAPI-1.16.2"
> PROJ="7.2.1" GDAL="GDAL 3.2.2, released 2021/03/05" LIBXML="2.9.10"
> LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" (core procs from
>
Hi Alexandre, I can reproduce the problem you reported with version
3.3.0, could you please file a ticket on trac.osgeo.org/postgis with
all the detail ? It sounds like a regression.
Use component "Topology" please.
I confirm using 2D only works fine.
Gory details: the problem likely lays in
On Mon, Aug 15, 2022 at 10:50:27AM +0200, Daniel Gustafsson wrote:
> > On 12 Aug 2022, at 18:29, Sandro Santilli wrote:
> > On Thu, Aug 11, 2022 at 09:44:52PM +0200, Daniel Gustafsson wrote:
> >>
> >> I've now upgraded to 3.2.2 and the issue remains. When buildi
On Thu, Aug 11, 2022 at 09:44:52PM +0200, Daniel Gustafsson wrote:
>
> I've now upgraded to 3.2.2 and the issue remains. When building and running
> make installcheck-upgrade against a 14.5 postgres cluster it fails with:
>
> NOTICE: Packaging extension postgis
> ERROR: function
On Wed, Jul 20, 2022 at 06:00:05PM +1000, Simon SPDBA Greener wrote:
> I could run up a quick test but does PostGIS topology have a mechanism for
> handling this situation? How does it handle linestrings defined as XYZ?
PostGIS Topology *forces* any planar intersection to generate a node.
On Fri, Jul 08, 2022 at 02:50:13PM +1000, Simon Greener wrote:
> To handle a change should I first delete the existing topogeom
> using clearTopoGeom() which modifies the underlying topology
What made you think clearTopoGeomy modifies the underlying topology ?
That function ONLY affects
On Fri, Jul 08, 2022 at 02:50:13PM +1000, Simon Greener wrote:
> QUESTION: If the new linestring that is added to the existing topology
> causes an existing underlying edge to change (eg split),
> what happens to any other topogeom objects in the table that reference the
> edge before it is
On Fri, Apr 15, 2022 at 09:08:09PM +0100, Shaozhong SHI wrote:
> This is very interesting.
>
> However, this needs to be further detailed with a table to explain a
> variety of cases and uses.
Here you can propose improvements in the workshop:
On Wed, Mar 16, 2022 at 09:20:10AM -0400, Greg Troxel wrote:
> Sandro Santilli writes:
>
> > Another solution proposed was to still keep a single table but NEVER
> > automatically upgrade it, providing a function to select "system
> > entries" to use for popula
Thanks Chris for your experience, comment below
On Tue, Mar 15, 2022 at 08:27:37PM -0700, Chris Tooley wrote:
> so I made sure
> I copied the original `proj4text` string and bit the bullet and modified
> the table with the following query:
>
> > update spatial_ref_sys set proj4text = '+proj=aea
On Sun, Feb 20, 2022 at 11:08:49AM -0500, Travis Kirstine wrote:
> Hi all I may have a relatively simple question but I don't have much
> experience with routing. I have a road network with topology built and I'd
> like to find the source and target ids from multiple edges. For example:
PostGIS
On Thu, Feb 17, 2022 at 08:21:24AM +, Shaozhong SHI wrote:
> Is there a function for calculating accumulative bearing given a
> zig-zagging line?
>
> If we set a segment to travel towards north and its bearing is 0. Next
> segment may zig-zag towards 10 degrees. The following one may zig-zag
On Mon, Feb 14, 2022 at 03:33:29PM -0500, Regina Obe wrote:
> the workaround is below, but not sure it will work on AWS
> RDS as updating system tables might be off limits.
>
> UPDATE pg_extension SET extversion = 'ANY'
> WHERE extname = 'postgis';
Allan: please let us know if AWS RDS allows or
On Thu, Feb 10, 2022 at 09:10:38AM -0600, Jim Klassen wrote:
>
> How do other people handle conflicting srids?
That's a good question. For sure at the time PostGIS doesn't
give official advice about this. Current state of things is:
- PostGIS upgrade via EXTENSION won't touch spatial_ref_sys
On Wed, Feb 09, 2022 at 01:28:13PM +, Robert Coup wrote:
> On Fri, 4 Feb 2022 at 17:05, Sandro Santilli wrote:
> > - Do you ever update the table with entries from newer
> > spatial_ref_sys.sql ?
>
> Yes. We keep postgis' spatial_ref_sys synchronised with the Pr
On Thu, Feb 10, 2022 at 10:43:29AM -0800, Paul Ramsey wrote:
> > On Feb 10, 2022, at 7:10 AM, Jim Klassen wrote:
> > How do other people handle conflicting srids?
>
> My guess is that it's pretty rare, since most people who have defined
> custom ranges for operational use have done what you
On Wed, Feb 09, 2022 at 09:55:14AM -0600, Jim Klassen wrote:
> I always thought it
> was cumbersome that I had to maintain the custom coordinate system in
> so many places (PROJ, PostGIS, older versions of GDAL, older versions
> of QGIS) when most of them are reaching back to PROJ to do the
On Fri, Feb 04, 2022 at 04:23:48PM -0600, Jim Klassen wrote:
> We've been starting at 20 and using EPSG
I shall note 200,000 is also not in the "user range" as proposed in
https://lists.osgeo.org/pipermail/postgis-devel/2012-February/018440.html
The official PostGIS Manual doesn't
include an entry for SRID=6933?
--strk;
>
> On 2/4/22, 12:04 PM, "postgis-users on behalf of Sandro Santilli"
> wrote:
>
> * CAUTION: This email originated from an outside source. Do not click
> links or open attachments unless you know they are s
Thanks for answering Paul, more question inline
On Fri, Feb 04, 2022 at 05:21:23PM +, Moen, Paul T. wrote:
> We have 54 custom entries that we store in spatial_ref_sys.sql.
Do you mean in the "spatial_ref_sys" PostgreSQL table or in the
"spatial_ref_sys.sql" file ?
How do you decide what
Following earlier may from Regina, I'm writing this as a user
inquiry, to get help in shaping the future of PostGIS handling
of custom CRSs.
The question I have for you is: do you keep your custom CRSs
in the spatial_ref_sys table ? If so:
- How many ?
- Do you also keep the entries
On Tue, Jan 11, 2022 at 05:45:16PM +, Nathan Wagner wrote:
> Could this have been done via 'create extension postgis from unpackaged'?
> I think that doesn't work for an in-place upgrade because it can't
> handle converting the internal representation.
You are right: "create extension from
On Mon, Jan 10, 2022 at 10:18:34AM -0800, Paul Ramsey wrote:
> > On Jan 10, 2022, at 10:01 AM, Nathan Wagner wrote:
>
> > So, why exactly is a hard upgrade needed from 1.5 to 2.5?
>
> Because the pg_dump, pre-2.0 would include all the function definitions
I think the correct answere here is:
I'm rewriting core PostGIS Topology function to speedup
topology population, with a focus on finding faces
_properly_ containing a point (having the point on the
interior, not on the boundary).
We currently have a topology.GetFaceByPoint function
which I'm tempted to re-use as a signature for the
On Sun, Apr 18, 2021 at 02:42:14PM +0200, Marco Boeringa wrote:
> Hi Sandro,
>
> Thanks for the answer, but this just raises a question, why was the
> official PostGIS 3.1.1 as available in the
>
> "http://apt.postgresql.org/pub/repos/apt/focal-pgdg main"
>
> repository, not compiled with GEOS
On Sat, Apr 17, 2021 at 09:01:33AM +0200, Marco Boeringa wrote:
> Before I upgraded libgeos from the ubuntugis repository,
> "PostGIS_Full_Version()" showed GEOS 3.8.0.
>
> So how do I potentially solve this? Or is this upgrade of GEOS only possible
> by compiling PostGIS from source yourself
On Mon, Jan 25, 2021 at 10:19:42AM +0300, Fatih Sazan wrote:
> When I run my code running on PostGIS version 2.5, I don't get an error but
> when I run it on 3.1 it the server gives an error and enters the recovery
> mode every time.
> Operating System: CentOS Linux 8
> CPE OS Name:
On Wed, Dec 23, 2020 at 05:38:23PM +0100, Andreas Neumann wrote:
> Hm, seems like it is still not good in master.
>
> As soon as I add "ST_MakeValid()" in the same SQL query, it goes back to
> "weird" mode.
Then there must be another memory issue. It would help to have a
sample of geoms which
On Wed, Dec 23, 2020 at 04:51:07PM +0100, Andreas Neumann wrote:
> Hi Strk and Nicolas,
>
> Thanks for your replies.
>
> I'm using GEOS 3.9, PostgreSQL 13.1 and Postgis 3.1 (self-compiled).
>
> The situation is really weird: if I run the same SQL query a second
> time, the contradiction is gone
On Wed, Dec 23, 2020 at 11:20:07AM +0100, Andreas Neumann wrote:
> Hi,
>
> I have the strange situation that ST_IsValid() claims a geometry is not
> valid, but then ST_IsValidReason() says 'Valid Geometry'
>
> Here is my query:
>
> SELECT
> t_id,
> ST_AsText(ST_MakeValid(geometrie)) AS
On Fri, Nov 20, 2020 at 04:55:06PM +, Alexandre Silva wrote:
> The slower ordering method results in the whole area being added to the
> topology in a layered style (rivers, roads, rural areas, etc.) and after the
> first one, there are already some faces with a large area, and the
>
On Mon, Oct 12, 2020 at 02:48:38PM -0700, Willem Buitendyk wrote:
> I recently upgraded Postgres and postgis to 13 and 3 respectively.
> Everything seems to be working but when I run:
>
> SELECT PostGIS_Full_Version();
>
> I’m seeing this: POSTGIS="3.0.2 2fb2a18" [EXTENSION] PGSQL="96" (procs
On Fri, Oct 09, 2020 at 10:16:43AM -0400, Brad Dworak wrote:
> gserialized_gist.c:12:10: fatal error: postgres.h: No such file or directory
[...]
> I'm running Ubuntu 18.04 and have
> PostGreSQL 11, 12, and 13 (specifically postgresql-13-postgis-3) installed.
You need the development packages:
On Tue, Aug 04, 2020 at 08:46:39AM -0700, Martin Davis wrote:
> The ST_ClosestPoint function (and the Linear Referencing functions) do have
> the segment index information internally. It would be nice if there was an
> extended version of ST_ClosestPoint which returned a record with both the
>
On Fri, Jun 12, 2020 at 09:18:22AM +, paul.m...@lfv.se wrote:
> Hi,
> If someone could help me with this, I would be grateful.
> I've converted a polygon layer to a line layer. Sometimes the lines segments
> are a duplicate of another line segment (from an adjacent polygon).
> I would like to
On Sat, Jun 06, 2020 at 07:33:59PM +0300, Darafei "Komяpa" Praliaskouski wrote:
> Best way to get it fixed is to stomp it into a Github pull request with
> minimized version of your case in regress suite.
There are different point of views on the matter. Best way to get it
fixed is surely fixing
On Fri, Mar 27, 2020 at 03:30:09PM +0100, Paolo Cavallini wrote:
>
>
> Il 27/03/20 14:41, Sandro Santilli ha scritto:
> > On Fri, Mar 27, 2020 at 11:22:17AM +0100, Paolo Cavallini wrote:
> >> Hi all,
> >> sorry for the noise, probably not the best cahnnel
On Fri, Mar 27, 2020 at 11:22:17AM +0100, Paolo Cavallini wrote:
> Hi all,
> sorry for the noise, probably not the best cahnnel to report this, but
> in https://postgis.net/support/ there is a broken link:
> http://refcardz.dzone.com/refcardz/essential-postgis
Here's how you do:
[ please keep postgis-users in the loop ]
On Wed, Mar 04, 2020 at 02:01:37PM +, paul.m...@lfv.se wrote:
> Thanks Sandro!
> I understand a bit more now, I'm quite new at this.
> And I have no idea how to:
> --> Instead, you'll want to make sure each and every face is assigned to one
> (and
On Wed, Mar 04, 2020 at 07:04:57AM +, Lars Aksel Opsahl wrote:
> When testing adding millions of linestrings by splitting in around 4000
> content based cells, one cell was using hours for adding a few thousands
> lines , but by changing the order and adding the non-closed line strings
>
On Wed, Mar 04, 2020 at 07:11:30AM +, paul.m...@lfv.se wrote:
> In both topo1- and topo2.face shows a box where Egypt is located, as for all
> other countries (type of bounding box?).
> In both topo1- and topo2.edge_data shows all countries as well as Egypt.
Ok, so the topology was fully
On Tue, Mar 03, 2020 at 02:30:11PM +, paul.m...@lfv.se wrote:
> Hi,
> I'm not sure of what you mean, Strk.
> I create a topology (topo1) with all geometries from a polygon layer.
> I can see the island and the Egypt polygon in the edge_data, they are not
> intersecting.
>
> Then I create a
On Tue, Mar 03, 2020 at 10:12:05AM +, paul.m...@lfv.se wrote:
> There was no difference between st_union() and st_unaryunion() when merging
> all adjacent polygons to larger polygons.
> The st_buffer() method is 3.5 times faster.
The reason why ST_Buffer is faster is because it builds the
On Fri, Feb 28, 2020 at 10:35:48AM +, paul.m...@lfv.se wrote:
> Thanks, Sandro!
> It worked with your LOOP! Great!
> The problem I can see on the result (I'm simplifying country polygons) is
> that the large polygon of Finland, Germany, Italy and Egypt is missing.
Did you get the WARNING for
On Mon, Mar 02, 2020 at 02:25:52PM +, paul.m...@lfv.se wrote:
> Hi list,
> I would like to do this:
> CREATE TABLE public."Areas_union" AS select
> (st_dump(st_union("the_geom"))).geom from "Areas";
>
> But it takes such a long time to execute, is there a smarter way to do it?
Try this:
On Fri, Feb 28, 2020 at 12:29:49PM +, paul.m...@lfv.se wrote:
> Hi again,
> I can see in the edge data of topo2 that the main polygon of Egypt intersects
> with an island next to the main polygon. If I delete the island in the
> original layer before running the SQL sequence the main polygon
On Wed, Feb 26, 2020 at 11:10:36AM +, Lars Aksel Opsahl wrote:
> Yes I can do that but then I have to remove this extra lines when done.
> This should by able to do by checking if two faces that share edge belongs
> the same original polygon.
Yes, it is a way.
> If checkout this code "git
On Wed, Feb 26, 2020 at 09:59:52AM +, Lars Aksel Opsahl wrote:
> * The output from pg_stat_statements is below, The only strange thing I
> see here is that the query “SELECT edge_id,geom FROM
> "test_topo_ar5".edge_data WHERE edge_id IN ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,”
> has length of
On Tue, Feb 25, 2020 at 01:22:39PM +, paul.m...@lfv.se wrote:
> Hi,
> Where do you mean I can play with the tolerance?
In TopoGeo_addLinestring
https://postgis.net/docs/manual-3.1/TopoGeo_AddLineString.html
> This is what I have done before the ST_createTopoGeo
> SELECT
On Tue, Feb 25, 2020 at 12:10:07PM +, paul.m...@lfv.se wrote:
>
> Hi,
> I'm running this command:
> SELECT topology.ST_CreateTopoGeo('topo1',ST_Collect("geom")) from
> "countries_first";
>
> and are getting this message:
> ERROR: Corrupted topology: adjacent edges 71 and -72 bind different
On Mon, Feb 10, 2020 at 06:01:40PM -0500, Diego Vargas wrote:
> Hello, I am using pgsql2shp and shp2pgsql to dump and load a table with gis
> data, and I’m getting the following message:
>
> "WARNING: Cannot determine spatial reference (empty table or unknown spatial
> ref). No prj file will be
On Mon, Jan 13, 2020 at 05:54:50PM -0800, john polo wrote:
> error: type "raster" does not exist
>
> Searching for some help, I came across the note from
> https://postgis.net/docs/manual-3.0/raster.html
[...]
> SELECT postgis_full_version();
[...]
> POSTGIS="3.0.0 r17983" [EXTENSION]
On Thu, Nov 21, 2019 at 07:26:47PM +0100, Sandro Santilli wrote:
> That said, -0 for the GitHub button, +1 for the other two :)
On double-checking, the Gitea repository mirror, being a mirror,
does not online-editing (turning it in a non-mirror would require work).
The GitLab one does:
ht
On Thu, Nov 21, 2019 at 01:05:23PM -0500, Regina Obe wrote:
> Our workshop page is a great learning page
>
> https://postgis.net/workshops/postgis-intro/
> I'm proposing we put two links
>
> "Edit this on Github"
> "Edit this on Gitea"
>
>
> We can accept pull requests from both places and I
On Sun, Oct 27, 2019 at 03:52:37PM -0700, Paul Ramsey wrote:
> Until the library loads the system doesn’t know about the GUCs. And querying
> the GUCs doesn’t for a library load (the system doesn’t having a binding from
> GUC to library). Querying a function, on the other hand, forces a load.
>
On Wed, Sep 04, 2019 at 11:20:33AM -0400, Regina Obe wrote:
> We allow people to have custom srids – that bit is to prevent our
> SRIDs from being backed up. So the only srids backed up are the ones
> not in our list..
That's the list coming with new release, right ?
I've been calling for an
On Thu, Jun 27, 2019 at 06:55:39PM +0200, olivier.lo...@umontpellier.fr wrote:
>
> > Le 27 juin 2019 à 17:59, Sandro Santilli a écrit :
> >
> > On Thu, Jun 27, 2019 at 12:46:03PM +0200, olivier.lo...@umontpellier.fr
> > wrote:
> >
> >> at line 2
On Thu, Jun 27, 2019 at 12:46:03PM +0200, olivier.lo...@umontpellier.fr wrote:
> at line 248, substring(upgraded from '[0-9]*\.([0-9]*)\.’) cannot be cast to
> int since it leads ‘’ because of the « SELECT '2.2'::text as upgraded » at
> line 242.
>
> replacing SELECT '2.2'::text as upgraded
On Wed, Jun 26, 2019 at 11:20:59AM +0200, olivier.lo...@umontpellier.fr wrote:
> Hi,
>
> On a postgresql 9.3 / postgis 2.1.8 / debian 8.11, I cannot upgrade postgis
> to 2.2.2 (or 2.3.3) :
>
> # ALTER EXTENSION postgis UPDATE TO '2.2.2';
> WARNING: nonstandard use of escape in a string
On Fri, Jun 07, 2019 at 10:02:23AM +, Lars Aksel Opsahl wrote:
> So the problem is how to use tolerances so we get a behavior equal to
> the test using meter.
>
>
> We can we define the layer in Postgis Topology with quite big value
> because this is just max value as it seems. So we can
On Mon, May 20, 2019 at 12:35:40PM +, Zwettler Markus (OIZ) wrote:
> You also think the errors are due to the version mismatch.
Is that a question ? If it is, my answer is: NO.
ERROR: relation "geometry_columns" already exists
It means PostGIS is already installed in the target DB, and
On Mon, May 20, 2019 at 07:16:15AM +, Zwettler Markus (OIZ) wrote:
> We tried to pg_restore this dump into a database with and without pre-created
> postgis extension. We got postgis errors in any case.
Check out postgis_restore.pl, to be used in place of pg_restore.
Is part of the postgis
On Thu, May 16, 2019 at 01:09:54PM +, Zwettler Markus (OIZ) wrote:
> We did a default PostGIS installation within a PostgreSQL 9.6 database:
>
> ===
> create extension if not exists postgis;
> create extension if not exists postgis_topology;
> create extension if not exists ogr_fdw;
> create
On Thu, Apr 04, 2019 at 08:33:47AM +0200, Paolo Cavallini wrote:
> solved by forcing install of official deb postgresql-9.4-postgis-2.1
> from there on, things work. so, why does apt remove the needed package?
> it seems appropriate to me keeping it until postgresql 9.4 is purged.
> am I missing
On Wed, Apr 03, 2019 at 07:34:33PM +0200, Paolo Cavallini wrote:
>
>
> On 03/04/19 19:04, Sandro Santilli wrote:
> > Can you show the ALTER EXTENSION command you're issuing and the
> > error you're getting ? Also please show the output of
> >
> > SELECT pos
On Wed, Apr 03, 2019 at 06:52:40PM +0200, Paolo Cavallini wrote:
> On 03/04/19 18:32, Sandro Santilli wrote:
>
> > In theory, any such function would be replaced by running
> > a soft upgrade of PostGIS in that database.
>
> how do I do a soft upgrade, given t
On Wed, Apr 03, 2019 at 06:20:22PM +0200, Paolo Cavallini wrote:
> On 03/04/19 18:10, Paul Ramsey wrote:
> >> On Apr 3, 2019, at 9:08 AM, Paolo Cavallini wrote:
> >>
> >> Hi all,
> >> I'm on a difficult situation: a debian sever with a pg9.4/pgis2.1 db has
> >> been upgraded to stretch, therefore
On Tue, Mar 26, 2019 at 02:07:55PM +, paul.m...@lfv.se wrote:
> UPDATE merged SET topo_geom = topology.toTopoGeom(the_geom, 'roads_topo', 1,
> 0.001);
[...]
> I get the following error:
> ERROR: Error: SQL/MM Spatial exception - geometry crosses edge 8618 CONTEXT:
> PL/pgSQL-function
1 - 100 of 420 matches
Mail list logo
