2012/3/1 Janko Mihelić
>
>
> Dana četvrtak, 1. ožujka 2012., korisnik Tom Brown
> je napisao:
>
> > Regarding your original proposal with Mo-Fr 08:00-23:00 t30:
> > Instead of putting the count of trips in a time period how about giving
> the average headway? When exact times are not provided tim
Dana četvrtak, 1. ožujka 2012., korisnik Tom Brown je
napisao:
> Regarding your original proposal with Mo-Fr 08:00-23:00 t30:
> Instead of putting the count of trips in a time period how about giving
the average headway? When exact times are not provided timetables and
riders often refer to "how of
Regarding your original proposal with Mo-Fr 08:00-23:00 t30:
Instead of putting the count of trips in a time period how about giving the
average headway? When exact times are not provided timetables and riders
often refer to "how often the bus/train comes". You could represent this
with strings suc
2012/3/1 Janko Mihelić
>
> "transport_frequency=Mo-Fr 08:00-23:00 t30; Sa 08:00-22:00 t25"
> This one would be ( 30/24 + 25/24 ) / 2 = 1.146 trips per hour
>
> Janko
>
No, I forgot to count Mo-Fr as 5 days, and Sunday that has no trips. So it
would be like this:
( 5*(30/24) + 1*(25/24) + 1*0 )
2012/3/1 Erik Johansson
> On Wed, Feb 29, 2012 at 16:07, Janko Mihelić wrote:
>
> The interpretation of what a low volume line is and isn't seems hard,
> and probably differ a lot between different areas.
>
> How do I do the decision that:
> "transport_frequency=Mo-Fr 08:00-23:00 t30; Sa 08:00-
On Wed, Feb 29, 2012 at 16:07, Janko Mihelić wrote:
> Hello,
>
> The problem with rendering transit lines right now is that the busy lines
> are rendered the same as the lines that go a few times a day. Those
> differences between lines should be seen right away, but we don't have that
> informati
2012/3/1 Bryce McKinlay
>
> GTFS is an open data format for public transport schedules. Just
> because it was invented by Google does not mean that it's only
> relevant to them.
>
> Many projects use GTFS data and have nothing to do with Google
> Transit. Example: opentripplanner.org
>
> Bryce
>
On Thu, Mar 1, 2012 at 9:17 AM, Janko Mihelić wrote:
> I must admit I don't know much about getting renderers to work, but
> summing frequencies of all bus lines on each way seems to be enough for
> now. And if you draw bus routes with colours ranging from blue (rare route)
> to red (busy route)
On Thu, Mar 1, 2012 at 6:45 AM, Andre Joost wrote:
> Am 29.02.2012 18:18, schrieb Paul Johnson:
>
>> On Wed, Feb 29, 2012 at 8:03 AM, Bryce McKinlay
>> wrote:
>>
>>> Secondly, GTFS is already a good, widely used, open format for transit
>>> schedules. Introducing a new set of tags for this stuff
2012/3/1 Andre Joost
>
> Sounds interesting. For densly populated areas, it would be better to give
> a frequency per hour, or every xy minutes.
>
Maybe my "t" could be replaced with "h10" for 10 trips every hour or "d40"
for 40 trips every day.
> But how should the renderer treat a service b
On Thu, Mar 1, 2012 at 6:51 AM, Andre Joost wrote:
> The renderer has to look up every bus service on a road, and count them
> together. This is not a simple thing with current mapnik.
>
>
>
Yes indeed. I've done it by applying local external rules (if ref=X13 then
behave as if frequency=6, becaus
11 matches
Mail list logo
