Friday, March 23, 2012
QGIS MS SQL provider has been added
Thanks to the support of Digital Mapping Solutions, Nathan Woodrow and I have now added the new native MS SQL provider in the QGIS mainstream. The new provider now supports full featured read-write access to the MS SQL databases. By using the dragdrop support in the browser window you can easily push layers up to the database. The driver creates fully registered layers (by adding entries to the spatial_ref_sys and geometry_columns metadata tables) which are compatible with the GDAL MSSQL driver as well (to take advantage of the author being the same :-). In the heat of the work we have also enabled the dragdrop upload capability for the PostGIS provider.
We encourage you to give it a try and let us know if you find issues, by adding an entry to the QGIS issue tracker.
Friday, February 17, 2012
www.gisinternals.com is not available
The gisinternals support site providing Windows builds for GDAL and Mapserver will not be available this weekend due to the reconfiguration of the local area network at the server. Hope it will work again on Sunday at 20:00 CET.
Saturday, November 26, 2011
www.gisinternals.com is down
The GDAL and Mapserver daily build package provider site www.gisinternals.com/sdk is currently not available due to server relocation. I hope it will be online again by the end of this weekend.
Tuesday, April 19, 2011
Windows SDK support site has been relocated
Looks like my account on dyndns has been lost :-( Since I'm getting tired to update the account in every month, I've already registered a domain to point to this location which is:
http://www.gisinternals.com/sdk/
If you have any links or bookmarks to point to the support site then update them to refer to this new location. The old URL is considered to be deprecated from now.
http://www.gisinternals.com/sdk/
If you have any links or bookmarks to point to the support site then update them to refer to this new location. The old URL is considered to be deprecated from now.
Thursday, February 3, 2011
GDAL installers for multiple Python versions
After a bit of tweaking in SWIG and Python distutils the installers for GDAL are now available targeting Python 2.6/2.7 and 3.1 (x86 and x64) at http://vbkto.dyndns.org/sdk/
Hmmm... I must mention that quietly, there haven't been made an effort to fix the problem descibed in this post with the recent Python versions. Probably I'm the only one who's trying to compile anything with MSVC2010? I doubt it. Looking forward to the next version...
Hmmm... I must mention that quietly, there haven't been made an effort to fix the problem descibed in this post with the recent Python versions. Probably I'm the only one who's trying to compile anything with MSVC2010? I doubt it. Looking forward to the next version...
Monday, January 24, 2011
Windows binaries for GDAL 1.8.0 and MapServer 5.6.6
As you may already know both GDAL and MapServer had a new stable release in the recent days and I've updated http://vbkto.dyndns.org/sdk/ to provide the Windows binaries according to these versions.
If you prefer using the latest stable releases (GDAL 1.8.0 and MapServer 5.6.6) then choose the 'release' packages, but you may also download the most recent daily builds of the stable branches (always containing all the subsequent changes since the last release) by choosing the 'stable' packages.
The development versions of GDAL and MapServer are also available for testing by using the 'development' packages.
I've also added Windows installers for the GDAL components providing to install the GDAL command line tools and the python bindings easily. Installers for MapServer with IIS registration and PHP support will also be available shortly.
If you prefer using the latest stable releases (GDAL 1.8.0 and MapServer 5.6.6) then choose the 'release' packages, but you may also download the most recent daily builds of the stable branches (always containing all the subsequent changes since the last release) by choosing the 'stable' packages.
The development versions of GDAL and MapServer are also available for testing by using the 'development' packages.
I've also added Windows installers for the GDAL components providing to install the GDAL command line tools and the python bindings easily. Installers for MapServer with IIS registration and PHP support will also be available shortly.
Wednesday, December 22, 2010
Daily built binary packages for MapServer with OpenSSL support
SSL support has been added to the daily built binaries which provides the option to access a secure WMS/WFS server on Windows. Here are the key steps to configure this option in your Mapserver/Mapscript installation:
1. Configure the mapfile with one or more WMS/WFS client layer
This will require to configure a layer with 'CONNECTIONTYPE WMS' or 'CONNECTIONTYPE WFS' and set up your connection information according to the following fragment:
LAYER
CONNECTION "https://www.secureservice.com/service?"
CONNECTIONTYPE WMS
METADATA
"wms_srs" "EPSG:4326"
"wms_name" "NAME"
"wms_format" "image/png"
"wms_server_version" "1.1.1"
"wms_auth_username" "username"
"wms_auth_password" "password"
END
TYPE RASTER
...
END
2. Make sure to install all the required files in your deployment
For the SSL support you require to install libeay32.dll and ssleay32.dll along with libcurl.dll in the run-time configuration. Without having OpenSSL added to the builds you got the following error:
msHTTPExecuteRequests(): HTTP request error. HTTP: request failed with curl error code 1 (Protocol https not supported or disabled in libcurl)
3. Set up the cerificate bundle along with your installation.
In short it will require to set up the CURL_CA_BUNDLE environment variable to point to the location of the .crt file. You can find this file (curl-ca-bundle.crt) in the /bin/curl folder of the binary packages mentioned above. The file contains the most recent version of http://curl.haxx.se/ca/cacert.pem (at the time of the nightly build).
Note: CURL_CA_BUNDLE can be set up system wide (in My Computer->Properties), however you may prefer to apply this environment setting only for the process hosting the mapserver libraries so as not to cause side effects for other applications using libcurl and openSSL. The main issue here is that most of the libararies use getenv to retrieve the environment setting, which operates only on the data structures accessible to the run-time library (msvcrt) and not on the environment "segment" created for the process by the operating system. In this regard the libraries work only on a snapshot of the variables that have been set during the process startup. In this regard you may choose to set up the environment before the process has been started (by using a startup script) or use _putenv to set up the environment variable at run time. I will be trying to discuss this topic in more detail in a subsequent post.
You may check whether your WMS/WFS server is working with the standalone installation of curl.exe in the binary packages and open an SDK command prompt by using SDKShell.bat supported with the packages. In the command prompt you may use a valid url to your service, like:
curl "https://username:password@www.secureservice.com/service?..."
At this point if you get valid data response you may omit the following step.
4. Extract the certificate entry from the server
In the previous step if you get the following error, your remote server probably use a self-signed SSL certificate and the server certificate is not included in your CA bundle file.
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
To get the remote server certificate you may use openssl.exe in the command prompt (also included in the daily buillt packages) according to the folowing example (you may probably use the default SSL port:443 in most cases):
openssl s_client -connect www.secureservice.com:443
Copy all from "-----BEGIN CERTIFICATE-----" tag to "-----END CERTIFICATE-----" tag. Paste it at the end of the curl-ca-bundle.crt file, and repeat #3 to make sure the certificate data is now working.
1. Configure the mapfile with one or more WMS/WFS client layer
This will require to configure a layer with 'CONNECTIONTYPE WMS' or 'CONNECTIONTYPE WFS' and set up your connection information according to the following fragment:
LAYER
CONNECTION "https://www.secureservice.com/service?"
CONNECTIONTYPE WMS
METADATA
"wms_srs" "EPSG:4326"
"wms_name" "NAME"
"wms_format" "image/png"
"wms_server_version" "1.1.1"
"wms_auth_username" "username"
"wms_auth_password" "password"
END
TYPE RASTER
...
END
2. Make sure to install all the required files in your deployment
For the SSL support you require to install libeay32.dll and ssleay32.dll along with libcurl.dll in the run-time configuration. Without having OpenSSL added to the builds you got the following error:
msHTTPExecuteRequests(): HTTP request error. HTTP: request failed with curl error code 1 (Protocol https not supported or disabled in libcurl)
3. Set up the cerificate bundle along with your installation.
In short it will require to set up the CURL_CA_BUNDLE environment variable to point to the location of the .crt file. You can find this file (curl-ca-bundle.crt) in the /bin/curl folder of the binary packages mentioned above. The file contains the most recent version of http://curl.haxx.se/ca/cacert.pem (at the time of the nightly build).
Note: CURL_CA_BUNDLE can be set up system wide (in My Computer->Properties), however you may prefer to apply this environment setting only for the process hosting the mapserver libraries so as not to cause side effects for other applications using libcurl and openSSL. The main issue here is that most of the libararies use getenv to retrieve the environment setting, which operates only on the data structures accessible to the run-time library (msvcrt) and not on the environment "segment" created for the process by the operating system. In this regard the libraries work only on a snapshot of the variables that have been set during the process startup. In this regard you may choose to set up the environment before the process has been started (by using a startup script) or use _putenv to set up the environment variable at run time. I will be trying to discuss this topic in more detail in a subsequent post.
You may check whether your WMS/WFS server is working with the standalone installation of curl.exe in the binary packages and open an SDK command prompt by using SDKShell.bat supported with the packages. In the command prompt you may use a valid url to your service, like:
curl "https://username:password@www.secureservice.com/service?..."
At this point if you get valid data response you may omit the following step.
4. Extract the certificate entry from the server
In the previous step if you get the following error, your remote server probably use a self-signed SSL certificate and the server certificate is not included in your CA bundle file.
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
To get the remote server certificate you may use openssl.exe in the command prompt (also included in the daily buillt packages) according to the folowing example (you may probably use the default SSL port:443 in most cases):
openssl s_client -connect www.secureservice.com:443
Copy all from "-----BEGIN CERTIFICATE-----" tag to "-----END CERTIFICATE-----" tag. Paste it at the end of the curl-ca-bundle.crt file, and repeat #3 to make sure the certificate data is now working.
Subscribe to:
Posts (Atom)
