RE: [GRASS5] [bug #4190] (grass) Could not import a NB Double Ste reographic shapefile - used EPSG #2036

Here's the output from ogrinfo on my shapefile:

ogrinfo 45256600_h_r.shp
INFO: Open of `45256600_h_r.shp'
using driver `ESRI Shapefile' successful.
1: 45256600_h_r (Polygon)

Hm, no projection info, coordinate system, nothing. But the prj is in the
same directory as the shapefile.

Maybe the problem lies in the shapefile and associated files (?)

~ Eric.

-----Original Message-----
From: grass5-admin@grass.itc.it
To: Request Tracker
Cc: grass5@grass.itc.it
Sent: 3/20/2006 8:29 PM
Subject: Re: [GRASS5] [bug #4190] (grass) Could not import a NB Double
Stereographic shapefile - used EPSG #2036

this bug's URL: http://intevation.de/rt/webrt?serial_num=4190
---------------------------------------------------------------------

Subject: Could not import a NB Double Stereographic shapefile - used
EPSG #2036

Platform: GNU/Linux/x86
grass obtained from: Trento Italy site
grass binary for platform: Downloaded precompiled Binaries
GRASS Version: Grass 6.1cvs 18-03-2006

I downloaded this shapefile:

https://www.web11.snb.ca/topo/aadb/shape/nbaa_5000_ranb.zip

The shapefile is in New Brunswick Double Stereographic, NAD83 CSRS98
(Canadian Spatial Reference System 1998)

This shapefile comes from a municipal government site, so is highly
likely that the shapefile is in the projection is says it is. Or at
least it's not suspect at this point.

Reading the .prj file shows that the projection is indeed New
Brunswick Double Stereographic. I created a new Location using EPSG
code #2036, which seemed to match the shapefile's projection
parameter-for-parameter. Imported shapefile into Location using:

v.in.ogr dsn=shapefile_directory output=nbaa_5000_ranb
layer=nbaa_5000_ranb

and received a seg fault, with no other error information. Importing
the shapefile using the 'location' parameter in v.in.ogr also gives a
seg fault, with no feedback.

what happens if you try looking at it with 'ogrinfo' ?

also, maybe quicker for you, the above can just be:
v.in.ogr dsn=directory/file.shp out=map # and no layer=

Hamish

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Eric,

this also confused me - but it's the usage of ogrinfo
(I didnÃ't manage to convince Frank to change that, see our
recent GDAL-ML communication):

Try instead:

ogrinfo -so 45256600_h_r.shp 45256600_h_r

then you'll see the proj info.

Markus

On Tue, Mar 21, 2006 at 07:28:13AM -0400, Patton, Eric wrote:

Here's the output from ogrinfo on my shapefile:

ogrinfo 45256600_h_r.shp
INFO: Open of `45256600_h_r.shp'
using driver `ESRI Shapefile' successful.
1: 45256600_h_r (Polygon)

Hm, no projection info, coordinate system, nothing. But the prj is in the
same directory as the shapefile.

Maybe the problem lies in the shapefile and associated files (?)

~ Eric.

-----Original Message-----
From: grass5-admin@grass.itc.it
To: Request Tracker
Cc: grass5@grass.itc.it
Sent: 3/20/2006 8:29 PM
Subject: Re: [GRASS5] [bug #4190] (grass) Could not import a NB Double
Stereographic shapefile - used EPSG #2036

> this bug's URL: http://intevation.de/rt/webrt?serial_num=4190
> ---------------------------------------------------------------------
>
> Subject: Could not import a NB Double Stereographic shapefile - used
> EPSG #2036
>
> Platform: GNU/Linux/x86
> grass obtained from: Trento Italy site
> grass binary for platform: Downloaded precompiled Binaries
> GRASS Version: Grass 6.1cvs 18-03-2006
>
> I downloaded this shapefile:
>
> https://www.web11.snb.ca/topo/aadb/shape/nbaa_5000_ranb.zip
>
> The shapefile is in New Brunswick Double Stereographic, NAD83 CSRS98
> (Canadian Spatial Reference System 1998)
>
> This shapefile comes from a municipal government site, so is highly
> likely that the shapefile is in the projection is says it is. Or at
> least it's not suspect at this point.
>
> Reading the .prj file shows that the projection is indeed New
> Brunswick Double Stereographic. I created a new Location using EPSG
> code #2036, which seemed to match the shapefile's projection
> parameter-for-parameter. Imported shapefile into Location using:
>
> v.in.ogr dsn=shapefile_directory output=nbaa_5000_ranb
> layer=nbaa_5000_ranb
>
> and received a seg fault, with no other error information. Importing
> the shapefile using the 'location' parameter in v.in.ogr also gives a
> seg fault, with no feedback.

what happens if you try looking at it with 'ogrinfo' ?

also, maybe quicker for you, the above can just be:
v.in.ogr dsn=directory/file.shp out=map # and no layer=

Hamish

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy