Ensure you have appropriately modified postgreql.conf & pg_hba.conf to allow
the appropriate external access to the required database, for the required
user, from the client IP (CIDR) address. If this is not enabled, such external
connections cannot happen.
Brent Wood
--- On Sat, 5/12/12, Siju
12.05.2012 12:00, Siju Wu ???:
Hi,
I began using the GDAL for my master projet last month. Before I
used OGR to read directly the maps of shapefile. But now I need to
store the data first in the database of PostgreSQL and then make
access to the database by using the driver of OGR. However
Sounds like 1.8 and my reading the docs more carefully :) would solve
my problems.
Thanks for the info Even I really appreciate it!
Even Rouault wrote:
Le samedi 15 octobre 2011
00:51:01, David J. Bakeman a écrit :
> Thanks Even and
everyone else who responded! It was the fact that
Le samedi 15 octobre 2011 00:51:01, David J. Bakeman a écrit :
> Thanks Even and everyone else who responded! It was the fact that I had
> created the tables without registering the geometry column. I did that
> and now things appear good to go! That is ogrinfo is successful and
> lists the thre
Thanks Even and everyone else who responded! It was the fact that I had
created the tables without registering the geometry column. I did that
and now things appear good to go! That is ogrinfo is successful and
lists the three tables with geometry.
Perhaps the normal user of ogr is aware th
> OK now we are getting somewhere! I did the following:
>
> env PG_LIST_ALL_TABLES=YES ogrinfo --debug on PG:'dbname=mydb'
> PG: DBName="mydb"
> PG: PostgreSQL version string : 'PostgreSQL 8.4.9 on
> x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.5.1 20100924 (Red
> Hat 4.5.1-4), 64-bit'
>
Even Rouault wrote:
Le vendredi 14 octobre 2011 22:57:32, David J. Bakeman a écrit :
Even Rouault wrote:
Le vendredi 14 octobre 2011 21:04:12, David J. Bakeman a écrit :
Try ogrinfo --debug on -ro PG:'dbname=mydb'
OK I am totally confused now here is the output:
ogrinfo --
Le vendredi 14 octobre 2011 22:57:32, David J. Bakeman a écrit :
> Even Rouault wrote:
> > Le vendredi 14 octobre 2011 21:04:12, David J. Bakeman a écrit :
> >
> > Try ogrinfo --debug on -ro PG:'dbname=mydb'
>
> OK I am totally confused now here is the output:
> ogrinfo --debug -ro PG:'dbname=m
Even Rouault wrote:
Le vendredi 14 octobre 2011 21:04:12, David J. Bakeman a écrit :
Try ogrinfo --debug on -ro PG:'dbname=mydb'
OK I am totally confused now here is the output:
ogrinfo --debug -ro PG:'dbname=mydb'
INFO: Open of `PG:dbname=mydb'
using driver `PostgreSQL' successful.
Le vendredi 14 octobre 2011 21:04:12, David J. Bakeman a écrit :
Try ogrinfo --debug on -ro PG:'dbname=mydb'
and see if something interesting shows up (and post the output to the list if
you don't find the solution by yourself)
It is really weird that it works with QGIS but not with OGR. Th
Sorry I was trying to limit the bandwidth I used I figured it was
probably something really stupid and someone would just say you forgot
to XX :<;
Anyway this is a test database so it really is named mydb and I copied
the ogrinfo command from the PostgreSQL driver page for OGR. I checked
bef
David,
It probably is a configuration or simple error, however, you've
not given much detail to let other people try to guess what it might
be. Kyle asked for the output of your command. Also, the exact
command (copied from terminal) may help too. I looked at the OGR
PosrgreSQL/PostGIS for
Mateusz Łoskot wrote:
On 13 October 2011 23:47, David J. Bakeman wrote:
I'm on Fedora core 14 with gdal 1.7.3.
I setup postgre and created a spatial enabled database with a table that
includes geometry. I can connect using psql mydb. However when I try
ogrinfo -ro PG:dbname=mydb it fails
On 13 October 2011 23:47, David J. Bakeman wrote:
> I'm on Fedora core 14 with gdal 1.7.3.
>
> I setup postgre and created a spatial enabled database with a table that
> includes geometry. I can connect using psql mydb. However when I try
> ogrinfo -ro PG:dbname=mydb it fails saying no driver fo
Can you show us the output of the command? And also ogrinfo --formats
From: gdal-dev-boun...@lists.osgeo.org
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of David J. Bakeman
Sent: Thursday, October 13, 2011 4:47 PM
To: gdal-dev@lists.osgeo.org
Subject: [gdal-dev] PostgreSQL problems
I'm s
> I can confirm this fixed my problem. I mentioned $bounty$ before, and I
> meant it. $50 sound ok? Let me know (off list if you like) an address,
> and I'll get you a check. (although its u.s. dollars, looks like you
> are from France?) Got a wish list someplace?
Thanks for the offer, but I
On 9/29/2011 11:28 AM, Even Rouault wrote:
Selon Andy Colson:
On 9/29/2011 1:36 AM, Even Rouault wrote:
Le mercredi 28 septembre 2011 21:28:26, Even Rouault a écrit :
Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
Hi List,
I'm using ogr2ogr to convert (and reproject) data from s
Selon Andy Colson :
> On 9/29/2011 1:36 AM, Even Rouault wrote:
> > Le mercredi 28 septembre 2011 21:28:26, Even Rouault a écrit :
> >> Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
> >>> Hi List,
> >>>
> >>> I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
> >>
On 9/29/2011 1:36 AM, Even Rouault wrote:
Le mercredi 28 septembre 2011 21:28:26, Even Rouault a écrit :
Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
Hi List,
I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
if I use insert statements the null dates are not
Le mercredi 28 septembre 2011 21:28:26, Even Rouault a écrit :
> Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
> > Hi List,
> >
> > I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
> > if I use insert statements the null dates are not a problem, but if I
> > set
On 9/28/2011 2:28 PM, Even Rouault wrote:
>
> On another layer, regardless of insert/copy, I'm getting:
>
> ERROR: numeric field overflow
> DETAIL: A field with precision 19, scale 11 must round to an absolute
> value less than 10^8.
> CONTEXT: COPY poltwppoly, line 1, column shape_area:
Le mercredi 28 septembre 2011 23:09:01, Andy Colson a écrit :
> Would a 16Meg .zip file, that extracts to 157Meg, be acceptable in Trac?
> I attempted to copy some records out, but it created the new shapefile
> with a type of ftString instead of ftDate.
I'm afraid 16 MB will be too big. Perhaps
Would a 16Meg .zip file, that extracts to 157Meg, be acceptable in Trac?
I attempted to copy some records out, but it created the new shapefile
with a type of ftString instead of ftDate.
-Andy
On 9/28/2011 2:28 PM, Even Rouault wrote:
Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit
Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
> Hi List,
>
> I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
> if I use insert statements the null dates are not a problem, but if I
> set PG_USE_COPY=YES, then I get errors:
>
> ERROR 1: COPY statement failed.
>
---
De : Andy Colson [mailto:a...@squeakycode.net]
Envoyé : Wednesday, 28 September 2011 5:23 PM
À : Ivan Price
Cc : gdal-dev@lists.osgeo.org
Objet : Re: [gdal-dev] PostgreSQL
Not simply. I am receiving data from many different places, some places send
nice clean data, other's, not so much (all
de.net]
Envoyé : Wednesday, 28 September 2011 5:09 PM
À : Ivan Price
Cc : gdal-dev@lists.osgeo.org
Objet : Re: [gdal-dev] PostgreSQL
They use a slightly older version of shapelib that doesnt quite work with null's.
If I ogr2ogr shapefile -> shapefile (to get it in the projection I want), then
igine-
De : Andy Colson [mailto:a...@squeakycode.net]
Envoyé : Wednesday, 28 September 2011 5:09 PM
À : Ivan Price
Cc : gdal-dev@lists.osgeo.org
Objet : Re: [gdal-dev] PostgreSQL
They use a slightly older version of shapelib that doesnt quite work with
null's. If I ogr2ogr shapefile -
g [mailto:gdal-dev-boun...@lists.osgeo.org]
De la part de Andy Colson
Envoyé : Wednesday, 28 September 2011 4:50 PM
À : gdal-dev@lists.osgeo.org
Objet : Re: [gdal-dev] PostgreSQL
Sorry to keep pestering. Is there a better place I should be seeking help?
Would a $bounty$ help?
-Andy
On 9/22/201
y Colson
Envoyé : Wednesday, 28 September 2011 4:50 PM
À : gdal-dev@lists.osgeo.org
Objet : Re: [gdal-dev] PostgreSQL
Sorry to keep pestering. Is there a better place I should be seeking help?
Would a $bounty$ help?
-Andy
On 9/22/2011 10:48 AM, Andy Colson wrote:
> Hi List,
>
> I
Sorry to keep pestering. Is there a better place I should be seeking
help? Would a $bounty$ help?
-Andy
On 9/22/2011 10:48 AM, Andy Colson wrote:
Hi List,
I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
if I use insert statements the null dates are not a problem, but
On Thu, Sep 22, 2011 at 9:18 PM, Andy Colson mailto:a...@squeakycode.net>> wrote:
Hi List,
I'm using ogr2ogr to convert (and reproject) data from shapefile to PG, if
I use insert statements the null dates are not a problem, but if I set
PG_USE_COPY=YES, then I get errors:
ERROR 1:
Andy,
Send me the problematic shapefiles and explain what conversions you are
trying to perform.
On Thu, Sep 22, 2011 at 9:18 PM, Andy Colson wrote:
> Hi List,
>
> I'm using ogr2ogr to convert (and reproject) data from shapefile to PG, if
> I use insert statements the null dates are not a probl
Hi Frank,
This is actually what I am doing, so no problems here ;-)
It was rather a suggestion in case it was not discussed, because it may have
been useful differently, but it is fine for me so.
Best Regards,
Matthieu
On Wednesday 03 November 2010 14:30:07 Frank Warmerdam wrote:
> On Wed, Nov
On Wed, Nov 3, 2010 at 9:23 AM, Matthieu Rigal wrote:
> Hi guys,
>
> I was checking and I did not found a proper way for now to add a unique or not
> null constraints to columns of a layer created/edited by OGR.
>
> If I am wrong, please correct me.
> Else, as I saw that a big refactoring of the P
Selon Casper Børgesen :
I'm not sure about options='-c client_encoding=latin1', but setting
PGCLIENTENCODING=LATIN1 instead as an environmnent variable/configuration option
should definitely work (provided that the source shape is effectively LATIN1
encoded)
ogr2ogr --config PGCLIENTENCODING LATI
35 matches
Mail list logo