OSM API changes caused by license change

[Don-vip]

Frederik has written a wiki page concerning OSM API changes that will occur during license change process:

​http://wiki.openstreetmap.org/wiki/Open_Database_License/Changes_in_the_API

These changes will impact JOSM at least in history handling and osmChange parsing.

[bastiK]

Does JOSM's history dialog work when versions are missing?

[skyper]

What about undelete and reverter plugins ?

[Don-vip]

Another page to read:
​http://www.osmfoundation.org/wiki/License/Rebuild_Plan

[bastiK]

Replying to bastiK:

Does JOSM's history dialog work when versions are missing?

I've tested this and is seems to work.

(The following node.js script can be used as API dummy. You need a file 'capabilities' and 'hist.osm' in current folder. It serves capabilities for ​http://127.0.0.1:8125/capabilities and hist.osm for all other requests.

var http = require('http');
var fs = require('fs');

http.createServer(function (request, response) {

    console.log("request:", request.url);

    var file = request.url == '/capabilities' ? './capabilities' : './hist.osm';
    fs.readFile(file, function(error, content) {
        if (error) {
            response.writeHead(500);
            response.end();
        }
        else {
            response.writeHead(200, { 'Content-Type': 'text/html' });
            response.end(content, 'utf-8');
        }
    });

}).listen(8125);

console.log('Server running at http://127.0.0.1:8125/');

)

[bastiK]

Replying to skyper:

What about undelete and reverter plugins ?

Should work unless your revert involves any hidden versions. In this case it must fail anyway.

[Don-vip]

In 5332/josm:

see #7505, see #7847 - Handle deleted nodes without coordinates in dataset consistency test due to recent API change

[Don-vip]

OK, this looks good :) (​http://www.openstreetmap.org/browse/node/311786538/history)

[Don-vip]

In 5333/josm:

see #7505, see #7847 - Nodes without coordinates in dataset consistency test: use of isVisible() rather than !isDeleted() to raise the issue if null coordinates are found with a node not yet deleted on server

[Don-vip]

In 5334/josm:

see #7505, see #7847 - Handle deleted nodes without coordinates in GeoJSON export (fix NPE)

[Don-vip]

There's some work to do when working with .osm files containing primitives that have been redacted meanwhile. Taking again the previous node example, I have saved two different copies of it (one for revision 1, and another one for a complete fake revision 2.
When loading this revsion 2, it goes bad:

The versions are not correctly sorted.

Worst, if we click on this revision in column A, this exception happens:

java.lang.IllegalArgumentException: Failed to set reference. Reference version 2 not available in history.
	at org.openstreetmap.josm.gui.history.HistoryBrowserModel.setReferencePointInTime(HistoryBrowserModel.java:305)
	at org.openstreetmap.josm.gui.history.HistoryBrowserModel$VersionTableModel.setReferencePointInTime(HistoryBrowserModel.java:476)
	at org.openstreetmap.josm.gui.history.HistoryBrowserModel$VersionTableModel.setValueAt(HistoryBrowserModel.java:456)
	at javax.swing.JTable.setValueAt(Unknown Source)
	at javax.swing.JTable.editingStopped(Unknown Source)
	at javax.swing.AbstractCellEditor.fireEditingStopped(Unknown Source)
	at org.openstreetmap.josm.gui.history.VersionTable$RadioButtonEditor.itemStateChanged(VersionTable.java:194)

[Don-vip]

In 5339/josm:

see #7505 - Add toString() method on History objects to ease debugging

[Don-vip]

In 5340/josm:

see #7505 - Hide redacted version in history browser when loading an .osm file containg primitives that have been redacted meanwhile

[anonymous]

Ticket #7867 has been marked as a duplicate of this ticket.

[Don-vip]

In 5346/josm:

fix #7867, see #7505, see #7847 - Handle deleted nodes without coordinates in history

[Don-vip]

Should be OK as well. Reopen the ticket if I missed something.