> But we are still in the thinking-about-this stage, haven't made any
> decisions, and are looking for suggestions and comments (hence this
> posting).
Let me make a suggestion: instead of producing duplicates and leaving mappers
with the frustrating task of tiding up, you could use JOSM to do
Could it be enhanced to handle stop_code? That would remove any ambiguity
about which stop was which when merging existing mapped stops with ones from
stops.txt.
Thanks John
On 1 July 2010 09:48, Roland Olbricht wrote:
> > But we are still in the thinking-about-this stage, haven't made any
> >
On Thu, Jul 1, 2010 at 2:48 PM, Roland Olbricht wrote:
> capabilities to solve conflicts immediately. I've extended the Public
> Transport Plug-In to offer an experimental GTFS import (for stops only at the
> moment). The aim of this software is to avoid cluttering the database with
Fantastic!
>
Since the JOSM plug_in will become the defacto standard since it will be
used by many people who don't read posts here or understand the issues may I
request that it uses the GTFS tag of stop_name and stop_code rather than the
tag of name.
In one location two stops with the same stop_name actually
I had proposed a spreadsheet editing mode in josm that would make data
driven tasks such as this a lot simpler.
Ticket: https://josm.openstreetmap.de/ticket/5038
UI Wireframe:
https://josm.openstreetmap.de/attachment/ticket/5038/josm%20table%20edit.png
I have still not ironed out the details for
