Skip to main content
Bumped by Community user
replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
Source Link

There are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr ErrorWriting shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version, but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required and therefore it seems that its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfully; however, 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?

There are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version, but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required and therefore it seems that its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfully; however, 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?

There are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version, but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required and therefore it seems that its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfully; however, 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?

thereThere are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version, but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required and therefore it seems that its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfullysuccessfully; however, 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?

there are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required therefore it seems its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfully however 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?

There are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version, but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required and therefore it seems that its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfully; however, 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?

Source Link

ogr2og2 fails with memory allocation error post v2.0 for MSSQLSpatial

there are a few of us encountering "Memory allocation" errors when using ogr2ogr to import spatial (shp/gpx) data into a MSSQLSpatial databse. According to this post: Writing shapefile to SQL Server database with ogr2ogr Error the problem is due to using the latest version of the gdal libraries. The "answer" is to use a previous version but I find this unacceptable for a number of reasons not the least of which is that an OSGeo4W installer will not enable you to install the 1.x version required therefore it seems its no longer possible to install older versions.

Im using gdal 1.11.2 with native SQL 11 driver successfully however 2.1.0 fails with same SQL driver.

Has anybody successfully had this work? What are the parameter/driver changes required to get this to work?