From OpenStreetMap Wiki
Jump to: navigation, search
Langues disponibles — Osmosis/TagTransform
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

Le greffon tag transform Osmosis plugin permet une première transformation arbitraire d'attributs sur de la donnée OSM avant l'utilisation d'autres outils, leur permettant ainsi de se focaliser sur leurs tâches sans avoir à gérer les différences énormes qu'il peut y avoir sur les divers jeux de données ainsi que les corrections d'erreurs.

La transformation s'effectue par une recherche (utilisation d'expressions régulières) sur les clés et les valeurs et permet de définir des valeurs (attributs) de sorties pour les éléments correspondants.


Brett a ajouté ce greffon dans le codebase principal comme partie intégrante dans la branche de l'actuelle version en développement : [1] et c'est maintenant publié dans les versions stables depuis la 0.42.


Le plugin fait maintenant partie du noyau de Osmosis depuis la version 0.42.

Pour les versions de Osmosis antérieures à la 0.42, le greffon est disponible ici.

Les versions anciennes, sous licence GPL, sont disponibles sur le dépôt SVN de OpenStreetMap. Il a maintenant été inclus dans le noyau de Osmosis avec une migration de la licence dans le domaine publique avec le reste du code source de Osmosis.


This plugin is now part of the code Osmosis, thus this is only here for historical reference with older version of Osmosis.

You can put the plugin directly into lib/default. A snippet follows that installs latest osmosis and tagtransform.jar.

# fetch latest osmosis and unpack
wget -O - | tar xz

# get a precompiled tagtransform.jar (tested with 0.40.1)
wget -O $(echo osmosis*)/lib/default/tagtransform.jar

# run osmosis on YOURFILE, doing transformations in TRANSFORM.xml, writing to OUTFILE
./osmosis*/bin/osmosis --read-xml file=YOURFILE --tag-transform file=TRANSFORM.xml --write-xml file=OUTFILE


Building the plugin yourself

Alternatively you may compile/build tagtransform.jar yourself.
You need ant, recent java and osmosis to do this. The following snippet

# fetches and unpacks latest osmosis
wget -O - | tar xz
svn co

cd tagtransform
rm -fr libs
ln -fs ../osmosis-*/lib/ libs

# creates a proper osmosis-plugins.conf so it is found by the PluginLoader of latest osmosis
echo "" > src/osmosis-plugins.conf

ant -f build.xml

# moves tagtransform.jar to osmosis plugin directory
mv build/dist/*.jar ../osmosis-*/lib/default/
cd ..

# runs osmosis on YOURFILE, doing transformations in TRANSFORM.xml, writing to OUTFILE
./osmosis*/bin/osmosis --read-xml file=YOURFILE --tag-transform file=TRANSFORM.xml --write-xml file=OUTFILE


Running a transform

All tasks are for API 0.6, and are available in the core Osmosis since Osmosis 0.42.

--tag-transform (--tt)

Transform the tags in the input stream according to the rules specified in a transform file.

Pipe Description
inPipe.0 Consumes an entity stream.
outPipe.0 Produces an entity stream.

Option Description Valid Values Default Value
file The name of the file containing the transform description. transform.xml
stats The name of a file to output statistics of match hit counts to. N/A

Specifying a transform

Transforms are specified as an XML file containing a series of translations. Each translation is made up of the following parts:

Part Required Description
name Name of the translation -- used in stats output
description Description of the translation for your own sanity and stats output
match Y Specifies the conditions that must be met for the output to be applied
find Specifies extra tags used in output that are not essential to achieve a match
output Specifies the tags to be output when an entity is matched

Translations are executed on each entity, with the output of the first translation used as the input for the second etc.

match and find

There are a couple of different match types. The top level element must be match or find.


The match element groups together other matches. It has two modes:

  • and (default) -- all contained matches must match (checking will stop at the first non-match)
  • or -- only one of the contained matches must match (all are checked regardless)

The entity type to enable matches for can also be specified. Valid values are all (default), node, way, and relation.


