Feature description
Instead of orginfo -al sometimes revealing the Geometry Column, and
sometimes not, how about it always give an answer no matter what?
We see that orginfo will sometimes even be so helpful as to reveal
Geometry Column = _ogr_geometry_
And if there really really is no Geometry Column, then have it say
instead of the current behavior, where one needs to dig through tons of
documentation to see if there is really no hope in figuring out what the Geometry Column is.
Yes, different answers could be provided according to -dialect, even
with no -sql.
Here we see ogrinfo is quite verbose about things like that. Why not also here?
Another problem is the user apparently needs to use -sql SELECT ... to coax out the name of the Geometry Column. But users usually want to find out column names first before writing random SELECT statements. https://gis.stackexchange.com/a/500471/77230
Feature description
Instead of
orginfo -alsometimes revealing theGeometry Column, andsometimes not, how about it always give an answer no matter what?
We see that
orginfowill sometimes even be so helpful as to revealAnd if there really really is no Geometry Column, then have it say
instead of the current behavior, where one needs to dig through tons of
documentation to see if there is really no hope in figuring out what the Geometry Column is.
Yes, different answers could be provided according to
-dialect, evenwith no
-sql.Here we see ogrinfo is quite verbose about things like that. Why not also here?
Another problem is the user apparently needs to use
-sql SELECT ...to coax out the name of theGeometry Column. But users usually want to find out column names first before writing random SELECT statements. https://gis.stackexchange.com/a/500471/77230