Hey Jürgen,
>
> There's always an extent, but that not necessarily reflect an actual bbox,
> but
> just sets the available bounds, which are often set much bigger than the
> actual
> data. But the bounding box is determined after insertion of the layer
> anyway.
>
Fair point, but for us it's de
Hi Jonathan,
On Mon, 10. Feb 2014 at 13:43:44 +, Jonathan Moules wrote:
> Thinking about it, the simplest solution is to just trust
> MDSYS.USER_SDO_GEOM_METADATA and get everything from that where possible -
> SRID and BBOX. The geometry-type it doesn't have, but is that strictly
> necessary
Hi Jürgen,
Thinking about it, the simplest solution is to just trust
MDSYS.USER_SDO_GEOM_METADATA and get everything from that where possible -
SRID and BBOX. The geometry-type it doesn't have, but is that strictly
necessary for the list?
This seems like the optimal solution for us; I'd suggest
Hi Jonathan,
On Tue, 04. Feb 2014 at 17:54:10 +, Jonathan Moules wrote:
>The native Oracle provider has been in QGIS for quite a while (a year?)
>and is generally quite good.
>However there are still two fundamental issues that we have with it, both
>as a result of the fact tha
Hi List,
The native Oracle provider has been in QGIS for quite a while (a year?) and
is generally quite good.
However there are still two fundamental issues that we have with it, both
as a result of the fact that Oracle doesn't store accurate spatial metadata:
a) Whenever I "Connect" to the Oracl