This is a special case of match's or-mode and can only be used as a top level tag. The find section can be used to get matches for tags used in the output, but which are not essential.


Matches individual or groups of tags. Tags are selected by regular expressions. These are standard Java regular expressions, and full information can be found at [2].

Attributes are used to specify the regexes:

  • k the key regex to match
  • v the value regex to match
  • match_id the ID to reference in output

The output may reference matches to output tags using the specified ID. Any groups extracted by the regex will be available to the output.


Matches on non-presence of tags. If any tag is matched by the regexes then a parent And matcher will fail.

  • k the key regex to not match
  • v the value regex to not match


The output is specified as a series of operations which are executed in order. Tag keys are considered unique, and so any operation writing to an existing key will overwrite that existing tag.

If no output section is specified then any matching entities will be dropped entirely


Copies all the original tags to the output unchanged.


Copies any tags not matched by match or find expressions.


Copies any tags which were matched by match or find expressions.


Output a specific tag, or multiple tags if referencing a match. The key and values for the new tag(s) are specified using output expressions. Within an output expression {0} will be replaced with the matched regex group of that number. 0 represents the whole match string, and the 1st matched group will be output by {1}.

The attributes used are:

  • from_match -- the match_id to take values from
  • k -- the key to output
  • v -- the value to output

If the referenced match doesn't exist (ie: it was part of find or an "or" mode match and no matching tags were found) then the tag output is omitted (even if groups aren't used in the strings).

If no match is referenced at all then the key and value are treated as simple strings and output verbatim.


Many applications may require considerably less access types than are available (or frequently mistyped):

<?xml version="1.0"?>
    <name>Simplify Access</name>
    <description>Simplifies the access restrictions to yes/no. We could limit for specific keys, but lets live dangerously.</description>
    <match mode="or">
      <tag k=".*" match_id="yes" v="true|designated|public|permissive"/>
      <tag k=".*" match_id="no" v="false|private|privat"/>
      <tag from_match="yes" v="yes"/>
      <tag from_match="no" v="no"/>

(XML surround omitted from now on for clarity)

Convert a crossing tagged using the wiki-voted crossing scheme into the heavily used crossing=toucan used in rendering the cyclemap:

  <description>Convert wiki-voted crossings to toucans, and short-cut the crossing_ref case too</description>
  <match mode="or" type="node">
      <tag k="crossing" v="traffic_signals"/>
      <tag k="bicycle" v="yes"/>
    <tag k="crossing_ref" v="toucan"/>
    <tag k="crossing" v="toucan"/>

There have been many ways of entering cycle routes suggested... we tend to use relations now, but lets regularise the legacy way tagging to ensure ncn=yes is placed on all ways

  <description>Find all the way ncn way variations and tag consistently</description>
    <match mode="or">
      <!-- this matches route=ncn, as well as route=bus;ncn etc. -->
      <tag k="route" v="(.*;|^)ncn(;.*|$)" match_id="route"/>
      <--! sometimes ncn_ref has been specified without ncn=yes -->
      <tag k="ncn_ref" v=".*"/>
    <!-- don't match where ncn was already set to something else -->
    <notag k="ncn" v=".*"/>
    <tag k="ncn" v="yes"/>
    <!-- output the route tag, but without the ncn part -->
    <tag k="route" from_match="route" v="{1}{2}"/>

I might not like the prefixes used by the piste:lift scheme for whatever reason. Lets remove them, but only on things which are definitely piste lifts:

  <name>Arbitrary Piste Remapping</name>
  <description>Remap the piste:lift:* style tags to reduce tag length and remove colons which aren't playing nice with tool X</description>
  <match type="way">
    <tag k="piste:lift" v=".*" match_id="type"/>
    <tag k="piste:lift:(.*)" v=".*" match_id="piste_attr"/>
    <tag from_match="type" k="piste_lift"/>
    <tag from_match="piste_attr" k="{1}" v="{0}"/>

And when you master all of this you get to say "Everybody stand back..."