v.in.shape error
Joseph Brian Adams, PhD
brian_adams at jbadams.com
Mon Sep 18 11:20:15 EDT 2000
I have updated to the latest v.in.shape source, and I am still getting the
same error. I get the following when I run it ...
"vtd42071" successfully opened
Creating dig_att(L) file "vtd42071"
v.in.shape: shp2dig.c:751: partCalcFieldsPolygon: Assertion `fabs(newx1) < 1.0e10 && fabs(newx2) < 1.0e10' failed.
Aborted (core dumped)
The same thing happens whether I use the defaults or smaller for the snap
distance. Should I be setting the resolution lower? I have it set at :01"
now, but I have tried 0:00:00.01 with no difference.
Brian
On Mon, 11 Sep 2000, David D Gray wrote:
> Brian
>
> I managed to import your files to the required projection.
>
> 1) I used v.in.shape (most recent snapshot - actually with the default
> values reduced further). This was imported to a LL location with the
> following settings:
>
>
> +40.34
> -76.74 -75.85
> +39.70
>
> NSres 0.001
> EWres 0.001
>
> Import parameters snapdist=0.0000001 sliver=0.0001
>
>
> 2) Create a UTM location with the following settings:
>
> 4465523.252
> 350836.065 427811.811
> 4395595.396
>
> NSres 5
> EWres 5
>
> Spheroid airy (you will prob choose something else)
> Zone: 18
>
> calculated from (1) with m.ll2u
>
>
> 3) In UTM projection, imported the map from the LL location with v.proj
>
> 4) Build with scale set to [1:]200
>
> Result:
>
> No unassigned attributes, but quite a lot of unlabelled areas. The map
> sems to have many little slivers, cut corners, generally quite poor
> topology. Ah well, you get this with shape files (not those made by
> GRASS mind you :) but most others from the common sources).
>
> I think the bugs that were causing the problems are those that havebeen
> fixed since Beta8 was released.
>
>
> David
More information about the grass-user
mailing list