Dear PostGIS users,
I have created set of database functions for managing editing history
of my PostgreSQL tables, including PostGIS geometry tables. Currently
it is in state of 'proof of concept', but usable. I would like to
share it and get some feedback. I was inspired by versioning functions
of
Hi Jan,
box3d is not a geometry, but it is it's very own type (along with box2d). If
you have pgAdminIII, you can browse these types (you may need to enable
visibility of "types" in the options), or if you use psql then the command
"\dT" will show all types.
Since it isn't a geometry, you can dir
On 10/18/2010 5:07 AM, Sebastian E. Ovide wrote:
Is there any reason why not to use gdal ogr2ogr ?
Much of the time I do not need to transform the geometry so I have not
loaded gdal/ogr on the system. The other reason is that I have loads of
scripts that use shp2pgsql because that is all I ne
Hi all,
what is the geometry type to chose when storing BOX3D type geometries?
Of what type does the column need to be? I mean how do I phrase this
correctly?
---
postgisdb=# SELECT AddGeometryColumn('boxes','box3d',31467,'BOX',3);
FEHLER: Invalid type name - valid ones are:
POINT, M
Is there any reason why not to use gdal ogr2ogr ?
On Thu, Oct 14, 2010 at 7:03 PM, Stephen Woodbridge wrote:
> On 10/14/2010 12:02 PM, Mark Cave-Ayland wrote:
>
>> Stephen Woodbridge wrote:
>>
>> Hi all,
>>>
>>> I'm running into a crashing problem with shp2pgsql on 1.5 release on a
>>> CentOS 5
