Comments on: Google Geocoding in SSIS

By: Mike D

Mike D — Wed, 08 Sep 2010 21:27:00 +0000

Thanks for putting this together. I used this and it worked great. I changed the script so that I am only coding address that return an 8 or higher accuracy code:

Public Shared Function GetCoordinates(ByVal address As String) As Coordinate
Dim client As WebClient = New WebClient()
Dim uri As Uri = GetGeoCodeUri(address)
Dim geoCodeInfo As String()
Try
geoCodeInfo = client.DownloadString(uri).Split(“,”)
If Convert.ToInt16(geoCodeInfo(1)) = 8 Then
Return New Coordinate(Convert.ToDouble(geoCodeInfo(2)), Convert.ToDouble(geoCodeInfo(3)))
Else
Return New Coordinate(0.0, 0.0)
End If
Catch ex As Exception
Return New Coordinate(0.0, 0.0)
End Try
End Function

Also I used an OLEDB Command to update the records instead of the OLEDB Destination because I could only get that to insert.

By: NothingMan

NothingMan — Fri, 29 Jan 2010 22:10:15 +0000

Hmmm, that didn’t happen for me. Something must be converting it to an integer either in the code or in the database. It’s almost impossible to debug script code in SSIS, but you can pull that code out and put it in a standalone .Net console app and see if it’s being rounded in the script code, but you should start by checking the datatypes in the table.

By: CJ

CJ — Mon, 23 Nov 2009 01:38:02 +0000

What did you have to do to ensure the coordinates do not lose precision in the database? When I run this, it works fine with the exception of truncating anything past the decimal.

i.e., 39.0000000 instead of 39.123456, etc…

Thanks!