Category Archives: JOSM

Demise of the humble segment

Its official. As of Sunday 7th Oct 2007 the OpenStreetMap segment is 410 Gone. It had a brief and at times difficult life sandwiched between nodes and overshadowed by ways. But shall we miss it? I think not. For the uninitiated, OSM moved to the new 0.5 server code at the weekend thanks to the hard work done by Frederik, Gabriel, TomH and others. The data model now consists only of the node and way plus the new Relationships (relation), which offers a whole new data creation experience. The majority of the OSM platform tools have been migrated to support the API v0.5, which is not backwards compatible with v0.4 tools. Both potlatch and JOSM work with the changes although for JOSM you will need to download the latest version.

JOSM goes multi data layer

The latest JOSM now supports multiple data layers again. This was requested since about the day after I removed the feature over a year ago ;-).

As another big data source hits the main database (AND’s netherland-parts-of-china-and-india map) the feature got more urgent. I think it is especally cool for people who want to compare two unrelated datasets ;-).

Every file open and every download opens the data into a new, seperate layer now. You can merge these layers using the merge button in the layer dialog. By selecting an layer in the layer dialog, you can switch the current editing dataset as needed.

Now for the bad news:

As the feature is a ground shaking one for the whole JOSM data holding structure, I expect many new bugs introduced :-(. If you run into problems that block you from mapping, please revert to the latest release from last week.

For Plugin writers:

Plugins, that used Main.ds could be affected as well. Main.ds now holds the dataset of the current editing layer rather than all the data together. If you are a plugin writer and your plugin is broken and you cannot fix it to work with josm-latest *and* the josm-1.5 release, please link a version which is working with the latest release at

New Release: JOSM 1.5 “Hits The Road”


after almost 9 months of more or less JOSM-coding, I finally announce a new JOSM release. In shortage of a better name and in spirit of the good old Sam & Max adventure game (which I finished yesterday.. Hurray!), I hereby call this release: “Hit The Road”. :-D

Before I get to the new features, I want to Frederick Ramm, Christof Dallermassl, Francisco R. Santos, Bruce Cowan, Thomas Walraet, Martijn van Oosterhout and all the other guys I forgot who send in patches, bug reports and ideas and who wrote plugins for the community. :-)

Ok, now to the facts:

online-help: F1 (or

Some new features since the last release

  • 0.4 complaint. I bet you already noticed that in the latest beta ;-)
  • Tons of new modes and tools as split / combine ways, reorder nodes in
    a line, reorder segments in a way, (un)select all…
  • Better support for plugins. There are over a dozen plugins
    already available. A basic plugin downloader has been integrated into
    JOSM to ease the plugin installation process. See for more
  • The MarkerLayer displaying annotations from gpx tracks.
  • More visualization options, e.g. drawing the segment ordering number
    or drawing boundary rectangles of all downloaded areas.
  • HCI improvements as one-time warnings, customization support for the
    toolbar on top (including annotation presets), detach the dialogs
    on the right, welcome screen, cuter images…
  • And of course: fixed tons of bugs.

I hope you enjoy the new release and good mapping.

Ciao, Imi.

This week on the OSM mailing lists

Its been another high-traffic week on the OSM mailing lists, so lets get ready for a whistle-stop tour to the world of OSM.

The legal debate continues, but the focus has shifted to an attempt to aggregate information about Case Law, Statute Law and general legal questions onto the Legal FAQ wiki page. The principal behind this is firstly to gather together information that we can present to a friendly (and perhaps charitable) copyright lawyer and secondly to get information about similar cases. There are a couple of papers that are definitely worth looking at, this one, written by Dr Charlotte Waelde from the AHRC Research Centre for Studies in Intellectual Property and Technology Law at the University of Edinburgh and this page from the Science Commons website. If reading a journal paper is just too much like hard work, Richard has summarised the main points of the paper here. If direct action is more your thing, some OSM users have been declaring their contributions Public Domain on this wiki page.

If you are new to OSM, Geo and OpenSource projects, there’s probably a lot of things that confuse you. If you are wondering what the difference is between GPX and GPS, head over to the glossary page of the wiki. If there’s a term you want defining, just add it without a definition and someone will update it before too long. There’s also a new mailing list for newbies – sign up here and start asking all those questions that have been bugging you.

There’s been a load of development going on in the OSM commuinty this week. Tom Higgy has written a script that will calibrate OSM image tiles letting you use them with the opensource Treck Buddy navigation software. Take a look at Tom’s work on his site. Next up, Mathew has been working on a new rendering engine that takes OSM data and produces a postscript file, an interesting new take on the rendering issue. The pragmitic developer says; “Maybe there is a use for it, maybe not. I just like hacking PostScript, so this seemed a sensible merge of two enjoyable things…”.

The “Applet” is the editing tool that you use when you click on the “Edit” tab on the OSM website. Its been around since the very beginning of OSM, the first version was written by Steve, the next by Tom Carden, the way support was put in by Imi and inbetween that a few other people have had a hack at it. The Yahoo imagery has prompted a fair bit of development work on the applet. Nick Burch put in some fixes a few weeks ago, and this week Dan Moore has made quite a few bug fixes, including enhanced panning and zooming functions – all of which are now on the live site.

