From OpenStreetMap Wiki
Jump to: navigation, search
I don't give a flying monkey's for tag voting, automatic changebots, endless discussions, categories, or any of that crap, but prefer to get on and actually do stuff.
en This user is a native speaker of English.
de-2 Dieser Benutzer hat fortgeschrittene Deutschkenntnisse.
Mastodon user Rorym toots on Mastodon/Fediverse as
OSM Logo This user submits data to OpenStreetMap under the name
JOSM Rorym submits data to OpenStreetMap using JOSM.
iD Rorym submits data to OpenStreetMap using iD.
Android icon Rorym uses an Android phone or tablet.
Flag of Ireland.svg This user hails from Ireland.
Flag of Europe.svg This user hails from Europe
Bike Rorym is a biker

Public-images-osm logo.svg
I support OSM by being a
member of the
OpenStreetMap Foundation
Are you?

Hi I'm Rorym. I'm originally from Dublin, Ireland, but now living in Karlsruhe, Germany, and working in Geofabrik.

What I'm working on


I'm helping to map townlands in Ireland, and have created to show off what we've done and debug it.


I've traveled in Africa and I'm going to trace over some of the cities I've been too. I'm currently working on the Livingstone/Victoria Falls region of Zambia/Zimbabwe, Addis Ababa, Ethiopia and Dar Es Salaam, Tanzania.


My Maps

My GPS device

I use a Garmin Vista HCx when I need a old fashioned GPS device. Usually I use aerial tracing, or using my phone (currently a Sony Xperia Z1 compact).


Converting an OSM file to a GPX file

When I've collected some traces, I convert them to OSM format and clean them up in JOSM. I break them into logical sections. Although GPSBabel can convert OSM to GPX, the resultant format is unsuitable for upload to OpenStreetMap. This XSLT file will convert an OSM file to GPX:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="">
<xsl:template match="/osm">

creator="gpsbabel -"

<xsl:for-each select="node">
    <xsl:sort select="@timestamp" />

        <xsl:attribute name="lat"><xsl:value-of select="@lat" /></xsl:attribute>
        <xsl:attribute name="lon"><xsl:value-of select="@lon" /></xsl:attribute>
        <time><xsl:value-of select="@timestamp" /></time>
        <xsl:if test="./tag[@k='gps:hdop']">
            <hdop><xsl:value-of select="./tag[@k='gps:hdop']/@v" /></hdop>
        <xsl:if test="./tag[@k='gps:vdop']">
            <vdop><xsl:value-of select="./tag[@k='gps:vdop']/@v" /></vdop>
        <xsl:if test="./tag[@k='gps:pdop']">
            <pdop><xsl:value-of select="./tag[@k='gps:pdop']/@v" /></pdop>
        <xsl:if test="./tag[@k='gps:sat']">
            <sat><xsl:value-of select="./tag[@k='gps:sat']/@v" /></sat>
        <xsl:if test="./tag[@k='gps:fix']">
            <fix><xsl:value-of select="./tag[@k='gps:fix']/@v" /></fix>





Copy and paste that into a file called osm2gpx.xslt. You can then apply this template to any osm file and get a gpx file out.


xsltproc osm2gpx.xslt tracks.osm > trackes.gpx

Overpass Queries

Missing waterway relations


Suitable for JOSM "Download from Overpass API":

  // all ways that are tagged river, and have a name
  // minus all the ways that are in a relation
  ( relation["type"="waterway"](bbox) ; > );
// print results
out meta;
out meta;