Skip to content


Subversion checkout URL

You can clone with
Download ZIP
A project to re-implement the standard OpenStreetMap mapnik style, in CartoCSS
CartoCSS Shell Other
Failed to load latest commit information.
scripts Modify the travis check to not create temp files
symbols Merge branch 'beauty-icon' of…
.gitattributes Treat MML files as binary
.gitignore Add localconfig to gitignore
.travis.yml Shorten travis setup Add a guideline on the mapper feedback loop and misspellings. Use single backticks for inline code unless the code itself contains … Update dependencies link
LICENSE.txt Add CC0 license. @mkoniecz -> @matkoniecz
addressing.mss Slightly lighten colour of house names and numbers
admin.mss Remove trailing whitespace from mss files.
aerialways.mss Aerialways.
amenity-points.mss Merge branch 'beauty-icon' of…
buildings.mss more red in buildings hue, darken building outline
citywalls.mss Remove castle_walls as per #1598.
ferry-routes.mss Improve ferry rendering Expand shapefile paths when unzipping
landcover.mss Merge branch 'zoo' Customize .style text for OpenStreetMap Carto
placenames.mss Clean up place name rendering
power.mss Merge pull request #1108 from nebulon42/png-cleanup
preview.png Update preview.png
project.mml Remove castle_walls as per #1598.
project.yaml Remove castle_walls as per #1598.
roads.mss Merge branch 'rail'
shapefiles.mss Make halos transparent (alpha 0.6)
stations.mss Merge pull request #1273 from math1985/halo
style.mss Use the correct name for Tibetan Machine Uni
water-features.mss Merge pull request #1436 from math1985/weir-size
water.mss wetland rendering differentiated by wetland type

OpenStreetMap Carto


These are the CartoCSS map stylesheets for the Standard map layer on

These stylesheets can be used in your own cartography projects, and are designed to be easily customised. They work with TileMill and also with the command-line CartoCSS processor.

Since August 2013 these stylesheets have been used on the OSMF tileservers (, and are updated from each point release. They supersede the previous XML-based stylesheets.


You need a PostGIS database populated with OpenStreetMap data in the standard osm2pgsql database layout, along with auxillary shapefiles. See


Contributions to this project are welcome, see for full details.


This project follows a MAJOR.MINOR.PATCH versioning system. In the context of a cartographic project you can expect the following:

  • PATCH: When a patch version is released, there would be no reason not to upgrade. PATCH versions contain only bugfixes e.g. stylesheets won't compile, features are missing by mistake, etc.
  • MINOR: These are routine releases and happen every 1-3 weeks. They will contain changes to what's shown on the map, how they appear, new features added and old features removed. They may rarely contain changes to assets i.e. shapefiles and fonts but will not contain changes that require software or database upgrades.
  • MAJOR: Any change the requires reloading a database, or upgrading software dependecies will trigger a major version change.


Initial Release (v1.0.0, December 2012)

This was a full re-implementation of the original OSM style, with only a few bugs discovered later. There's been no interest in creating further point releases in the v1.x series.

Current work (v2.x)

The v2.x series focuses on refactoring the style, both to to fix glitches and to leverage new features in CartoCSS / mapnik to simplify the stylesheets with only small changes to the output. It's also appropriate to pull out the 'old-skool' tagging methods that are now rarely used.

Care is being taken to not get too clever with variables and expressions. While these often make it easier to customise, experience has shown that over-cleverness (e.g. interpolated entities) can discourage contributions.

The end goal will be a style that remains familiar but is much more suitable for further development, and/or forking for third-parties to customise.

Future (v3.x)

There are over 300 open requests, some that have been open for years. These need reviewing and dividing into obvious fixes, or additional new features that need some cartographic judgement. The work done already in v1.0 and v2.0 will make it much easier to process these.


There are many open-source stylesheets written for creating OpenStreetMap-based maps using mapnik, many based on this project. Some alternatives are:


Something went wrong with that request. Please try again.