> Yep. Used,
>
> those files with md5sums of
>
> 60c1d5f7a6a36728b88db947359757ba nsw.dbf
> 4b7c97864fdf18acd2bbe0af0d897f7c nsw.shp
> d41d8cd98f00b204e9800998ecf8427e nsw.shx
>
> and running
>
> shp2pgsql nsw
>
> gives attached results.
>
> Using postgis package 1.5.3-2 (unstable)
Ok, the
On 15/12/12 17:34, Thomas Chung wrote:
> On Sat, Dec 15, 2012 at 4:37 PM, Andrew Harvey
> wrote:
>>
>> Your attached shx file is empty as such,
>>
>
> That empty shx file is part of the setup. It does not segfault if the
> file does not exist. Could you confirm that you tried it with all
> three
On Sat, Dec 15, 2012 at 4:37 PM, Andrew Harvey wrote:
>
> Your attached shx file is empty as such,
>
That empty shx file is part of the setup. It does not segfault if the
file does not exist. Could you confirm that you tried it with all
three files as attached?
I was trying to create a minimal e
Your attached shx file is empty as such,
.shx file is unreadable, or corrupt.
nsw: shape (.shp) or index files (.shx) can not be opened, will just
import attribute data.
which runs fine.
signature.asc
Description: OpenPGP digital signature
___
Pk
Package: postgis
Version: 1.5.1-5
Severity: important
On running shp2pgsql on a particular data set, a segfault occurs.
$ ls
nsw.dbf nsw.shp nsw.shx
$ shp2pgsql nsw
Shapefile type: Polygon
Postgis type: MULTIPOLYGON[2]
SET CLIENT_ENCODING TO UTF8;
SET STANDARD_CONFORMING_STRINGS TO ON;
BEGIN;
5 matches
Mail list logo
