bng2latlong

Name: bng2latlong API
Brand: bng2latlong
Availability: InStock

✓ Official Vendor SpecMaps GeolocationGeocodingnone1 EndpointsREST

For Agents

Convert British National Grid (OSGB36) easting/northing coordinates to WGS84 latitude and longitude with a single unauthenticated GET request.

Quickstart

Get started with bng2latlong in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"convert british national grid easting northing to latitude longitude"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with bng2latlong API.

Convert OSGB36 easting and northing values to WGS84 latitude and longitude

Return the converted coordinates with the original easting and northing echoed for traceability

Operate without API keys, OAuth, or any credential setup

Handle UK-specific coordinate transforms used by Ordnance Survey datasets

GET STARTED

Start building with bng2latlong API

Explore with Jentic

View OpenAPI Document

Use for: I need to convert a British National Grid coordinate to latitude and longitude, Convert OSGB36 easting 651409 northing 313177 to WGS84, Get the WGS84 coordinates for a UK property reference, Translate Ordnance Survey grid references for a web map

Not supported: Does not handle address geocoding, routing, or reverse WGS84-to-OSGB conversion — use for OSGB36 easting/northing to WGS84 latitude/longitude conversion only.

The bng2latlong API converts an OSGB36 easting and northing coordinate pair from the British National Grid into a WGS84 latitude and longitude. The single GET endpoint accepts the easting and northing as path parameters and returns the converted coordinates plus the original input echoed back. It is unauthenticated and aimed at UK GIS, surveying, and property workflows that need to bridge British National Grid data into modern web map layers.

Use Cases

Patterns agents use bng2latlong API for, with concrete tasks.

★ Plot UK Ordnance Survey Data on Web Maps

Many UK datasets — land registry, planning, environmental surveys — use British National Grid (OSGB36) easting and northing coordinates that web maps like Google Maps, Mapbox, and Leaflet do not understand. The bng2latlong API converts each grid reference into WGS84 latitude and longitude in a single GET call so points can be plotted on a standard tile layer without bundling a coordinate-transform library.

Call GET /bng2latlong/651409/313177 and return the WGS84 latitude and longitude in the response body.

Property and Surveying Lookups

Surveyors, conveyancers, and PropTech tools regularly receive coordinates in OSGB36 format from Ordnance Survey or Land Registry exports and need to display them on a consumer-facing map. The bng2latlong API removes the need for proj4 or custom transform code — a single GET request returns the converted coordinates with the input echoed for audit purposes.

Convert easting 530000 northing 180000 and verify the result falls within Greater London (latitude ~51.5, longitude ~-0.1).

AI Agent Geographic Reasoning

When an agent receives a UK address dataset that uses British National Grid references, it can call bng2latlong to normalise every record to WGS84 before reasoning over distances or rendering on a map. Through Jentic the operation is discoverable by the natural-language intent 'convert OSGB to lat lon' and returns a typed response, so the agent does not need to read the docs first.

For each row in the dataset, convert its easting/northing to WGS84 and append the latitude and longitude to the row.

Key Endpoints

1 endpoints — the bng2latlong api converts an osgb36 easting and northing coordinate pair from the british national grid into a wgs84 latitude and longitude.

METHOD

PATH

DESCRIPTION

GET

/bng2latlong/{easting}/{northing}

Convert OSGB36 easting/northing to WGS84 latitude/longitude

GET

/bng2latlong/{easting}/{northing}

Convert OSGB36 easting/northing to WGS84 latitude/longitude

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

bng2latlong needs no credentials, so Jentic invokes the endpoint directly. There is nothing to store or rotate, which is rare in the catalogue.

Intent-based discovery

Agents search by intent (e.g. 'convert OSGB to WGS84') and Jentic returns the GET /bng2latlong/{easting}/{northing} operation with its parameter schema for direct execution.

Time to first call

Direct integration: under 30 minutes (read docs, write GET request). Through Jentic: under 5 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

OpenStreetMap

OpenStreetMap consumes WGS84 coordinates returned by bng2latlong for tile-based rendering

Use OpenStreetMap as the rendering layer for the latitude/longitude output of bng2latlong

Alternative

Positionstack

Positionstack offers global forward and reverse geocoding for postal addresses; bng2latlong is UK-grid specific

Use Positionstack when the input is a postal address worldwide; use bng2latlong only when the input is an OSGB36 grid reference

FAQs

Specific to using bng2latlong API through Jentic.

What authentication does bng2latlong use?

bng2latlong is unauthenticated — no API key, OAuth token, or credential is required. Through Jentic it is callable directly with no vault setup, which is unusual; most APIs in the catalogue require Jentic's encrypted credential handling.

Can I convert a single OSGB36 coordinate with bng2latlong?

Yes. GET /bng2latlong/{easting}/{northing} accepts the easting and northing as path parameters and returns the WGS84 latitude and longitude alongside the original input echoed back. There is no batch endpoint — for a list of points, call the endpoint once per coordinate.

What are the rate limits for bng2latlong?

The spec does not declare explicit rate limits. The service is community-run, so production workloads should throttle requests sensibly and cache results for repeated grid references.

How do I convert a British National Grid coordinate through Jentic?

Search Jentic for 'convert OSGB easting northing to lat long'. Jentic returns the GET /bng2latlong/{easting}/{northing} operation with its schema; load it, pass the easting and northing, and execute to get back WGS84 coordinates.

Does bng2latlong support reverse conversion from WGS84 back to OSGB36?

No. The single available endpoint converts from OSGB36 easting/northing to WGS84 only. For the reverse direction use a complementary tool such as the Ordnance Survey OS Maps API or a local proj4 transform.