pg.ddx.io postgis-users@lists.osgeo.org mailing list archive (PostGIS users)
help / color / mirror / Atom feed[postgis-users] (no subject)
131+ messages / 102 participants
[nested] [flat]
* [postgis-users] (no subject)
@ 1970-01-01 00:00 songsubo <songsubo@163.com>
0 siblings, 0 replies; 131+ messages in thread
From: songsubo @ 1970-01-01 00:00 UTC (permalink / raw)
Use geos.
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2002-05-31 11:11 molinet <molinet@ibp.u-psud.fr>
0 siblings, 0 replies; 131+ messages in thread
From: molinet @ 2002-05-31 11:11 UTC (permalink / raw)
Which are the additional functionalities of POSTGIS
compared to postgreSQL? are there additional geometrical types,
operators and functions ? which are there ?
thanks for your help
Institut de Biotechnologie des Plantes
Universit? Paris Sud XI
MOLINET S.
t?l 01 69 15 33 85
fax 01 69 15 34 25
molinet at ibp.u-psud.fr
www.ibp.u-psud.fr
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2002-07-27 19:46 David Garnier <david.garnier@etudier-online.com>
0 siblings, 0 replies; 131+ messages in thread
From: David Garnier @ 2002-07-27 19:46 UTC (permalink / raw)
Hello,
WKB4J is a small Java toolkit designed to parse WKB data stored in a PostGIS database and convert it into Java objects. WKB4J implements the Simple Features Specification for SQL as defined by the OpenGIS consortium.
WKB4J is lean and mean, meaning that speed and reduced memory footprint where the primary concern. WKB4J is approximately 3 to 10 times faster than going through the WKT format. One other problem is that there are many Java geographical toolkit around, so WKB4J was built with portability in mind. Thoses concerns are highlighted in the design of the library. Right now, WKB4J supports the following toolkits:
* OpenMap
* JTS
* PostGIS
If your preferred toolkit isn't supported, building support for it is an easy job if your design is close to Simple Features Specification for SQL.
WKB4J is still in beta. It is a small and focused library, so it should'nt stay in beta for too long. The design and implementation is done but the code hasn't been tested enough.
For now, discussions of the WKB4J toolkit will take place in the postgis-user mailing list.
WKB4J is available here: http://wkb4j.etudier-online.com/. This website contains a more detailed overview of WKB4J. It is released under the GPL.
Feel free to use it, extend it, hack it, abuse it. If you have problems with the library, you're welcome to send me an email and I will do my best to solve your problems. Patches are welcome too!
Best Regards,
David Garnier
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2002-09-25 23:08 Noel Nasayao <ini_47@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: Noel Nasayao @ 2002-09-25 23:08 UTC (permalink / raw)
I'm a new user of postgis... and honestly i find it a bit hard to establish a good grasp on the geometry functionalities of this postgresql extension... can anyone be kind enough to refer me to any existing websites regarding as to how the these functions manipulate shapefiles??? or are there any existing documentations (detailed) regarding them?? thanks guys!
---------------------------------
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20020925/46fa0bf7/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2002-09-25 23:29 Tyler Mitchell <TMitchell@lignum.com>
0 siblings, 0 replies; 131+ messages in thread
From: Tyler Mitchell @ 2002-09-25 23:29 UTC (permalink / raw)
Are you already familiar with postgresql in itself and the concept of
relational databases? If so, think of postgis as adding (among other
things) simply another data type called "geometry". Rather than just
storing text and number attributes in the tables, you can also store
geometry (that is, sets of coordinates that define points, lines, polygons,
etc.). It doesn't run off or manipulate shapefiles - but there are tools
available that can take a shapefile and convert it into a bunch of
statements to insert the geometry (and attributes) into a postgis table.
Does that make some sense to you?
Tyler
Noel Nasayao <ini_47 at yahoo.com>
Sent by: To: postgis-users at postgis.refractions.net
postgis-users-admin at postgis.refr cc:
actions.net Fax to:
Subject: [postgis-users] (no subject)
09/25/2002 04:08 PM
Please respond to postgis-users
I'm a new user of postgis... and honestly i find it a bit hard to establish
a good grasp on the geometry functionalities of this postgresql
extension... can anyone be kind enough to refer me to any existing websites
regarding as to how the these functions manipulate shapefiles??? or are
there any existing documentations (detailed) regarding them?? thanks guys!
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2002-11-03 06:29 Geoff Anderson <javageoff@hotmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: Geoff Anderson @ 2002-11-03 06:29 UTC (permalink / raw)
Hi,
I am eagerly awaiting the addition of topological operators to PostGIS. In
the mean time for fun I'm hacking together a GML centric vector overlay
thing built around PostGIS, Java2D and a lot of PHP. Clearly there's lot's
of good reasons why you can't do real spatial processing around massive text
files, but is there a particularly good/fast PostGIS to GML writer out
there? What's the best way to bounding box intersect two tables? (select
the features from table_a that intersect the selected features of
table_b...) And how soon will I be able to construct new geometries from
of-the-shelf PostGIS sql?
Geoff Anderson
Boulder, CO
javageoff at hotmail.com
_________________________________________________________________
Choose an Internet access plan right for you -- try MSN!
http://resourcecenter.msn.com/access/plans/default.asp
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2002-11-03 15:07 Frank Warmerdam <warmerdam@pobox.com>
parent: Geoff Anderson <javageoff@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Frank Warmerdam @ 2002-11-03 15:07 UTC (permalink / raw)
Geoff Anderson wrote:
> Hi,
>
> I am eagerly awaiting the addition of topological operators to
> PostGIS. In the mean time for fun I'm hacking together a GML centric
> vector overlay thing built around PostGIS, Java2D and a lot of PHP.
> Clearly there's lot's of good reasons why you can't do real spatial
> processing around massive text files, but is there a particularly
> good/fast PostGIS to GML writer out there? What's the best way to
> bounding box intersect two tables? (select the features from table_a
> that intersect the selected features of table_b...) And how soon will I
> be able to construct new geometries from of-the-shelf PostGIS sql?
Geoff,
My ogr2ogr utility can be used to dump the results of a PostGIS query to
GML. It is written in C++ and is I think at least reasonably fast.
Let me know if you want more info.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-02-22 21:19 jpalmer at paradise.net.nz <jpalmer@paradise.net.nz>
0 siblings, 1 reply; 131+ messages in thread
From: jpalmer at paradise.net.nz @ 2004-02-22 21:19 UTC (permalink / raw)
Yes I installed postgres from the RPM's. But it still might be useful to
know how to do it both ways, with the source (with redhat's directory
structure) and the rpms.
Thanks
-----Original Message-----
From: Darren Houston [mailto:dhouston at beyondcompliance.ca]
Sent: Sunday, 22 February 2004 11:26 p.m.
To: PostGIS Users Discussion
Cc: jpalmer at paradise.net.nz
Subject: Re: [postgis-users] Help on Postgresql 7.4.1 install with postgis
0.81
Hello Jeremy,
Am I correct in assuming you installed PostgreSQL 7.4.1 from RPMs?
You can install PostGIS with an RPM installed PostgreSQL, but it takes a
little
ingenuity. If you installed PostgreSQL from source, then PostGIS is a snap.
E-mail back telling how PostgreSQL was installed and I'll help you out.
Jeremy Palmer <jpalmer at paradise.net.nz> said:
> Hi,
>
> I'm new to the world of postgis and postgreSQL. Up until now I have used
the
> redhat 9.0 rpms for the install of postgis, geos and proj. However the
rpms
> have only been compiled for postgres 7.3.1 and I wanted to use the latest
> version of 7.4.1. I have downloaded and installed all of the sources. My
> question is that with postgresql, postgis, proj and geos it seems the
> configure scripts by default install the files to /usr/local/lib and
> /usr/local/pgsql, and as far as I can tell I think under the redhat the
> files should be going to /usr/bin and /usr/bin and postgresql data
directory
> should be in the /var/lib/pgsql/? Could someone please show me how to
> configure postgresql, postgis, geos and proj scripts so that the "make
> install" of the sources will install into the correct directories. The
> configure options are a little confusing to me!
>
> Thank you very much for your time.
>
> Jeremy
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
--
Darren Houston
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-02-22 23:59 Gerry Creager N5JXS <gerry.creager@tamu.edu>
parent: jpalmer at paradise.net.nz <jpalmer@paradise.net.nz>
0 siblings, 0 replies; 131+ messages in thread
From: Gerry Creager N5JXS @ 2004-02-22 23:59 UTC (permalink / raw)
I've had significant problems using the RH RPMs to install PostGres. I
now use the following command (rpm -e postgres) to start the fix process.
I'm not completely sure what RedHat does to PostGres, but it's caused me
headaches in the past...
jpalmer at paradise.net.nz wrote:
> Yes I installed postgres from the RPM's. But it still might be useful to
> know how to do it both ways, with the source (with redhat's directory
> structure) and the rpms.
>
> Thanks
>
> -----Original Message-----
> From: Darren Houston [mailto:dhouston at beyondcompliance.ca]
> Sent: Sunday, 22 February 2004 11:26 p.m.
> To: PostGIS Users Discussion
> Cc: jpalmer at paradise.net.nz
> Subject: Re: [postgis-users] Help on Postgresql 7.4.1 install with postgis
> 0.81
>
>
> Hello Jeremy,
>
> Am I correct in assuming you installed PostgreSQL 7.4.1 from RPMs?
>
> You can install PostGIS with an RPM installed PostgreSQL, but it takes a
> little
> ingenuity. If you installed PostgreSQL from source, then PostGIS is a snap.
>
> E-mail back telling how PostgreSQL was installed and I'll help you out.
>
> Jeremy Palmer <jpalmer at paradise.net.nz> said:
>
>
>>Hi,
>>
>>I'm new to the world of postgis and postgreSQL. Up until now I have used
>
> the
>
>>redhat 9.0 rpms for the install of postgis, geos and proj. However the
>
> rpms
>
>>have only been compiled for postgres 7.3.1 and I wanted to use the latest
>>version of 7.4.1. I have downloaded and installed all of the sources. My
>>question is that with postgresql, postgis, proj and geos it seems the
>>configure scripts by default install the files to /usr/local/lib and
>>/usr/local/pgsql, and as far as I can tell I think under the redhat the
>>files should be going to /usr/bin and /usr/bin and postgresql data
>
> directory
>
>>should be in the /var/lib/pgsql/? Could someone please show me how to
>>configure postgresql, postgis, geos and proj scripts so that the "make
>>install" of the sources will install into the correct directories. The
>>configure options are a little confusing to me!
>>
>>Thank you very much for your time.
>>
>>Jeremy
>>
>>
>>
>>_______________________________________________
>>postgis-users mailing list
>>postgis-users at postgis.refractions.net
>>http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>
>
>
>
>
> --
> Darren Houston
>
>
>
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
--
Gerry Creager -- gerry.creager at tamu.edu
Network Engineering -- AATLT, Texas A&M University
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578
Page: 979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-05 08:43 Gregory S. Williamson <gsw@globexplorer.com>
0 siblings, 1 reply; 131+ messages in thread
From: Gregory S. Williamson @ 2004-03-05 08:43 UTC (permalink / raw)
I am running postgres 7.4, Linux 2.4.21-0.13 i686
pgsql2shp -f shape_file -g the_geom gex_runtime sid_content_navi
FATAL: database "postgres" does not exist
The database, gex_runtime, does in fact exist on port 5432, on this server. As does this table, with a column by that name, which is in the geometry_columns table.
Can someone please inform this addled person what he's doing wrong ? This is quite urgent and I can't get any traction on it at all. This is really very frustrating.
Thanks!
Greg Williamson
DBA
GlobeXplorer LLC
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-05 17:36 Tyler Mitchell <TMitchell@lignum.com>
parent: Gregory S. Williamson <gsw@globexplorer.com>
0 siblings, 0 replies; 131+ messages in thread
From: Tyler Mitchell @ 2004-03-05 17:36 UTC (permalink / raw)
> pgsql2shp -f shape_file -g the_geom gex_runtime sid_content_navi
> FATAL: database "postgres" does not exist
>
> The database, gex_runtime, does in fact exist on port 5432, on this
> server. As does this table, with a column by that name, which is in
> the geometry_columns table.
Bizarre, are you running this locally on the server or from another
machine?
I assume you are logged in as user "postgres" - it looks like the program
isn't recognizing the database parameter and is, by default, looking for a
database with the same name as the user. I've seen that when running
"psql" but not pgsql2shp - which I haven't really used much. You may
want to try using ogr2ogr instead. Let me know if you need more info
using it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20040305/4683bc88/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-16 09:30 David Sharp <dsharp@altobridge.com>
0 siblings, 0 replies; 131+ messages in thread
From: David Sharp @ 2004-03-16 09:30 UTC (permalink / raw)
Hi ,
I just have a quick question , I am developing a gps/gis application at
the moment and I am using postgresql as my database with postgis as a
spatial extension.
I was wondering is it possible to calculate the distance between an
external point and a polygon . I am using lat/lon as units . The error I
am receiving is
>
> when I enter
>
> SELECT ('(10.9,-62.)'::point <@> '((18.418 -65.772,17.957
> -65.832,18.0515 -66.865,18.361 -66.986,18.418
> -65.772))'::polygon)::numeric(20,5);
>
>
> ERROR: Bad polygon external representation '((18.418 -65.772,17.957
> -65.832,18.0515 -66.865,18.361 -66.986,18.418 -65.772))'
>
> Any help much appreciated
>
> David Sharp
>
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-16 11:16 Mark Cave-Ayland <m.cave-ayland@webbased.co.uk>
0 siblings, 1 reply; 131+ messages in thread
From: Mark Cave-Ayland @ 2004-03-16 11:16 UTC (permalink / raw)
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net
> [mailto:postgis-users-bounces at postgis.refractions.net] On
> Behalf Of David Sharp
> Sent: 16 March 2004 09:31
> To: postgis-users at postgis.refractions.net
> Subject: [postgis-users] (no subject)
>
>
> Hi ,
>
> I just have a quick question , I am developing a gps/gis
> application at the moment and I am using postgresql as my
> database with postgis as a spatial extension.
> I was wondering is it possible to calculate the distance
> between an external point and a polygon . I am using lat/lon
> as units . The error I am receiving is
> >
> > when I enter
> >
> > SELECT ('(10.9,-62.)'::point <@> '((18.418 -65.772,17.957
> > -65.832,18.0515 -66.865,18.361 -66.986,18.418
> > -65.772))'::polygon)::numeric(20,5);
> >
> >
> > ERROR: Bad polygon external representation '((18.418
> -65.772,17.957
> > -65.832,18.0515 -66.865,18.361 -66.986,18.418 -65.772))'
> >
> > Any help much appreciated
> >
> > David Sharp
Hi David,
From the query you've given above, it looks as if even though you have
the PostGIS spatial extensions installed, you are still using the
internal PostgreSQL geometric operators. I can't find the <@> operator
in the PostgreSQL documentation, but the format of the data vertices is
different which is why the polygon fails above. If you are not working
on an existing system then I would highly recommend using the PostGIS
functions over the internal ones :) Please take a good look at the
online documentation at http://postgis.refractions.net/docs/ if you're
not sure about this.
The main advantage of using the PostGIS functions is that they are aware
of the projection of the data that you are working on, unlike the
unbuilt PostgreSQL geometric operators. As an example, the following
PostGIS query should give you what you need:
select distance(geometryfromtext('POINT(10.9 -62.0)', -1),
geometryfromtext('POLYGON((18.418 -65.772,17.957 -65.832,18.0515
-66.865,18.361 -66.986,18.418 -65.772))', -1));
Note that the distance returned will be in the units you are working in,
e.g. decimal degrees. If you want to convert it to metres/feet then you
will need to alter the query to reproject the lat/long points from a
sphere to a flat distance using the PostGIS distance_spheroid()
function.
Cheers,
Mark.
---
Mark Cave-Ayland
Webbased Ltd.
Tamar Science Park
Derriford
Plymouth
PL6 8BX
England
Tel: +44 (0)1752 764445
Fax: +44 (0)1752 764446
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender. You
should not copy it or use it for any purpose nor disclose or distribute
its contents to any other person.
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-18 12:06 David Sharp <dsharp@altobridge.com>
parent: Mark Cave-Ayland <m.cave-ayland@webbased.co.uk>
0 siblings, 1 reply; 131+ messages in thread
From: David Sharp @ 2004-03-18 12:06 UTC (permalink / raw)
Hi ,
thanks mark for the reply ,I have come across another problem though ,
I am trying to get the distance between a point and a polygon using the
spherical distance function. Using degrees as units I would like to
represent my distance in metres.
Is my query incorrect
select distance_spheroid((geometryfromtext('POINT(10.9 -62.0)',
-1)),(geometryfromtext('POLYGON((18.418 -65.772 0,17.957 -65.832
0,18.0515 -66.865 0,18.361 -66.986 0,18.418 -65.772
0))',-1)),'SPHEROID["WGS84",6378137,298.257223563]');
because I receive the error
"optimistic_overlap: second arg isnt a point "
Is the function only possible between two points ?
any feedback helpful
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-18 17:07 David Blasby <dblasby@refractions.net>
parent: David Sharp <dsharp@altobridge.com>
0 siblings, 0 replies; 131+ messages in thread
From: David Blasby @ 2004-03-18 17:07 UTC (permalink / raw)
David Sharp wrote:
> Is the function only possible between two points ?
Yes.
The calculations for line-point distance on a ellipse are extreamly
complex - just point-point distance calculation are several 100 lines...
dave
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-29 15:31 David Sharp <dsharp@altobridge.com>
0 siblings, 2 replies; 131+ messages in thread
From: David Sharp @ 2004-03-29 15:31 UTC (permalink / raw)
Hi ,
I was just wondering , I am playing around with a gis/gps application at
the moment using postgis as my spatial extension . But my problem is I
may have to sell my code soon and I am using postgresql as my database
and the gpl license doesn't agree with the companies wishes .
Does anyone now where I can find a commercial gis database , that could
take postgresql/postgis's place .
thanks
David Sharp
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-29 16:41 Tyler Mitchell <TMitchell@lignum.com>
parent: David Sharp <dsharp@altobridge.com>
1 sibling, 0 replies; 131+ messages in thread
From: Tyler Mitchell @ 2004-03-29 16:41 UTC (permalink / raw)
Hi David,
That's quite an interesting predicament. You probably should look more
into whether or not this really is an issue. Others can speak to the
point, but from my understanding, as long as you are not modifying or
using the code, you should be able to redistribute it without a problem.
Can you tell us more specifically what the issue is.
But back to your question, these guys have some commercial offerings at
reasonable prices and provide support:
http://www.commandprompt.com
Hope that helps.
Tyler
postgis-users-bounces at postgis.refractions.net wrote on 03/29/2004 07:31:18
AM:
>
>
> Hi ,
>
>
> I was just wondering , I am playing around with a gis/gps application at
> the moment using postgis as my spatial extension . But my problem is I
> may have to sell my code soon and I am using postgresql as my database
> and the gpl license doesn't agree with the companies wishes .
>
> Does anyone now where I can find a commercial gis database , that could
> take postgresql/postgis's place .
>
>
> thanks
>
> David Sharp
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-29 20:00 Pericles Nacionales <nacional@cbs.umn.edu>
parent: David Sharp <dsharp@altobridge.com>
1 sibling, 0 replies; 131+ messages in thread
From: Pericles Nacionales @ 2004-03-29 20:00 UTC (permalink / raw)
David,
Since PostgreSQL is under the BSD license, you don't have to worry about
the DBMS itself. If you are using PostGIS on its own (along with
PostgreSQL), I'd suggest talking to the Refractions folks. If they alone
own the copyrights to PostGIS source code then they might be able to work
a licensing deal with you. That might be the best deal for you and
Refractions... and perhaps for the rest of us PostGIS users (although we'd
still hope you'd share some of your work :).
If your company insists on using another geospatial database engine,
there's Oracle and informix. Not cheap.
I hope this helps even though IANAL.
-Perry Nacionales
On Mon, 29 Mar 2004, David Sharp wrote:
>
>
> Hi ,
>
>
> I was just wondering , I am playing around with a gis/gps application at
> the moment using postgis as my spatial extension . But my problem is I
> may have to sell my code soon and I am using postgresql as my database
> and the gpl license doesn't agree with the companies wishes .
>
> Does anyone now where I can find a commercial gis database , that could
> take postgresql/postgis's place .
>
>
> thanks
>
> David Sharp
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-03-31 17:20 Okeh, Sam <Sam.Okeh@co.fulton.ga.us>
0 siblings, 0 replies; 131+ messages in thread
From: Okeh, Sam @ 2004-03-31 17:20 UTC (permalink / raw)
Hello listers again,
This is probably easy for unix users but it doesn't seem to be working
for me so far.
We have a shape file called Streets in our data catalog.
I need to convert this to PostGIS using shpPg.
The following is the command that I am using:
*
shpPg -db=gis -schema=transportation -table=Streets -dbf=<Street
shapefile> -initial
I just keep getting this error:
Street: no such directory or file exists
Can anyone help, please
*************************************************************
Select * From Population WHERE skillset > average
*************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20040331/ff981df1/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-04-16 13:30 David Sharp <dsharp@altobridge.com>
0 siblings, 1 reply; 131+ messages in thread
From: David Sharp @ 2004-04-16 13:30 UTC (permalink / raw)
Hi ,
I was just wondering , at the moment I am using the following command to
enter data into my database.
insert into
table(id,poly_geom,name,level)values(1,GeometryFromText('POLYGON((5
2.30 -9.75 0,52.30 -9.66 0,52.25 -9.66 0,52.25 -9.75 0,52.30 -9.75
0))',-1),'
If I wanted to integrate height also into my table of polygons would I
just replace the zero value with the height in meters.
Once I then query the database for places within a 30km range will it
take the height into account when It returns my result.
Any help appreciated
regards
David Sharp
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-04-16 14:45 Paul Ramsey <pramsey@refractions.net>
parent: David Sharp <dsharp@altobridge.com>
0 siblings, 0 replies; 131+ messages in thread
From: Paul Ramsey @ 2004-04-16 14:45 UTC (permalink / raw)
Over 30 km, your elevations are not going to make much of a difference
to your distance calculations. There is no distance3d function, because
of the difficulties in coding it and relative obscurity of the
functionality (always a deadly combination :). There is a length3d
function, which tends to be more useful (how far is it *really* from A
to B, including up and down hills).
P.
On Friday, April 16, 2004, at 06:30 AM, David Sharp wrote:
> Hi ,
>
> I was just wondering , at the moment I am using the following command
> to
> enter data into my database.
>
> insert into
> table(id,poly_geom,name,level)values(1,GeometryFromText('POLYGON((5
> 2.30 -9.75 0,52.30 -9.66 0,52.25 -9.66 0,52.25 -9.75 0,52.30 -9.75
> 0))',-1),'
>
>
> If I wanted to integrate height also into my table of polygons would I
> just replace the zero value with the height in meters.
>
> Once I then query the database for places within a 30km range will it
> take the height into account when It returns my result.
>
> Any help appreciated
>
> regards
>
> David Sharp
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
Paul Ramsey
Refractions Research
Email: pramsey at refractions.net
Phone: (250) 885-0632
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-07-15 11:22 marc.soutter at epfl.ch <marc.soutter@epfl.ch>
0 siblings, 0 replies; 131+ messages in thread
From: marc.soutter at epfl.ch @ 2004-07-15 11:22 UTC (permalink / raw)
hello everybody
Got the same problems than reported by Bato Pure in installing postgis, with
Fedora 2 as well as with Mandrake 10 (almost standard basic installs on a dell
latitude 640). The error message looks like this :
postgres at localhost postgres]$ /usr/local/pgsql/bin/psql -d gesro -f
/usr/local/pgsql/share/postgis.sql
BEGIN
message
------------------------
PL/PgSQL is installed.
(1 row)
NOTICE: type "histogram2d" is not yet defined
DETAIL: Creating a shell type definition.
psql:/usr/local/pgsql/share/postgis.sql:37: NOTICE: type "histogram2d" is not
yet defined
DETAIL: Creating a shell type definition.
ERROR: could not load library "/usr/local/pgsql/lib/libpostgis.so.0.8":
libgeos.so.1: cannot open shared object file: No such file or directory
psql:/usr/local/pgsql/share/postgis.sql:37: ERROR: could not load library
"/usr/local/pgsql/lib/libpostgis.so.0.8": libgeos.so.1: cannot open shared
object file: No such file or directory
ERROR: current transaction is aborted, commands ignored until end of
transaction block
psql:/usr/local/pgsql/share/postgis.sql:42: ERROR: current transaction is
aborted, commands ignored until end of transaction block
...
I do not remember how I got to this, may be just trying, but I noticed (and did
not understand why) that this problem may be solved with Fedora by installing
the tcl and tk resources and then compiling postgresql again using the
--with-tcl --with-tclconfig=/.../ option.
This did not work with Mandrake. However, the error does not occur if the
GEOS_USE option in the postgis makefile is set to 0. I guess something is wrong
with the library paths ?
Any explanations and advice are welcome.
Marc
PS. In both cases everything was intalled form the latest tarballs.
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-07-23 18:53 AGT <alejandrogalindo@tutopia.com>
0 siblings, 0 replies; 131+ messages in thread
From: AGT @ 2004-07-23 18:53 UTC (permalink / raw)
what is the exact sentence ?? thanks
Try using a DATA statement like this:
"bbox from data_specimen using SRID=26716 using unique specimen_id"
dave
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-08-05 16:57 PINKTOMATE <pinktomate@spymac.com>
0 siblings, 0 replies; 131+ messages in thread
From: PINKTOMATE @ 2004-08-05 16:57 UTC (permalink / raw)
Hi DarrenH
happen that I tried to display maps generated by postgis in a WMS, but
not found a stable way to do it, what do you recommend, alov it's great
but not work with postgis, mapserver does not work easily more code to
do :(, what do you think, whats your recommendation, regards
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-11-25 12:12 pinktomate <pinktomate@spymac.com>
0 siblings, 0 replies; 131+ messages in thread
From: pinktomate @ 2004-11-25 12:12 UTC (permalink / raw)
Hi, peace for all!!!
If I have a shapefile with a line (one highway for instance) what is the
correct sintax to a query in postgis to generate a buffer of 1000 meters
around the highway???
absolutelly thanks for the help
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2004-12-09 07:42 Fabio Fioravanti <ff@ascoli.biz>
0 siblings, 0 replies; 131+ messages in thread
From: Fabio Fioravanti @ 2004-12-09 07:42 UTC (permalink / raw)
> I can't help but reflect on all the wonderful open source software that
I've
> been able to use in building a GIS: apache mapserver/mapscript python
> ogr/gdal/proj postgresql postGis/geos mozilla ...
Remember: you CAN help!
apache http://www.apache.org/foundation/contributing.html
python http://www.python.org/psf/donations.html
postgresql http://developer.postgresql.org/~scrappy/donate.html
mozilla http://www.mozilla.org/foundation/donate.html
just to name a few...
best regards,
Fabio Fioravanti
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2005-05-07 16:21 edgardo cornelio <eliseo_c1@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: edgardo cornelio @ 2005-05-07 16:21 UTC (permalink / raw)
_________________________________________________________
Do You Yahoo!?
Informaci?n de Estados Unidos y Am?rica Latina, en Yahoo! Noticias.
Vis?tanos en http://noticias.espanol.yahoo.com
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2005-07-11 11:54 Christian Schwartze <chris81@minet.uni-jena.de>
0 siblings, 0 replies; 131+ messages in thread
From: Christian Schwartze @ 2005-07-11 11:54 UTC (permalink / raw)
Hi to all PostGIS-users....
I have a table "earthquakes" with a GiSt-index on column "geo". I search for all earthquakes along a street using a buffer distance.
Does somebody know, why the GiST-index is not in use (as per explain), when combining the &&-operator with the transform()-function like in:
select quake_id, location, x(geo), y(geo)
from earthquakes
where geo && envelope(buffer(transform((select geo from roads where name = 'U.S. Hwy 85'),102009),5)) and within(geo,(select buffer(transform((select geo from roads where name = 'U.S. Hwy 85'),102009),5)));
Without the transform-function the query is very quick because of the GiST-index, but i need the transform-function to calculate in unit "meter".
Can somebody help me, thanks a lot!
Christian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20050711/b172e8ce/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2005-07-18 17:35 dblasby at openplans.org <dblasby@openplans.org>
0 siblings, 0 replies; 131+ messages in thread
From: dblasby at openplans.org @ 2005-07-18 17:35 UTC (permalink / raw)
>This sounds like floating point comparisons failing because
>> of numerical
>> rounding issues.
>
>Highly unlikely - JTS/GEOS is very robust wrt predicates.
I think he means the 2 geometries arent actually identical - the points
maybe "10-7 off". These differences would be hidden by converting to
WKT (since it doesnt show all 64bits of precision).
Try something like this:
SELECT encode( asBinary( geometry1 ) , 'hex'),
encode( asBinary( geometry2 ) , 'hex')
FROM ... ;
And see if the two are actually equal.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2005-07-18 17:44 Martin Davis <mbdavis@VividSolutions.com>
0 siblings, 1 reply; 131+ messages in thread
From: Martin Davis @ 2005-07-18 17:44 UTC (permalink / raw)
Good point, Dave - that would produce the same symptoms.
Hmmm - this sort of thing sounds like it could be a real problem, if
there's extra junk precision which isn't visible textually, but causes
strange results in spatial operations. Maybe one answer to this is to
allow specifying the desired precision when storing and operating on
PostGIS data? This would have the added benefit of encouraging people
to store their data with no more than the actual precision contained in
the original observations.
SDE has this capability by default, since it forces you to define a
mapping to its internal integer storage. Oracle sort of has this by
virtue of its tolerance (although AFAIK there's no way of enforcing
actual storage to a given precision).
Martin Davis, Senior Technical Architect
Vivid Solutions Inc. www.vividsolutions.com
Suite #1A-2328 Government Street Victoria, B.C. V8T 5G5
Phone: (250) 385 6040 - Local 308 Fax: (250) 385 6046
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net
> [mailto:postgis-users-bounces at postgis.refractions.net] On
> Behalf Of dblasby at openplans.org
> Sent: July 18, 2005 10:36 AM
> To: postgis-users at postgis.refractions.net
> Subject: [postgis-users] (no subject)
>
>
> >This sounds like floating point comparisons failing because
> >> of numerical
> >> rounding issues.
> >
> >Highly unlikely - JTS/GEOS is very robust wrt predicates.
>
> I think he means the 2 geometries arent actually identical -
> the points maybe "10-7 off". These differences would be
> hidden by converting to WKT (since it doesnt show all 64bits
> of precision).
>
> Try something like this:
>
> SELECT encode( asBinary( geometry1 ) , 'hex'),
> encode( asBinary( geometry2 ) , 'hex')
> FROM ... ;
>
> And see if the two are actually equal.
>
> dave
>
>
>
>
>
> ----------------------------------------------------------
> This mail sent through IMP: https://webmail.limegroup.com/
> _______________________________________________
> postgis-users mailing list postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2005-07-18 18:03 Mark Fenbers <Mark.Fenbers@noaa.gov>
parent: Martin Davis <mbdavis@VividSolutions.com>
0 siblings, 0 replies; 131+ messages in thread
From: Mark Fenbers @ 2005-07-18 18:03 UTC (permalink / raw)
I had a similar problem when the values were different at the 13th
decimal place. This was way too much precision for me, so I was able to
get around the problem by using the SnapToGrid(0.0000001) function on my
data before using the Difference() function, etc.
Mark
Martin Davis wrote:
>Good point, Dave - that would produce the same symptoms.
>
>Hmmm - this sort of thing sounds like it could be a real problem, if
>there's extra junk precision which isn't visible textually, but causes
>strange results in spatial operations. Maybe one answer to this is to
>allow specifying the desired precision when storing and operating on
>PostGIS data? This would have the added benefit of encouraging people
>to store their data with no more than the actual precision contained in
>the original observations.
>
>SDE has this capability by default, since it forces you to define a
>mapping to its internal integer storage. Oracle sort of has this by
>virtue of its tolerance (although AFAIK there's no way of enforcing
>actual storage to a given precision).
>
>Martin Davis, Senior Technical Architect
>Vivid Solutions Inc. www.vividsolutions.com
>Suite #1A-2328 Government Street Victoria, B.C. V8T 5G5
>Phone: (250) 385 6040 - Local 308 Fax: (250) 385 6046
>
>
>
>
>>-----Original Message-----
>>From: postgis-users-bounces at postgis.refractions.net
>>[mailto:postgis-users-bounces at postgis.refractions.net] On
>>Behalf Of dblasby at openplans.org
>>Sent: July 18, 2005 10:36 AM
>>To: postgis-users at postgis.refractions.net
>>Subject: [postgis-users] (no subject)
>>
>>
>>
>>
>>>This sounds like floating point comparisons failing because
>>>
>>>
>>>>of numerical
>>>>rounding issues.
>>>>
>>>>
>>>Highly unlikely - JTS/GEOS is very robust wrt predicates.
>>>
>>>
>>I think he means the 2 geometries arent actually identical -
>>the points maybe "10-7 off". These differences would be
>>hidden by converting to WKT (since it doesnt show all 64bits
>>of precision).
>>
>>Try something like this:
>>
>>SELECT encode( asBinary( geometry1 ) , 'hex'),
>> encode( asBinary( geometry2 ) , 'hex')
>>FROM ... ;
>>
>>And see if the two are actually equal.
>>
>>dave
>>
>>
>>
>>
>>
>>----------------------------------------------------------
>>This mail sent through IMP: https://webmail.limegroup.com/
>>_______________________________________________
>>postgis-users mailing list postgis-users at postgis.refractions.net
>>http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>>
>>
>_______________________________________________
>postgis-users mailing list
>postgis-users at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Mark.Fenbers.vcf
Type: text/x-vcard
Size: 283 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20050718/c05fe1da/attachment.vcf;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2006-01-11 14:44 sergio at labtrans.ufsc.br <sergio@labtrans.ufsc.br>
0 siblings, 0 replies; 131+ messages in thread
From: sergio at labtrans.ufsc.br @ 2006-01-11 14:44 UTC (permalink / raw)
I am looking a function that can finds the line next to one determined
point, being that the type of the line is MULTILINESTRING and the point
is POINT
Grateful
Sergio Zarth Jr
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2006-01-13 19:08 Peter König <peter.koenig@ccgis.de>
0 siblings, 3 replies; 131+ messages in thread
From: Peter König @ 2006-01-13 19:08 UTC (permalink / raw)
Hi all,
I am trying to install PostGIS on an Ubuntu-Linux for two days now -
unfortunatly without success. Since I saw some postings here about
successful installations on Ubuntu and the AMD64-architecture, maybe there
is someone who could give me a hint.
The first attemt was to install Postgres via the source-distribution:
apt-get -b source postgresql-8.0 postgresql-server-dev-8.0
I also installed proj and geos.
Then I copied PostGIS-archive ( tried 1.1 and 1.06) to the pg-contrib-dir
in the "build-tree"-path and extracted them there. After configuring
(1.1)/ modifiying the Makefile.config (1.0.6), proj and geos were
correctly found, "make" and "make install" proceeded without errors (but
many warnings [*] ) and I got liblwgeom.so.xx in
/usr/lib/postgresql/8.0/lib (liblwgeom.so.1 and liblwgeom.so in the same
dir were link to it)
Then I chowned the regess-dir to postgres:postgres and started "make" in
that dir (as user "postgres") to perform the tests. V 1.0.6 produced a lot
of errors complaining about an uninstalled "geos" and with V 1.1.0 I
received the message, that 8 of 9 tests have failed. Although I see the
PostGIS-Funtions in a new db they do not work.
Another approach was to try to install the ubuntu deb-package of postgis
1.0.6 from arocaware, but it also failed.
Any idea to solve this would be welcome. Thanks,
Peter
[*]:
Warnung: Zeigerziele in Zuweisung unterscheiden sich im Vorzeichenbesitz
Warnung: Zeigerziele bei ?bergabe des Arguments 1 von ?HexDecode?
unterscheiden sich im Vorzeichenbesitz
May be loosly translated as "the targets of the pointers in the assignment
are differently signed" and "the targets of the pointers of argument 1 of
HexDecode are differently signed" (I am not c-coder ..).
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2006-01-13 21:43 TECHER David <davidtecher@yahoo.fr>
parent: Peter König <peter.koenig@ccgis.de>
2 siblings, 0 replies; 131+ messages in thread
From: TECHER David @ 2006-01-13 21:43 UTC (permalink / raw)
Hi Peter
When PostGIS Regression Tests if it complains about geos
error about libgeos (if you've installed geos 2.2.1) it is because
/usr/local/lib where U can find it in geos lib is not in your
LD_LIBRARY_PATH
so as root
do
echo $(geos-config --prefix)/lib >> /etc/ld.so.conf
ldconfig -v | grep libgeos
that should give you something like
libgeos.so.2 -> libgeos.so.2.1.3
or
libgeos.so.2 -> libgeos.so.2.2.1
then
psql -U postgres -d template1 -c "drop database postgis_reg"
rerun postgis regression test
Peter K?nig a ?crit :
>Hi all,
>I am trying to install PostGIS on an Ubuntu-Linux for two days now -
>unfortunatly without success. Since I saw some postings here about
>successful installations on Ubuntu and the AMD64-architecture, maybe there
>is someone who could give me a hint.
>
>The first attemt was to install Postgres via the source-distribution:
>apt-get -b source postgresql-8.0 postgresql-server-dev-8.0
>
>I also installed proj and geos.
>
>Then I copied PostGIS-archive ( tried 1.1 and 1.06) to the pg-contrib-dir
>in the "build-tree"-path and extracted them there. After configuring
>(1.1)/ modifiying the Makefile.config (1.0.6), proj and geos were
>correctly found, "make" and "make install" proceeded without errors (but
>many warnings [*] ) and I got liblwgeom.so.xx in
>/usr/lib/postgresql/8.0/lib (liblwgeom.so.1 and liblwgeom.so in the same
>dir were link to it)
>
>Then I chowned the regess-dir to postgres:postgres and started "make" in
>that dir (as user "postgres") to perform the tests. V 1.0.6 produced a lot
>of errors complaining about an uninstalled "geos" and with V 1.1.0 I
>received the message, that 8 of 9 tests have failed. Although I see the
>PostGIS-Funtions in a new db they do not work.
>
>Another approach was to try to install the ubuntu deb-package of postgis
>1.0.6 from arocaware, but it also failed.
>
>Any idea to solve this would be welcome. Thanks,
>Peter
>
>[*]:
>Warnung: Zeigerziele in Zuweisung unterscheiden sich im Vorzeichenbesitz
>Warnung: Zeigerziele bei ?bergabe des Arguments 1 von ?HexDecode?
>unterscheiden sich im Vorzeichenbesitz
>
>May be loosly translated as "the targets of the pointers in the assignment
>are differently signed" and "the targets of the pointers of argument 1 of
>HexDecode are differently signed" (I am not c-coder ..).
>
>
>_______________________________________________
>postgis-users mailing list
>postgis-users at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
___________________________________________________________________________
Nouveau : t?l?phonez moins cher avec Yahoo! Messenger ! D?couvez les tarifs exceptionnels pour appeler la France et l'international.
T?l?chargez sur http://fr.messenger.yahoo.com
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2006-01-14 02:21 alex bodnaru <alexbodn@012.net.il>
parent: Peter König <peter.koenig@ccgis.de>
2 siblings, 0 replies; 131+ messages in thread
From: alex bodnaru @ 2006-01-14 02:21 UTC (permalink / raw)
hi peter,
i am not including the file again, because of it's volume (round 100k).
please see my previous answer to assad.
i'll be glad to find it would work for you.
alex
Peter K?nig wrote:
> Hi all,
> I am trying to install PostGIS on an Ubuntu-Linux for two days now -
> unfortunatly without success. Since I saw some postings here about
> successful installations on Ubuntu and the AMD64-architecture, maybe there
> is someone who could give me a hint.
>
> The first attemt was to install Postgres via the source-distribution:
> apt-get -b source postgresql-8.0 postgresql-server-dev-8.0
>
> I also installed proj and geos.
>
> Then I copied PostGIS-archive ( tried 1.1 and 1.06) to the pg-contrib-dir
> in the "build-tree"-path and extracted them there. After configuring
> (1.1)/ modifiying the Makefile.config (1.0.6), proj and geos were
> correctly found, "make" and "make install" proceeded without errors (but
> many warnings [*] ) and I got liblwgeom.so.xx in
> /usr/lib/postgresql/8.0/lib (liblwgeom.so.1 and liblwgeom.so in the same
> dir were link to it)
>
> Then I chowned the regess-dir to postgres:postgres and started "make" in
> that dir (as user "postgres") to perform the tests. V 1.0.6 produced a lot
> of errors complaining about an uninstalled "geos" and with V 1.1.0 I
> received the message, that 8 of 9 tests have failed. Although I see the
> PostGIS-Funtions in a new db they do not work.
>
> Another approach was to try to install the ubuntu deb-package of postgis
> 1.0.6 from arocaware, but it also failed.
>
> Any idea to solve this would be welcome. Thanks,
> Peter
>
> [*]:
> Warnung: Zeigerziele in Zuweisung unterscheiden sich im Vorzeichenbesitz
> Warnung: Zeigerziele bei ?bergabe des Arguments 1 von ?HexDecode?
> unterscheiden sich im Vorzeichenbesitz
>
> May be loosly translated as "the targets of the pointers in the assignment
> are differently signed" and "the targets of the pointers of argument 1 of
> HexDecode are differently signed" (I am not c-coder ..).
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2006-01-14 18:23 Blair Zajac <blair@orcaware.com>
parent: Peter König <peter.koenig@ccgis.de>
2 siblings, 0 replies; 131+ messages in thread
From: Blair Zajac @ 2006-01-14 18:23 UTC (permalink / raw)
Peter K?nig wrote:
> Hi all,
> I am trying to install PostGIS on an Ubuntu-Linux for two days now -
> unfortunatly without success. Since I saw some postings here about
> successful installations on Ubuntu and the AMD64-architecture, maybe there
> is someone who could give me a hint.
>
> The first attemt was to install Postgres via the source-distribution:
> apt-get -b source postgresql-8.0 postgresql-server-dev-8.0
>
> I also installed proj and geos.
>
> Then I copied PostGIS-archive ( tried 1.1 and 1.06) to the pg-contrib-dir
> in the "build-tree"-path and extracted them there. After configuring
> (1.1)/ modifiying the Makefile.config (1.0.6), proj and geos were
> correctly found, "make" and "make install" proceeded without errors (but
> many warnings [*] ) and I got liblwgeom.so.xx in
> /usr/lib/postgresql/8.0/lib (liblwgeom.so.1 and liblwgeom.so in the same
> dir were link to it)
>
> Then I chowned the regess-dir to postgres:postgres and started "make" in
> that dir (as user "postgres") to perform the tests. V 1.0.6 produced a lot
> of errors complaining about an uninstalled "geos" and with V 1.1.0 I
> received the message, that 8 of 9 tests have failed. Although I see the
> PostGIS-Funtions in a new db they do not work.
>
> Another approach was to try to install the ubuntu deb-package of postgis
> 1.0.6 from arocaware, but it also failed.
What was the problem with these packages?
You could try to rebuild using these sources, as they do successfully build on Ubuntu.
Regards,
Blair
--
Blair Zajac, Ph.D.
<blair at orcaware.com>
Subversion training and consulting
http://www.orcaware.com/svn/
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2006-08-11 03:14 smithveg <smithveg@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: smithveg @ 2006-08-11 03:14 UTC (permalink / raw)
Dear,
I had installed the mapbender GIS succesfully yesterday. When i login to it,
i totally confuse and cannnot understand how its really works. Can i have
more document and user guide.
thanks
--
smithveg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20060810/47071d91/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-04-26 10:11 Johannes Scholz <j.scholz@inode.at>
0 siblings, 0 replies; 131+ messages in thread
From: Johannes Scholz @ 2007-04-26 10:11 UTC (permalink / raw)
Dear List members,
i am writing due to a serious problem with shp2pgsql on my windows vista
os. if i convert shapefiles to sql i am able to view them normally in the
windows editor but not in crimson or other editors - there the geometry
field is somehow not visible. Only if i want to mark the empty space
(where normally the WKB should be) i am able to see the geometry....
mysterious? and also in the pgadmin i am not able to see the geometry
fields - so i can not put in data into the database...
i guess it must have something to do with the encoding of the shapefiles
or the basic encoding on the Vista....
hopefully someone can help
thanks in advance
Johannes Scholz
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-05-02 15:57 gavin.churcher at bt.com <gavin.churcher@bt.com>
0 siblings, 0 replies; 131+ messages in thread
From: gavin.churcher at bt.com @ 2007-05-02 15:57 UTC (permalink / raw)
Hi, I'm looking to call some spatial functions that are contained within liblwgeom.dll (postgis) from inside my own code (c# / .NET) but can't quite get the signatures right. Is there an API available (or header file) that I could use?
Thanks,
Gavin
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-05-30 06:02 Jennehag Åke <Ake.Jennehag@lm.se>
0 siblings, 0 replies; 131+ messages in thread
From: Jennehag Åke @ 2007-05-30 06:02 UTC (permalink / raw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070530/e0f97301/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-06-08 21:16 Gary Townsend <garyt@spatialmapping.com>
0 siblings, 1 reply; 131+ messages in thread
From: Gary Townsend @ 2007-06-08 21:16 UTC (permalink / raw)
Below is a function I am trying to create that will take a series of
geographic points form a UTM projection and translate it to lat/long that's
not the problem though the translation works wonderfully as a separate
select statement. I'm trying to encapsulate this into a function now and I
am getting a problem returned saying:
ERROR: syntax error at or near "$2"
SQL state: 42601
Character: 137
Context: PL/pgSQL function "vts_insert_stop" line 10 at select into
variables
I'm not sure where I've gone sideways on this but seeing as how I'm still
learning the pgplsql syntax I figured it could be anywhere I thought maybe
someone here may have a better soloution to what I'm trying to do or can see
what I'm doin wrong.
CREATE OR REPLACE FUNCTION vts_insert_stop(text, text, numeric, numeric,
numeric)
RETURNS numeric AS
'
DECLARE
stopnum ALIAS for $1;
stopdes ALIAS for $2;
stopeasting ALIAS for $3;
stopnorthing ALIAS for $4;
projection ALIAS for $5;
transCoord RECORD;
BEGIN
SELECT INTO transCoord X(SubSel.transformed_geom),
Y(SubSel.transformed_geom) FROM (
SELECT SetSRID(
Transform(
GeomFromText(
''POINT('' || stopeasting || '' '' stopnorthing || '')'',
projection
), 4326
),
-1) AS transformed_geom) SubSel;
INSERT INTO
vts_route_stops(stop_number,stop_description,stop_latitude,stop_longitude)
VALUES(stopnum,stopdes,transCoord.Y,transCoord.X);
RERTURN void;
END'
LANGUAGE 'plpgsql' VOLATILE;
Gary Townsend (Systems Programmer & Developer )
Spatial Mapping Ltd.
#200 484 2nd Ave. Prince George, B.C., Canada V2L 2Z7
Phone: 250 564 1928
Fax: 250 564 0751
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070608/40dccc3a/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2661 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070608/40dccc3a/attachment.gif;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-06-11 12:41 Obe, Regina <robe.dnd@cityofboston.gov>
parent: Gary Townsend <garyt@spatialmapping.com>
0 siblings, 1 reply; 131+ messages in thread
From: Obe, Regina @ 2007-06-11 12:41 UTC (permalink / raw)
Gary,
1) That's the old way of writing pgsql functions. I forget the
transition period - I think it was around 8.0 - the new way uses $
dollar quoting and doesn't require aliasing in pgsql althought it still
does in sql procedural.
2) If you are using RECORD objects, I think you need to specify the
field datatypes before you can use it.
3) That whole record thing seems like an unnecessary step anyway.
Try instead - hope I didn't make any mistakes since I didn't test it in
my typing (you might be able to skip the declare part since I've
eradicated all the variables)
CREATE OR REPLACE FUNCTION vts_insert_stop(stopnum text, stopdes text,
stopeasting numeric, stopnorthing numeric, projection numeric)
RETURNS numeric AS
$BODY$
DECLARE
BEGIN
INSERT INTO
vts_route_stops(stop_number,stop_description,stop_latitude,stop_longitud
e)
SELECT stopnum, stopdes, Y(SubSel.transformed_geom),
X(SubSel.transformed_geom)
FROM
(SELECT SetSRID(
Transform(GeomFromText('POINT(' || stopeasting || ' '
stopnorthing || ')', projection), 4326),-1) AS transformed_geom) SubSel;
RERTURN void;
END
$BODY$
LANGUAGE 'plpgsql' VOLATILE;
________________________________
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Gary
Townsend
Sent: Friday, June 08, 2007 5:17 PM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] (no subject)
Below is a function I am trying to create that will take a series of
geographic points form a UTM projection and translate it to lat/long
that's not the problem though the translation works wonderfully as a
separate select statement. I'm trying to encapsulate this into a
function now and I am getting a problem returned saying:
ERROR: syntax error at or near "$2"
SQL state: 42601
Character: 137
Context: PL/pgSQL function "vts_insert_stop" line 10 at select into
variables
I'm not sure where I've gone sideways on this but seeing as how I'm
still learning the pgplsql syntax I figured it could be anywhere I
thought maybe someone here may have a better soloution to what I'm
trying to do or can see what I'm doin wrong.
CREATE OR REPLACE FUNCTION vts_insert_stop(text, text, numeric, numeric,
numeric)
RETURNS numeric AS
'
DECLARE
stopnum ALIAS for $1;
stopdes ALIAS for $2;
stopeasting ALIAS for $3;
stopnorthing ALIAS for $4;
projection ALIAS for $5;
transCoord RECORD;
BEGIN
SELECT INTO transCoord X(SubSel.transformed_geom),
Y(SubSel.transformed_geom) FROM (
SELECT SetSRID(
Transform(
GeomFromText(
''POINT('' || stopeasting || '' '' stopnorthing || '')'',
projection
), 4326
),
-1) AS transformed_geom) SubSel;
INSERT INTO
vts_route_stops(stop_number,stop_description,stop_latitude,stop_longitud
e)
VALUES(stopnum,stopdes,transCoord.Y,transCoord.X);
RERTURN void;
END'
LANGUAGE 'plpgsql' VOLATILE;
Gary Townsend (Systems Programmer & Developer )
Spatial Mapping Ltd.
#200 484 2nd Ave. Prince George, B.C., Canada V2L 2Z7
Phone: 250 564 1928
Fax: 250 564 0751
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070611/473629c1/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2661 bytes
Desc: image001.gif
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070611/473629c1/attachment.gif;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-06-11 12:47 Obe, Regina <robe.dnd@cityofboston.gov>
parent: Obe, Regina <robe.dnd@cityofboston.gov>
0 siblings, 0 replies; 131+ messages in thread
From: Obe, Regina @ 2007-06-11 12:47 UTC (permalink / raw)
typo I spelled RETURN wrong - but evidentally I think I got that from
you :)
________________________________
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Obe,
Regina
Sent: Monday, June 11, 2007 8:42 AM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] (no subject)
Gary,
1) That's the old way of writing pgsql functions. I forget the
transition period - I think it was around 8.0 - the new way uses $
dollar quoting and doesn't require aliasing in pgsql althought it still
does in sql procedural.
2) If you are using RECORD objects, I think you need to specify the
field datatypes before you can use it.
3) That whole record thing seems like an unnecessary step anyway.
Try instead - hope I didn't make any mistakes since I didn't test it in
my typing (you might be able to skip the declare part since I've
eradicated all the variables)
CREATE OR REPLACE FUNCTION vts_insert_stop(stopnum text, stopdes text,
stopeasting numeric, stopnorthing numeric, projection numeric)
RETURNS numeric AS
$BODY$
DECLARE
BEGIN
INSERT INTO
vts_route_stops(stop_number,stop_description,stop_latitude,stop_longitud
e)
SELECT stopnum, stopdes, Y(SubSel.transformed_geom),
X(SubSel.transformed_geom)
FROM
(SELECT SetSRID(
Transform(GeomFromText('POINT(' || stopeasting || ' '
stopnorthing || ')', projection), 4326),-1) AS transformed_geom) SubSel;
RERTURN void;
END
$BODY$
LANGUAGE 'plpgsql' VOLATILE;
________________________________
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Gary
Townsend
Sent: Friday, June 08, 2007 5:17 PM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] (no subject)
Below is a function I am trying to create that will take a series of
geographic points form a UTM projection and translate it to lat/long
that's not the problem though the translation works wonderfully as a
separate select statement. I'm trying to encapsulate this into a
function now and I am getting a problem returned saying:
ERROR: syntax error at or near "$2"
SQL state: 42601
Character: 137
Context: PL/pgSQL function "vts_insert_stop" line 10 at select into
variables
I'm not sure where I've gone sideways on this but seeing as how I'm
still learning the pgplsql syntax I figured it could be anywhere I
thought maybe someone here may have a better soloution to what I'm
trying to do or can see what I'm doin wrong.
CREATE OR REPLACE FUNCTION vts_insert_stop(text, text, numeric, numeric,
numeric)
RETURNS numeric AS
'
DECLARE
stopnum ALIAS for $1;
stopdes ALIAS for $2;
stopeasting ALIAS for $3;
stopnorthing ALIAS for $4;
projection ALIAS for $5;
transCoord RECORD;
BEGIN
SELECT INTO transCoord X(SubSel.transformed_geom),
Y(SubSel.transformed_geom) FROM (
SELECT SetSRID(
Transform(
GeomFromText(
''POINT('' || stopeasting || '' '' stopnorthing || '')'',
projection
), 4326
),
-1) AS transformed_geom) SubSel;
INSERT INTO
vts_route_stops(stop_number,stop_description,stop_latitude,stop_longitud
e)
VALUES(stopnum,stopdes,transCoord.Y,transCoord.X);
RERTURN void;
END'
LANGUAGE 'plpgsql' VOLATILE;
Gary Townsend (Systems Programmer & Developer )
Spatial Mapping Ltd.
#200 484 2nd Ave. Prince George, B.C., Canada V2L 2Z7
Phone: 250 564 1928
Fax: 250 564 0751
________________________________
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure pursuant
to Massachusetts law. It is intended solely for the addressee. If you
received this in error, please contact the sender and delete the
material from any computer.
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070611/e43dd4ea/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2661 bytes
Desc: image001.gif
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070611/e43dd4ea/attachment.gif;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-07-03 09:50 Santosh Gaikwad <Santosh.Gaikwad@saama.com>
0 siblings, 0 replies; 131+ messages in thread
From: Santosh Gaikwad @ 2007-07-03 09:50 UTC (permalink / raw)
Dear Jeff,
I read your post with answer too. Well SRID 4269 refers to NAD83. Will
you please tell me to which projection SRID 2163 refers? Using this will
I have units in Meters?
Thanks & regards,
Santosh Gaikwad
Senior Software Developer
Saama Technologies (India) Pvt Ltd.
6th Floor West Wing, Marisoft III,
Marigold Premises, Kalayani Nagar,
Pune - 411014. India
Phone : +91 20 66071319 Extn: 397
Mobile: +91-9422005927
E-mail :Santosh.Gaikwad at saama.com
http://www.saama.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070703/8a393001/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Santosh Gaikwad.vcf
Type: text/x-vcard
Size: 145 bytes
Desc: Santosh Gaikwad.vcf
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070703/8a393001/attachment.vcf;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-07-04 11:19 Santosh Gaikwad <Santosh.Gaikwad@saama.com>
0 siblings, 1 reply; 131+ messages in thread
From: Santosh Gaikwad @ 2007-07-04 11:19 UTC (permalink / raw)
Hi,
I have US address which have been geocoded to get latitude and
longitude.
I am following the below steps
1. Add column
SELECT AddGeometryColumn( 'public', 'california', 'the_geom', 4326,
'POINT', 2 );
2. Populate geometry
UPDATE california
SET the_geom = PointFromText('POINT(' || longitude || ' ' ||
latitude || ')',4326)
3. Spatial query (I would like to build the spatial query for listing
out the locations for a given radius of 100 meters from a particular
location.)
Select *
from california
where setSRID(
buffer(
transform(GeomFromText('POINT(-121.962459
37.388364)',4326),2163),
100
),
2163)&& transform(the_geom, 2163)
This returns back me the locations with specified 100 meters radius.
This seems to be working fine but I am not confidant about it. When I
checked out SRID 2163 in spatial_ref_sys table, it says that the
projection is US national atlas equal area and unit is meters. I would
like to know whether this projection covers whole USA satisfactorily or
not. When I am using openjump by bringing postgis data into it, I can
not see the distance in meters on map. Why it is so? Thus this means
SRID 2163 has been used only to transform the projection.
Next I want to work on whole USA data. Please kindly let me know whether
I am following the correct steps or not?
Santosh Gaikwad
Senior Software Developer
Saama Technologies (India) Pvt Ltd.
6th Floor West Wing, Marisoft III,
Marigold Premises, Kalayani Nagar,
Pune - 411014. India
Phone : +91 20 66071319 Extn: 397
Mobile: +91-9422005927
E-mail :Santosh.Gaikwad at saama.com
http://www.saama.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070704/bc001494/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Santosh Gaikwad.vcf
Type: text/x-vcard
Size: 145 bytes
Desc: Santosh Gaikwad.vcf
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070704/bc001494/attachment.vcf;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-07-04 16:08 Webb Sprague <webb.sprague@gmail.com>
parent: Santosh Gaikwad <Santosh.Gaikwad@saama.com>
0 siblings, 0 replies; 131+ messages in thread
From: Webb Sprague @ 2007-07-04 16:08 UTC (permalink / raw)
Please only mail once to the list !
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-07-05 13:04 Broun Uganda <tekuganda@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Broun Uganda @ 2007-07-05 13:04 UTC (permalink / raw)
Dear allI have many points in a map layer which i want to surround with a polygon. Is there a way to automatically create optimum polygons that each enclose only one point and snap at their vertices?Thank youBroun Uganda
_________________________________________________________________
Make every IM count. Download Windows Live Messenger and join the i?m Initiative now. It?s free.?
http://im.live.com/messenger/im/home/?source=TAGWL_June07
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070705/183cc0c6/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-07-09 17:30 Broun Uganda <tekuganda@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Broun Uganda @ 2007-07-09 17:30 UTC (permalink / raw)
Dear all,A trying to write a trigger that would automatically create lines joining points in the sequence in which i insert them. If I insert point AA then BB then CC, i want lines drawn as AA-BB & BB-CC, Using the trigger below lines are drawn ( atleast i can see the gid in table links) without the geometry.May anyone advise me on this.Thank youCREATE OR REPLACE FUNCTION insert_new_links() RETURNS "trigger" AS 'DECLAREstartpoint geometry; endpoint geometry;BEGINstartpoint = asEWKT(NEW.the_geom) WHERE NEW.gid = NEW.gid;endpoint = asEWKT(NEW.the_geom) WHERE NEW.gid = NEW.gid+1;INSERT INTO links(the_geom)VALUES(MakeLine(startpoint, endpoint ));RETURN NEW; END' LANGUAGE plpgsql; CREATE OR TRIGGER insert_new_links_insert BEFORE INSERT ON nodes FOR EACH ROW EXECUTE PROCEDURE insert_new_links();Broun Uganda
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070709/ab1d1cbe/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-08-10 19:33 mero mero <mero_mero2266@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: mero mero @ 2007-08-10 19:33 UTC (permalink / raw)
---------------------------------
Got a little couch potato?
Check out fun summer activities for kids.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070810/6200073b/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-10-05 09:42 Jennehag Åke <Ake.Jennehag@lm.se>
0 siblings, 1 reply; 131+ messages in thread
From: Jennehag Åke @ 2007-10-05 09:42 UTC (permalink / raw)
Hi all!
I work with a cadastral map project i Kyrgyzstan. In this project we will usesPostGIS as the database to store the cadastral objects. What is the most important thing then buying a server to run PostGIS? Is it disk access? Memory? CPU? What are your experiences?
Regards
?ke Jennehag, Swedesurvey consultant (now in Kyrgyzstan)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20071005/a5715204/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2007-10-05 10:23 Gregory Williamson <Gregory.Williamson@digitalglobe.com>
parent: Jennehag Åke <Ake.Jennehag@lm.se>
0 siblings, 0 replies; 131+ messages in thread
From: Gregory Williamson @ 2007-10-05 10:23 UTC (permalink / raw)
This is sort of a broad question, especially without any details about the type of application (OLTP ? Data Warehouse ? What volumes in ? How many connections needed ? etc.).
That said, it is a rare database that is limited by CPU power, although that can happen. If you can buy enough RAM to fit all (or most) of your data into memory then applications which are more-or-less read only will be very fast. (But writing data still needs to go to disk.)
Mostly databases have issues moving lots of data to/from disk, so to that end I generally lean towards recommending lots of disks (more spindles better than sheer RPMs usually), battery backed cache if you can, both for speed and for safety, and don't use RAID5 unless your data is not very important.
Try searching the PostgreSQL archives (see <http://www.postgresql.org/community/lists/; and performance list in particular) for previous questions like this. Since postGIS builds on the database engine for most purposes a good understanding of the database itself are useful.
HTH,
Greg Williamson
Senior DBA
GlobeXplorer LLC, a DigitalGlobe company
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and must be protected in accordance with those provisions. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
(My corporate masters made me say this.)
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net on behalf of Jennehag ?ke
Sent: Fri 10/5/2007 3:42 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] (no subject)
Hi all!
I work with a cadastral map project i Kyrgyzstan. In this project we will usesPostGIS as the database to store the cadastral objects. What is the most important thing then buying a server to run PostGIS? Is it disk access? Memory? CPU? What are your experiences?
Regards
?ke Jennehag, Swedesurvey consultant (now in Kyrgyzstan)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20071005/9ff1e2d6/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2008-04-17 10:29 Priya Sundararajan <priyasundararajan@yahoo.co.in>
0 siblings, 1 reply; 131+ messages in thread
From: Priya Sundararajan @ 2008-04-17 10:29 UTC (permalink / raw)
Hi,
Is it necessary to close the cursor in PLPGSQL ? I didnt close the
cursor. But still i am able to connect to java and work on it efficiently. But
the speed of java(using struts) has been decreased. I have created all the
tables in PLPGSQL using tablespace. Please respond soon. Thanks in
advance.
bye
---------------------------------
Get the freedom to save as many mails as you wish. Click here to know how.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20080417/b6cd0974/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2008-04-18 03:51 RAVI KUMAR <ravivundavalli@yahoo.com>
parent: Priya Sundararajan <priyasundararajan@yahoo.co.in>
0 siblings, 0 replies; 131+ messages in thread
From: RAVI KUMAR @ 2008-04-18 03:51 UTC (permalink / raw)
Hi,
nice to find some Indians on this list.
I use post GIS with JUMP. Eagerly await PostGIS to develop tools for Overlay-UNION, Overlay-Intersection for GIS analysis.
They are there but give result not suitable for analysis.
Would you mind giving
Institute / Project you work for.
OpstGIS, which is your preserred front end (Jump. Qgis. GRASS etc)
What kind of GIS, Raster / Vector you do mostly.
Making a data base of Indians using FOSS GIS.
V. Ravi Kumar
Co-Chair Events OSGeo-India
http://wiki.osgeo.org/wiki/India_Chapter_Report_2007
Priya Sundararajan <priyasundararajan at yahoo.co.in> wrote: Hi,
Is it necessary to close the cursor in PLPGSQL ? I didnt close the
cursor. But still i am able to connect to java and work on it efficiently. But
the speed of java(using struts) has been decreased. I have created all the
tables in PLPGSQL using tablespace. Please respond soon. Thanks in
advance.
bye
---------------------------------
Get the freedom to save as many mails as you wish. Click here to know how._______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20080417/0f3cc9b3/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 06:26 rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
0 siblings, 3 replies; 131+ messages in thread
From: rahul.pachaghare at tcs.com @ 2009-05-13 06:26 UTC (permalink / raw)
Hi,
I am new to this and I am trying to install PostGIS -1.3.6.I have followed
the instructions upto createlang plpgsql..But for
Now load the PostGIS object and function definitions into your database by
loading the lwpostgis.sql definitions file.
# psql -d [yourdatabase] -f lwpostgis.
I am getting a huge errors.The errors are as:
psql:lwpostgis.sql:3295: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3334: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3347: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3354: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3359: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3365: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3374: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3378: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3388: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3392: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3397: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3401: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3405: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3409: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3413: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3417: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3469: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3479: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3485: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3491: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3497: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3503: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3509: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3515: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3521: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3527: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3533: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3539: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3545: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3551: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3557: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3564: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3570: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3576: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3582: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3588: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3594: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3600: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3606: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3612: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3618: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3624: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3630: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3636: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3642: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3648: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3651: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3652: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3653: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3654: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3655: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3656: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3657: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3658: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3659: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3660: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3661: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3662: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3663: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3674: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3680: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3687: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3693: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3700: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3706: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3713: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3719: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3726: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3732: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3738: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3744: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3754: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3760: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3766: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3772: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3778: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3784: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3790: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3796: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3802: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3808: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3818: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3824: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3830: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3836: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3842: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3848: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3854: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3860: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3867: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3873: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3879: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3885: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3891: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3897: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3903: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3909: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3915: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3921: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3927: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3934: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3941: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3947: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3953: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3961: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3969: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3975: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3981: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3987: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3993: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:3999: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4005: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4011: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4017: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4024: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4030: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4036: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4042: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4048: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4055: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4060: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4066: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4073: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4079: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4085: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4092: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4098: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4104: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4111: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4117: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4123: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4129: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4136: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4142: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4149: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4155: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4161: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4168: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4174: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4181: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4187: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4193: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4199: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4205: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4211: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4217: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4223: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4229: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4235: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4241: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4247: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4253: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4263: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4269: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4275: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4281: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4287: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4293: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4302: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4309: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4315: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4322: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4328: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4335: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4342: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4352: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4359: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4365: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4372: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4379: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4385: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4392: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4399: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4409: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4415: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4421: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4427: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4433: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4439: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4445: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4456: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4462: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4468: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4474: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4480: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4486: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4492: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4498: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4504: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4510: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4516: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4522: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4528: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4534: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4540: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4546: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4552: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4579: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4585: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4591: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4597: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4603: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4609: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4615: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4621: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4627: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4633: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4639: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4645: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4651: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4657: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4663: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4669: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4675: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4681: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4687: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4693: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4699: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4705: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4711: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4717: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4723: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4729: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4735: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4741: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4747: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4753: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4759: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4765: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4771: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4777: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4782: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4787: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4792: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4797: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4807: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4817: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4827: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4838: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4848: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4858: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4868: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4878: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4884: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4890: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4900: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4910: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4920: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4930: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4936: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4942: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4948: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4954: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4965: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4976: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4986: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:4996: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5002: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5008: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5014: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5020: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5030: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5040: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5050: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5060: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5066: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5072: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5078: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5084: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5090: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5100: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5110: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5120: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5130: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5136: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5142: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5148: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5154: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5165: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5176: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5187: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5198: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5204: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5210: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5216: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5222: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5232: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5242: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5252: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5262: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5272: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5282: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5292: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5302: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5312: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5322: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5332: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5342: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5352: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5362: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5372: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5382: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5392: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5402: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5412: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5422: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5432: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5442: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5452: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5462: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5472: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5482: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5492: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5502: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5512: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5522: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5532: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5542: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5552: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5562: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5572: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5582: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5592: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5602: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5612: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5622: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5632: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5642: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5652: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5662: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5673: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5684: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5695: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5706: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5749: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5778: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5814: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5838: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5882: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5933: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5940: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5947: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5954: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:5987: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6020: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6027: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6032: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6037: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6096: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6114: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6159: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6218: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6238: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6295: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6318: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6332: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6346: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6360: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6366: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6372: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6410: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6459: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6482: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6488: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6512: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6523: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6528: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:6533: ERROR: current transaction is aborted, commands
ignored until end of transaction block
ROLLBACK
Above is not the complete list of errors.....Anyone got any idea?
Thank You in advance.
Regards,
Rahul Pachaghare
Member,TEG Open Source
Tata Consultancy Services
Mailto: rahul.pachaghare at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 06:51 strk <strk@keybit.net>
parent: rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2 siblings, 1 reply; 131+ messages in thread
From: strk @ 2009-05-13 06:51 UTC (permalink / raw)
On Wed, May 13, 2009 at 11:56:45AM +0530, rahul.pachaghare at tcs.com wrote:
>
> Hi,
> I am new to this and I am trying to install PostGIS -1.3.6.I have followed
> the instructions upto createlang plpgsql..But for
>
> Now load the PostGIS object and function definitions into your database by
> loading the lwpostgis.sql definitions file.
>
>
> # psql -d [yourdatabase] -f lwpostgis.
>
> I am getting a huge errors.The errors are as:
> psql:lwpostgis.sql:3295: ERROR: current transaction is aborted, commands
You should be looking for the first error you get.
Guys, we should really document in the README the flag to tell
psql to abort on first error. I keep forgetting it.
--strk;
Free GIS & Flash consultant/developer () ASCII Ribbon Campaign
http://foo.keybit.net/~strk/services.html /\ Keep it simple!
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 06:55 Anton Patrushev <anton@orkney.co.jp>
parent: rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2 siblings, 1 reply; 131+ messages in thread
From: Anton Patrushev @ 2009-05-13 06:55 UTC (permalink / raw)
Hi,
It looks like you forgot to create Pl/pgSQL language in your database.
Anton.
On Wed, May 13, 2009 at 3:26 PM, <rahul.pachaghare at tcs.com> wrote:
>
> Hi,
> I am new to this and I am trying to install PostGIS -1.3.6.I have followed
> the instructions upto createlang plpgsql..But for
>
> Now load the PostGIS object and function definitions into your database by
> loading the lwpostgis.sql definitions file.
>
>
> # psql -d [yourdatabase] -f lwpostgis.
>
>
> I am getting a huge errors.The errors are as:
> psql:lwpostgis.sql:3295: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3334: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3347: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3354: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3359: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3365: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3374: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3378: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3388: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3392: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3397: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3401: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3405: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3409: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3413: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3417: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3469: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3479: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3485: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3491: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3497: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3503: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3509: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3515: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3521: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3527: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3533: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3539: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3545: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3551: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3557: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3564: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3570: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3576: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3582: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3588: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3594: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3600: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3606: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3612: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3618: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3624: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3630: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3636: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3642: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3648: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3651: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3652: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3653: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3654: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3655: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3656: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3657: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3658: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3659: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3660: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3661: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3662: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3663: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3674: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3680: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3687: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3693: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3700: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3706: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3713: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3719: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3726: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3732: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3738: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3744: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3754: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3760: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3766: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3772: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3778: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3784: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3790: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3796: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3802: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3808: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3818: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3824: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3830: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3836: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3842: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3848: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3854: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3860: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3867: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3873: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3879: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3885: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3891: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3897: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3903: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3909: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3915: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3921: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3927: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3934: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3941: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3947: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3953: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3961: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3969: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3975: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3981: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3987: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3993: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3999: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4005: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4011: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4017: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4024: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4030: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4036: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4042: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4048: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4055: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4060: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4066: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4073: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4079: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4085: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4092: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4098: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4104: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4111: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4117: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4123: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4129: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4136: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4142: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4149: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4155: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4161: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4168: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4174: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4181: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4187: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4193: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4199: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4205: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4211: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4217: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4223: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4229: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4235: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4241: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4247: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4253: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4263: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4269: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4275: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4281: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4287: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4293: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4302: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4309: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4315: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4322: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4328: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4335: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4342: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4352: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4359: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4365: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4372: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4379: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4385: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4392: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4399: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4409: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4415: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4421: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4427: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4433: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4439: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4445: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4456: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4462: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4468: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4474: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4480: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4486: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4492: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4498: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4504: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4510: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4516: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4522: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4528: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4534: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4540: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4546: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4552: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4579: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4585: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4591: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4597: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4603: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4609: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4615: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4621: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4627: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4633: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4639: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4645: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4651: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4657: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4663: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4669: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4675: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4681: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4687: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4693: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4699: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4705: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4711: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4717: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4723: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4729: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4735: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4741: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4747: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4753: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4759: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4765: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4771: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4777: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4782: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4787: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4792: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4797: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4807: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4817: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4827: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4838: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4848: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4858: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4868: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4878: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4884: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4890: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4900: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4910: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4920: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4930: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4936: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4942: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4948: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4954: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4965: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4976: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4986: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4996: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5002: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5008: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5014: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5020: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5030: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5040: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5050: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5060: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5066: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5072: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5078: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5084: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5090: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5100: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5110: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5120: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5130: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5136: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5142: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5148: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5154: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5165: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5176: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5187: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5198: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5204: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5210: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5216: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5222: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5232: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5242: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5252: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5262: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5272: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5282: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5292: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5302: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5312: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5322: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5332: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5342: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5352: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5362: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5372: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5382: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5392: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5402: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5412: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5422: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5432: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5442: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5452: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5462: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5472: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5482: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5492: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5502: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5512: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5522: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5532: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5542: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5552: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5562: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5572: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5582: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5592: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5602: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5612: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5622: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5632: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5642: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5652: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5662: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5673: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5684: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5695: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5706: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5749: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5778: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5814: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5838: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5882: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5933: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5940: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5947: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5954: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5987: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6020: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6027: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6032: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6037: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6096: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6114: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6159: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6218: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6238: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6295: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6318: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6332: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6346: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6360: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6366: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6372: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6410: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6459: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6482: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6488: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6512: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6523: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6528: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6533: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> ROLLBACK
>
> Above is not the complete list of errors.....Anyone got any idea?
>
> Thank You in advance.
>
>
>
>
> Regards,
> Rahul Pachaghare
> Member,TEG Open Source
> Tata Consultancy Services
> Mailto: rahul.pachaghare at tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. ? IT Services
> ? ? ? ? ? ? ? ? ?Business Solutions
> ? ? ? ? ? ? ? ? ?Outsourcing
> ____________________________________________
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 06:55 Ben Madin <ben@remoteinformation.com.au>
parent: rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2 siblings, 1 reply; 131+ messages in thread
From: Ben Madin @ 2009-05-13 06:55 UTC (permalink / raw)
Rahul,
For a start, look at the start of the list of errors - something has
gone wrong, and so nothing else is being processed - try sending the
first few lines of the errors.
cheers
Ben
On 13/05/2009, at 2:26 PM, rahul.pachaghare at tcs.com wrote:
>
> Hi,
> I am new to this and I am trying to install PostGIS -1.3.6.I have
> followed
> the instructions upto createlang plpgsql..But for
>
> Now load the PostGIS object and function definitions into your
> database by
> loading the lwpostgis.sql definitions file.
>
>
> # psql -d [yourdatabase] -f lwpostgis.
>
>
> I am getting a huge errors.The errors are as:
> psql:lwpostgis.sql:3295: ERROR: current transaction is aborted,
> commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6533: ERROR: current transaction is aborted,
> commands
> ignored until end of transaction block
> ROLLBACK
>
> Above is not the complete list of errors.....Anyone got any idea?
>
> Thank You in advance.
>
> Regards,
> Rahul Pachaghare
--
Ben Madin
REMOTE INFORMATION
t : +61 8 9192 5455
f : +61 8 9192 5535
m : 0448 887 220
Broome WA 6725
ben at remoteinformation.com.au
Out here, it pays to know...
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 07:03 rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
parent: Anton Patrushev <anton@orkney.co.jp>
0 siblings, 1 reply; 131+ messages in thread
From: rahul.pachaghare at tcs.com @ 2009-05-13 07:03 UTC (permalink / raw)
Hi..
I have created plgsql with the command
createlang plpgsql [yourdatabase]
Thank you.
Regards,
Rahul Pachaghare
Member,TEG Open Source
Tata Consultancy Services
Mailto: rahul.pachaghare at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
Anton Patrushev
<anton at orkney.co.
jp> To
Sent by: PostGIS Users Discussion
postgis-users-bou <postgis-users at postgis.refractions.
nces at postgis.refr net>
actions.net cc
Subject
05/13/2009 12:25 Re: [postgis-users] (no subject)
PM
Please respond to
PostGIS Users
Discussion
<postgis-users at po
stgis.refractions
.net>
Hi,
It looks like you forgot to create Pl/pgSQL language in your database.
Anton.
On Wed, May 13, 2009 at 3:26 PM, <rahul.pachaghare at tcs.com> wrote:
>
> Hi,
> I am new to this and I am trying to install PostGIS -1.3.6.I have
followed
> the instructions upto createlang plpgsql..But for
>
> Now load the PostGIS object and function definitions into your database
by
> loading the lwpostgis.sql definitions file.
>
>
> # psql -d [yourdatabase] -f lwpostgis.
>
>
> I am getting a huge errors.The errors are as:
> psql:lwpostgis.sql:3295: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3334: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3347: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3354: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3359: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3365: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3374: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3378: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3388: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3392: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3397: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3401: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3405: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3409: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3413: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3417: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3469: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3479: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3485: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3491: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3497: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3503: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3509: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3515: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3521: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3527: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3533: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3539: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3545: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3551: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3557: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3564: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3570: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3576: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3582: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3588: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3594: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3600: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3606: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3612: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3618: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3624: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3630: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3636: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3642: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3648: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3651: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3652: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3653: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3654: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3655: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3656: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3657: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3658: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3659: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3660: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3661: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3662: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3663: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3674: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3680: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3687: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3693: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3700: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3706: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3713: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3719: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3726: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3732: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3738: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3744: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3754: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3760: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3766: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3772: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3778: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3784: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3790: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3796: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3802: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3808: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3818: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3824: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3830: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3836: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3842: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3848: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3854: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3860: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3867: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3873: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3879: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3885: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3891: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3897: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3903: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3909: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3915: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3921: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3927: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3934: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3941: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3947: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3953: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3961: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3969: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3975: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3981: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3987: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3993: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:3999: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4005: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4011: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4017: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4024: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4030: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4036: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4042: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4048: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4055: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4060: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4066: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4073: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4079: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4085: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4092: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4098: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4104: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4111: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4117: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4123: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4129: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4136: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4142: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4149: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4155: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4161: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4168: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4174: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4181: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4187: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4193: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4199: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4205: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4211: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4217: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4223: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4229: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4235: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4241: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4247: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4253: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4263: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4269: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4275: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4281: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4287: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4293: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4302: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4309: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4315: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4322: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4328: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4335: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4342: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4352: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4359: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4365: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4372: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4379: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4385: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4392: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4399: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4409: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4415: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4421: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4427: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4433: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4439: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4445: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4456: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4462: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4468: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4474: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4480: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4486: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4492: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4498: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4504: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4510: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4516: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4522: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4528: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4534: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4540: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4546: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4552: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4579: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4585: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4591: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4597: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4603: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4609: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4615: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4621: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4627: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4633: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4639: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4645: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4651: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4657: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4663: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4669: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4675: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4681: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4687: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4693: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4699: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4705: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4711: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4717: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4723: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4729: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4735: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4741: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4747: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4753: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4759: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4765: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4771: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4777: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4782: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4787: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4792: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4797: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4807: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4817: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4827: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4838: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4848: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4858: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4868: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4878: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4884: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4890: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4900: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4910: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4920: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4930: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4936: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4942: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4948: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4954: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4965: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4976: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4986: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:4996: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5002: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5008: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5014: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5020: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5030: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5040: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5050: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5060: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5066: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5072: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5078: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5084: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5090: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5100: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5110: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5120: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5130: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5136: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5142: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5148: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5154: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5165: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5176: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5187: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5198: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5204: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5210: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5216: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5222: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5232: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5242: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5252: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5262: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5272: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5282: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5292: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5302: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5312: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5322: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5332: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5342: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5352: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5362: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5372: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5382: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5392: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5402: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5412: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5422: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5432: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5442: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5452: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5462: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5472: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5482: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5492: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5502: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5512: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5522: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5532: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5542: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5552: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5562: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5572: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5582: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5592: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5602: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5612: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5622: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5632: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5642: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5652: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5662: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5673: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5684: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5695: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5706: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5749: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5778: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5814: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5838: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5882: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5933: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5940: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5947: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5954: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:5987: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6020: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6027: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6032: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6037: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6096: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6114: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6159: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6218: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6238: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6295: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6318: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6332: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6346: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6360: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6366: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6372: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6410: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6459: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6482: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6488: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6512: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6523: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6528: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6533: ERROR: ?current transaction is aborted, commands
> ignored until end of transaction block
> ROLLBACK
>
> Above is not the complete list of errors.....Anyone got any idea?
>
> Thank You in advance.
>
>
>
>
> Regards,
> Rahul Pachaghare
> Member,TEG Open Source
> Tata Consultancy Services
> Mailto: rahul.pachaghare at tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. ? IT Services
> ? ? ? ? ? ? ? ? ?Business Solutions
> ? ? ? ? ? ? ? ? ?Outsourcing
> ____________________________________________
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
ForwardSourceID:NT00003A6E
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 07:12 Pradeep B V <pradeepbv@gmail.com>
parent: rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
0 siblings, 0 replies; 131+ messages in thread
From: Pradeep B V @ 2009-05-13 07:12 UTC (permalink / raw)
Rahul,
See if this can help
http://www.mail-archive.com/postgis-users at postgis.refractions.net/msg00644.html
- p
On Wed, May 13, 2009 at 12:33 PM, <rahul.pachaghare at tcs.com> wrote:
> Hi..
> I have created plgsql with the command
> createlang plpgsql [yourdatabase]
>
> Thank you.
> Regards,
> Rahul Pachaghare
> Member,TEG Open Source
> Tata Consultancy Services
> Mailto: rahul.pachaghare at tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. IT Services
> Business Solutions
> Outsourcing
> ____________________________________________
>
>
>
> Anton Patrushev
> <anton at orkney.co.
> jp> To
> Sent by: PostGIS Users Discussion
> postgis-users-bou <postgis-users at postgis.refractions.
> nces at postgis.refr net>
> actions.net cc
>
> Subject
> 05/13/2009 12:25 Re: [postgis-users] (no subject)
> PM
>
>
> Please respond to
> PostGIS Users
> Discussion
> <postgis-users at po
> stgis.refractions
> .net>
>
>
>
>
>
>
> Hi,
>
> It looks like you forgot to create Pl/pgSQL language in your database.
>
> Anton.
>
> On Wed, May 13, 2009 at 3:26 PM, <rahul.pachaghare at tcs.com> wrote:
> >
> > Hi,
> > I am new to this and I am trying to install PostGIS -1.3.6.I have
> followed
> > the instructions upto createlang plpgsql..But for
> >
> > Now load the PostGIS object and function definitions into your database
> by
> > loading the lwpostgis.sql definitions file.
> >
> >
> > # psql -d [yourdatabase] -f lwpostgis.
> >
> >
> > I am getting a huge errors.The errors are as:
> > psql:lwpostgis.sql:3295: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3334: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3347: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3354: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3359: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3365: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3374: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3378: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3388: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3392: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3397: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3401: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3405: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3409: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3413: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3417: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3469: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3479: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3485: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3491: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3497: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3503: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3509: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3515: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3521: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3527: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3533: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3539: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3545: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3551: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3557: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3564: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3570: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3576: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3582: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3588: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3594: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3600: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3606: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3612: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3618: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3624: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3630: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3636: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3642: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3648: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3651: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3652: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3653: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3654: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3655: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3656: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3657: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3658: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3659: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3660: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3661: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3662: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3663: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3674: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3680: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3687: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3693: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3700: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3706: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3713: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3719: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3726: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3732: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3738: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3744: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3754: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3760: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3766: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3772: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3778: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3784: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3790: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3796: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3802: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3808: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3818: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3824: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3830: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3836: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3842: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3848: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3854: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3860: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3867: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3873: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3879: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3885: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3891: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3897: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3903: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3909: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3915: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3921: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3927: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3934: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3941: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3947: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3953: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3961: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3969: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3975: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3981: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3987: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3993: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:3999: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4005: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4011: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4017: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4024: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4030: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4036: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4042: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4048: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4055: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4060: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4066: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4073: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4079: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4085: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4092: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4098: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4104: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4111: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4117: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4123: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4129: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4136: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4142: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4149: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4155: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4161: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4168: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4174: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4181: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4187: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4193: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4199: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4205: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4211: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4217: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4223: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4229: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4235: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4241: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4247: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4253: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4263: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4269: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4275: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4281: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4287: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4293: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4302: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4309: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4315: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4322: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4328: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4335: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4342: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4352: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4359: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4365: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4372: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4379: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4385: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4392: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4399: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4409: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4415: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4421: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4427: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4433: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4439: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4445: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4456: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4462: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4468: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4474: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4480: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4486: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4492: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4498: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4504: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4510: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4516: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4522: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4528: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4534: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4540: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4546: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4552: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4579: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4585: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4591: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4597: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4603: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4609: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4615: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4621: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4627: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4633: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4639: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4645: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4651: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4657: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4663: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4669: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4675: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4681: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4687: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4693: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4699: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4705: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4711: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4717: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4723: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4729: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4735: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4741: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4747: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4753: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4759: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4765: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4771: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4777: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4782: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4787: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4792: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4797: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4807: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4817: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4827: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4838: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4848: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4858: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4868: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4878: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4884: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4890: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4900: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4910: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4920: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4930: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4936: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4942: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4948: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4954: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4965: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4976: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4986: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:4996: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5002: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5008: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5014: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5020: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5030: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5040: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5050: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5060: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5066: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5072: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5078: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5084: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5090: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5100: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5110: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5120: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5130: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5136: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5142: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5148: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5154: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5165: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5176: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5187: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5198: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5204: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5210: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5216: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5222: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5232: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5242: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5252: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5262: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5272: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5282: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5292: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5302: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5312: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5322: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5332: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5342: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5352: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5362: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5372: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5382: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5392: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5402: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5412: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5422: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5432: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5442: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5452: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5462: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5472: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5482: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5492: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5502: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5512: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5522: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5532: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5542: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5552: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5562: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5572: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5582: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5592: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5602: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5612: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5622: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5632: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5642: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5652: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5662: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5673: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5684: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5695: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5706: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5749: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5778: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5814: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5838: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5882: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5933: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5940: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5947: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5954: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:5987: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6020: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6027: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6032: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6037: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6096: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6114: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6159: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6218: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6238: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6295: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6318: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6332: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6346: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6360: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6366: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6372: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6410: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6459: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6482: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6488: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6512: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6523: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6528: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > psql:lwpostgis.sql:6533: ERROR: current transaction is aborted, commands
> > ignored until end of transaction block
> > ROLLBACK
> >
> > Above is not the complete list of errors.....Anyone got any idea?
> >
> > Thank You in advance.
> >
> >
> >
> >
> > Regards,
> > Rahul Pachaghare
> > Member,TEG Open Source
> > Tata Consultancy Services
> > Mailto: rahul.pachaghare at tcs.com
> > Website: http://www.tcs.com
> > ____________________________________________
> > Experience certainty. IT Services
> > Business Solutions
> > Outsourcing
> > ____________________________________________
> >
> > =====-----=====-----=====
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
> >
> >
> >
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> >
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
> ForwardSourceID:NT00003A6E
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
--
Pradeep B V
+91 94498 23772
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20090513/903adc1b/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 07:17 rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
parent: Ben Madin <ben@remoteinformation.com.au>
0 siblings, 0 replies; 131+ messages in thread
From: rahul.pachaghare at tcs.com @ 2009-05-13 07:17 UTC (permalink / raw)
Hi..
Thank you for your reply....
the first few lines are:
psql -d newpsqldb -f lwpostgis.sql -U postgres | less
psql:lwpostgis.sql:44: NOTICE: type "histogram2d" is not yet defined
DETAIL: Creating a shell type definition.
psql:lwpostgis.sql:44: ERROR: could not load library
"/usr/local/pgsql/lib/liblwgeom.so": libgeos_c.so.1: cannot open shared
object file: No such file or directory
psql:lwpostgis.sql:50: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:56: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:62: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:70: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:88: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:94: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:100: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:106: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:113: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:131: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:137: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:143: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:149: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:159: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:170: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:176: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:183: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:189: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:196: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:202: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:209: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:215: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:222: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:228: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:235: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:241: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:247: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:253: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:259: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:265: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:272: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:278: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:285: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:291: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:299: ERROR: current transaction is aborted, commands
ignored until end of transaction block
Thank you.
Regards,
Rahul Pachaghare
Member,TEG Open Source
Tata Consultancy Services
Mailto: rahul.pachaghare at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
Ben Madin
<ben at remoteinform
ation.com.au> To
Sent by: PostGIS Users Discussion
postgis-users-bou <postgis-users at postgis.refractions.
nces at postgis.refr net>
actions.net cc
Subject
05/13/2009 12:25 Re: [postgis-users] (no subject)
PM
Please respond to
PostGIS Users
Discussion
<postgis-users at po
stgis.refractions
.net>
Rahul,
For a start, look at the start of the list of errors - something has
gone wrong, and so nothing else is being processed - try sending the
first few lines of the errors.
cheers
Ben
On 13/05/2009, at 2:26 PM, rahul.pachaghare at tcs.com wrote:
>
> Hi,
> I am new to this and I am trying to install PostGIS -1.3.6.I have
> followed
> the instructions upto createlang plpgsql..But for
>
> Now load the PostGIS object and function definitions into your
> database by
> loading the lwpostgis.sql definitions file.
>
>
> # psql -d [yourdatabase] -f lwpostgis.
>
>
> I am getting a huge errors.The errors are as:
> psql:lwpostgis.sql:3295: ERROR: current transaction is aborted,
> commands
> ignored until end of transaction block
> psql:lwpostgis.sql:6533: ERROR: current transaction is aborted,
> commands
> ignored until end of transaction block
> ROLLBACK
>
> Above is not the complete list of errors.....Anyone got any idea?
>
> Thank You in advance.
>
> Regards,
> Rahul Pachaghare
--
Ben Madin
REMOTE INFORMATION
t : +61 8 9192 5455
f : +61 8 9192 5535
m : 0448 887 220
Broome WA 6725
ben at remoteinformation.com.au
Out here, it pays to know...
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
ForwardSourceID:NT00003A76
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-05-13 07:22 rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
parent: strk <strk@keybit.net>
0 siblings, 0 replies; 131+ messages in thread
From: rahul.pachaghare at tcs.com @ 2009-05-13 07:22 UTC (permalink / raw)
Hi..
Thank you for your reply....
the first few lines are:
psql -d newpsqldb -f lwpostgis.sql -U postgres | less
psql:lwpostgis.sql:44: NOTICE: type "histogram2d" is not yet defined
DETAIL: Creating a shell type definition.
psql:lwpostgis.sql:44: ERROR: could not load library
"/usr/local/pgsql/lib/liblwgeom.so": libgeos_c.so.1: cannot open shared
object file: No such file or directory
psql:lwpostgis.sql:50: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:56: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:62: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:70: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:88: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:94: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:100: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:106: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:113: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:131: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:137: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:143: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:149: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:159: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:170: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:176: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:183: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:189: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:196: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:202: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:209: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:215: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:222: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:228: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:235: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:241: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:247: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:253: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:259: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:265: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:272: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:278: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:285: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:291: ERROR: current transaction is aborted, commands
ignored until end of transaction block
psql:lwpostgis.sql:299: ERROR: current transaction is aborted, commands
ignored until end of transaction block
Thank you.
Regards,
Rahul Pachaghare
Member,TEG Open Source
Tata Consultancy Services
Mailto: rahul.pachaghare at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
strk
<strk at keybit.net>
Sent by: To
postgis-users-bou PostGIS Users Discussion
nces at postgis.refr <postgis-users at postgis.refractions.
actions.net net>
cc
05/13/2009 12:21 Subject
PM Re: [postgis-users] (no subject)
Please respond to
PostGIS Users
Discussion
<postgis-users at po
stgis.refractions
.net>
On Wed, May 13, 2009 at 11:56:45AM +0530, rahul.pachaghare at tcs.com wrote:
>
> Hi,
> I am new to this and I am trying to install PostGIS -1.3.6.I have
followed
> the instructions upto createlang plpgsql..But for
>
> Now load the PostGIS object and function definitions into your database
by
> loading the lwpostgis.sql definitions file.
>
>
> # psql -d [yourdatabase] -f lwpostgis.
>
> I am getting a huge errors.The errors are as:
> psql:lwpostgis.sql:3295: ERROR: current transaction is aborted, commands
You should be looking for the first error you get.
Guys, we should really document in the README the flag to tell
psql to abort on first error. I keep forgetting it.
--strk;
Free GIS & Flash consultant/developer () ASCII Ribbon Campaign
http://foo.keybit.net/~strk/services.html /\ Keep it simple!
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
ForwardSourceID:NT00003A6A
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-08-14 08:40 Pena Kupen <kupen@wippies.fi>
0 siblings, 0 replies; 131+ messages in thread
From: Pena Kupen @ 2009-08-14 08:40 UTC (permalink / raw)
Leo,
>Which version of PostGIS is this? I presume 1.3.6?
in fgs it seems to be
postgis-lib:1.3.5
>You could always compile yourself or
Yeps that's one solution, but I like to use fgs ready made packeges of Mapserver
>maybe this is left over from your
>PostgreSQL 8.3 install and postgis really wasn't installed.
My postgres is running on 8.4 and there has not been any previous one.
To mee it show that postgis is installed ok.
--
pk
-----Original Message-----
Pena,
Which version of PostGIS is this? I presume 1.3.6?
You could always compile yourself or maybe this is left over from your
PostgreSQL 8.3 install and postgis really wasn't installed.
Leo
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Pena
Kupen
Sent: Thursday, August 13, 2009 10:57 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Version mismatch
Hello all,
I'm runnig postgres 8.4.0 on centos 5
and postgis installed from latest fgs package.
It seems that fgs libraries are old one's.
I got error below, when try to rung
psql -d mydatabase -f lwpostgis.sql
BEGIN
psql:lwpostgis.sql:44: NOTICE: type "histogram2d" is not yet defined
DETAIL: Creating a shell type definition.
psql:lwpostgis.sql:44: ERROR: incompatible library
"/opt/fgs/lib/liblwgeomso": version mismatch
DETAIL: Server is version 8.4, library is version 8.3.
Is there anything I can do, but downgrade to postgres 8.3?
--
pk
--
Saunalahti DataPaketti - tilaa nyt, saat 2 kk veloituksetta ja Nettitikun kaupan p??lle!
http://saunalahti.fi/gsm/gsmdatapaketti.php
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-09-29 17:10 eehab hamzeh <eehab40@hotmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: eehab hamzeh @ 2009-09-29 17:10 UTC (permalink / raw)
thanks for your replay, do you mean to add some like this, i keep receiving error
CREATE TABLE example_intersections_b AS (select id, SELECT DISTINCT st_intersects(part_1.the_geom, part_2.the_geom)
FROM source AS part_1,
faces_obj AS part_2
WHERE part_1.id <> part_2.id
);
kind regards
ihab
hello all,
>
> I need to know the id of the object that are intersect, i use the following
> query. can any body help to develop it to contain the id.
>
>
> CREATE TABLE example_intersections_b AS (
> SELECT DISTINCT st_intersects(part_1.the_geom, part_2.the_geom)
> FROM source AS part_1,
> faces_obj AS part_2
> WHERE part_1.id <> part_2.id
> );
>
CREATE TABLE example_intersections_b AS
(
SELECT DISTINCT st_intersects(part_1.the_geom, part_2.the_geom),
part_1.id,
part_2.id
FROM source AS part_1,
faces_obj AS part_2
WHERE part_1.id <> part_2.id
);
You don't need anything complicated here. Just add your ids directly in your
SELECT query.
Emilie Laffray
_________________________________________________________________
Drag n? drop?Get easy photo sharing with Windows Live? Photos.
http://www.microsoft.com/windows/windowslive/products/photos.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20090929/b5e0f916/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2009-09-29 18:36 Emilie Laffray <emilie.laffray@gmail.com>
parent: eehab hamzeh <eehab40@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Emilie Laffray @ 2009-09-29 18:36 UTC (permalink / raw)
eehab hamzeh wrote:
> thanks for your replay, do you mean to add some like this, i keep
> receiving error
>
> CREATE TABLE example_intersections_b AS (select id, SELECT DISTINCT
> st_intersects(part_1.the_geom, part_2.the_geom)
> FROM source AS part_1,
> faces_obj AS part_2
> WHERE part_1.id <> part_2.id
> );
Your query is not valid. Your double select is not valid SQL. This
should be the valid sequence. Obviously, I don't have your table
structure, but in theory this should work.
CREATE TABLE example_intersections_b AS
( SELECT DISTINCT
part_1.id,
part_2.id,
st_intersects(part_1.the_geom,
part_2.the_geom)
FROM source AS part_1,
faces_obj AS part_2
WHERE part_1.id <> part_2.id
);
Plus you may want to give the error you are getting to be helped in a
more efficient manner.
Emilie Laffray
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20090929/e4c3688a/attachment.pgp;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-04-07 00:47 Chen, Li [Contractor] <Li.Chen@andrew.com>
0 siblings, 0 replies; 131+ messages in thread
From: Chen, Li [Contractor] @ 2010-04-07 00:47 UTC (permalink / raw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100407/e8afb682/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-05-22 17:29 Ivan Mincik <ivan.mincik@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Ivan Mincik @ 2010-05-22 17:29 UTC (permalink / raw)
2010/5/22 eehab hamzeh <eehab40 at hotmail.com>
> Hello,
>
> Thanks for your replay, but in my PostGIS 1.5.1 it works fine, i don't have
> any problem in geometry
> try it again please
>
> Yes, now it is giving valid geometry in my PostGIS.
"POSTGIS="1.3.3" GEOS="3.0.0-CAPI-1.4.1" PROJ="Rel. 4.6.0, 21 Dec 2007"
USE_STATS"
Sorry, I do not have any 1.5 version installed.
Your geometry is now:
"MULTIPOLYGON(((433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.130099999 5793254.90431)),((433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431)),((433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.137969999 5793254.88592)),((433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.137969999
5793254.88592)),((433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.125979999 5793254.86991)),((433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.125979999
5793254.86991)),((433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.106129999 5793254.87229)),((433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.106129999
5793254.87229)),((433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.098259999 5793254.89068)),((433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.098259999
5793254.89068)),((433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669)),((433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.110239999
5793254.90669)),((433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.110239999 5793254.90669)),((433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431,433354.136499999 5793254.89617,433354.136499999
5793254.89617,433354.136499999 5793254.89617,433354.137969999
5793254.88592,433354.137969999 5793254.88592,433354.137969999
5793254.88592,433354.134119999 5793254.87631,433354.134119999
5793254.87631,433354.134119999 5793254.87631,433354.125979999
5793254.86991,433354.125979999 5793254.86991,433354.125979999
5793254.86991,433354.115739999 5793254.86844,433354.115739999
5793254.86844,433354.115739999 5793254.86844,433354.106129999
5793254.87229,433354.106129999 5793254.87229,433354.106129999
5793254.87229,433354.099729999 5793254.88043,433354.099729999
5793254.88043,433354.099729999 5793254.88043,433354.098259999
5793254.89068,433354.098259999 5793254.89068,433354.098259999
5793254.89068,433354.102109999 5793254.90029,433354.102109999
5793254.90029,433354.102109999 5793254.90029,433354.110239999
5793254.90669,433354.110239999 5793254.90669,433354.110239999
5793254.90669,433354.120489999 5793254.90816,433354.120489999
5793254.90816,433354.120489999 5793254.90816,433354.130099999
5793254.90431,433354.130099999 5793254.90431,433354.130099999
5793254.90431)))"
Ivan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100522/ffe47b3b/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-09-13 19:04 Rorie Overby <ogrears@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Rorie Overby @ 2010-09-13 19:04 UTC (permalink / raw)
http://niyutona.tripod.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100913/63b976a7/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-09-16 15:11 Henri De Feraudy <feraudyh@yahoo.com>
0 siblings, 1 reply; 131+ messages in thread
From: Henri De Feraudy @ 2010-09-16 15:11 UTC (permalink / raw)
The SQL Cookbook recommends the following SQL code to copy a table's structure
from table1 to table2:
create table table2 as select * from table1 where 1=0;
What's great about this is that it obviates the need to know the structure of
table1.
But what if table1 has a geometry column?
As geometry column existence is recorded in some other tables it doesnt look as
if the above trick is doing enough.
What's your suggestion?
Henri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100916/d8771b1b/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-09-16 15:53 Kevin Neufeld <kneufeld@refractions.net>
parent: Henri De Feraudy <feraudyh@yahoo.com>
0 siblings, 1 reply; 131+ messages in thread
From: Kevin Neufeld @ 2010-09-16 15:53 UTC (permalink / raw)
It's true that if you create a table in this manner, the geometry column
of table2 won't be registered with the geometry column metadata
information listed in geometry_columns (which is often needed by
third-party applications). Further, the table2 table will be missing
the usual 3 sanity check constraints usually placed on a geometry
column. In other words, after table2 has been created, you could
theoretically update the geometry column to contain mixed geometry
types, projections, or dimensions - a sure source of bugs in any
application.
Populate_Geometry_Columns() addresses these issues.
http://postgis.refractions.net/docs/Populate_Geometry_Columns.html
SELECT Populate_Geometry_Columns('table2'::regclass);
Cheers,
Kevin
On 9/16/2010 8:11 AM, Henri De Feraudy wrote:
> The SQL Cookbook recommends the following SQL code to copy a table's
> structure from table1 to table2:
>
> create table table2 as select * from table1 where 1=0;
>
> What's great about this is that it obviates the need to know the
> structure of table1.
>
> But what if table1 has a geometry column?
> As geometry column existence is recorded in some other tables it
> doesnt look as if the above trick is doing enough.
> What's your suggestion?
> Henri
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100916/986e2dd2/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-09-16 17:13 Henri De Feraudy <feraudyh@yahoo.com>
parent: Kevin Neufeld <kneufeld@refractions.net>
0 siblings, 1 reply; 131+ messages in thread
From: Henri De Feraudy @ 2010-09-16 17:13 UTC (permalink / raw)
Thankyou Kevin,
I suppose that the oid of a table is what 'table2'::regclass returns.
I wonder what the parameterless version of Populate_Geometry_Columns does, I
can't see its description in the documentation.
Henri
________________________________
From: Kevin Neufeld <kneufeld at refractions.net>
To: postgis-users at postgis.refractions.net
Sent: Thu, September 16, 2010 5:53:04 PM
Subject: Re: [postgis-users] (no subject)
It's true that if you create a table in this manner, the geometry column of
table2 won't be registered with the geometry column metadata information listed
in geometry_columns (which is often needed by third-party applications).
Further, the table2 table will be missing the usual 3 sanity check constraints
usually placed on a geometry column. In other words, after table2 has been
created, you could theoretically update the geometry column to contain mixed
geometry types, projections, or dimensions - a sure source of bugs in any
application.
Populate_Geometry_Columns() addresses these issues.
http://postgis.refractions.net/docs/Populate_Geometry_Columns.html
SELECT Populate_Geometry_Columns('table2'::regclass);
Cheers,
Kevin
On 9/16/2010 8:11 AM, Henri De Feraudy wrote:
The SQL Cookbook recommends the following SQL code to copy a table's structure
from table1 to table2:
>
>
>create table table2 as select * from table1 where 1=0;
>
>
>What's great about this is that it obviates the need to know the structure of
>table1.
>
>
>But what if table1 has a geometry column?
>As geometry column existence is recorded in some other tables it doesnt look as
>if the above trick is doing enough.
>What's your suggestion?
>Henri
>
>
> _______________________________________________ postgis-users mailing list
>postgis-users at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100916/cef44949/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-09-16 17:17 Henri De Feraudy <feraudyh@yahoo.com>
parent: Henri De Feraudy <feraudyh@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: Henri De Feraudy @ 2010-09-16 17:17 UTC (permalink / raw)
Oops, sorry I didnt read far enough to see what the parameterless version does.
It's time I took a break from work.
Henri
________________________________
From: Henri De Feraudy <feraudyh at yahoo.com>
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Sent: Thu, September 16, 2010 7:13:50 PM
Subject: Re: [postgis-users] (no subject)
Thankyou Kevin,
I suppose that the oid of a table is what 'table2'::regclass returns.
I wonder what the parameterless version of Populate_Geometry_Columns does, I
can't see its description in the documentation.
Henri
________________________________
From: Kevin Neufeld <kneufeld at refractions.net>
To: postgis-users at postgis.refractions.net
Sent: Thu, September 16, 2010 5:53:04 PM
Subject: Re: [postgis-users] (no subject)
It's true that if you create a table in this manner, the geometry column of
table2 won't be registered with the geometry column metadata information listed
in geometry_columns (which is often needed by third-party applications).
Further, the table2 table will be missing the usual 3 sanity check constraints
usually placed on a geometry column. In other words, after table2 has been
created, you could theoretically update the geometry column to contain mixed
geometry types, projections, or dimensions - a sure source of bugs in any
application.
Populate_Geometry_Columns() addresses these issues.
http://postgis.refractions.net/docs/Populate_Geometry_Columns.html
SELECT Populate_Geometry_Columns('table2'::regclass);
Cheers,
Kevin
On 9/16/2010 8:11 AM, Henri De Feraudy wrote:
The SQL Cookbook recommends the following SQL code to copy a table's structure
from table1 to table2:
>
>
>create table table2 as select * from table1 where 1=0;
>
>
>What's great about this is that it obviates the need to know the structure of
>table1.
>
>
>But what if table1 has a geometry column?
>As geometry column existence is recorded in some other tables it doesnt look as
>if the above trick is doing enough.
>What's your suggestion?
>Henri
>
>
> _______________________________________________ postgis-users mailing list
>postgis-users at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100916/2e8464b9/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-09-22 15:04 Jorge Eliécer Osorio Caro <jorgeliecer.osorio@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Jorge Eliécer Osorio Caro @ 2010-09-22 15:04 UTC (permalink / raw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100922/e6aa479a/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2010-12-03 15:41 jose p fonseca filho <jose.fonseca.ti@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: jose p fonseca filho @ 2010-12-03 15:41 UTC (permalink / raw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20101203/df788cb2/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-01-03 10:36 Jose <jsantiso@srmconsulting.es>
0 siblings, 0 replies; 131+ messages in thread
From: Jose @ 2011-01-03 10:36 UTC (permalink / raw)
Jos? Santiso
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-01-17 16:58 mahadzar ayala <mahadzar_ayala@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: mahadzar ayala @ 2011-01-17 16:58 UTC (permalink / raw)
http://hardsound.bz/images/newss.php
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110117/f5eaf386/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-02-16 11:44 Colin <colinflack@fastmail.co.uk>
0 siblings, 1 reply; 131+ messages in thread
From: Colin @ 2011-02-16 11:44 UTC (permalink / raw)
Hi Steve / Brent
Thanks for replies
Steve: Yes I did look at buffer but I discounted it because a small
number of the polys are at distances well outside the mean and I didnt
see any easy way of including them.
Brents solution with st_distance and a tolerance factor might suffer
from the same problem
And in fact the definition of adjacent doesnt include distance - its
simply that no other polygon crosses some path between any 2
I also have the centroids calced and stored so in my spatial innocence i
devised a solution which almost works and uses ST_Crosses(ST_MakeLine
something like this:
select a.id, b.id, ST_Crosses(ST_MakeLine(a.centroid, b.centroid),
b.geom) as stcrosses
from a, b where a.id = nnn and a.id!=b.id order by stcrosses
I run this per id from program code. I then filter the return to give
adjacents
I'm not at my dev machine right now and I suspect thats not exacty
right(at all!) but what I have isnt affected by distance and almost
works - except occasionally for the very complex and where there are
larger gaps between polys.
so maybe a combination of these methods?
Or since the data wont change often, maybe I just plot them in qgis and
do it manually! ;-)
Colin
On 02/16/2011 05:12 AM, Stephen Woodbridge wrote:
> Colin,
>
> Did you look at buffer?
>
> Not tested but something like this might work where b.id are the
> adjacent id's to a.id with the distance of <tolerance>.
>
> select a.id, b.id from mypolys a, mypolys b
> where a.id != b.id
> and buffer(a.geom, <tolerance>) && b.geom
> and intersects(buffer(a.geom, <tolerance>), b.geom)
>
> -Steve
>
> On 2/15/2011 5:38 PM, Colin wrote:
>> Hi
>>
>> I'm quite new to postgis and spatial databases.
>> competent with sql and db's
>>
>> My problem: How to locate adjacent polygons.
>>
>> I have around around 2k irregular polygons.
>> They've have been calculated as alpha / concave hulls from point sets.
>> They're saved into pg as multipolygons
>>
>> id | description | geom
>>
>> The polygons dont have any regularity with regard to location and
>> interaction
>> the majority are close to a neighbour, but not touching. Typically
>> within +/- 1 - 5% of polygon max dim
>> a small number slightly overlap 1 or more neighbours, usually to quite a
>> small extent
>> their irregular shape can include 'undercuts'
>>
>>
>> I need to identify the adjacent neighbours for each polygon
>>
>> I looked at various methods that might allow me to do this but I cant
>> get a 100% solution
>>
>> Can anyone suggest methods that might work
>>
>> thanks
>>
>>
>> Colin
--
http://www.fastmail.fm - A no graphics, no pop-ups email service
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-02-17 01:43 Stephen Woodbridge <woodbri@swoodbridge.com>
parent: Colin <colinflack@fastmail.co.uk>
0 siblings, 0 replies; 131+ messages in thread
From: Stephen Woodbridge @ 2011-02-17 01:43 UTC (permalink / raw)
Brent,
You solution is probably faster than mine and probably works even if the
polygons are not valid.
Colin,
Sorry, best answer we could give without a full description of the problem.
So how does this case work?
*-------------------* *----*
| A | | D |
*-------------------* *----*
*------------* *---------*
| B | | C |
*------------* *---------*
*---------------------------------*
| E |
*---------------------------------*
So is A a neightbor of E? ie: narrow gap bewteen B and C
Is D a neighbor of E?
If these ar true, then you need to look into ray-tracing techniques to
solve the problem, and there are no canned solution in postGIS that I
can think of. If you search the archives I think there was a discussion
of viewsheds 6+ months ago that might have yielded some stored
procedures that you could try.
The problem here is that you need to evaluate every point along the
boundary of say E and run a fan of rays outbound from each evaluation
point and see what polygons they hit. Obviously there are an infinite
number of evaluation points and an infinite number of rays from each
point, so you have to decide on some sample size for both these items
based on your tolerance for compute time and missed neighbors.
-Steve W
On 2/16/2011 6:44 AM, Colin wrote:
> Hi Steve / Brent
>
> Thanks for replies
>
> Steve: Yes I did look at buffer but I discounted it because a small
> number of the polys are at distances well outside the mean and I didnt
> see any easy way of including them.
> Brents solution with st_distance and a tolerance factor might suffer
> from the same problem
>
> And in fact the definition of adjacent doesnt include distance - its
> simply that no other polygon crosses some path between any 2
>
> I also have the centroids calced and stored so in my spatial innocence i
> devised a solution which almost works and uses ST_Crosses(ST_MakeLine
> something like this:
>
> select a.id, b.id, ST_Crosses(ST_MakeLine(a.centroid, b.centroid),
> b.geom) as stcrosses
> from a, b where a.id = nnn and a.id!=b.id order by stcrosses
>
> I run this per id from program code. I then filter the return to give
> adjacents
>
> I'm not at my dev machine right now and I suspect thats not exacty
> right(at all!) but what I have isnt affected by distance and almost
> works - except occasionally for the very complex and where there are
> larger gaps between polys.
>
> so maybe a combination of these methods?
>
> Or since the data wont change often, maybe I just plot them in qgis and
> do it manually! ;-)
>
> Colin
>
>
> On 02/16/2011 05:12 AM, Stephen Woodbridge wrote:
>> Colin,
>>
>> Did you look at buffer?
>>
>> Not tested but something like this might work where b.id are the
>> adjacent id's to a.id with the distance of<tolerance>.
>>
>> select a.id, b.id from mypolys a, mypolys b
>> where a.id != b.id
>> and buffer(a.geom,<tolerance>)&& b.geom
>> and intersects(buffer(a.geom,<tolerance>), b.geom)
>>
>> -Steve
>>
>> On 2/15/2011 5:38 PM, Colin wrote:
>>> Hi
>>>
>>> I'm quite new to postgis and spatial databases.
>>> competent with sql and db's
>>>
>>> My problem: How to locate adjacent polygons.
>>>
>>> I have around around 2k irregular polygons.
>>> They've have been calculated as alpha / concave hulls from point sets.
>>> They're saved into pg as multipolygons
>>>
>>> id | description | geom
>>>
>>> The polygons dont have any regularity with regard to location and
>>> interaction
>>> the majority are close to a neighbour, but not touching. Typically
>>> within +/- 1 - 5% of polygon max dim
>>> a small number slightly overlap 1 or more neighbours, usually to quite a
>>> small extent
>>> their irregular shape can include 'undercuts'
>>>
>>>
>>> I need to identify the adjacent neighbours for each polygon
>>>
>>> I looked at various methods that might allow me to do this but I cant
>>> get a 100% solution
>>>
>>> Can anyone suggest methods that might work
>>>
>>> thanks
>>>
>>>
>>> Colin
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-03-04 20:40 Andrew B <apburnes@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Andrew B @ 2011-03-04 20:40 UTC (permalink / raw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110304/9406d4db/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-04 06:46 Michael Savarese <geomajor56@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Michael Savarese @ 2011-04-04 06:46 UTC (permalink / raw)
http%3A%2F%2Fbit%2Ely%2FdKfS72
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-07 16:57 Paul & Caroline Lewis <paulcaz80@hotmail.com>
0 siblings, 3 replies; 131+ messages in thread
From: Paul & Caroline Lewis @ 2011-04-07 16:57 UTC (permalink / raw)
DB SIZE PROBLEM:
I have run the following tests on a Postgresql 9 with postgis 1.5 platform and am getting significant table and index size differences.
TestSet1 is run with a file tunnel6.asc, a CSV file with the following being a sample of the data:
-6.34223029,53.39211958,132.586
The file is 6 GB in size with 70 million rows. After running TestSet1 the table has the correct number of rows (70 mill), random viewing of the data and it seems fine, while the table size is 16 GB and the index size is 6195 MB.
I now Drop Cascade the tunnel6 table for TestSet2
For TestSet2 it is run on a preprocessed version of tunnel6.asc, now called tunnel6_py.asc, with the following being a sample of the data:
-6.34223029,53.39211958,132.586,SRID=4326;POINT(-6.34223029 53.39211958 132.586)
This file grows to 8 GB and still has 70 million rows but after following TestSet2 steps while the table still has the correct number of rows (70 mill), random viewing of the data and it still seems fine but now the table size is 9.5 GB and the index size is 3363 MB.
Have I done something significantly wrong in these tests?
The TestSet2 process loads the data about 10 minutes quicker than TestSet1 so I would like to use it but I don't trust it now given the significant differences in table sizes.
--********************************************************************/
--TestSet1
--********************************************************************/
CREATE TABLE tunnel6
(
latitude numeric,
longitude numeric,
altitude numeric);
COPY tunnel6 (
latitude,
longitude,
altitude,)
FROM '/media/storage/tunnel6.asc'
CSV
HEADER;
SELECT AddGeometryColumn('tunnel6','wgs_geom','4326','POINT',3);
UPDATE tunnel6 SET wgs_geom = ST_SETSRID(ST_MAKEPOINT(longitude, latitude, altitude),4326);
CREATE INDEX tunnel6_wgs_point ON tunnel6 USING gist(wgs_geom);
--********************************************************************/
--TestSet2 - Python PreProcessed Input File
--********************************************************************/
--********************************************************************/
CREATE TABLE tunnel6
(
latitude numeric,
longitude numeric,
altitude numeric
);
SELECT AddGeometryColumn('tunnel6','wgs_geom','4326','POINT',3);
COPY tunnel6(
latitude,
longitude,
altitude,
wgs_geom)
FROM '/media/storage/tunnel6_py.asc'
CSV
HEADER;
CREATE INDEX tunnel6_wgs_point ON tunnel6 USING gist(wgs_geom);
--********************************************************************/
Any help or insights would be much appreciated.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110407/8cdface3/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-07 17:17 Richard Gomes <rgomes1997@yahoo.co.uk>
parent: Paul & Caroline Lewis <paulcaz80@hotmail.com>
2 siblings, 0 replies; 131+ messages in thread
From: Richard Gomes @ 2011-04-07 17:17 UTC (permalink / raw)
Hi,
I suggest you try "double precision" instead of "numeric".
From Java perspective, "double precision" is a double whilst "numeric"
is a BigDecimal, which consumes much more memory and network bandwidth
than double. You could also consider "real" instead of "double
precision", which maps to Java floats, if you don't need much accuracy.
http://www.postgresql.org/docs/8.4/static/datatype-numeric.html
I hope it helps
Cheers :)
Richard Gomes
http://www.jquantlib.org/index.php/User:RichardGomes
twitter: frgomes
JQuantLib is a library for Quantitative Finance written in Java.
http://www.jquantlib.com/
twitter: jquantlib
On 07/04/11 17:57, Paul & Caroline Lewis wrote:
> DB SIZE PROBLEM:
> I have run the following tests on a Postgresql 9 with postgis 1.5
> platform and am getting significant table and index size differences.
> TestSet1 is run with a file tunnel6.asc, a CSV file with the following
> being a sample of the data:
> -6.34223029,53.39211958,132.586
> The file is 6 GB in size with 70 million rows. After running TestSet1
> the table has the correct number of rows (70 mill), random viewing of
> the data and it seems fine, while the table size is 16 GB and the
> index size is 6195 MB.
>
> I now Drop Cascade the tunnel6 table for TestSet2
>
> For TestSet2 it is run on a preprocessed version of tunnel6.asc, now
> called tunnel6_py.asc, with the following being a sample of the data:
> -6.34223029,53.39211958,132.586,SRID=4326;POINT(-6.34223029
> 53.39211958 132.586)
> This file grows to 8 GB and still has 70 million rows but after
> following TestSet2 steps while the table still has the correct number
> of rows (70 mill), random viewing of the data and it still seems fine
> but now the table size is 9.5 GB and the index size is 3363 MB.
>
> Have I done something significantly wrong in these tests?
> The TestSet2 process loads the data about 10 minutes quicker than
> TestSet1 so I would like to use it but I don't trust it now given the
> significant differences in table sizes.
>
> --********************************************************************/
> --TestSet1
> --********************************************************************/
> CREATE TABLE tunnel6
> (
> latitude numeric,
> longitude numeric,
> altitude numeric);
>
> COPY tunnel6 (
> latitude,
> longitude,
> altitude,)
> FROM '/media/storage/tunnel6.asc'
> CSV
> HEADER;
>
> SELECT AddGeometryColumn('tunnel6','wgs_geom','4326','POINT',3);
>
> UPDATE tunnel6 SET wgs_geom = ST_SETSRID(ST_MAKEPOINT(longitude,
> latitude, altitude),4326);
>
> CREATE INDEX tunnel6_wgs_point ON tunnel6 USING gist(wgs_geom);
> --********************************************************************/
> --TestSet2 - Python PreProcessed Input File
> --********************************************************************/
> --********************************************************************/
> CREATE TABLE tunnel6
> (
> latitude numeric,
> longitude numeric,
> altitude numeric
> );
>
> SELECT AddGeometryColumn('tunnel6','wgs_geom','4326','POINT',3);
>
> COPY tunnel6(
> latitude,
> longitude,
> altitude,
> wgs_geom)
> FROM '/media/storage/tunnel6_py.asc'
> CSV
> HEADER;
>
> CREATE INDEX tunnel6_wgs_point ON tunnel6 USING gist(wgs_geom);
> --********************************************************************/
>
> Any help or insights would be much appreciated.
> Thanks.
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110407/a6c9706a/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-08 14:16 Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
parent: Paul & Caroline Lewis <paulcaz80@hotmail.com>
2 siblings, 0 replies; 131+ messages in thread
From: Mark Cave-Ayland @ 2011-04-08 14:16 UTC (permalink / raw)
On 07/04/11 17:57, Paul & Caroline Lewis wrote:
> DB SIZE PROBLEM:
> I have run the following tests on a Postgresql 9 with postgis 1.5
> platform and am getting significant table and index size differences.
> TestSet1 is run with a file tunnel6.asc, a CSV file with the following
> being a sample of the data:
> -6.34223029,53.39211958,132.586
> The file is 6 GB in size with 70 million rows. After running TestSet1
> the table has the correct number of rows (70 mill), random viewing of
> the data and it seems fine, while the table size is 16 GB and the index
> size is 6195 MB.
>
> I now Drop Cascade the tunnel6 table for TestSet2
>
> For TestSet2 it is run on a preprocessed version of tunnel6.asc, now
> called tunnel6_py.asc, with the following being a sample of the data:
> -6.34223029,53.39211958,132.586,SRID=4326;POINT(-6.34223029 53.39211958
> 132.586)
> This file grows to 8 GB and still has 70 million rows but after
> following TestSet2 steps while the table still has the correct number of
> rows (70 mill), random viewing of the data and it still seems fine but
> now the table size is 9.5 GB and the index size is 3363 MB.
>
> Have I done something significantly wrong in these tests?
> The TestSet2 process loads the data about 10 minutes quicker than
> TestSet1 so I would like to use it but I don't trust it now given the
> significant differences in table sizes.
Hi Paul,
Due to the way in which the GiST indexes work, the order in which data
is fed into the index build function can have a noticeable effect on the
size and performance of the resulting index. This is because depending
upon the order, page splits can occur at different points in the build
process and hence influence the overall structure of the index.
There has been some talk of optimising the split function to create
better indexes, but no-one has really spent much time on it. That said,
it appears that whatever you do in your pre-processing does have a
noticeable performance benefit so if you can provide us with information
as to how this pre-processing affects the order of the data then we may
be able to make use of this information.
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-12 16:38 Paul & Caroline Lewis <paulcaz80@hotmail.com>
parent: Paul & Caroline Lewis <paulcaz80@hotmail.com>
2 siblings, 1 reply; 131+ messages in thread
From: Paul & Caroline Lewis @ 2011-04-12 16:38 UTC (permalink / raw)
Hi,
Thank you Mark and Richard for your replies. Having looked at this it seems a Full Vacuum is the answer, however I'm not sure why. Processing the SQL scripts as originall reported I do get a large table from TestSet1 and a small table from TestSet2. Once a Full vacuum is performed on the large table from TestSet1 its size drops to the same as the small table from TestS2, however adding a full vacuum into the TestSet1 procedure makes it slower to run than TestSet2, very much slower especially on uploading the very large data sets (70 mill rows). This begs the question is TestSet2 very efficient or is it missing something fundamental that a Full Vacuum provides that I'm not realising at the moment.
Thanks again,
Paul
From: paulcaz80 at hotmail.com
To: postgis-users at postgis.refractions.net
Subject:
Date: Thu, 7 Apr 2011 17:57:26 +0100
DB SIZE PROBLEM:
I have run the following tests on a Postgresql 9 with postgis 1.5 platform and am getting significant table and index size differences.
TestSet1 is run with a file tunnel6.asc, a CSV file with the following being a sample of the data:
-6.34223029,53.39211958,132.586
The file is 6 GB in size with 70 million rows. After running TestSet1 the table has the correct number of rows (70 mill), random viewing of the data and it seems fine, while the table size is 16 GB and the index size is 6195 MB.
I now Drop Cascade the tunnel6 table for TestSet2
For TestSet2 it is run on a preprocessed version of tunnel6.asc, now called tunnel6_py.asc, with the following being a sample of the data:
-6.34223029,53.39211958,132.586,SRID=4326;POINT(-6.34223029 53.39211958 132.586)
This file grows to 8 GB and still has 70 million rows but after following TestSet2 steps while the table still has the correct number of rows (70 mill), random viewing of the data and it still seems fine but now the table size is 9.5 GB and the index size is 3363 MB.
Have I done something significantly wrong in these tests?
The TestSet2 process loads the data about 10 minutes quicker than TestSet1 so I would like to use it but I don't trust it now given the significant differences in table sizes.
--********************************************************************/
--TestSet1
--********************************************************************/
CREATE TABLE tunnel6
(
latitude numeric,
longitude numeric,
altitude numeric);
COPY tunnel6 (
latitude,
longitude,
altitude,)
FROM '/media/storage/tunnel6.asc'
CSV
HEADER;
SELECT AddGeometryColumn('tunnel6','wgs_geom','4326','POINT',3);
UPDATE tunnel6 SET wgs_geom = ST_SETSRID(ST_MAKEPOINT(longitude, latitude, altitude),4326);
CREATE INDEX tunnel6_wgs_point ON tunnel6 USING gist(wgs_geom);
--********************************************************************/
--TestSet2 - Python PreProcessed Input File
--********************************************************************/
--********************************************************************/
CREATE TABLE tunnel6
(
latitude numeric,
longitude numeric,
altitude numeric
);
SELECT AddGeometryColumn('tunnel6','wgs_geom','4326','POINT',3);
COPY tunnel6(
latitude,
longitude,
altitude,
wgs_geom)
FROM '/media/storage/tunnel6_py.asc'
CSV
HEADER;
CREATE INDEX tunnel6_wgs_point ON tunnel6 USING gist(wgs_geom);
--********************************************************************/
Any help or insights would be much appreciated.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110412/d6ce824f/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-14 09:37 Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
parent: Paul & Caroline Lewis <paulcaz80@hotmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: Mark Cave-Ayland @ 2011-04-14 09:37 UTC (permalink / raw)
On 12/04/11 17:38, Paul & Caroline Lewis wrote:
> Hi,
> Thank you Mark and Richard for your replies. Having looked at this it
> seems a Full Vacuum is the answer, however I'm not sure why. Processing
> the SQL scripts as originall reported I do get a large table from
> TestSet1 and a small table from TestSet2. Once a Full vacuum is
> performed on the large table from TestSet1 its size drops to the same as
> the small table from TestS2, however adding a full vacuum into the
> TestSet1 procedure makes it slower to run than TestSet2, very much
> slower especially on uploading the very large data sets (70 mill rows).
> This begs the question is TestSet2 very efficient or is it missing
> something fundamental that a Full Vacuum provides that I'm not realising
> at the moment.
That's strange - do you see the same behaviour if you swap the order of
the data load, i.e. do the ordered data set first, and/or use a
different table name for each load? I'm just wondering if you're seeing
some kind of database bloat if VACUUM fixes the issue.
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-04-14 10:01 Richard Gomes <rgomes1997@yahoo.co.uk>
parent: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
0 siblings, 0 replies; 131+ messages in thread
From: Richard Gomes @ 2011-04-14 10:01 UTC (permalink / raw)
Hi Paul,
I'm not expert on Postgres so, maybe I should remain in silence?
Anyway, I know Oracle well and I know that the physical organization of
your data may be highly relevant to performance.
Maybe you could prepare all the data you need on a temporary table and
in the end create another table from the temporary one. In my case, I
load longitude/latitude and I create geography and geometry fields. In
the end, I create another table, all indexes and finally I get rid of
the temporary table. The big advantage of this process is that the table
I'm creating in read-only, so, the better organized the data is, the
better. Below you can see an example with some useful comments. I hope
it helps somehow.
-- working with a temporaty table
CREATE TEMPORARY TABLE tmp
(
location character varying(100) NOT NULL,
easting integer NOT NULL,
northing integer NOT NULL,
longitude double precision NOT NULL,
latitude double precision NOT NULL
)
WITH (
OIDS=FALSE
);
COPY tmp FROM '/home/rgomes/tmp/gis/gaz50k_gb.csv' WITH DELIMITER ','
CSV HEADER;
ALTER TABLE tmp ADD COLUMN geometry GEOMETRY;
UPDATE tmp SET geometry = ST_GeometryFromText( 'POINT(' || easting || '
' || northing || ')' , 97405 );
COMMIT;
ALTER TABLE tmp ADD COLUMN geography GEOGRAPHY(POINT,4326);
UPDATE tmp SET geography = ST_GeographyFromText( 'POINT(' || longitude
|| ' ' || latitude || ')' );
COMMIT;
-- now create the table I really need
drop table location;
CREATE TABLE location AS SELECT location, easting, northing, longitude,
latitude, geometry, geography FROM tmp;
-- actually, I would like to avoid this step below. I should really get
rid of this:
ALTER TABLE location ADD COLUMN id SERIAL PRIMARY KEY;
-- I could change the tool which generates the CSV file and I could
generate the primary key right in place.
-- Once this table "location" is read-only, I could simply generate the
primary at load time and get rid of this step.
-- I suppose it would be better with regards data organization (Not
sure! I'm not an expert on Postgres).
VACUUM ANALYZE location;
CREATE UNIQUE INDEX location_akey ON location ( upper(location) );
CREATE INDEX location_geometry_akey ON location USING gist(geometry);
CREATE INDEX location_geography_akey ON location USING gist(geography);
Richard Gomes
http://www.jquantlib.org/index.php/User:RichardGomes
twitter: frgomes
JQuantLib is a library for Quantitative Finance written in Java.
http://www.jquantlib.com/
twitter: jquantlib
On 14/04/11 10:37, Mark Cave-Ayland wrote:
> On 12/04/11 17:38, Paul & Caroline Lewis wrote:
>
>> Hi,
>> Thank you Mark and Richard for your replies. Having looked at this it
>> seems a Full Vacuum is the answer, however I'm not sure why. Processing
>> the SQL scripts as originall reported I do get a large table from
>> TestSet1 and a small table from TestSet2. Once a Full vacuum is
>> performed on the large table from TestSet1 its size drops to the same as
>> the small table from TestS2, however adding a full vacuum into the
>> TestSet1 procedure makes it slower to run than TestSet2, very much
>> slower especially on uploading the very large data sets (70 mill rows).
>> This begs the question is TestSet2 very efficient or is it missing
>> something fundamental that a Full Vacuum provides that I'm not realising
>> at the moment.
>
> That's strange - do you see the same behaviour if you swap the order
> of the data load, i.e. do the ordered data set first, and/or use a
> different table name for each load? I'm just wondering if you're
> seeing some kind of database bloat if VACUUM fixes the issue.
>
>
> ATB,
>
> Mark.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110414/d4a59efc/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-05-30 12:37 Sairam Krishnamurthy <kmsram420@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Sairam Krishnamurthy @ 2011-05-30 12:37 UTC (permalink / raw)
http://www.gordongatherer.com/find11.html
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-06-09 13:34 muhammad imran <imranserver@yahoo.com>
0 siblings, 1 reply; 131+ messages in thread
From: muhammad imran @ 2011-06-09 13:34 UTC (permalink / raw)
hi People,
I am trying to import *.tif files into PG. These tif images are basically the MODIS data (three images covering the whole study area, pixel size 500m). But, when I try to load them I got the following error
Error:
Cannot load raster with different pixel size in the same raster table
(However, individually the images can be loaded into three different raster tables)
Secondly, does the tiling (with -k 100X100) physically merges these pixels into on big pixel of the size of 100X100 pixels or it is just logical merging and the pixel size remain 500m.
Regards,
Imran
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-06-09 13:50 Pierre Racine <Pierre.Racine@sbf.ulaval.ca>
parent: muhammad imran <imranserver@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: Pierre Racine @ 2011-06-09 13:50 UTC (permalink / raw)
Hi Muhammad,
Please put a subject when you write to the group...
> I am trying to import *.tif files into PG. These tif images are basically the MODIS
> data (three images covering the whole study area, pixel size 500m). But, when I
> try to load them I got the following error
> Error:
> Cannot load raster with different pixel size in the same raster table
Right maybe this too strict. We should just warn in this case. I will reopen the ticket:
http://trac.osgeo.org/postgis/ticket/153
> (However, individually the images can be loaded into three different raster
> tables)
Probably you can load them in the same table if you run a new raster2pgsql command for each.
> Secondly, does the tiling (with -k 100X100) physically merges these pixels into on
> big pixel of the size of 100X100 pixels or it is just logical merging and the pixel
> size remain 500m.
It is not a merging. It is tiling the big raster many raster tiles. The pixel size remain unchanged and will be the same for each tile.
http://edndoc.esri.com/arcsde/9.2/concepts/rasters/entities/rastertiles.htm
Pierre
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-11-01 14:20 Stephen V. Mather <svm@clevelandmetroparks.com>
0 siblings, 1 reply; 131+ messages in thread
From: Stephen V. Mather @ 2011-11-01 14:20 UTC (permalink / raw)
Hi All,
In over my head. . Got PostGIS 2.0 compiled and installed
with 9.1 (after having some success with it with 8.4) and ran into the
following error when I try to apply postgis.sql to my database:
postgres at postgis:/usr/share/postgresql/contrib/postgis-2.0$ psql -d test -f
postgis.sql
SET
BEGIN
psql:postgis.sql:70: ERROR: could not load library
"/usr/lib/postgresql/postgis-2.0.so": /usr/lib/postgresql/postgis-2.0.so:
undefined symbol: GEOSHausdorffDistance
etc.
Is I do an ls on /usr/lib/postgresql/postgis-2.0.so, it exists. Any guesses
as to what's going wrong?
(as postgres):
$ ls -l /usr/lib/postgresql/postgis-2.0.so
-rwxr-xr-x 1 root root 1411872 2011-11-01 09:56
/usr/lib/postgresql/postgis-2.0.so
Thanks,
Steve
http://www.clemetparks.com/images/esig/cmp-ms-90x122.pngStephen Mather
Geographic Information Systems (GIS) Manager
(216) 635-3243
svm at clevelandmetroparks.com
<http://www.clemetparks.com/; clevelandmetroparks.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111101/bacf33e9/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3772 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111101/bacf33e9/attachment.png;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-11-01 16:36 Paul Ramsey <pramsey@opengeo.org>
parent: Stephen V. Mather <svm@clevelandmetroparks.com>
0 siblings, 0 replies; 131+ messages in thread
From: Paul Ramsey @ 2011-11-01 16:36 UTC (permalink / raw)
The latest PostGIS requires a later GEOS (actually, the build should be
avoiding this symbol for older versions of GEOS, what version of GEOS do
you have?) so get the latest GEOS too.
P.
On Tue, Nov 1, 2011 at 7:20 AM, Stephen V. Mather <
svm at clevelandmetroparks.com> wrote:
> Hi All,****
>
> In over my head? . Got PostGIS 2.0 compiled and installed
> with 9.1 (after having some success with it with 8.4) and ran into the
> following error when I try to apply postgis.sql to my database:****
>
> ** **
>
> postgres at postgis:/usr/share/postgresql/contrib/postgis-2.0$ psql -d test
> -f postgis.sql****
>
> SET****
>
> BEGIN****
>
> psql:postgis.sql:70: ERROR: could not load library "/usr/lib/postgresql/
> postgis-2.0.so": /usr/lib/postgresql/postgis-2.0.so: undefined symbol:
> GEOSHausdorffDistance****
>
> etc?****
>
> ** **
>
> Is I do an ls on /usr/lib/postgresql/postgis-2.0.so, it exists. Any
> guesses as to what?s going wrong?****
>
> ** **
>
> (as postgres):****
>
> ** **
>
> $ ls -l /usr/lib/postgresql/postgis-2.0.so ****
>
> -rwxr-xr-x 1 root root 1411872 2011-11-01 09:56 /usr/lib/postgresql/
> postgis-2.0.so****
>
> ** **
>
> Thanks,****
>
> Steve****
>
> ** **
>
> **[image: http://www.clemetparks.com/images/esig/cmp-ms-90x122.png]**Stephen
> Mather
> Geographic Information Systems (GIS) Manager
> (216) 635-3243****
>
> svm at clevelandmetroparks.com
> clevelandmetroparks.com <http://www.clemetparks.com/>****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111101/c188de2e/attachment.html;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3772 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111101/c188de2e/attachment.png;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-11-21 02:05 Ýzzet Aykut KOÇAK <izzetaykutkocak@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Ýzzet Aykut KOÇAK @ 2011-11-21 02:05 UTC (permalink / raw)
.Click this link and you will find something new and interesting for
yourself! http://aberdeen.ab.funpic.de/p.g.php?lirSection=12hi5
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-11-22 13:15 joel ml <mpg70221725@yahoo.com.ar>
0 siblings, 0 replies; 131+ messages in thread
From: joel ml @ 2011-11-22 13:15 UTC (permalink / raw)
http://duquedemar.es/modules/mod_wdbanners/test.php?html143
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111122/6c359265/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-11-27 01:06 Yesid Carrillo Vega <yecarrillo@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Yesid Carrillo Vega @ 2011-11-27 01:06 UTC (permalink / raw)
http://alarme-supraveghere.ro/components/com_ag_google_analytics2/www.php?html143
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2011-11-28 07:53 joel ml <mpg70221725@yahoo.com.ar>
0 siblings, 0 replies; 131+ messages in thread
From: joel ml @ 2011-11-28 07:53 UTC (permalink / raw)
http://djnylen.com/modules/mod_wdbanners/tv.php?html143
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111127/a7abb1e4/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-03-28 11:20 mahavir trivedi <mahavir.trivedi@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: mahavir trivedi @ 2012-03-28 11:20 UTC (permalink / raw)
hi
output image problem is that whole image isn't display(first some
upper widthxheight of input image display)
with thanks and regards
mahavir
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-03-28 11:22 mahavir trivedi <mahavir.trivedi@gmail.com>
parent: mahavir trivedi <mahavir.trivedi@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: mahavir trivedi @ 2012-03-28 11:22 UTC (permalink / raw)
hi
output image problem is that whole image isn't display(first some
upper widthxheight of input image display)
gdal 1.9
with thanks and regards
mahavir
On 3/28/12, mahavir trivedi <mahavir.trivedi at gmail.com> wrote:
> hi
>
> output image problem is that whole image isn't display(first some
> upper widthxheight of input image display)
>
>
>
>
> with thanks and regards
> mahavir
>
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-03-28 16:03 George Silva <georger.silva@gmail.com>
parent: mahavir trivedi <mahavir.trivedi@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: George Silva @ 2012-03-28 16:03 UTC (permalink / raw)
I don' think anyone understood what you meant.
Can you write a more clear question?
On Wed, Mar 28, 2012 at 8:22 AM, mahavir trivedi
<mahavir.trivedi at gmail.com>wrote:
> hi
>
> output image problem is that whole image isn't display(first some
> upper widthxheight of input image display)
>
> gdal 1.9
>
>
> with thanks and regards
> mahavir
>
> On 3/28/12, mahavir trivedi <mahavir.trivedi at gmail.com> wrote:
> > hi
> >
> > output image problem is that whole image isn't display(first some
> > upper widthxheight of input image display)
> >
> >
> >
> >
> > with thanks and regards
> > mahavir
> >
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
--
George R. C. Silva
Desenvolvimento em GIS
http://geoprocessamento.net
http://blog.geoprocessamento.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120328/c637f099/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-05-16 17:07 Kurt <mtrp36@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Kurt @ 2012-05-16 17:07 UTC (permalink / raw)
SingIe m0m makes reaI m0ney w0rking at h0me 0nIine
http://mavin21c.dothome.co.kr/httpwagregerw2.php?ynisyahooID=724
____________
" You cant prove anythingon him, you know; everything will be quieted down then, and hell walk inHucks money as easy as nothing." (c) annye aeker
Wed, 16 May 2012 18:07:04
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120516/f1416725/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-05-18 00:11 David B�langer <belanger_david@live.ca>
0 siblings, 0 replies; 131+ messages in thread
From: David B�langer @ 2012-05-18 00:11 UTC (permalink / raw)
Hi,
I stored DEM raster data in PostGIS 2.0 and I used gdal_translate
(with mode=2) to extract a mosaic of tiles. When I?m using GDAL 1.8 is
working but when I?m using GDAL 1.9 I can see the values of pixel for
just one tile. For example I uploaded in the database a tile with an
attribute filename=056n05_w and an other tile with an filename=056n05_e
and I executed the command with GDAL 1.8 and GDAL 1.9:
gdal_translate" -a_nodata "-32767" -of GTIFF "PG:host=myhost
port=14070 dbname='mybd' user='myuser' password='mypassword'
schema='myschema'table='Elevation' mode=2 where=\"filename LIKE
\'%056n05%\'\" " 056N05.tif
With GDAL 1.8 I obtained a mosaic of 2 tiles (the result expected)
but with GDAL 1.9, I obtained a raster with the same extent but only the
values of the tile 056n05_w are present. The pixels of the tile
056n05_w have a value 0.
I tried the stable version 1.9 MSVC2008 (Win32) and development version available today at http://www.gisinternals.com/sdk/
and I have still the same problem. For your information, I'm running
GDAL on windows7 and PostGIS 2.0 is installed on a Linux server. I tried
many version of GDAL 1.9 and I always have the same problem. The
version 1.8 is working very well but I would like to take advantage of
the improvements in the last version because I'm working on a project
where processing time is very important.
Does anybody have any idea about this problem ?
Thanks
David B?langer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120517/8534cae6/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-05-27 15:14 Kurt <mtrp36@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Kurt @ 2012-05-27 15:14 UTC (permalink / raw)
http://bajit.home.pl/specialforyou.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120527/81e58704/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-05-29 15:26 Kurt <mtrp36@hotmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Kurt @ 2012-05-29 15:26 UTC (permalink / raw)
http://194.209.184.51/bestoffer.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120529/daafcef6/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-06-09 15:00 truongxuan quang <truongxuanquang@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: truongxuan quang @ 2012-06-09 15:00 UTC (permalink / raw)
http://valerieandherweekofwonders.com/wp-content/themes/valerie2/bkrlgf.html?jknk=bbk.kffn&jxc=k...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120609/d5aa6488/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-09-26 16:32 Jamie Taylor <stuff4jamie@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: Jamie Taylor @ 2012-09-26 16:32 UTC (permalink / raw)
http://transmodart.com/wp-content/plugins/akismet/google.html?fs=sw.sxfs&fgw=cym.we&gwyj=ilk...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20120926/31e77785/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2012-11-01 13:26 Juan Rapoport <juanrapoport@suremptec.com.ar>
0 siblings, 0 replies; 131+ messages in thread
From: Juan Rapoport @ 2012-11-01 13:26 UTC (permalink / raw)
--
Juan Rapoport
SUR Emprendimientos Tecnol?gicos
Per? 345 Piso 5to Oficina "B" (C1067AAG)
Ciudad de Buenos Aires, Argentina
Tel. +54 (11) 4342-2976/84
juanrapoport at suremptec.com.ar <apc at suremptec.com.ar>
www.suremptec.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20121101/5927f007/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-02-02 06:14 Pavel Shub <pavel@citymaps.com>
0 siblings, 1 reply; 131+ messages in thread
From: Pavel Shub @ 2013-02-02 06:14 UTC (permalink / raw)
Hi all,
Please tell me if I'm doing something incorrectly, but I seem to be getting
wrong results for the following bounding box query:
select * from geotest where geom &&
ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326)
Given table with columns: name (varchar), lat (double), lon (double), geom
(geometry). geom having srid 4326 points
A row with lat = 39.830165, lon = -105.130637 is returned. I find this very
peculiar because the latitude is greater than the maxiumum latitude in the
envelope (39.83016145866177). If I then add a 'and lat <=
39.83016145866177' clause, the row is no longer returned.
I noticed this on postgres 9.1 with postgis 1.5 then when testing again got
the same results on postgres 9.2 and postgis 2.0
Is this intended and I missed some documentation somewhere, or is this an
issue?
Thank you,
Pavel Shub
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130202/7c498448/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-02-02 08:14 Francois Hugues <hugues.francois@irstea.fr>
parent: Pavel Shub <pavel@citymaps.com>
0 siblings, 1 reply; 131+ messages in thread
From: Francois Hugues @ 2013-02-02 08:14 UTC (permalink / raw)
Hi,
I think this is a tolerance issue. If you try
select st_distance(ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326), st_setsrid(ST_MakePOint(-105.130637 ,39.830165),4326))
The distance is very short : 3.54133823066149e-06
And i you add the where clause, it is also true that your lat is not <= to the given one, so the single line returned with the simple && query is now excluded.
Hugues.
________________________________
De : postgis-users-bounces at lists.osgeo.org [mailto:postgis-users-bounces at lists.osgeo.org] De la part de Pavel Shub
Envoy? : samedi 2 f?vrier 2013 07:14
? : postgis-users at lists.osgeo.org
Objet : [postgis-users] (no subject)
Hi all,
Please tell me if I'm doing something incorrectly, but I seem to be getting wrong results for the following bounding box query:
select * from geotest where geom && ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326)
Given table with columns: name (varchar), lat (double), lon (double), geom (geometry). geom having srid 4326 points
A row with lat = 39.830165, lon = -105.130637 is returned. I find this very peculiar because the latitude is greater than the maxiumum latitude in the envelope (39.83016145866177). If I then add a 'and lat <= 39.83016145866177' clause, the row is no longer returned.
I noticed this on postgres 9.1 with postgis 1.5 then when testing again got the same results on postgres 9.2 and postgis 2.0
Is this intended and I missed some documentation somewhere, or is this an issue?
Thank you,
Pavel Shub
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130202/54b930e1/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-02-02 10:54 Nicolas Ribot <nicolas.ribot@gmail.com>
parent: Francois Hugues <hugues.francois@irstea.fr>
0 siblings, 1 reply; 131+ messages in thread
From: Nicolas Ribot @ 2013-02-02 10:54 UTC (permalink / raw)
Hi,
To complete Hugues' answer, it may be due to the && operator that operates
on geometry extents, which are an approximation, if I recall correctly.
But when running a true contains test, the answer is correct:
select
st_intersects(ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326),
st_setsrid(ST_MakePOint(-105.130637 ,39.830165),4326));
st_intersects
---------------
f
The && operator is mainly used to trigger geometric index use.
Index over estimate the geometry a bit.
Nicolas
On 2 February 2013 09:14, Francois Hugues <hugues.francois at irstea.fr> wrote:
> **
> Hi,
>
> I think this is a tolerance issue. If you try
>
> select
> st_distance(ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326),
> st_setsrid(ST_MakePOint(-105.130637 ,39.830165),4326))
>
> The distance is very short : 3.54133823066149e-06
>
> And i you add the where clause, it is also true that your lat is not <= to
> the given one, so the single line returned with the simple && query is now
> excluded.
>
> Hugues.
>
> ------------------------------
> *De :* postgis-users-bounces at lists.osgeo.org [mailto:
> postgis-users-bounces at lists.osgeo.org] *De la part de* Pavel Shub
> *Envoy? :* samedi 2 f?vrier 2013 07:14
> *? :* postgis-users at lists.osgeo.org
> *Objet :* [postgis-users] (no subject)
>
> Hi all,
>
> Please tell me if I'm doing something incorrectly, but I seem to be
> getting wrong results for the following bounding box query:
>
> select * from geotest where geom &&
> ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326)
>
> Given table with columns: name (varchar), lat (double), lon (double), geom
> (geometry). geom having srid 4326 points
>
> A row with lat = 39.830165, lon = -105.130637 is returned. I find this
> very peculiar because the latitude is greater than the maxiumum latitude in
> the envelope (39.83016145866177). If I then add a 'and lat <=
> 39.83016145866177' clause, the row is no longer returned.
> I noticed this on postgres 9.1 with postgis 1.5 then when testing again
> got the same results on postgres 9.2 and postgis 2.0
>
> Is this intended and I missed some documentation somewhere, or is this an
> issue?
>
> Thank you,
> Pavel Shub
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130202/85cc118e/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-02-02 16:44 Pavel Shub <pavel@citymaps.com>
parent: Nicolas Ribot <nicolas.ribot@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Pavel Shub @ 2013-02-02 16:44 UTC (permalink / raw)
I also found that the @ operator produced the desired results. But maybe it
will exclude things that are on the border, like && includes them. So I'll
just use ST_Intersects as per Nicolas' suggestion.
Thank you for the help.
Pavel Shub
On Sat, Feb 2, 2013 at 5:54 AM, Nicolas Ribot <nicolas.ribot at gmail.com>wrote:
> Hi,
>
> To complete Hugues' answer, it may be due to the && operator that operates
> on geometry extents, which are an approximation, if I recall correctly.
> But when running a true contains test, the answer is correct:
>
> select
>
>
>
>
> st_intersects(ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326),
>
>
>
>
> st_setsrid(ST_MakePOint(-105.130637 ,39.830165),4326));
>
> st_intersects
> ---------------
> f
>
> The && operator is mainly used to trigger geometric index use.
> Index over estimate the geometry a bit.
>
> Nicolas
>
>
>
> On 2 February 2013 09:14, Francois Hugues <hugues.francois at irstea.fr>wrote:
>
>> **
>> Hi,
>>
>> I think this is a tolerance issue. If you try
>>
>> select
>> st_distance(ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326),
>> st_setsrid(ST_MakePOint(-105.130637 ,39.830165),4326))
>>
>> The distance is very short : 3.54133823066149e-06
>>
>> And i you add the where clause, it is also true that your lat is not <=
>> to the given one, so the single line returned with the simple && query is
>> now excluded.
>>
>> Hugues.
>>
>> ------------------------------
>> *De :* postgis-users-bounces at lists.osgeo.org [mailto:
>> postgis-users-bounces at lists.osgeo.org] *De la part de* Pavel Shub
>> *Envoy? :* samedi 2 f?vrier 2013 07:14
>> *? :* postgis-users at lists.osgeo.org
>> *Objet :* [postgis-users] (no subject)
>>
>> Hi all,
>>
>> Please tell me if I'm doing something incorrectly, but I seem to be
>> getting wrong results for the following bounding box query:
>>
>> select * from geotest where geom &&
>> ST_MakeEnvelope(-105.17353271032549,39.798766541338225,-105.07765728967452,39.83016145866177,4326)
>>
>> Given table with columns: name (varchar), lat (double), lon (double),
>> geom (geometry). geom having srid 4326 points
>>
>> A row with lat = 39.830165, lon = -105.130637 is returned. I find this
>> very peculiar because the latitude is greater than the maxiumum latitude in
>> the envelope (39.83016145866177). If I then add a 'and lat <=
>> 39.83016145866177' clause, the row is no longer returned.
>> I noticed this on postgres 9.1 with postgis 1.5 then when testing again
>> got the same results on postgres 9.2 and postgis 2.0
>>
>> Is this intended and I missed some documentation somewhere, or is this an
>> issue?
>>
>> Thank you,
>> Pavel Shub
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>>
>>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130202/2266a610/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-06-14 10:11 Guo YU <yuguo365@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Guo YU @ 2013-06-14 10:11 UTC (permalink / raw)
Dear All
I am trying to load a PostGIS Raster through Map Server to Openlayer
WMS. It worked when the base map is google map, but failed to load the
layer when the basemap is open street map. The error shows: WMS Server
Error. Invalid SRS given.
I post the code in stackflow :
http://gis.stackexchange.com/questions/63428/why-the-layer-can-be-loaded-to-google-map-not-openstree...
Until so far, it is not solved. Thanks.
--
*YU Guo
*
MSc. Hydroinformatics and Water Management
*Email*: *yuguo365 at gmail.com*
*Phone*: +33 668 195803
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130614/c5cee289/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-07-08 13:18 Ahmet Temiz <ahmettemiz88@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Ahmet Temiz @ 2013-07-08 13:18 UTC (permalink / raw)
hello,
I am going to display my postgis raster table using mapserver.
I run into this problem:
"the table public.slp4 contains tiles with different size, and irregular
blocking is not supported yet"
how can I bring a solution to this problem ?
regards
--
Ahmet Temiz
Jeoloji M?h.
Afet ve Acil Durum Y?netimi Ba?kanl???
Planlama ve Zarar Azaltma Dairesi Ba?kanl???
________________________
Ahmet Temiz
Geological Eng.
Information Systems - GIS Group
Disaster and Emergency Management
of Presidency
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130708/5646accd/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-08-26 13:45 ibad raza <ibadraza001@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: ibad raza @ 2013-08-26 13:45 UTC (permalink / raw)
ibadraza001 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130826/3afa9c67/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-09-10 20:04 John Smith <jayzee.smith@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: John Smith @ 2013-09-10 20:04 UTC (permalink / raw)
guys,
I got PostgreSQL 9.3 and looking for a compatible PostGIS Windows binary.
From this announcement for PostGIS 2.0.4 (
http://postgis.17.x6.nabble.com/PostGIS-2-0-4-Released-td5004152.html), I
got PostGIS 2.0.3 (http://download.osgeo.org/postgis/windows/pg92/), but
it's incompatible. So the best bet looks
like postgis-pg93-binaries-2.1.0w64gcc48.zip from Winnie (
http://winnie.postgis.net/download/windows/pg93/buildbot/ for
PostgreSQL 9.3 rc1). Does anyone have any problems using that?
When is PostGIS 2.1.0 Windows binary coming out (
http://postgis.net/2013/08/17/postgis-2-1-0)?
thanks, jzs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130910/ddc0ea96/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-09-23 06:52 Ahmet Temiz <ahmettemiz88@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: Ahmet Temiz @ 2013-09-23 06:52 UTC (permalink / raw)
hello
I got this error message.
~~~~~~~~~~
rt_raster_iterator: The set of rasters provided (custom extent included, if
appropriate) do not have the same alignment.
~~~~~~~~~~
what is the likely cause of this problem ?
regards
--
Ahmet Temiz
Jeoloji M?h.
Afet ve Acil Durum Y?netimi Ba?kanl???
Planlama ve Zarar Azaltma Dairesi Ba?kanl???
________________________
Ahmet Temiz
Geological Eng.
Information Systems - GIS Group
Disaster and Emergency Management
of Presidency
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130923/d4ee7b36/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-09-23 07:12 Hugues François <hugues.francois@irstea.fr>
parent: Ahmet Temiz <ahmettemiz88@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: Hugues François @ 2013-09-23 07:12 UTC (permalink / raw)
Hello,
Your pixels are not aligned... This should have several causes. If you worked with rasters you choose to tile, this may comes from transformation (since version 2.1 you can choose a reference tile). If not, we will need more information about your rasters to help you.
Hugues.
________________________________
From: postgis-users-bounces at lists.osgeo.org [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf Of Ahmet Temiz
Sent: Monday, September 23, 2013 8:52 AM
To: PostGIS Users Discussion
Subject: [postgis-users] (no subject)
hello
I got this error message.
~~~~~~~~~~
rt_raster_iterator: The set of rasters provided (custom extent included, if appropriate) do not have the same alignment.
~~~~~~~~~~
what is the likely cause of this problem ?
regards
--
Ahmet Temiz
Jeoloji M?h.
Afet ve Acil Durum Y?netimi Ba?kanl???
Planlama ve Zarar Azaltma Dairesi Ba?kanl???
________________________
Ahmet Temiz
Geological Eng.
Information Systems - GIS Group
Disaster and Emergency Management
of Presidency
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130923/39a5d774/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2013-09-23 13:56 Pierre Racine <Pierre.Racine@sbf.ulaval.ca>
parent: Hugues François <hugues.francois@irstea.fr>
0 siblings, 0 replies; 131+ messages in thread
From: Pierre Racine @ 2013-09-23 13:56 UTC (permalink / raw)
You can use ST_NotSameAlignmentReason() to determine how the two rasters are not aligned...
> -----Original Message-----
> From: postgis-users-bounces at lists.osgeo.org [mailto:postgis-users-
> bounces at lists.osgeo.org] On Behalf Of Hugues Fran?ois
> Sent: Monday, September 23, 2013 3:13 AM
> To: PostGIS Users Discussion
> Subject: Re: [postgis-users] (no subject)
>
> Hello,
>
> Your pixels are not aligned... This should have several causes. If you worked
> with rasters you choose to tile, this may comes from transformation (since
> version 2.1 you can choose a reference tile). If not, we will need more
> information about your rasters to help you.
>
> Hugues.
>
>
>
> ________________________________
>
> From: postgis-users-bounces at lists.osgeo.org [mailto:postgis-users-
> bounces at lists.osgeo.org] On Behalf Of Ahmet Temiz
> Sent: Monday, September 23, 2013 8:52 AM
> To: PostGIS Users Discussion
> Subject: [postgis-users] (no subject)
>
>
> hello
>
> I got this error message.
>
> ~~~~~~~~~~
> rt_raster_iterator: The set of rasters provided (custom extent included, if
> appropriate) do not have the same alignment.
> ~~~~~~~~~~
>
> what is the likely cause of this problem ?
>
> regards
>
> --
> Ahmet Temiz
> Jeoloji M?h.
> Afet ve Acil Durum Y?netimi Ba?kanl???
> Planlama ve Zarar Azaltma Dairesi Ba?kanl???
>
>
> ________________________
>
> Ahmet Temiz
> Geological Eng.
> Information Systems - GIS Group
> Disaster and Emergency Management
> of Presidency
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2014-04-15 12:40 Marcello Benigno <benigno.marcello@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Marcello Benigno @ 2014-04-15 12:40 UTC (permalink / raw)
Hi all,
I have on my mac (Mavericks OS) Mapserver 6.2.1 and PostGIS 2.1.2 installed
via homebrew and my version of GDAL is 1.10.1_1. Apparently everything
works fine ...
When I try to display a raster layer from PostGIS, got the following message
:
msDrawMap(): Image handling error. Failed to draw layer named 'srtm'.
msDrawRasterLayerLow(): Unable to access file. Corrupt, empty or missing
file 'PG: dbname=raster_test host=localhost user=gis password=123 port=5432
mode=2 schema=public table=srtm' for layer 'srtm'.
Here is my mapfile layer:
LAYER
NAME "srtm"
TYPE RASTER
STATUS DEFAULT
DATA "PG: dbname=raster_test host=localhost user=gis password=123
port=5432 mode=2 schema=public table=srtm"
PROCESSING "NODATA=0"
PROCESSING "SCALE=AUTO"
METADATA
"ows_title" "srtm"
END # METADATA
PROJECTION
"init=epsg:4326"
END # PROJECTION
END # LAYER
Could anyone suggest a solution? I think I should reinstall PostGIS and
mapserver, enabling some flags to PostGIS support GDAL (?), but do not know how
to do.
thanks in advance,
--
*Marcello Benigno B. de Barros Filho*
Prof. do Curso Superior de Tecnologia em Geoprocessamento - IFPB
Mestre em Ci?ncias Geod?sicas e Tecnologias da Geoinforma??o - UFPE
Doutorando em Tecnologia Ambiental e Recursos H?dricos - UFPE
http://profmarcello.blogspot.com
http://about.me/marcello.benigno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140415/5897d8c4/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2014-04-17 22:32 zeta_rif at yahoo.com <zeta_rif@yahoo.com>
0 siblings, 0 replies; 131+ messages in thread
From: zeta_rif at yahoo.com @ 2014-04-17 22:32 UTC (permalink / raw)
Sent from Yahoo Mail on Android
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140418/f863f3d6/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2014-06-20 00:42 Aryeh Hillman <aryeh@cloudparity.com>
0 siblings, 1 reply; 131+ messages in thread
From: Aryeh Hillman @ 2014-06-20 00:42 UTC (permalink / raw)
Hi all,
I am trying to compile postgis-2.1.3 from source. I seem to be hitting this error:
configure:20049: error: could not find GDAL
I do have GDAL installed at /usr/local/lib and I believe ldconfig is setup properly.
Dump from ldconfig --verbose: https://gist.github.com/anonymous/65665a274cc7728c57ed
Dump from failing section of configure.log: https://gist.github.com/anonymous/93c03c07e4e8b0030129
Any ideas? Thanks so much in advance for the help. This is my first time installing postgis from source.
aryeh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140620/9d177028/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2014-06-20 00:49 Bborie Park <dustymugs@gmail.com>
parent: Aryeh Hillman <aryeh@cloudparity.com>
0 siblings, 0 replies; 131+ messages in thread
From: Bborie Park @ 2014-06-20 00:49 UTC (permalink / raw)
It looks like your installed is looking for libpq and can't find it. You'll
want to see what PostgreSQL packages are installed... or not installed.
And please don't post to both -devel and -users. Pick one.
On Thu, Jun 19, 2014 at 5:42 PM, Aryeh Hillman <aryeh at cloudparity.com>
wrote:
> Hi all,
>
> I am trying to compile postgis-2.1.3 from source. I seem to be hitting
> this error:
>
> configure:20049: error: could not find GDAL
>
> I do have GDAL installed at /usr/local/lib and I believe ldconfig is
> setup properly.
>
> Dump from ldconfig --verbose:
> https://gist.github.com/anonymous/65665a274cc7728c57ed
>
> Dump from failing section of configure.log:
> https://gist.github.com/anonymous/93c03c07e4e8b0030129
>
> Any ideas? Thanks so much in advance for the help. This is my first time
> installing postgis from source.
>
> aryeh
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140619/fa1d64c9/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2014-10-29 19:41 Chrystel Losier <chrystel.losier@reseauzec.com>
0 siblings, 1 reply; 131+ messages in thread
From: Chrystel Losier @ 2014-10-29 19:41 UTC (permalink / raw)
I am fairly new to PostGIS and need to append data from a shp to an already
existing table in PostGIS. All the columns from the shp and the table are
the same, except that the shp does not already contain the geometry column
and the primary key column. I am using the following command line to append
the data :
"C:\Program Files\PostgreSQL\9.3\bin\shp2pgsql.exe" -g the_geom -W latin1
-s 900913 -a peche_gue_final_projeter.shp corpo.peche_gue | "C:\Program
Files\PostgreSQL\9.3\bin\psql.exe" -h demo.spatialytics.com -d zec_quebec
-U jlabelle ?q
I get the following error message :
Error : duplicate key value violates unique constraint ? peche_gue_pkey ?
Details : Key ? id_p_gue ? = ? 1 ? already exists.
The table in PostGIS to which I want to append data already has a primary
key column : . ? id_p_gue ? which is in serial.
Any ideas how to deal with this problem?
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20141029/d2d9b2fc/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2014-10-29 19:44 Chrystel Losier <chrystel.losier@reseauzec.com>
parent: Chrystel Losier <chrystel.losier@reseauzec.com>
0 siblings, 0 replies; 131+ messages in thread
From: Chrystel Losier @ 2014-10-29 19:44 UTC (permalink / raw)
Sorry...I figured out the problem...I had manually entered one line of data
into the table in PostGIS so the pkey 1 already existed, by deleting this
row there was no problem appending
2014-10-29 15:41 GMT-04:00 Chrystel Losier <chrystel.losier at reseauzec.com>:
> I am fairly new to PostGIS and need to append data from a shp to an
> already existing table in PostGIS. All the columns from the shp and the
> table are the same, except that the shp does not already contain the
> geometry column and the primary key column. I am using the following
> command line to append the data :
>
>
>
> "C:\Program Files\PostgreSQL\9.3\bin\shp2pgsql.exe" -g the_geom -W latin1
> -s 900913 -a peche_gue_final_projeter.shp corpo.peche_gue | "C:\Program
> Files\PostgreSQL\9.3\bin\psql.exe" -h demo.spatialytics.com -d zec_quebec
> -U jlabelle ?q
>
>
>
> I get the following error message :
>
>
>
> Error : duplicate key value violates unique constraint ? peche_gue_pkey ?
>
> Details : Key ? id_p_gue ? = ? 1 ? already exists.
>
>
>
> The table in PostGIS to which I want to append data already has a primary
> key column : . ? id_p_gue ? which is in serial.
>
>
>
> Any ideas how to deal with this problem?
>
>
>
> Thanks!
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20141029/615434e5/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2015-04-20 11:31 Ahmet Temiz <ahmettemiz88@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Ahmet Temiz @ 2015-04-20 11:31 UTC (permalink / raw)
hello
after creating tiles with gdal_retile.py ....,
I tried to load rasters to postgis with ...
raster2pgsql -c -I -C -s 4326 -M -Y -F ./test2/*.tif rdem2 > rdem2.sql
I got this message
Processing 84/84: ./test2/dem2_4326_06_14.tif
ERROR: diff_rastinfo: Could not run raster alignment test
Can you tell me why ?
regards
--
Ahmet Temiz
Jeoloji M?h.
Afet ve Acil Durum Y?netimi Ba?kanl???
Bilgi ??lem Dairesi Ba?kanl???-CBS Grubu
________________________
Ahmet Temiz
Geological Eng.
Information Systems - GIS Group
Disaster and Emergency Management
of Presidency
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20150420/9cc43aed/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2015-05-08 08:46 Ahmet Temiz <ahmettemiz88@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Ahmet Temiz @ 2015-05-08 08:46 UTC (permalink / raw)
hello,
How can we get correct values from ST_Slope, if raster table is in
EPSG:4326 ?
or
we have to transform dem table to metric projection.
please let me know
kind regards
--
Ahmet Temiz
Jeoloji M?h.
Afet ve Acil Durum Y?netimi Ba?kanl???
Bilgi ??lem Dairesi Ba?kanl???-CBS Grubu
________________________
Ahmet Temiz
Geological Eng.
Information Systems - GIS Group
Disaster and Emergency Management
of Presidency
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20150508/ae1574f5/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2015-11-14 22:30 Ruby Tahboub <ruby.tahboub@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: Ruby Tahboub @ 2015-11-14 22:30 UTC (permalink / raw)
Dear PostGIS-Users,
I'm debugging the sources of PostGIS (using Eclipse) for the purpose of
understanding how spatial predicates work and how to go about adding new
ones. I noticed that I can't step into postgis/gserialized_gist_2d.c, other
locations under the same directory e.g., postgis/geography_measurements.c
can step into nicely. Could you double check my configurations:
CFLAGS="-g3 -O0" ./configure
--with-pgconfig=/usr/local/pgsql2/bin/pg_config --with-projdir=/usr/local
--enable-debug
postgis-2.2.0dev
Thanks,
Ruby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20151114/3d892968/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2015-11-15 16:36 Paul Ramsey <pramsey@cleverelephant.ca>
parent: Ruby Tahboub <ruby.tahboub@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: Paul Ramsey @ 2015-11-15 16:36 UTC (permalink / raw)
In addition to building your postgis with debugging (as you have done)
you need to build your postgresql with debugging on, because the
./postgis directory inherits its build configuration from the
postgresql sources (thanks to pgxs, a mixed blessing). So go back and
rebuild your postgresql too.
ATB,
P
On Sat, Nov 14, 2015 at 2:30 PM, Ruby Tahboub <ruby.tahboub at gmail.com> wrote:
> Dear PostGIS-Users,
>
> I'm debugging the sources of PostGIS (using Eclipse) for the purpose of
> understanding how spatial predicates work and how to go about adding new
> ones. I noticed that I can't step into postgis/gserialized_gist_2d.c, other
> locations under the same directory e.g., postgis/geography_measurements.c
> can step into nicely. Could you double check my configurations:
>
> CFLAGS="-g3 -O0" ./configure --with-pgconfig=/usr/local/pgsql2/bin/pg_config
> --with-projdir=/usr/local --enable-debug
>
> postgis-2.2.0dev
>
> Thanks,
> Ruby
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/postgis-users
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2015-11-15 19:46 Ruby Tahboub <ruby.tahboub@gmail.com>
parent: Paul Ramsey <pramsey@cleverelephant.ca>
0 siblings, 1 reply; 131+ messages in thread
From: Ruby Tahboub @ 2015-11-15 19:46 UTC (permalink / raw)
Hi Paul,
I did enable debugging in my postgres: *./configure
--prefix=/usr/local/pgsql2/ CFLAGS="-g -O0" --enable-debug *
The only issue the debugger does not step into anything defined inside
(postgis/gserialized_gist_2d.c
or postgis/gserialized_gist_nd.c) but it steps into other locations. What
do you think?
Here's an example:
*SELECT ST_Intersects(ST_GeographyFromText('SRID=4326;LINESTRING(-43.23456
72.4567,-43.23456 72.4568)'),
ST_GeographyFromText('SRID=4326;POINT(-43.23456 72.4567772)'))*
I placed a breakpoint inside *postgres* in:
*/src/backend/executor/execQual.c* inside function:
*ExecMakeFunctionResultNoSets* in Line:
*result = FunctionCallInvoke(fcinfo);* // as you already know, this is the
postgres macro which invokes functions as the ones defined inside postgis
The debugger nicely stepped into *postgis/geography_inout.c* function:
*geography_from_text* but NOT *gserialized_overlaps* defined inside
*postgis/**gserialized_overlaps_nd*
Thanks,
Ruby
On Sun, Nov 15, 2015 at 11:36 AM, Paul Ramsey <pramsey at cleverelephant.ca>
wrote:
> In addition to building your postgis with debugging (as you have done)
> you need to build your postgresql with debugging on, because the
> ./postgis directory inherits its build configuration from the
> postgresql sources (thanks to pgxs, a mixed blessing). So go back and
> rebuild your postgresql too.
>
> ATB,
> P
>
> On Sat, Nov 14, 2015 at 2:30 PM, Ruby Tahboub <ruby.tahboub at gmail.com>
> wrote:
> > Dear PostGIS-Users,
> >
> > I'm debugging the sources of PostGIS (using Eclipse) for the purpose of
> > understanding how spatial predicates work and how to go about adding new
> > ones. I noticed that I can't step into postgis/gserialized_gist_2d.c,
> other
> > locations under the same directory e.g., postgis/geography_measurements.c
> > can step into nicely. Could you double check my configurations:
> >
> > CFLAGS="-g3 -O0" ./configure
> --with-pgconfig=/usr/local/pgsql2/bin/pg_config
> > --with-projdir=/usr/local --enable-debug
> >
> > postgis-2.2.0dev
> >
> > Thanks,
> > Ruby
> >
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20151115/5a5ece76/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2015-11-16 14:40 Paul Ramsey <pramsey@cleverelephant.ca>
parent: Ruby Tahboub <ruby.tahboub@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Paul Ramsey @ 2015-11-16 14:40 UTC (permalink / raw)
I have no idea then, sorry.
P.
On Sun, Nov 15, 2015 at 11:46 AM, Ruby Tahboub <ruby.tahboub at gmail.com> wrote:
> Hi Paul,
>
> I did enable debugging in my postgres: ./configure
> --prefix=/usr/local/pgsql2/ CFLAGS="-g -O0" --enable-debug
>
> The only issue the debugger does not step into anything defined inside
> (postgis/gserialized_gist_2d.c or postgis/gserialized_gist_nd.c) but it
> steps into other locations. What do you think?
>
> Here's an example:
>
> SELECT ST_Intersects(ST_GeographyFromText('SRID=4326;LINESTRING(-43.23456
> 72.4567,-43.23456 72.4568)'),
> ST_GeographyFromText('SRID=4326;POINT(-43.23456 72.4567772)'))
>
>
> I placed a breakpoint inside postgres in:
>
> /src/backend/executor/execQual.c inside function:
> ExecMakeFunctionResultNoSets in Line:
>
> result = FunctionCallInvoke(fcinfo); // as you already know, this is the
> postgres macro which invokes functions as the ones defined inside postgis
>
> The debugger nicely stepped into postgis/geography_inout.c function:
> geography_from_text but NOT gserialized_overlaps defined inside
> postgis/gserialized_overlaps_nd
>
>
> Thanks,
> Ruby
>
> On Sun, Nov 15, 2015 at 11:36 AM, Paul Ramsey <pramsey at cleverelephant.ca>
> wrote:
>>
>> In addition to building your postgis with debugging (as you have done)
>> you need to build your postgresql with debugging on, because the
>> ./postgis directory inherits its build configuration from the
>> postgresql sources (thanks to pgxs, a mixed blessing). So go back and
>> rebuild your postgresql too.
>>
>> ATB,
>> P
>>
>> On Sat, Nov 14, 2015 at 2:30 PM, Ruby Tahboub <ruby.tahboub at gmail.com>
>> wrote:
>> > Dear PostGIS-Users,
>> >
>> > I'm debugging the sources of PostGIS (using Eclipse) for the purpose of
>> > understanding how spatial predicates work and how to go about adding new
>> > ones. I noticed that I can't step into postgis/gserialized_gist_2d.c,
>> > other
>> > locations under the same directory e.g.,
>> > postgis/geography_measurements.c
>> > can step into nicely. Could you double check my configurations:
>> >
>> > CFLAGS="-g3 -O0" ./configure
>> > --with-pgconfig=/usr/local/pgsql2/bin/pg_config
>> > --with-projdir=/usr/local --enable-debug
>> >
>> > postgis-2.2.0dev
>> >
>> > Thanks,
>> > Ruby
>> >
>> > _______________________________________________
>> > postgis-users mailing list
>> > postgis-users at lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/postgis-users
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/postgis-users
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/postgis-users
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2018-08-05 19:29 Arto Vuorela <arto.k.vuorela@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Arto Vuorela @ 2018-08-05 19:29 UTC (permalink / raw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20180805/95f0535a/attachment.html;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2023-08-23 09:30 celati Laurent <laurent.celati@gmail.com>
0 siblings, 1 reply; 131+ messages in thread
From: celati Laurent @ 2023-08-23 09:30 UTC (permalink / raw)
Good morning,
I have 5 postgis tables which have different types of geometries (1 point,
1 linear, 3 polygon). And also different field structures. These tables
share fields that provide the same information (project_monitoring,
municipality, etc.). Although the name of these fields is not always
identical according to the tables.
I would like to be able to create a view that can retrieve a few fields
from these tables: the geom, the values of municipalities, the
monitoring_scope Do you know how I can do?
Thanks a lot.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230823/54d03617/attachment.htm;
^ permalink raw reply [nested|flat] 131+ messages in thread
* [postgis-users] (no subject)
@ 2023-08-23 10:36 Nicolas Ribot <nicky666@gmail.com>
parent: celati Laurent <laurent.celati@gmail.com>
0 siblings, 0 replies; 131+ messages in thread
From: Nicolas Ribot @ 2023-08-23 10:36 UTC (permalink / raw)
Hello,
Yes you can by creating a view using UNION ALL (or UNION if you want to
filter out duplicate lines) between tables you want to use, for instance:
create or replace view myview as
select suivi_dossier as suivi_dossier, commune as commune, geom
from table1 UNION ALL
select suividossier, comm, geom from table2 UNION ALL
select ... from table3;
Each select must define the same number and type of columns, first
select gives column names for the view.
(OpenJump is a GIS software that can display such views/tables
containing heterogeneous geometry types, as QGIS does not like them)
Nicolas
On Wed, 23 Aug 2023 at 11:31, celati Laurent <laurent.celati at gmail.com>
wrote:
> Good morning,
>
> I have 5 postgis tables which have different types of geometries (1 point,
> 1 linear, 3 polygon). And also different field structures. These tables
> share fields that provide the same information (project_monitoring,
> municipality, etc.). Although the name of these fields is not always
> identical according to the tables.
>
> I would like to be able to create a view that can retrieve a few fields
> from these tables: the geom, the values of municipalities, the
> monitoring_scope Do you know how I can do?
>
> Thanks a lot.
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230823/53c512c4/attachment.htm;
^ permalink raw reply [nested|flat] 131+ messages in thread
* No subject
@ 2024-10-15 09:42 Łukasz Szałek <Lukasz.Szalek@tomtom.com>
0 siblings, 0 replies; 131+ messages in thread
From: Łukasz Szałek @ 2024-10-15 09:42 UTC (permalink / raw)
Hi all
Sorry for the email, I am new at this list. I hope this is a correct way to post issue.
Anyway what I have is:
1)
PostgreSQL 15.1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
POSTGIS="3.3.2 4975da8" [EXTENSION] PGSQL="150" GEOS="3.11.1-CAPI-1.17.1" PROJ="7.2.1" LIBXML="2.9.1" LIBJSON="0.11"
Query:
select ST_SRID(ST_GeomFromText('POLYGON ((4.9882543 50.4415584, 4.9882543 50.4415586, 4.9882545 50.4415586, 4.9882545 50.4415584, 4.9882543 50.4415584))',4326)), st_srid(ST_UNION(ARRAY[ST_GeomFromText('POLYGON ((4.9882543 50.4415584, 4.9882543 50.4415586, 4.9882545 50.4415586, 4.9882545 50.4415584, 4.9882543 50.4415584))',4326)]));
st_srid | st_srid
---------+---------
4326 | 4326
(1 row)
2)
PostgreSQL 17.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), 64-bit
POSTGIS="3.3.7 a0c7967" [EXTENSION] PGSQL="170" GEOS="3.13.0-CAPI-1.19.0" PROJ="9.5.0" LIBXML="2.9.13" LIBJSON="0.14" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)"
Query:
select ST_SRID(ST_GeomFromText('POLYGON ((4.9882543 50.4415584, 4.9882543 50.4415586, 4.9882545 50.4415586, 4.9882545 50.4415584, 4.9882543 50.4415584))',4326)), st_srid(ST_UNION(ARRAY[ST_GeomFromText('POLYGON ((4.9882543 50.4415584, 4.9882543 50.4415586, 4.9882545 50.4415586, 4.9882545 50.4415584, 4.9882543 50.4415584))',4326)]));
st_srid | st_srid
---------+---------
4326 | 0
Is there a regression between those versions?
Thanks for any info and help
Best regards
Lukasz Szalek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20241015/ffb5a9a9/attachment.htm;
^ permalink raw reply [nested|flat] 131+ messages in thread
end of thread, other threads:[~2024-10-15 09:42 UTC | newest]
Thread overview: 131+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1970-01-01 00:00 [postgis-users] (no subject) songsubo <songsubo@163.com>
2002-05-31 11:11 [postgis-users] (no subject) molinet <molinet@ibp.u-psud.fr>
2002-07-27 19:46 [postgis-users] (no subject) David Garnier <david.garnier@etudier-online.com>
2002-09-25 23:08 [postgis-users] (no subject) Noel Nasayao <ini_47@yahoo.com>
2002-09-25 23:29 [postgis-users] (no subject) Tyler Mitchell <TMitchell@lignum.com>
2002-11-03 06:29 [postgis-users] (no subject) Geoff Anderson <javageoff@hotmail.com>
2002-11-03 15:07 ` Frank Warmerdam <warmerdam@pobox.com>
2004-02-22 21:19 [postgis-users] (no subject) jpalmer at paradise.net.nz <jpalmer@paradise.net.nz>
2004-02-22 23:59 ` Gerry Creager N5JXS <gerry.creager@tamu.edu>
2004-03-05 08:43 [postgis-users] (no subject) Gregory S. Williamson <gsw@globexplorer.com>
2004-03-05 17:36 ` Tyler Mitchell <TMitchell@lignum.com>
2004-03-16 09:30 [postgis-users] (no subject) David Sharp <dsharp@altobridge.com>
2004-03-16 11:16 [postgis-users] (no subject) Mark Cave-Ayland <m.cave-ayland@webbased.co.uk>
2004-03-18 12:06 ` David Sharp <dsharp@altobridge.com>
2004-03-18 17:07 ` David Blasby <dblasby@refractions.net>
2004-03-29 15:31 [postgis-users] (no subject) David Sharp <dsharp@altobridge.com>
2004-03-29 16:41 ` Tyler Mitchell <TMitchell@lignum.com>
2004-03-29 20:00 ` Pericles Nacionales <nacional@cbs.umn.edu>
2004-03-31 17:20 [postgis-users] (no subject) Okeh, Sam <Sam.Okeh@co.fulton.ga.us>
2004-04-16 13:30 [postgis-users] (no subject) David Sharp <dsharp@altobridge.com>
2004-04-16 14:45 ` Paul Ramsey <pramsey@refractions.net>
2004-07-15 11:22 [postgis-users] (no subject) marc.soutter at epfl.ch <marc.soutter@epfl.ch>
2004-07-23 18:53 [postgis-users] (no subject) AGT <alejandrogalindo@tutopia.com>
2004-08-05 16:57 [postgis-users] (no subject) PINKTOMATE <pinktomate@spymac.com>
2004-11-25 12:12 [postgis-users] (no subject) pinktomate <pinktomate@spymac.com>
2004-12-09 07:42 [postgis-users] (no subject) Fabio Fioravanti <ff@ascoli.biz>
2005-05-07 16:21 [postgis-users] (no subject) edgardo cornelio <eliseo_c1@yahoo.com>
2005-07-11 11:54 [postgis-users] (no subject) Christian Schwartze <chris81@minet.uni-jena.de>
2005-07-18 17:35 [postgis-users] (no subject) dblasby at openplans.org <dblasby@openplans.org>
2005-07-18 17:44 [postgis-users] (no subject) Martin Davis <mbdavis@VividSolutions.com>
2005-07-18 18:03 ` Mark Fenbers <Mark.Fenbers@noaa.gov>
2006-01-11 14:44 [postgis-users] (no subject) sergio at labtrans.ufsc.br <sergio@labtrans.ufsc.br>
2006-01-13 19:08 [postgis-users] (no subject) Peter König <peter.koenig@ccgis.de>
2006-01-13 21:43 ` TECHER David <davidtecher@yahoo.fr>
2006-01-14 02:21 ` alex bodnaru <alexbodn@012.net.il>
2006-01-14 18:23 ` Blair Zajac <blair@orcaware.com>
2006-08-11 03:14 [postgis-users] (no subject) smithveg <smithveg@gmail.com>
2007-04-26 10:11 [postgis-users] (no subject) Johannes Scholz <j.scholz@inode.at>
2007-05-02 15:57 [postgis-users] (no subject) gavin.churcher at bt.com <gavin.churcher@bt.com>
2007-05-30 06:02 [postgis-users] (no subject) Jennehag Åke <Ake.Jennehag@lm.se>
2007-06-08 21:16 [postgis-users] (no subject) Gary Townsend <garyt@spatialmapping.com>
2007-06-11 12:41 ` Obe, Regina <robe.dnd@cityofboston.gov>
2007-06-11 12:47 ` Obe, Regina <robe.dnd@cityofboston.gov>
2007-07-03 09:50 [postgis-users] (no subject) Santosh Gaikwad <Santosh.Gaikwad@saama.com>
2007-07-04 11:19 [postgis-users] (no subject) Santosh Gaikwad <Santosh.Gaikwad@saama.com>
2007-07-04 16:08 ` Webb Sprague <webb.sprague@gmail.com>
2007-07-05 13:04 [postgis-users] (no subject) Broun Uganda <tekuganda@hotmail.com>
2007-07-09 17:30 [postgis-users] (no subject) Broun Uganda <tekuganda@hotmail.com>
2007-08-10 19:33 [postgis-users] (no subject) mero mero <mero_mero2266@yahoo.com>
2007-10-05 09:42 [postgis-users] (no subject) Jennehag Åke <Ake.Jennehag@lm.se>
2007-10-05 10:23 ` Gregory Williamson <Gregory.Williamson@digitalglobe.com>
2008-04-17 10:29 [postgis-users] (no subject) Priya Sundararajan <priyasundararajan@yahoo.co.in>
2008-04-18 03:51 ` RAVI KUMAR <ravivundavalli@yahoo.com>
2009-05-13 06:26 [postgis-users] (no subject) rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2009-05-13 06:51 ` strk <strk@keybit.net>
2009-05-13 07:22 ` rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2009-05-13 06:55 ` Anton Patrushev <anton@orkney.co.jp>
2009-05-13 07:03 ` rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2009-05-13 07:12 ` Pradeep B V <pradeepbv@gmail.com>
2009-05-13 06:55 ` Ben Madin <ben@remoteinformation.com.au>
2009-05-13 07:17 ` rahul.pachaghare at tcs.com <rahul.pachaghare@tcs.com>
2009-08-14 08:40 [postgis-users] (no subject) Pena Kupen <kupen@wippies.fi>
2009-09-29 17:10 [postgis-users] (no subject) eehab hamzeh <eehab40@hotmail.com>
2009-09-29 18:36 ` Emilie Laffray <emilie.laffray@gmail.com>
2010-04-07 00:47 [postgis-users] (no subject) Chen, Li [Contractor] <Li.Chen@andrew.com>
2010-05-22 17:29 [postgis-users] (no subject) Ivan Mincik <ivan.mincik@gmail.com>
2010-09-13 19:04 [postgis-users] (no subject) Rorie Overby <ogrears@hotmail.com>
2010-09-16 15:11 [postgis-users] (no subject) Henri De Feraudy <feraudyh@yahoo.com>
2010-09-16 15:53 ` Kevin Neufeld <kneufeld@refractions.net>
2010-09-16 17:13 ` Henri De Feraudy <feraudyh@yahoo.com>
2010-09-16 17:17 ` Henri De Feraudy <feraudyh@yahoo.com>
2010-09-22 15:04 [postgis-users] (no subject) Jorge Eliécer Osorio Caro <jorgeliecer.osorio@gmail.com>
2010-12-03 15:41 [postgis-users] (no subject) jose p fonseca filho <jose.fonseca.ti@gmail.com>
2011-01-03 10:36 [postgis-users] (no subject) Jose <jsantiso@srmconsulting.es>
2011-01-17 16:58 [postgis-users] (no subject) mahadzar ayala <mahadzar_ayala@yahoo.com>
2011-02-16 11:44 [postgis-users] (no subject) Colin <colinflack@fastmail.co.uk>
2011-02-17 01:43 ` Stephen Woodbridge <woodbri@swoodbridge.com>
2011-03-04 20:40 [postgis-users] (no subject) Andrew B <apburnes@gmail.com>
2011-04-04 06:46 [postgis-users] (no subject) Michael Savarese <geomajor56@gmail.com>
2011-04-07 16:57 [postgis-users] (no subject) Paul & Caroline Lewis <paulcaz80@hotmail.com>
2011-04-07 17:17 ` Richard Gomes <rgomes1997@yahoo.co.uk>
2011-04-08 14:16 ` Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
2011-04-12 16:38 ` Paul & Caroline Lewis <paulcaz80@hotmail.com>
2011-04-14 09:37 ` Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
2011-04-14 10:01 ` Richard Gomes <rgomes1997@yahoo.co.uk>
2011-05-30 12:37 [postgis-users] (no subject) Sairam Krishnamurthy <kmsram420@gmail.com>
2011-06-09 13:34 [postgis-users] (no subject) muhammad imran <imranserver@yahoo.com>
2011-06-09 13:50 ` Pierre Racine <Pierre.Racine@sbf.ulaval.ca>
2011-11-01 14:20 [postgis-users] (no subject) Stephen V. Mather <svm@clevelandmetroparks.com>
2011-11-01 16:36 ` Paul Ramsey <pramsey@opengeo.org>
2011-11-21 02:05 [postgis-users] (no subject) Ýzzet Aykut KOÇAK <izzetaykutkocak@gmail.com>
2011-11-22 13:15 [postgis-users] (no subject) joel ml <mpg70221725@yahoo.com.ar>
2011-11-27 01:06 [postgis-users] (no subject) Yesid Carrillo Vega <yecarrillo@gmail.com>
2011-11-28 07:53 [postgis-users] (no subject) joel ml <mpg70221725@yahoo.com.ar>
2012-03-28 11:20 [postgis-users] (no subject) mahavir trivedi <mahavir.trivedi@gmail.com>
2012-03-28 11:22 ` mahavir trivedi <mahavir.trivedi@gmail.com>
2012-03-28 16:03 ` George Silva <georger.silva@gmail.com>
2012-05-16 17:07 [postgis-users] (no subject) Kurt <mtrp36@hotmail.com>
2012-05-18 00:11 [postgis-users] (no subject) David B�langer <belanger_david@live.ca>
2012-05-27 15:14 [postgis-users] (no subject) Kurt <mtrp36@hotmail.com>
2012-05-29 15:26 [postgis-users] (no subject) Kurt <mtrp36@hotmail.com>
2012-06-09 15:00 [postgis-users] (no subject) truongxuan quang <truongxuanquang@yahoo.com>
2012-09-26 16:32 [postgis-users] (no subject) Jamie Taylor <stuff4jamie@yahoo.com>
2012-11-01 13:26 [postgis-users] (no subject) Juan Rapoport <juanrapoport@suremptec.com.ar>
2013-02-02 06:14 [postgis-users] (no subject) Pavel Shub <pavel@citymaps.com>
2013-02-02 08:14 ` Francois Hugues <hugues.francois@irstea.fr>
2013-02-02 10:54 ` Nicolas Ribot <nicolas.ribot@gmail.com>
2013-02-02 16:44 ` Pavel Shub <pavel@citymaps.com>
2013-06-14 10:11 [postgis-users] (no subject) Guo YU <yuguo365@gmail.com>
2013-07-08 13:18 [postgis-users] (no subject) Ahmet Temiz <ahmettemiz88@gmail.com>
2013-08-26 13:45 [postgis-users] (no subject) ibad raza <ibadraza001@gmail.com>
2013-09-10 20:04 [postgis-users] (no subject) John Smith <jayzee.smith@gmail.com>
2013-09-23 06:52 [postgis-users] (no subject) Ahmet Temiz <ahmettemiz88@gmail.com>
2013-09-23 07:12 ` Hugues François <hugues.francois@irstea.fr>
2013-09-23 13:56 ` Pierre Racine <Pierre.Racine@sbf.ulaval.ca>
2014-04-15 12:40 [postgis-users] (no subject) Marcello Benigno <benigno.marcello@gmail.com>
2014-04-17 22:32 [postgis-users] (no subject) zeta_rif at yahoo.com <zeta_rif@yahoo.com>
2014-06-20 00:42 [postgis-users] (no subject) Aryeh Hillman <aryeh@cloudparity.com>
2014-06-20 00:49 ` Bborie Park <dustymugs@gmail.com>
2014-10-29 19:41 [postgis-users] (no subject) Chrystel Losier <chrystel.losier@reseauzec.com>
2014-10-29 19:44 ` Chrystel Losier <chrystel.losier@reseauzec.com>
2015-04-20 11:31 [postgis-users] (no subject) Ahmet Temiz <ahmettemiz88@gmail.com>
2015-05-08 08:46 [postgis-users] (no subject) Ahmet Temiz <ahmettemiz88@gmail.com>
2015-11-14 22:30 [postgis-users] (no subject) Ruby Tahboub <ruby.tahboub@gmail.com>
2015-11-15 16:36 ` Paul Ramsey <pramsey@cleverelephant.ca>
2015-11-15 19:46 ` Ruby Tahboub <ruby.tahboub@gmail.com>
2015-11-16 14:40 ` Paul Ramsey <pramsey@cleverelephant.ca>
2018-08-05 19:29 [postgis-users] (no subject) Arto Vuorela <arto.k.vuorela@gmail.com>
2023-08-23 09:30 [postgis-users] (no subject) celati Laurent <laurent.celati@gmail.com>
2023-08-23 10:36 ` Nicolas Ribot <nicky666@gmail.com>
2024-10-15 09:42 No subject Łukasz Szałek <Lukasz.Szalek@tomtom.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox