mcp · Global

roadstyle

Road cartography for Python: turn road edges (OSM, osmnx, GeoPandas) into styled, interactive, offline HTML maps (MapLibre) with Street View

Claim this listing

Represent roadstyle? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: road edges (LineString geometry with highway class) rendered as styled maps · OpenStreetMap road network via osmnx · interactive offline HTML map · colour-by-data road maps · map and query dashboard · Google Street View from clicked road
Coverage docs-verified: Any place with OpenStreetMap coverage, or any area covered by the user's own road data
Formats llm-inferred: HTML (offline MapLibre map, output) · PNG (preview, output) · GeoPackage (.gpkg) input · GeoDataFrame input (any CRS) · MCP stdio
Access docs-verified: Open source, MIT licence. No key needed for basic use. Optional CARTO_API_KEY for default base maps and optional Google Maps JavaScript API key for Linked Street View; keyless base maps are available.

Use cases llm-inferred: Draft road-network figures for a FRA or drainage report from OSM edges of a catchment or site · Colour road edges by AADT or speed to support construction traffic routing review · Offline HTML road map deliverable for client or planning submission · Street View check of road access and highway geometry during site visits
Audience llm-inferred: GIS analysts · transport planners · civils engineers · drainage engineers · AI-assisted workflow users via MCP

Constraints llm-inferred: Python 3.10 or later required · Does not supply road data itself; user provides a GeoDataFrame or file, or fetches OSM via osmnx · Street View needs the map served over a web server, not opened from disk · Linked Street View works only on the addresses listed in the Google key restrictions · Google key is written into the page, so browser-side restriction is the only protection · Default CARTO base maps show an API KEY REQUIRED stamp without a key · PNG preview needs Chromium installed once · Docs name MCP tools render_place, render_file and snapshot; metadata tool list (name, oneway, edge_id) matches data columns, not tools · MCP argument names are not documented in the docs · Metadata lists CARTO_API_KEY as auth, but docs say keys are optional · Maintenance activity and release cadence not verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Daily discovery 2026-10-15: GitHub search; verified via GitHub API. Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · daily-2026-10-15 (github-search)