[OSM-dev] JOSM plugin public transport update (Google Summer of Code program)

Mateusz Konieczny bulwersator at gmail.com
Wed Mar 12 22:15:43 UTC 2014


I have some questions regarding of "JOSM plugin public transport
update" project. The quotations below come from the Project Idea =>
http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas#Editors

1.
Where can I find description of tagging scheme that the project
should support? I can read: "The JOSM plugin
public transport is out of sync with the public transport scheme from
the wiki.". Can I assume that
http://wiki.openstreetmap.org/w/index.php?title=Public_transport&oldid=945502
is the documentation of the new tagging scheme? Or maybe it is
http://wiki.openstreetmap.org/w/index.php?title=Proposed_features/Public_Transport&oldid=930877
?

2.
"Although bus lines follow most of the time the most direct way, the
mapper has still to collect all these segments by hand. This is a
really tedious job. A routing engine could suggest a route after the
user has clicked starting and ending point. A sufficiently fast
textbook implementation of an A* algorithm is present, it needs to be
configured to the types of roads suitable for buses."

I think that a bit different tool based on this idea would solve far
wider problem. Linear features like highway=*, waterways and railways
often suffer from fragmentation (and probably also other linear
features). It makes many sort of edits overly complicated. Problem is
limited not only to adding bus lines. Any edit that involves editing
longer part of segmented linear feature triggers this problem. For
example I encountered it during adding lit and surface info and it
discouraged me from this type of edits. It is easy to imagine that
the same will happen with many other edits.

Moreover only starting and ending point are not enough to generate
fully correct bus route. It will work only for specific routing of
bus lines that may be rare in some countries (for example in Poland).

Additionally JOSM has significant lag while operating at city-sized
datasets (around 150MB) and changing this would be hard and
complicated enough as separate project.

Maybe it should not be a part of the specific plugin but should be
developed as JOSM improvement and contributed directly as part of
JOSM development (developing it would be a part of the GSoC project).

In order to tag segment of bus route, it would not be necessary to
manually select separate ways. It would be possible to mark two nodes
and use the new function to select multiple ways connecting them (and
possibly also split ways in cases where it is necessary). This would
make possible to add them in one group. Bus route would consist of
one (as in original proposal) or more segments.

Example of separate ways: http://www.openstreetmap.org/way/81942097 +
http://www.openstreetmap.org/way/81942097 +
http://www.openstreetmap.org/way/218427525 + and 18 subsequent ways
Example of two nodes, selecting them and using new tool would be
equivalent of marking 21 ways from previous example: at
http://osm.org/go/0L0Ncg8PB--?m= and at
http://osm.org/go/0L0N2eLaV--?m=

This approach may make coding more complicated but it would solve far
more general problem.

3.
"plugin should no longer break well-tagged existing structures"

Should plugin fully support outdated tagging schemes? Or is it enough
that updated plugin will not break it?

4.
Where can I find bug tracker for this tool?

I found
http://svn.openstreetmap.org/applications/editors/josm/plugins/public_transport/
and its git mirror but I have still to find the bug tracker. This
would be especially useful as project involves "improve stability
such that no more crashes happen" and "plugin should no longer break
well-tagged existing structures". I thought that maybe tickets reside
at JOSM bug tracker but search for keyword like "public", "transport"
and "public_transport" gives no useful tickets.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20140312/5b486d1a/attachment.html>


More information about the dev mailing list