Mitc.Integrations.CensusGeocoder

A lightweight client over the US Census Bureau geocoder's Find Locations service. Supply one or more addresses, get back coordinates.

Scope

• Find Locations — address in, coordinates (longitude/latitude) out.
• Distance & route planning — great-circle distance between coordinates, and a brute-force shortest-route optimizer for small stop sets.
• Not covered: Find Geographies (census tract/block lookups), reverse geocoding, and LUCA services.

Usage

services.AddCensusGeocoder();

// Single address
Result<GeocodeMatch> result = await geocoder.GeocodeAsync(
    CensusAddress.OneLine("4600 Silver Hill Rd, Washington, DC 20233"));

// Batch — keyed by your own id (int, long, string, or Guid)
var addresses = new Dictionary<int, CensusAddress>
{
    [1] = CensusAddress.Parsed("4600 Silver Hill Rd", "Washington", "DC", "20233"),
};
IReadOnlyDictionary<int, Result<GeocodeMatch>> results = await geocoder.GeocodeBatchAsync(addresses);

Distance & route planning

All coordinate math is pure and synchronous — no API calls, no DI.

// Great-circle distance between two coordinates
Distance d = a.Coordinates.DistanceTo(b.Coordinates);
double miles = d.Miles;

// Shortest order to visit stops from a distribution center (origin).
// Stops are keyed by your own id; the plan returns those ids in visiting order.
// Capped at RoutePlanner.MaxStops (10) — the search is factorial in the stop count.
var stops = new Dictionary<int, Coordinates>
{
    [1] = stop1.Coordinates,
    [2] = stop2.Coordinates,
};
RoutePlan<int> plan = RoutePlanner.FindShortestRoute(origin, stops, returnToOrigin: true);
// plan.Order          -> ids in optimal visiting sequence
// plan.TotalDistance  -> Distance for the whole route

Result statuses

The Census three-way outcome is mapped onto Mitc.Support.Results.ResultStatus: