Embedding Ali Maps
One <iframe>. The map draws and routes entirely in the
visitor's browser against static files — there is no API key, no request to
us per view, and nothing to rate-limit.
The snippet
<iframe></iframe>
Parameters
| Name | Meaning |
|---|---|
embed | 1 hides the controls. A framed page is treated as embedded anyway. |
marker | lat,lon, or lat,lon|Title|Description. Repeat it for several. Tapping one opens its description and a Directions link out to Google Maps. |
title, desc | Name the first marker, for the one-pin case. |
lat, lon | Open on a place rather than fitting everything. |
z | How many metres the view is across. Default 600. |
from, to | lat,lon each. Routes on load and fits the result. |
k | How many distinct roads a snap may try. Default 1. |
Embedding a route
An embed can carry the journey, so a page can link to the route it is writing about rather than to a map somebody has to drive themselves.
<iframe src="https://maps.ali-web-services.com/?from=24.8869,46.6255&to=24.8935,46.6335"
width="100%" height="420" style="border:0" loading="lazy"></iframe>
What an embed cannot choose
An embedded Ali Maps is always the detected corpus and always the newest published map. There is no layer switch: no satellite imagery (our imagery licence is internal review only), no OpenStreetMap demo, and no pinning to an older release. Asking for one in the URL is refused in the page rather than ignored — a map on somebody else's site that quietly shows imported data, or that goes stale with nobody to notice, is the confusion this is here to avoid.
Status
In development. The corpus is sparse on purpose: it holds only road we have detected, with no network imported from anywhere at any stage. Routes that fail are reported as failures rather than quietly redrawn, and road we can draw but cannot route on is shown in pink.