Geocoding.net

Appearance

Geocoding.netProvider-agnostic geocoding for .NET

One interface for forward geocoding, reverse geocoding, and migration-aware provider support across modern and compatibility services.

Get Started
Compare Providers

Unified API

Build against shared abstractions in Geocoding.Core while swapping concrete provider implementations per environment.

Provider Playbooks

Each provider guide covers package selection, account setup, credential provisioning, operational caveats, and migration notes.

Async Native

Public APIs are async-first and designed for modern .NET applications, services, and background workers.

Provider Isolation

Each provider keeps its own request models, exception types, and address extensions without leaking into shared abstractions.

Compatibility Aware

Bing Maps and Yahoo remain documented as migration and compatibility surfaces without being presented as the default choice for new integrations.

Sample App

The sample web app demonstrates how to wire providers into a minimal ASP.NET Core application.

Quick Example ​

csharp
using System.Collections.Generic;
using System.Linq;
using System.Threading;
using Geocoding;
using Geocoding.Google;

CancellationToken cancellationToken = default;
IGeocoder geocoder = new GoogleGeocoder("your-google-api-key");
IEnumerable<Address> addresses = await geocoder.GeocodeAsync(
    "1600 Pennsylvania Ave NW Washington DC 20500",
    cancellationToken);

Address first = addresses.First();
Console.WriteLine(first.FormattedAddress);
Console.WriteLine($"{first.Coordinates.Latitude}, {first.Coordinates.Longitude}");

Provider Snapshot ​

ProviderStatusBest ForGuide
Google MapsSupportedBroad global coverage and provider-specific address metadataGoogle Maps
Azure MapsSupportedNew Microsoft-backed integrationsAzure Maps
HERESupportedHERE Geocoding and Search API consumersHERE provider guide
MapQuestSupportedCommercial MapQuest integrationsMapQuest
Bing MapsCompatibility onlyExisting enterprise deployments migrating off BingBing Maps Compatibility
YahooCompatibility onlyLegacy code paths you still need to retire safelyYahoo Compatibility

Integration Checklist ​

  1. Start with Getting Started to choose packages and verify the basic calling pattern.
  2. Use Provider Support to pick the provider that matches your operational constraints.
  3. Follow the provider-specific setup guide to create credentials and wire the right geocoder implementation.
  4. Run the Sample App when you want a minimal end-to-end verification harness.

Learn More ​

Provider-agnostic geocoding for .NET.