On 12/1/2013 5:32 PM, Jo wrote:
Hmm, I was thinking of staying more or less within the lines of what we
have now, but take away the burden of 10, 20, 70 relations on the same
piece of road.
I'm just curious - what type of data consumer could use information
from OSM which contains 70 routes i
On Mon, Dec 2, 2013 at 3:55 AM, Jo wrote:
> That sounds like a totally different ballpark, which will never fit in the
> organised way it's done here. So the model as it is now doesn't fit and
> what I'm proposing doesn't fit either. Are there even fixed positions where
> the buses would stop? Ho
Hmm, I was thinking of staying more or less within the lines of what we
have now, but take away the burden of 10, 20, 70 relations on the same
piece of road. Those sub relations could describe how to get from one stop
to the next, or describe the common parts of how buses get from A to J with
sever
That sounds like a totally different ballpark, which will never fit in the
organised way it's done here. So the model as it is now doesn't fit and
what I'm proposing doesn't fit either. Are there even fixed positions where
the buses would stop? How do you know where the bus will take you? If it's
o
On Sun, Dec 1, 2013 at 1:09 PM, Shaun McDonald
wrote:
> Which is why I believe that it’s better to use GTFS data, and auto snap the
> GTFS data to the OSM data. There then needs to be some hints in the OSM data
> as to which roads buses do and don’t or shouldn’t run on. Bus routes also
> change fa
The complexity of the current PT schema makes it close to impossible to
creat or maintain this kind of data in India, where bus transport systems
are a lot more complex, unstructured and dynamic.
I have found making bus frequency based renderings to be a lot more useful
here [1], where the only da
You're certainly not alone. I'm mapping the _single_ bus route in my
area, but it has about a zillion variations, none of which is entirely
predictable without access to the full timetable data. This single route
is effectively a mini network all by itself.
I thought as you did, that some commonal
I'm brooding on this for over a year now, but it's only recently that I've
started to add lots of route relations for buses and trams, complete with
all the variations.
This proposal would, of course, also make it a lot easier to add the
relations in the first place.
For the conversion, I can com
Which is why I believe that it’s better to use GTFS data, and auto snap the
GTFS data to the OSM data. There then needs to be some hints in the OSM data as
to which roads buses do and don’t or shouldn’t run on. Bus routes also change
far more frequently than fixed infrastructure or cycle or walk
Hi,
You're certainly not alone: I was precisely thinking of such a kind of solution
these last days.
I'm usually mapping bus routes and the variants are really heavy to duplicate.
This is also the reason why I didn't get too close yet to the train
lines/infrastructure (which are far longer in
Hi,
This subject has come up here and there already. I'm in the process of
adding public transport routes for all the buses and trams in my region.
- each variation of a route gets its own route relation
- at times there are 40 variations
- on average 2-6
- buses tend to use the same ways for sev
11 matches
Mail list logo
