[Gdal-dev] OCI-geometry recognition
Stephan Holl
holl at gdf-hannover.de
Wed Sep 27 05:49:36 EDT 2006
Hello Frank,
On Thu, 21 Sep 2006 10:02:05 -0400 Frank Warmerdam
<warmerdam at pobox.com> wrote:
> Stephan Holl wrote:
> >> This is not uncommon with different kinds of drivers, so if QGIS
> >> can't handle it, I think QGIS should be improved.
> >
> > In what way? That it can deal with wkbUnknown or that it can
> > 'identify' the correct geometry by itself?
>
> Stephan,
>
> Well, I was thinking in terms of working with wkbUnknown in some
> reasonable way - even if it ends up having to scan some features to
> establish a type or ask the user if it really needs a single geometry
> type. Note that there are drivers which return a mix of geometry
> types such as DGN, and potentially OCI.
I have digged into this and found out the following (using QGIS):
When loading a line-layer, I get this wkbtype: 2147483650
Debug: qgsvectorlayer.cpp: 3322: (drawFeature) 2147483650
File: qgsvectorlayer.cpp, Line: 3438: UNKNOWN WKBTYPE ENCOUNTERED
export to Wkt: LINESTRING (599410.286458709975705
4925218.247969940304756 0,599446.169775799964555 4925223.06831809040159
0,599667.214197290013544 4925284.553749489597976
0,599766.326235549990088 4925326.424210700206459 0)
Exporting this as WKT it says it is LINESTRING(x, y, z).
So the mystery-value of 2147483650 seems strange. Is this a bug in OGR?
Same applies to point and geometry layers:
WKB for points: 2147483649
WKB fr lines: 2147483650
WKB for polygons: 2147483651
?!
Thank you and TIA!
Stephan
--
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office - Mengendamm 16d - D-30177 Hannover
Internet: www.gdf-hannover.de - Email: holl at gdf-hannover.de
Phone : ++49-(0)511.39088507 - Fax: ++49-(0)511.39088508
More information about the Gdal-dev
mailing list