Keith Sharp’s been bussy too, adding a script to extract polygons from the weekly planet dump – useful if you want to extract a particular area of data, rather than load the entire dataset. You can grab a copy here.

My personal “app of the week” is Franciso Santos’ fantastic new Yahoo! imagery plugin for JOSM. Download the plugin from here, then fire up JOSM and get ready for some productive mapping. The plugin works by caching image tiles via Firefox and then loading the image into JOSM – get more info here.

Putney Bridge as seen using the JOSM Yahoo! plugin

The tagging discussions have continued this week too. One problem that’s been identified is that there is currently no way to distinguish a tube station from another type of railway station. Currently we tag railway stations with:


Robert “Jamie” Munro’s not happy though, “that’s just wrong”, he says, and he has a point. After all a railway station is not part of the railway, and so shouldn’t be tagged with “key: railway”. One suggestion is to allow multiple tags with the same key, something like:


Whilst this is supported by XML, it is not currently supported by the OSM API. You can follow discussions about tagging and the OSM ontology here. There are a load of new proposed features that you can vote on this week too- take a look at this wiki page and have your say.

As the amount of data in the OSM database grows, and as the uses of OSM data become more sophisticated and diverse, the underlying data structure will become increasingly important. The idea of “superways” is not a new one, but David Earl has brought the matter to light this week, largely in response to mailing list discussions about tagging motorway junctions. David’s proposal is firstly to introduce the idea of a “superway” as a higher level structure on top of the existing ways, as well as encouraging the API and editors to enforce the existing “rules” of ways (they are contiguous, ordered, unidirectional, non-branching sets of segments). David sees several advantages of the proposed scheme; a road in a housing estate that has numerous branches for example, can be grouped as one object, likewise a complex road junction which is not a single node or a roundabout could also be represented as one object.

Basically all we’re trying to do is assign tags to groups of ways without having to do it to each way, or have an easy method of selecting multiple ways – John McKerrell

There are several strands to this debate, but primarily there is the need to represent real-world objects in the OSM database and however this is done it will involve some level of abstraction. Aled Morris makes a good point that the ability of a renderer to render a particular data-model should not affect the development of that data model. The problem is, that the output of renderers will inevitably affect the way people tag objects and the way people perceive the OSM data model. Nigel Magnay makes the point that whilst you could feasibly tag your way around many situations, this is an inefficient way of dealing with the underlying problem, and what we should be doing modeling the fundamentals properly. Of course different people have different ideas of what the “fundamentals” are and what “properly” is. The herding of cats springs to mind, but then this is all part of OSM’s open, community based way of doing things.

Thats all for this week. With all the new development thats been going on there’s plenty of new toys for every kind of mapper to play with – so get out there (or fire up JOSM) and have some fun.

JOSM goes Applet


Practically nobody knowed it, but JOSM had a possibility built in to be launched as an applet. This was implemented many month ago. Now I finally got myseld into fixing the last problems (including a bit of server hacking) and made a demonstration setup.

You can either use the standard login or create your own at Note, that this is currently a test server and so your entered data, including your account, is thrown away after some time (unless we decide otherwise). On the good news, feel free to browse around, it will not disturb the main server in any way (hopefully).

I also setup a Testserver API of the upcoming Version 0.4 (the Ruby on Rails thingie Steve is coding on). It runs in development mode, so a) data may be resetted frequently and b) it is not a clever target for doing benchmarks.

Testserver API (0.4):

Try it out! It won’t bite you.

Ciao, Imi.

JOSM Birthday Release

A new release of JOSM is available today, called the “Birthday Release”. The Version number is 1.4, the subversion revision is 166. The main idea of this release is to give plugin writer a more stable environment to build on (please, mark your plugins in some way, if they work with this release).

What changed?

Many new stuff has been included since the century release. Improvements are mostly in the amount of features and the performance.

These are the main new features:

  • A Plugin system has been integrated to sandbox fragile and unstable code and to help other people writing addons.
  • Translations to german, french, romanian and british-english are provided by community members. They are available as plugins.
  • Some highly requested, special operations as “reverse segment”, “download incomplete ways”, “align nodes in a circle” and “select all segments in a straight” have been included.
  • GUI addons like a scaler or the annotation preset feature (to quickly select typical properties)
  • A Wiki-Help system hopefully improve usability for beginners (once the community start to help me filling it up ;) )

Some performance gains since last release:

  • JOSM does not depend on the memory hungry JDOM Parser anymore but features MinML2, a very fast and tiny SAX-Parser.
  • Cleanups in the coordinate storing system result in ~20% less memory consumption.
  • Some time consuming processes have been put into a seperate thread.

Where to get it?

main site:
some mirrors:
complete log:

Ciao, Imi.

Bugtracker for JOSM has moved (again)

The tracker for JOSM bugs in has moved and merged into the one at ..

In the past, two trackers existed and both are now merged to reduce the number of places to look for new bugs ;). Unfortunatly I cannot close the existing bugs at – there is a (temporary?) problem with the server and I am not able to login.

So for future bug reporting, use

Ciao, Imi.