Static map images
Static maps images offer an easy way to embed maps on a webpage.
You simply use an <img /> tag.
Its src attribute forms a request, specifying the location of the map, the size of the image, the zoom level, the type of map, etc.
When the webpage is displayed, the browser requests the image from the Static Maps script and it renders within the image location.
The Static Maps script can be hosted within your webspace or on an osm (dev-)server.
The following services are available and maintained:
OSM's own Export tab is suitable for small-scale non-scripted use.
The following services also exist but may not be recommended due to heavy load on the OSM servers.
- StaticMap 
- ws-compose and ws-pinwin
- (check above list and move items out of it if known not to cause load)
Of course you can also grab a static map image by simply taking a screenshot; instructions for this vary between operating systems.
|Image types||gif, jpeg||jpeg, png||png||png|
|Supported URL Parameters|
|Support of Markers|
|Multiple Markers||Yes||max. 10||Yes||No|
|Custom Markers||No||URL based||3 styles||No|
|Support of Path / Vectors / Polygons / Overlays|
Things To Do
- a more consistent approach (parameters) for interoperatibility
- a good documentation for developers and skilled end-users
- seperation of actual tile rendering and interface/wizzard/tool scripts
- more links throughout this wiki
- list of some external use examples
People who are working on this
Proposal for unified Request Parameters
Besides varying in supported features each implementation has it's own request paramater syntax. If you are planning to use one of those, read the documetation that comes with it.
Below you find a proposal for a more unified approach. Eventually some projects will adapt or implement compatibility modes.
Google Static Maps API
WMS Client getMap Request
The schemes Google Static Maps API and WMS Client getMap Request are for compatibility reasons encouraging people the switch with little adjustments needed.