Re: [postgis-users] noding problem

2007-10-19 Thread Chris Hermansen
Hi Martin, everyone; The polygons were converted to linestrings in the previous step, and I've checked... Martin Davis wrote: > Did you convert your polygons to linestrings? If not, then you are > running the union operation on polygonal geometry. This is the usual > source of topology errors (

Re: [postgis-users] Re: PROJ projection issues

2007-10-19 Thread Paul Ramsey
Are there grid files in the proj directory? On 19-Oct-07, at 2:36 PM, Brian Timoney wrote: Paul: Thanks for the quick reply. The more recent version with dubious results was using the standard PostGIS Windows installer. Brian Proj has the funny build process where you have to untar the

[postgis-users] St_Simplify usage with adjacent polygons

2007-10-19 Thread Dane Blakely Springmeyer
A question regarding the function ST_Simplify: I have a postgis layer of watershed polygons that I would like to simplify, yet while keeping all shared edges. In other words, I'd like to remove vertices along shared boundaries without creating gaps between adjacent polygons. I'm no expert i

[postgis-users] Re: PROJ projection issues

2007-10-19 Thread Brian Timoney
Paul: Thanks for the quick reply. The more recent version with dubious results was using the standard PostGIS Windows installer. Brian Proj has the funny build process where you have to untar the nadcon grids into the source tree before building. If you forget that step, your proj won'

Re: [postgis-users] Discovering where roads cross rivers

2007-10-19 Thread Brent Wood
> > On 15-Sep-07, at 8:03 AM, Dave Potts wrote: > > > >> I am trying to discover all the data points when a river system > >> crosses a road system, my data is expressed as two different > >> shapefiles, I had assumed that it was just a case of calling the > >> Intersection method > >> > >> eg

RE: [postgis-users] ESRI Shapes from database

2007-10-19 Thread Brent Wood
--- Lee Keel <[EMAIL PROTECTED]> wrote: > > Steffen, > > Thanks for the reply, but I am not sure how to call COPY using STDIN. Do > you have an example? I really don't see how to call COPY using STDIN if I > am using an npgsqlcommand object in .NET. So I am guessing there is no > specific per

Re: [postgis-users] PROJ projection issues?

2007-10-19 Thread Paul Ramsey
Proj has the funny build process where you have to untar the nadcon grids into the source tree before building. If you forget that step, your proj won't have the grids available for conversion. P On 19-Oct-07, at 2:03 PM, Brian Timoney wrote: Was whatever does the datum shifts between NAD27

RE: [postgis-users] ESRI Shapes from database

2007-10-19 Thread Lee Keel
> -Original Message- > From: [EMAIL PROTECTED] [mailto:postgis-users- > [EMAIL PROTECTED] On Behalf Of Steffen Macke > Sent: Friday, October 19, 2007 3:03 PM > To: PostGIS Users Discussion > Subject: Re: [postgis-users] ESRI Shapes from database > > Lee, > > > have just figured out that t

[postgis-users] PROJ projection issues?

2007-10-19 Thread Brian Timoney
List: I noticed this awhile back when we were running some NAD27 to NAD83 conversions but didn't get around to posting until the issue came up in another context-- SQL Statement: select astext(transform((Geomfromtext('POINT(-106.95384 44.96925)',4267)),4269)); a. Old PostGIS version--Li

Re: [postgis-users] ESRI Shapes from database

2007-10-19 Thread Steffen Macke
Lee, > have just figured out that the COPY command requires superuser permissions. I found the following: > But, the copy command does allow ordinary users to use it if you are using > the "FROM > STDIN" clause. Hope that helps. Regards, Steffen __

RE: [postgis-users] ESRI Shapes from database

2007-10-19 Thread Lee Keel
I have gotten things working under acceptable time constrains with C# by writing to a file and using the COPY command. My new problem now is that I have just figured out that the COPY command requires superuser permissions. Does anyone know if there is any specific permission that I can grant to a

Re: [postgis-users] noding problem

2007-10-19 Thread Martin Davis
Did you convert your polygons to linestrings? If not, then you are running the union operation on polygonal geometry. This is the usual source of topology errors (which are caused by robustness & precision issues in the underlying linework). Chris Hermansen wrote: Hi folks; I posted someth

[postgis-users] noding problem

2007-10-19 Thread Chris Hermansen
Hi folks; I posted something a few days back on a noding problem I'm having, and received no answer. At this point I have more details and I think there is something seriously wrong. This is Postgis 1.3.1 and GEOS 3.0.0rc4. The Postgis Wiki has an example of putting two somewhat overlapping pol

Re: [postgis-users] indexing images stored in PostGres

2007-10-19 Thread Brent Wood
--- P Kishor <[EMAIL PROTECTED]> wrote: > The topic of storing satellite imagery in the db vs. on the filesystem > has been discussed before. I am hoping for answer to the following -- > > Can I store imagery in the db with the hope of being able to query for > specific areas of interest (AOI) i

RE: [postgis-users] Buffer generation & drawing problem

2007-10-19 Thread Obe, Regina
Luis, I forgot to mention. If you want to output this as KML and save yourself some work in your script code, you may want to look into using AsKML instead of AsText function. I think AsKML exists in version 1.2 and up or somewhere around that vicinity. Hope that helps, Regina -Original M

RE: [postgis-users] Buffer generation & drawing problem

2007-10-19 Thread Obe, Regina
Luis, I'm not sure if anyone has answered your question, but I didn't see one so here is my answer. I think the problem you are having is that you are working in degree coordinates so when you say buffer 0.1 that actually isn't a constant radius. If you can - the best way to fix the problem is t

[postgis-users] Re: Upgrade 1.2.1 to 1.3.1 - Problems

2007-10-19 Thread Brian Hamlin
Per-Olof My worst problem it seems is that I had expected the clear warnings as described in the README and doc. I just tried a freshly created DB, initialized with postgis 1.3.1 and got none of those terrible errors. So things are able to work. It looks like I will have to 'hard upgrade' the