[geos-devel] depth mismatch
strk
strk at keybit.net
Wed Apr 21 10:10:32 EDT 2004
Hello Martin,
I'm trying to figure out why doesn't the buffer operation
work in GEOS CVS. Turning some debugging on I receive
TopologyException: depth mismatch (150,350)
at every bufferFixedPrecision() attempt but the one with 0 precision
digits (the last one) which in turn drops an empty resultGeometry.
Can you tell me if sizeBasedScaleFactor matches max precision digits ?
And more on, what is a depth mismatch exception ?
TIA
--strk;
Here is the complete debugging output:
POINT (150.00 350.00)
Trying with 12 max precision digits
sizeBasedScaleFactor: 1e+10
TopologyException: depth mismatch at (150,350)
Trying with 11 max precision digits
sizeBasedScaleFactor: 1e+09
TopologyException: depth mismatch at (150,350)
Trying with 10 max precision digits
sizeBasedScaleFactor: 1e+08
TopologyException: depth mismatch at (150,350)
Trying with 9 max precision digits
sizeBasedScaleFactor: 1e+07
TopologyException: depth mismatch at (150,350)
Trying with 8 max precision digits
sizeBasedScaleFactor: 1e+06
TopologyException: depth mismatch at (150,350)
Trying with 7 max precision digits
sizeBasedScaleFactor: 100000
TopologyException: depth mismatch at (150,350)
Trying with 6 max precision digits
sizeBasedScaleFactor: 10000
TopologyException: depth mismatch at (150,350)
Trying with 5 max precision digits
sizeBasedScaleFactor: 1000
TopologyException: depth mismatch at (150,350)
Trying with 4 max precision digits
sizeBasedScaleFactor: 100
TopologyException: depth mismatch at (150,350)
Trying with 3 max precision digits
sizeBasedScaleFactor: 10
TopologyException: depth mismatch at (150,350)
Trying with 2 max precision digits
sizeBasedScaleFactor: 1
TopologyException: depth mismatch at (150,350)
Trying with 1 max precision digits
sizeBasedScaleFactor: 0.1
TopologyException: depth mismatch at (150,350)
Trying with 0 max precision digits
sizeBasedScaleFactor: 0.01
resultGeom != NULL
More information about the geos-devel
mailing list