bcuff / geocodesharp

An async .NET client for the Google geocode API

GeocodeSharp

An async .NET client for the Google geocode API

The object model closely follows the model documented here.

##Example

using System;
using System.Linq;
using System.Threading.Tasks;
using GeocodeSharp.Google;

var address = "21 Henrietta St, Bristol, UK";
var client = new GeocodeClient();
var response = await client.GeocodeAddress(address);
if (response.Status == GeocodeStatus.Ok)
{
    var firstResult = response.Results.First();
    var location = firstResult.Geometry.Location;
    var lat = location.Latitude;
    var lng = location.Longitude;
    // ...
}

geocodesharp's Issues

Remove unused (missed) parameter sensor from GeocodeAddress method

It seems the committer who removed the obsolete sensor functionality forgot the parameter to the GeocodeClient.GeocodAddress method.

Add support for System.Text.Json attributes

When the results are serialized using System.Text.Json, the property names aren't mapped back to the Google property names.

A solution would be to add in a System.Text.Json.Serialization.JsonPropertyNameAttribute for all the properties along side the Newtonsoft.Json.JsonPropertyAttribute.

Would this be something that could be included? If so, I'll get a PR put together.

place_id and types fields are absent in the response

When I poke Geocoding service using Fiddler, I noticed there's a couple of fields missing - namely "place_id" and "types"

Would you mind if I do the PR to add them?

Using a proxy

Given that 2500 req/day is a free limit, I'm thinking about using a proxy for this library. I personally have multiple projects that utilize Geocoding API, and daily volumes will only increase from this point forward.
Unfortunately, proxy usage can vary by server implementation.
Would you be open to a slight refactoring - introducing something like IRequestExecutor with default implementation being current logic, but so we can plug in any other technique (sending requests through nginx, for example)? I would volunteer for this, of course.

Reverse Geocoding

Something more like suggestion.

Because result of reverse geocoding (Address Lookup) is same as geocoding (Latitude/Longitude Lookup) I suggest adding method also for this thing. At first look base difference is change of parameter in URL from "address" to "latlng" and some optional parameters.

request denied if key provided

the key needs to be changed to api_key in geocoderclient.cs

thanks for the code.