Hi all,
I tracked down my problem with shape-decode to a case of uncaught
parallel lines in the function getIntersection in util.cxx. The
resulting computed intersection point was obviously very distant,
creating the strange coordinates that Curt noticed.
I fixed it by raising the "epsilon" co
Curtis Olson wrote:
>
> A bucket coordinate of -593:2 suggests that this shapefile may contain
> some bogus data. (or there could be a bug leading up to this) but I
> believe the portion prior to the ":" represents a whole degree
> coordinate of the bucket, so this should range from -180 to +179
On Tue, Aug 4, 2009 at 8:11 AM, Maxime Guillaud wrote:
> Hi all,
>
> shape-decode has been crashing on me for a certain shapefile and I can
> not figure out why. I am using terragear-cs downloaded today from the
> GIT repository. The rest of the toolchain runs fine.
>
> shape-decode runs for a wh
Hi all,
shape-decode has been crashing on me for a certain shapefile and I can
not figure out why. I am using terragear-cs downloaded today from the
GIT repository. The rest of the toolchain runs fine.
shape-decode runs for a while and stops with the following error:
[...]
distance = 239.828
0.6
4 matches
Mail list logo
