Score difference

[steveoh]

add score difference param to address geocoding api.

{
 "result": {
  "addresses": [
   {
    "id": 1,
    "location": {
     "x": 416300.626283878,
     "y": 4569533.98219385
    },
    "score": 90.87,
    "locator": "Centerlines.StatewideRoads",
    "matchAddress": "766 N DEPOT DR, OGDEN",
    "inputAddress": "766 south Depot Drive, riverdale",
    "addressGrid": "OGDEN",
    "scoreDifference": 0
   },
   {
    "id": 3,
    "location": {
     "x": 430178.9702896076,
     "y": 4506818.444710031
    },
    "score": 90.87,
    "locator": "AddressPoints.AddressGrid",
    "matchAddress": "2236 E ATKIN AVE, SALT LAKE CITY",
    "inputAddress": "2236 atkin ave, slc",
    "standardizedAddress": "2236 atkin avenue",
    "addressGrid": "SALT LAKE CITY",
    "scoreDifference": 21
   }
  ]
 },
 "status": 200
}

closes #34 refs #32

[steveoh]

Does this seem to answer your problem from earlier @JustinBerger?

[JustinBerger]

Absolutely. It gives a simple way to do big batches of records, and still know when there are very similar potential matches. Is it possible for 2 different endpoints to return the same geocode? It makes sense to drop those 'ties' since they are really the same.

[steveoh]

On the example I showed the ties are different addresses with the same score so I wouldn't recommend dropping them. The locators themselves would not return the same address unless it is an apartment but we already handle that. The address points could return similar to a range geocode but the address points are weighted in the case of a tie. I'll release this today so you can give it a spin.