Thanks for clarifying!
Cheers, Mike
On Sat, Dec 1, 2018, 02:04 Andre Joost wrote:
> Hi Michael,
>
> running eosdump on the file, I get:
>
> File Size: 94926773
> Number of grids: 1
> Number of swaths: 0
> Number of points: 0
> Grid: GLASS02B06
> projection: SNSOID
> griddataclas
Hi
Please find my 6th status report at
https://erouault.blogspot.com/2018/11/srs-barn-raising-6th-report.html
Best regards,
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
htt
Hi Michael,
running eosdump on the file, I get:
File Size: 94926773
Number of grids: 1
Number of swaths: 0
Number of points: 0
Grid: GLASS02B06
projection: SNSOID
griddataclash:
GRID GLASS02B06 {{{
xdim: 7200
ydim: 3600
upleft: -2.00151e+07, 1.00076e+07
lowrig
Hi Bo,
Yes the original commandstring did have that error, however the main error was
that I didn’t have access to the MSSQLSpatial driver because the ODBC driver
wasn’t bundled with the version of GDAL that I installed via conda-forge. When
I installed GDAL via ‘apt-get install gdal-bin’ it di
Hi Pete -
Your first take on the commandstring probably contains an error...
ogr2ogr -f MSSQLSpatial
"MSSQL:server=localhost;database=[database-name];username=sa;password=*
*;trusted_connection=yes*" [path-to-shape-file]
You probably hasn't made the necessary setup with kerberos to use
"inte
Hi Jukka,
Thanks for the note about row by row inserts - this would explain the large
performance difference.
I'd agree it is best to filter out features explicitly. Sometimes -skipfeatures
is just handy for having a quick look at the data though in a different format.
The main issue was the
I've had a bit of time to look at this again and I have got it working, I
didn't rebuild GDAL myself though, just used a build that had ODBC support.
I've listed the steps below in case anyone else finds them useful, they are as
Mateusz suggested so thank you for your help!
Steps to connect to
