On Mon, Jan 30, 2012 at 04:34:35PM -0700, Yusuf Siddiqui wrote:
> SELECT count, geometry, ST_GeometryType(geometry)
> FROM (
> SELECT COUNT(*) AS count,
>
> ST_Buffer(ST_Buffer(ST_Union(ST_Buffer(ST_SimplifyPreserveTopology(geometry,
> 0.001), 1e-005)),.001), -.001) A
On Mon, Jan 30, 2012 at 10:55:41PM +, Martin Tomko wrote:
> Excellent work strk, thanks for this!
> Could you please provide some examples how this can be used in queries? Does
> it speed up querying for neighbours etc.?
The focus insofar is about normalized storage. Speed you can squeeze out
John,
I'm no expert at this, but assuming that your query returns multiple rows, I
suspect this is to do with the WMS layer only identifying one feature (which
then only returns one of row). This would seem like standard WMS behaviour. If
you have multiple features at the same point, you might
On 01/30/2012 09:00 PM, John Morgan wrote:
Hello,
I am attempting to get a one (polys) to many (table) to load postgis data
within a mapserver wms. I have the following defined in the .map file.
DATA "the_geom FROM (SELECT polys.gid AS gid, polys.the_g
eom AS the_geom, table.pt_id AS pt_id, ta
Hello,
I am attempting to get a one (polys) to many (table) to load postgis data
within a mapserver wms. I have the following defined in the .map file.
DATA "the_geom FROM (SELECT polys.gid AS gid, polys.the_g
eom AS the_geom, table.pt_id AS pt_id, table.agent AS agent FROM polys
RIGHT OUTER JOIN
On Jan 29, 2012, at 11:39 PM, pcr...@pcreso.com wrote:
> > When did this become available?
> > I'm using pgsql2shp from Postgis version 1.5.3 for Linux, which is pretty
> > current,
> > and that is not a listed command line option.
>
> Not really sure when but see
>
> http://trac.osgeo.org
Thanks for the feedback guys. The -n option on shp2pgsql worked well.
Derek
On Sun, Jan 29, 2012 at 9:17 PM, John Morgan wrote:
> Hello,
> This may be more of a postgresql question, but it is related to my postgis
> setup. I was hoping that someone might know of an easy way to load a dbf
>
Dear group,
I've been having trouble trying to do a nested PostGIS query on our system.
The query looks something like this:
SELECT count, geometry, ST_GeometryType(geometry)
FROM (
SELECT COUNT(*) AS count,
ST_Buffer(ST_Buffer(ST_Union(ST_Buffer(ST_SimplifyPreserve
Excellent work strk, thanks for this!
Could you please provide some examples how this can be used in queries? Does it
speed up querying for neighbours etc.?
Also, does it support network topologies, something I could use with pgrouting
or so?
Thanks,
Martin
--
Martin Tomko, PhD.
Senior Project
On Thu, Jan 26, 2012 at 9:33 PM, Nicolas Ribot wrote:
> >>
> >> From: Nicolas Ribot
> >>
> >> Hi
> >>
> >> WITH RECURSIVE needs an UNION ALL to link the "non recursive" term
> >> with the "recursive" one.
> >>
> >
> > Wow, that at least runs... though I think the recursion might be
> infinite.
>
On Mon, Jan 30, 2012 at 04:34:44PM +0200, Sindile Bidla wrote:
> Thanks strk,
>
> I was trying to use the topology functions.
>
> UPDATE public.sa_provinces
> SET topogeom = toTopoGeom(the_geom, 'sa_provinces_topo');
>
> I get the following message:
>
> ERROR: function totopogeom(geometry, u
Thanks strk,
I was trying to use the topology functions.
UPDATE public.sa_provinces
SET topogeom = toTopoGeom(the_geom, 'sa_provinces_topo');
I get the following message:
ERROR: function totopogeom(geometry, unknown) does not exist
LINE 2: SET topogeom = toTopoGeom(the_geom, 'sa_provinces_
It's been around for years. Since 1.4 I'd guess. When you type shp2pgsql
you should see this option:
-n Only import DBF file.
The OP was how to load a dbf into postgres, you're exporting with
pgsql2shp, which will export only the dbf if there is not geometry column
in the table being exported.
Maybe Paul Ramsey's recent posting provides some inspiration:
http://blog.opengeo.org/2012/01/27/getting-curvey/
Regards,
Edward
Date: Mon, 30 Jan 2012 14:50:46 +0100
From: r.pisp...@gmail.com
To: postgis-users@postgis.refractions.net
Subject: [postgis-users] Select smoothed lines
Hi all,
my
On Mon, Jan 30, 2012 at 02:50:46PM +0100, Rocco Pispico wrote:
> Hi all,
> my database contains a lot of paths of storms.
> Each storm path is generated by joining the centroids of the storm at any
> moment of measurement.
> The result is sometimes a line with a lot of edge.
> Can you suggest me a
Hi all,
my database contains a lot of paths of storms.
Each storm path is generated by joining the centroids of the storm at any
moment of measurement.
The result is sometimes a line with a lot of edge.
Can you suggest me a method to select these lines a little bit smoothed.
TIA Rocco
_
Thanks strk,
this is great news - thank you for your efforts,
cheers
Ben
On 30/01/2012, at 7:49 PM, Sandro Santilli wrote:
> As of revision 8963 (included in upcoming 2.0.0alpha3 [1]), the function
> to convert simple layers to topologically defined layers [2] is completed.
>
> [1] 2.0.0alph
On Mon, Jan 30, 2012 at 01:01:12PM +0100, Jose Carlos Martinez wrote:
> It would be really nice if some people from QGIS, gvSIG, uDIG, etc.
> start thinking about building a plugin for it.
We've discussed it some for QGIS in Zurich, mostly storming and comparing
GRASS and PostGIS topology to see
Great news,
Congratulations! Lets try it!!
It would be really nice if some people from QGIS, gvSIG, uDIG, etc.
start thinking about building a plugin for it.
Regards,
Jose
On 30/01/2012 12:49, Sandro Santilli wrote:
As of revision 8963 (included in upcoming 2.0.0alpha3 [1]), the function
to c
As of revision 8963 (included in upcoming 2.0.0alpha3 [1]), the function
to convert simple layers to topologically defined layers [2] is completed.
[1] 2.0.0alpha3 http://www.postgis.org/download/
[2] toTopoGeom http://trac.osgeo.org/postgis/ticket/1017
This means that building a persistent top
Volkmar,
Many thanks for trying to help. Unfortunately I already did all of those
things. To make matters worse I just tried the procedure on my 32bit windows
system in my office and I am getting the same issue. The dll is in the right
place and the system variable and PATH are setup as per th
On Mon, Jan 30, 2012 at 12:49:18AM -0800, Giannis Giakoumidakis wrote:
> It's ending of January, when we should expect the new release of Post GIS 2.0?
You should expect it to be out as soon as all blocker bugs are closed:
http://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reope
It's ending of January, when we should expect the new release of Post GIS 2.0?
Thanx.
___
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
On Mon, Jan 30, 2012 at 07:40:01AM +0100, Stefan Keller wrote:
> 2012/1/27 Sandro Santilli :
> > On Thu, Jan 26, 2012 at 09:50:25PM +0100, Stefan Keller wrote:
...
> >> Am I missing something?
> >
> > A ticket on the trac system, most likely :)
>
> So you think it's not redundant to ticket #660?
O
24 matches
Mail list logo
