francesco1119/osm_to_mssql

Import OSM to MSSQL on SSMS through a SQL query with an HTTP request. BOOM!!!

OSM_to_MSSQL

Import OSM to MSSQL on SSMS and retrieve JSON through T-SQL with an HTTP request. BOOM!!!

The Story

The idea to build a simple way to import Open Street Map to Microsoft SQL Server was born after this post when I tragically realised that there was no current way to import easily and on the fly OSM to MSSQL.

The idea became even more challenging when people start blathering that it was impossible (why?) and that OSM felt better on MySQL or PostgreSQL database.

At that stage it became personal and I started coding.

How to use

1. Open SSMS and enable Ole Automation Procedures running this query:

sp_configure 'show advanced options', 1;  
GO  
RECONFIGURE;  
GO  
sp_configure 'Ole Automation Procedures', 1;  
GO  
RECONFIGURE;  
GO

2. Download the query in attach and paste it into SSMS.
3. Edit DECLARE @place as NVARCHAR(30) = 'Paris' and instead of Paris put Barcelona or Spain or whatever
4. Edit DECLARE @amenity as NVARCHAR(30) = 'cinema' and put whatever you want from the list of the amenities
5. Press F5 and run the query

Troubleshooting:

• If you run into troubles set DECLARE @Debug as Int = 1. Options are 0 = OFF, 1 = ON
• This SQL query is basically a REST call so use your fantasy to create a new one. Here some examples:
  • Overpass API/Overpass API by Example
  • Overpass API/Overpass QL
  • Useful Overpass queries

How it works under the hood

Every time you run the query OSM_to_MSSQL creates a table called 'OSM_' + @amenity + '_' + @place.

Re-running the query will drop the old table and recreate a new one so yes, you can stick this query into a stored procedure and your data can be fresh new every day.

How cool is that?

Let's have an argument

OSM_to_MSSQL is using sp_OACreate and MSXML2.ServerXMLHTTP.6.0 to create the request. Using sp_OACreate is considered bad practice and MSXML2.ServerXMLHTTP.6.0 is deprecated. If you are not OK with that you can use SQLCRL but don't think not even for a second that this will be safer or it will query the API better or faster or it will provide you a place in Heaven.

Future developent

On spare time my TODO list is:

• Brake the @URL into:
  • node(area.a)[amenity=cinema]
  • way(area.a)[amenity=cinema]
  • rel(area.a)[amenity=cinema]
• Eventually create {{bbox}} URL for retrieve data from all over the World ([bbox=-180,-90,180,90])
• Eventually provide development for MSXML6 call