<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 6/17/2015 10:41 AM, Daniel Koć wrote:<br>
<blockquote
cite="mid:4f86e804a1ab8f1d79cf95de7c4d8001@xn--ko-wla.pl"
type="cite">
<blockquote type="cite" style="color: #000000;">getmap works with
so called public static image APIs, which are provided by
Mapquest and Google. AFAIR, OSM does <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>not<span class="moz-txt-tag">*</span></b>
provide such an API - at least at last time I checked. But, I've
read that OSM now provides direct routing. If they would also
provide an static image API, ... <span class="moz-smiley-s3"
title=";-)"><span>;-)</span></span>
<br>
</blockquote>
<br>
So what about that "public static image APIs" - do we have it (or
will we some day)?
</blockquote>
<br>
OSM doesn't provide APIs except the editing API*. The routing on
osm.org is from third-party providers using OSM data. I believe
MapQuest Open has a static image API like MapQuest.com, except using
OSM data globally. That would probably be very easy for them to
implement, as it would basically reuse their existing MapQuest code.<br>
<br>
There is the /cgi-bin/export endpoint on the tile servers, but that
is not suited for an application like this.<br>
<br>
* And arguably tile.osm.org<br>
</body>
</html>