Hi Jose !
how sql should looks like?
I use PHP. so i want to use it whit PostgreSql...
is there any doc. about this function?
Question about Python class...i am not python programer can you
describe my how i can use it?
thx :)
Hi,
On 9/14/07, Maciej Skorczewski [EMAIL PROTECTED]
Paul Ramsey wrote:
How many folks are using the latest PostGIS on PgSQL 8.0?
From a development point-of-view, the quantity of
backwards-compatibility code is growing and growing, and that makes the
code base a lot less pleasant.
Are there still lots of people using PgSQL 8.0 with the latest
On Thu, 2007-09-13 at 15:26 +0200, Stefan Zweig wrote:
Mark,
thank you very much for your response. As far as I understand, pre-computed
bounding boxes are stored (by default) to each Geometry object (wherever that
is) to make bounding box based queries faster, see
as_kml()?! there's another askml() in line with asgml(). why this
alias/name change/confusion?
anyway how does it really work? getting a Must contain
'geometry_column from table_name' or 'geom from (subselect) as foo'
(couldnt find ' from '). what do i do after passing bbox=... and
type=kml to
This isn't a bug per se, because it's doing exactly what we want,
but I think it's very possible we don't want to do this.
We have so many other checks and balances with regard to SRID coherence
(in index building, in the table constraints build by the default
loader, in the geometry
Chris,
select uniqid from thetable where not st_isvalid(the_geom);
And if you're feeling lucky (punk), try to fix them with:
update thetable set the_geom = st_buffer(the_geom,0.0) where not
st_isvalid(the_geom);
Paul
Chris Hermansen wrote:
Hello again;
So with GEOS 3.0.0RC4 the problem
Currently your only option is to run isValid on your geometry table. It
will identify any geometries which are not valid.
To see the actual nature and location of the errors you will have to
export them to another tool (such as JUMP or JTS TestBuilder) to see the
actual nature location of
Thanks, Martin, I will give those a try and report back on what I find
out.
On Fri, 2007-14-09 at 10:01 -0700, Martin Davis wrote:
Currently your only option is to run isValid on your geometry table. It
will identify any geometries which are not valid.
To see the actual nature and
On Friday 14 September 2007, John Smith wrote:
as_kml()?! there's another askml() in line with asgml(). why this
alias/name change/confusion?
anyway how does it really work? getting a Must contain
'geometry_column from table_name' or 'geom from (subselect) as foo'
(couldnt find ' from ').
http://www.bostongis.com/PrinterFriendly.aspx?content_name=ogr_cheatsheet
I use ogr2ogr for doing that.. however sometimes its best to write the KML
using your own structure, descriptions, and element names.
http://www.gdal.org/ogr/drv_kml.html will describe the options that let you
name the
I used Paul's command and here's an excerpt of what I found:
clh=# select gid from v2007 where not st_isvalid(the_geom);
NOTICE: Self-intersection at or near point 1.01727e+06 886743
NOTICE: Self-intersection at or near point 1.06218e+06 960196
NOTICE: Self-intersection at or near point
Thats so cool it hurts.. I love offloading processing to the big bad server
while the little wimpy sql clients request the data. Good find!
On 9/14/07, Kevin Neufeld [EMAIL PROTECTED] wrote:
Absolutely.
See attached, a simple plpgsql function that adds header info around the
current askml
12 matches
Mail list logo
