Yep.
For the downgrading I tried it a while ago for a subset of the same schema,
https://github.com/Remi-C/pointcloud/blob/master/lib/pc_api.h#L445
The idea was that usually we don't need all dimensions, particularly when
working on the geometry.
So I wrote a couple of functions to allow a pc_expl
I am working through some postgis stuff for a Drupal module, and noticed
that the geometry storage in Drupal is "bytea" (because it tends to be
mysql-centric?).
What is the difference, i.e., advantage offered by the PostGIS custom type
"geometry"?
Thanks,
/r/b
--
--
Robert W. Burgholzer
'Makin
Is there any chance to load multiple rasters in the same table?
Raffaele
--
« Nunc est bibendum, nunc pede libero pulsanda tellus »
___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-use
2014-10-31 15:08 GMT+01:00 Raffaele Morelli :
> Is there any chance to load multiple rasters in the same table?
>
> Raffaele
Yes.
Similarly to vector, a raster layer in PostGIS is made of a pair:
table and column, not just a table.
Best regards,
--
Mateusz Łoskot, http://mateusz.loskot.net
Hi!
I'm am turning to you all hoping you'll have some tricks to help with
this problem:
I created a topology for 2290 polygons and populated a topogeom column
using these commands:
SELECT topology.CreateTopology('de_20k_topo', find_srid('syshiera',
'de_20k', 'geom_32198'), 1e-4);
SELECT topology
On Fri, Oct 31, 2014 at 08:47:59AM -0400, Robert Burgholzer wrote:
> I am working through some postgis stuff for a Drupal module, and noticed
> that the geometry storage in Drupal is "bytea" (because it tends to be
> mysql-centric?).
>
> What is the difference, i.e., advantage offered by the PostG
Thanks for the response - I was thinking that may be the case. I suppose I
should ask if PostGIS has anything that would make it behave badly when
called on geometries stored as plain old blob's?
On Fri, Oct 31, 2014 at 12:23 PM, Sandro Santilli wrote:
> On Fri, Oct 31, 2014 at 08:47:59AM -0400
On Fri, Oct 31, 2014 at 10:17:48AM -0400, Guillaume Drolet wrote:
> I created a topology for 2290 polygons and populated a topogeom column
[...]
> I need to fix 1) extra nodes along edges that are not at an
> intersection and 2) sliver polygons.
[...]
> For cases in 2, I can remove some sliver
On Fri, Oct 31, 2014 at 12:26:44PM -0400, Robert Burgholzer wrote:
> Thanks for the response - I was thinking that may be the case. I suppose I
> should ask if PostGIS has anything that would make it behave badly when
> called on geometries stored as plain old blob's?
PostgreSQL would only call P
Dear all,
I'm working with windows 8 & postgis 2.1.
I have several gps (gpx) files. I would like to import directly those gpx
files into my postgis database.
What would be the easiest way?
In advance, thank you to throw light for me.
Regards.
--
View this message in context:
http://pos
Working at the module level in Drupal, creating queries with spatial
operators for Views. Basically, Drupal's GeoField module stores geoms as
"bytea", which the PostGIS functions seem to handle quite nicely without a
cast. Ultimately, I will push to have the database column in GeoField
created as
Hi Sandro,
Thanks for your help!
topology.ValidateTopology gives this:
error id1 id2
character varying integer integer
-- ---
face has no rings 1831
If
On Fri, Oct 31, 2014 at 01:49:59PM -0400, Robert Burgholzer wrote:
> Working at the module level in Drupal, creating queries with spatial
> operators for Views. Basically, Drupal's GeoField module stores geoms as
> "bytea", which the PostGIS functions seem to handle quite nicely without a
> cast.
OK cool. So if I understand correctly, it seems that there may be no
immediate danger to the use of bytea, at the very least it is requiring an
implicit cast which may decrease performance.
Thanks for all the insight on this... will be rolling forward with an eye
towards migrating to "geometry" t
On Fri, Oct 31, 2014 at 12:19:31PM -0700, Guillaume Drolet wrote:
> Hi Sandro,
>
> Thanks for your help!
>
> topology.ValidateTopology gives this:
>
> error id1 id2
> character varying integer integer
> --
So just for accuracy, I was incorrect, sort of. While the functions that I
am currently using "contains, within, ..." will do the CAST implicitly, the
GIST index does not like the bytea type. Which makes the adoption of an
actual geometry column even more urgent.
Thanks again,
/r/b
--
--
Robert
16 matches
Mail list logo