RSS Feed icon


Regional Taginfo Instances

2.10.2023 | Frederik Ramm

The regional taginfo server at has been updated with the newest taginfo codebase which means, among other things, that you can get a “chronology” view for many tags telling you how the use of that tag changed over time.

For those of you who have used the service in the past and who were probably used to frequent “internal server errors” forcing a reload, those toothing pains should now be a thing of the past, and we’ve added direct links to the respective regions on – taginfo should have pages for every region supported by the download server. Feel free to report any issues you still encounter.

For quite a while now we’ve been offering a region called “Alps” on our download server and simply assigned it a rectangular bounding box. There have been some legitimate complaints about this box missing some bits in the Southwest (notably the Maritime Alps). We’re therefore changing the boundary polygon, but in order to keep the size manageable, we’re also getting rid of some of the areas that were included until now but are definitely not part of the “Alps” by any definition. Here’s the old (rectangular) and the new (potato-shaped) areas:

Notably the old file contained all of Bern, Zürich, Munich, Linz, Venezia, Zagreb, and Milano; these cities are not in the new “Alps” any more.

We’ll be making the change on September 25 which will lead to a relatively large diff, deleting all the stuff that isn’t in the file any more and adding all that is new. If you somehow rely on the old polygon, you’ll have to stop updating now.

We’ve started making vector tile packages available on our download server at At the moment you’ll find a .tar.gz file with vector tiles typically on the same level where you’d also find shape files — i.e. we don’t give you a package for all of Europe, but for individual European countries, and we don’t have a package for all of the US, but for individual states and so on.

excerpt of a screenshot of, the link to the .tar.gz vectortile package is highlighted

These vector tiles use our Shortbread schema, and we create them with the excellent open source Tilemaker software. For suitable MapLibre vector styles, have a look at the VersaTiles repository.

This is supposed to be an experiment and we don’t yet make any promises about the structure and update frequency of this offer. We’re happy to hear your ideas though. At present, the .tar.gz files simply contain all vector tiles for the region as simple files (which are themselves .gz compressed so you might have to instruct your web server to add the appropriate encoding headers).

Like everything else on our download server, these tiles are made from OpenStreetMap data and come under Open Database License 1.0 with an OpenStreetMap attribution requirement.

This weekend we’ll implement a change that affects the handling of boundary-straddling multipolygons in our OSM extracts. (See this 2017 blog article for some background.)

We’ll stop completing cross-border multipolygons except landuse polygons and a hand-picked list of natural polygons (e.g. water, grassland, wetland).

This has become necessary because of the propensity of OSM mappers to create huge multipolygons like “the Iberian penisula” or “the Alps”, artifacts that not only unnecessarily increase the data volume of any given PBF but also have unexpected consequences – for example, for a while anyone processing the rivers of the Switzerland extract would find a stretch of the River Danube in Vienna, because it happened to be part of the outline of the “Alps” multipolygon.

We hope that by restricting multipolygon completion to landuse and a small list of natural polygons we’ll be able to curb these unexpected side effects of polygon completion.

As a result of this change, the .osc.gz files generated on Friday night will contain “delete” operations for ways and nodes that were heretofore contained in the extracts due to multipolygon completion, but are not any longer.

Some data extracts, notably those for small islands or archipelagos, will shrink by more than 10%, but for most extracts the size will not be affected dramatically.

A few days ago we have added a couple of new road-related layers to our OSM Inspector.

Relations with highway=*

Screenshot of OSM Inspector showing a mountainbike route with highway=cycleway

In the past, highway=* was sometimes added to route relations (type=route + route=road). This is not in line with current tagging standards any more, and can even lead to duplicated line geometries when importing OSM data into PostgreSQL with Osm2pgsql.

The layer shows these old-style relations in dark red.

Not all relations with highway=* are a problem – for example, pedestrian areas and rest areas mapped as multipolygons relations (type=multipolygon) are totally fine and hence not shown as errors. This exception applies to multipolygons with a highway=* value of pedestrian, footway, service, rest_area or services.

Multipolygon relations with other highway=* values are likely candidates for changing to area:highway=*. See the OSM Wiki page aboutarea:highway=* for details about mapping roads as areas.

Out-of-use Roads

Even though OSM records “facts on the ground” and not historic or future data, it is generally accepted to map roads and paths which are not in use any more (or are not completed yet).

In recent years, the so-called Lifecycle Tagging Schema was adopted by many mappers and is used to tag feature which are not actively used any more, are (partially) removed or expected to be created in the future. The schema works by adding the lifecycle state as a colon-separated prefix to main key of the feature. If a road tagged as highway=secondary becomes disused, the tag is changed to disused:highway=secondary. Other tags of the feature remain unchanged.

(An older, but equally valid, way of describing lifecycle states is to put highway=construction together with construction=secondary. The new OSMI layers treat both methods in the same way.)

The following lifecycle sates are in use:

  • razed or dismantled or removed (note that the use of these prefixes is often subject to discussion and may be discouraged in your region)
  • abandoned
  • disused
  • in use (normal state)
  • construction
  • proposed (note that mapping proposed features may contravene the on-the-ground mapping rule and may be discouraged in your region)

OSM Inspector now has four new layers displaying all linear highway=* features which are abandoned, disused, under construction, or proposed.

Screenshot of OSM Inspector showing abandoned and disused paths in Saxon Switzerland National Park

Two new layers render frequent mapping mistakes:

  • Red: If a way has tags of contradicting lifecycle states, it is rendered on the Multiple lifecycle states layer in red. There can be valid reasons for such tagging, for example when a minor road is reconstructed to be a larger road (or a track in the forest is not maintained any more and becomes a narrow path). But in most cases this is an error.
  • Orange: If the old method of lifecycle tagging is used in an incomplete way, e.g. highway=construction without a construction=* tag), this is considered an error. Sometimes the correct tag value can be discovered from the object history; otherwise a survey is required.

Screenshot of OSM Inspector showing a trunk road under construction with an additional proposed=* tag

Use quality assurance tools responsibly

Please use quality assurance tools responsibly. They are often wrong. And even when they point you to poor mapping, simply repairing the mistakes is not a good choice. Poor mapping is often a sign of lack of knowledge (e.g. newbies), bad intentions, or mechanical edits, organised editing or imports gone wrong. It is worth having a look at an object’s history and other edits by the mappers involved to avoid simply “cleaning” the map and therefore possibly hiding a systemic issue. When contacting others about mistakes they have made, always remember that we all make mistakes and we can only become better by supporting each other.