Skip to main content

Use PowerShell to get coordinates from BING.

By
As I am continuing to build my module to support Bing using PowerShell, I needed a way to send Bing a location and get its coordinates back.  I had to do some research and I found Kevin Pelgrim’s code to do just that.  I also wanted the geographic rectangle of the selected address so I did some re-coding and also changed the code to match my programming style.  Here is the end result. Check out the help file for details.  You may notice some word wrapping going on.  Especially in the items in purple.  You may need to remove carriage returns if you copy and paste this code from those lines.  The items in green are the start of those lines.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
1
Function Get-BINGCoordinates
{
       [CmdletBinding()]
       Param (
              [String]$Location,
              [String]$Key = "Enter Your key Here"
       )
      
    # Custom Object
       Function Get-BingCoordinates-Object
       {
              $Obj = New-Object -TypeName PSObject -Property @{
                     "Address" = $Null
                     "Latitude" = $Null
                     "Longitude" = $Null
                     "NELatitude" = $Null
                     "NELongitude" = $Null
                     "SWLatitude" = $Null
                     "SWLongitude" = $Null
                     "Found" = $False
              }
              $Obj.PSObject.TypeNames.Insert(0, 'BingMaps.Coordinates')
              Write-Output $Obj
       } # END: Function Get-BingCoordinates-Object
      
       # Code borrowed from Kevin Pelgrims.
    # https://kevinpelgrims.wordpress.com/2011/08/18/bing-maps-geocoding-in-powershell/
       $ws = New-WebServiceProxy -uri http://dev.virtualearth.net/webservices/v1/geocodeservice/geocodeservice.svc?wsdl
       $wsgr = New-Object Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1ervice_geocodeservice_svc_wsdl.GeocodeRequest
       $wsc = New-Object Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1ervice_geocodeservice_svc_wsdl.Credentials;
       $wsc.ApplicationId = $key;
       $wsgr.Credentials = $wsc;
       $wsgr.Query = $Location;
       $wsr = $ws.Geocode($wsgr);
      
       # Populate the output object.
       $Obj = Get-BingCoordinates-Object
       $Result = $wsr.Results[0] # Used to shorten the property addresses below.
       $Loc = $Result.Locations[0] # Used to shorten the property addresses below.
       $BV = $Result.BestView[0] # Used to shorten the property addresses below.
       $Obj.Address = $wsr.Results[0].Address.FormattedAddress
       $Obj.Latitude = $Loc.Latitude
       $Obj.Longitude = $Loc.Longitude
       $Obj.NELatitude = $BV.NorthEast.Latitude
       $Obj.NELongitude = $BV.NorthEast.Longitude
       $Obj.SWLatitude = $BV.SouthWest.Latitude
       $Obj.SWLongitude = $BV.SouthWest.Longitude
      
       # If an exact match is found, then flag FOUND as $True.
       If ($Obj.Address -eq $Location)
       {
              $Obj.Found = $True  
       }
       Write-Output $Obj
<#
.SYNOPSIS
Returns coordinate information from BING.
 
.DESCRIPTION
Returns coordinate information from BING. This includes the geographic
rectangle for the specified item.
 
.PARAMETER Location
An address or location to get the coordinates for.
 
.PARAMETER Key
Your BING map key
 
.EXAMPLE
Get-BINGCoordinates -Location "Indianapolis, IN"
      
Returns the coordinate information for Indianapolis, IN
 
.EXAMPLE
Get-BINGCoordinates -Location "Grand Canyon National Park"
Address     : Grand Canyon National Park, AZ
Latitude    : 36.2985153198242
NELongitude : -111.613616943359
NELatitude  : 36.8462715148926
SWLongitude : -113.970611572266
Found       : False
SWLatitude  : 35.7507591247559
Longitude   : -112.792114257813
 
.NOTES
Thank you to Kevin Pelgrims for his post on accessing BING.
https://kevinpelgrims.wordpress.com/2011/08/18/bing-maps-geocoding-in-powershell/
===============================================================================
== Cmdlet: Get-BINGCoordinates                                               ==
== Author: Jason A. Yoder                                                    ==
== Company: MCTExpert of Arizona                                             ==
== Date: 2015JUN02                                                           ==
== Copyright: All rights reserved.                                           ==
== Version: 1.0.0.0                                                          ==
== Legal: The user assumes all responsibility and liability for the usage of ==
== this PowerShell code.  MCTExpert of Arizona, Its officers, shareholders,  ==
== owners, and their relatives are not liable for any damages.  As with all  ==
== code, review it and understand it prior to usage.  It is recommended that ==
== this code be fully tested and validated in a test environment prior to    ==
== usage in a production environment.                                        ==
==                                                                           ==
== Does this code make changes: NO                                           ==
===============================================================================
#>
      
} # END: Get-BINGCoordinates
 
Get-BINGCoordinates -Location "Grand Canyon National Park"
 
Labels:

Comments

Unknown said…
Very nice coding - well done and it looks great. Very useful when wanting to use other services like auto mapping!
June 5, 2015 at 8:49 AM
Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more