One of the areas where the mapping systems for Windows Phone and Windows 8 are lacking, is the ability to draw *circles*. In particular in Windows Store apps, where you have the ability to use geofences, it would come in pretty handy to be able to draw the outline of a geofence (typically a circle, as this is the only supported type right now) on the map – if only for testing purposes.

To this end I have created a set of extension methods, both for Windows Phone 8 and for Windows Store apps. In the first case, they cannot be used to display the location of a geofence as there *are* no geofences in Windows Phone 8, but well – drawing circles may come in handy anyway.

The results look something like this

These are not circles – they *look* like circles. Basically they are just normal polygons, but their points are drawn in a form to resemble a circle. Would you zoom in very far, you would actually be able to see this. Would you calculate it’s surface area, you would actually find it fraction smaller than a real circle area. But what the heck – it serves the purpose.

I have created a few extension methods to get this done. I will start with Windows Phone code - hey, I am not a Windows *Phone* MVP for nothing, right? ;-) -which starts off with this piece of math:

using System; using System.Collections.Generic; using System.Device.Location; namespace WpWinNl.Utilities { public static class GeoCoordinateExtensions { public static GeoCoordinate GetAtDistanceBearing(this GeoCoordinate point, double distance, double bearing) { const double degreesToRadian = Math.PI / 180.0; const double radianToDegrees = 180.0 / Math.PI; const double earthRadius = 6378137.0; var latA = point.Latitude * degreesToRadian; var lonA = point.Longitude * degreesToRadian; var angularDistance = distance / earthRadius; var trueCourse = bearing * degreesToRadian; var lat = Math.Asin( Math.Sin(latA) * Math.Cos(angularDistance) + Math.Cos(latA) * Math.Sin(angularDistance) * Math.Cos(trueCourse)); var dlon = Math.Atan2( Math.Sin(trueCourse) * Math.Sin(angularDistance) * Math.Cos(latA), Math.Cos(angularDistance) - Math.Sin(latA) * Math.Sin(lat)); var lon = ((lonA + dlon + Math.PI) % (Math.PI * 2)) - Math.PI; var result = new GeoCoordinate(lat * radianToDegrees, lon * radianToDegrees); return result; } } }

This is a method that, given a coordinate, a distance in meters, and a bearing (in degrees) gives you another point. So a entering 50 for distance and 180 for bearing would give you a point 50 meters south of your original point. An impressive piece of math, if I may say so. Which I totally stole from here - as I am into maps, not so much into math. Having this, it’s pretty easy to add a second extension method:

public static IList<GeoCoordinate> GetCirclePoints(this GeoCoordinate center, double radius, int nrOfPoints = 50) { var angle = 360.0 / nrOfPoints; var locations = new List<GeoCoordinate>(); for (var i = 0; i <= nrOfPoints; i++) { locations.Add(center.GetAtDistanceBearing(radius, angle * i)); } return locations; }

It divides the circle of 360 degrees in the number of points you want, and then simply adds points to the shape at the same distance but at every 360/points degrees. The higher the number of points, the more the shape will look like a real circle. Drawing the circle on a Windows Phone map is child’s play now:

void MainPageLoaded(object sender, RoutedEventArgs e) { var location = new GeoCoordinate(52.181427, 5.399780); MyMap.Center = location; MyMap.ZoomLevel = 16; var fill = Colors.Purple; var stroke = Colors.Red; fill.A = 80; stroke.A = 80; var circle = new MapPolygon { StrokeThickness = 2, FillColor = fill, StrokeColor = stroke, StrokeDashed = false, }; foreach( var p in location.GetCirclePoints(150)) { circle.Path.Add(p); } MyMap.MapElements.Add(circle); }

This draws a circle of 150 meters around my house.

For Windows Store, the story is nearly the same. The differences are:

- You will need to install the Bing Maps SDK for Windows 8.1 Store apps
- The Bing Maps SDK does not understand System.Device.Location.GeoCoordinate you will need to make the extension method on Bing.Maps.Location

It’s very unfortunate that the mapping APIs for Windows Phone and Windows Store lack convergence even at the point of something as basic the naming of location types. I hope this will get more attention in the future, as mapping is something that I really care about - in case you had not noticed that from this blog ;-).

However, clever use of C# aliasing brings this convergence a bit closer. I changed the top of this file to

using System; using System.Collections.Generic; #if WINDOWS_PHONE using GeoCoordinate = System.Device.Location.GeoCoordinate; #else using GeoCoordinate=Bing.Maps.Location; #endif

et voilĂˇ, this file compiles under both Windows Phone and Windows Store (provided you have the Map SDK installed). You can forget about PCLs, but sharing code is definitely a possibility now as far as this little method goes.

Drawing a shape in the Windows Store app is now nearly the same:

void MainPageLoaded(object sender, RoutedEventArgs e) { var location = new Location(52.181427, 5.399780); MyMap.Center = location; MyMap.ZoomLevel = 18; var fill = Colors.Purple; fill.A = 80; var circle = new MapPolygon { FillColor = fill, }; foreach (var p in location.GetCirclePoints(150)) { circle.Locations.Add(p); } var layer = new MapShapeLayer(); layer.Shapes.Add(circle); MyMap.ShapeLayers.Add(layer); }

Although attentive readers might notice there is no stroke color defined (as MapPolygon in Windows Store does not feature a separate outer shape border) and adding shapes to a map regrettably also works a bit differently. The API of both mapping systems definitely could benefit from some attention here. But anyway – it get’s the job done now at this point.

Full demo solution is downloadable here. One more time – to be able to compile this you will need to install the Bing Maps SDK for Windows 8.1 Store apps first!

## 5 comments:

This works, and I doubt performance difference will be noticeable unless you calculate lots of circle polygons, but I would refactor out the repeated trigonometry calls with same parameters into local variables so you only calculate these expensive operations only once if you can (maybe even precalculate sin/cos/atan lookup tables, trading some memory for a lot more speed).

Plus, I would use a single radian counter that I would increase in 360°/#steps (in radians) by using addition instead of doing a for loop of number of steps around the 360° "watchface" and doing a multiplication of the loop counter and the step size in loop instance. After all multiplication is just repeated addition, so a lot of work gets done multiple times this way.

But then again, math and that kind of performance tweaking really is *my* thing. ;-)

Great post again, as ever, though. Useful to many people, I'm sure.

" Plus, I would use a single radian counter that I would increase in 360°/#steps (in radians) by using addition" - Can you please explain on this; about how this can be optimized.

Leny (lenypm@gmail.com)

@Leny my friend Jarno has made a severly updated version of this code. Download the zip file from here http://1drv.ms/1wNgTQF - the code is in there

hello

Example esmuy good, and easy to follow.

I'm getting a Windows Phone 8.0 app, and I have a problem with a function that tells me that there is, GetAtDistanceBearing, not if I can lend a hand in this, this method I have to do? or where he got it?

thanks

regards

Jair Ronny Ruiz Andia...

@Ronny It's hard to decipher what your problem is - but GetAtDistanceBearing is not a standard method. It's an extension method I wrote myself.

Post a Comment