I've spent a good bit of free time lately working on migrating Weather Now to Azure. Part of this includes rewriting its Gazetteer, or catalog of places that it uses to find weather stations for users. For this version I'm using Entity Framework 5.0, which in turn allows me to use LINQ extensively.
I always try to avoid duplicating code, and I always try to write sufficient unit tests to prevent (and fix) any coding errors I make. (I also use ReSharper and Visual Studio Code Analysis to keep me honest.)
There are two methods in the Gazetteer's PlaceFinder class that search for places by distance. The prototypes are:
public static IEnumerable FindNearby(ILocatable center, Length radius)
public static IEnumerable FindNearby(ILocatable center, Length radius, Expression<Func<Place, bool>> predicate)
But in order for the first method to work, it has to create a predicate of its own to draw a box around the center location. (The ILocatable interface requires Latitude and Longitude. Length is a class in the Inner Drive Extensible Architecture representing a measurable two-dimensional distance.) So in order for the second method to work, it has to chain predicates.
Fortunately, I found Joe and Ben Albahari's library of LINQ extensions. Here's the second method:
public static IEnumerable<PlaceDistance> FindNearby(
Expression<Func<Place, bool>> predicate)
var searchPredicate =
var places = Find(searchPredicate);
return SearchDistanceResults(places, center, radius);
This allows me to use a single Find method that takes a predicate, engages a retry policy, and returns exactly what I'm looking for. And it allows me to do this, which just blows my mind:
var results = PlaceFinder.FindNearby(TestNode, TestRadius, p => p.Feature.Name == "airport");
Compared with the way Weather Now works under the hood right now, and how much coding the existing code took to achieve the same results, I'm just stunned. And it will make migrating Weather Now a lot easier.