maybe we can use some keys like eta_link:shortnameofbuscompanyA=*
and eta_link:shortnameofbuscompanyB=* to show different operators
information
在 2019年3月13日週三 15:01，Graeme Fitzpatrick 寫道：
>
>
> On Wed, 13 Mar 2019 at 14:30, Phake Nick wrote:
>
>> but in term of GTFS I don't think anyone in the
On Wed, 13 Mar 2019 at 14:30, Phake Nick wrote:
> but in term of GTFS I don't think anyone in the world supply data
> individually for each stops.
>
Of course!
It would be nice (but probably impossible) to have a single worldwide
answer but I don't think that will be possible in the
There are processed data for each stop, but in term of GTFS I don't think
anyone in the world supply data individually for each stops. My
understanding is that each GTFS file usually cover a line or a network.
在 2019年3月13日週三 10:32，Graeme Fitzpatrick 寫道：
>
>
> On Wed, 13 Mar 2019 at 11:18,
For the coordinated schedule, as an example there is a route that departure
at the following time:
08:00, 08:00, 08:03, 08:06, 08:09, 08:12, 08:15, 08:18, 08:22, 08:25,
08:29, 08:33, 08:38, 08:38, 08:38, 08:41, 08:44, 08:47, 08:51, 08:54,
08:57, 09:01, 09:05, 09:09, 09:13, and of these departures,
On Wed, 13 Mar 2019 at 11:18, Andrew Davidson wrote:
> However, you may want to include the feed_id every
> time to make it easier to search for stops. Also do we want to repeat
> the same information at every stop or should we store it in a single
> relation?
>
Unless I've misunderstood the
On 2/3/19 10:02 am, Leif Rasmussen wrote:
> It seems like the best way forward now is for a proposal allowing
OpenStreetMap data to be tightly integrated with outside sources (such
as GTFS) to be created by someone. This would avoid the issues of
maintainability in OpenStreetMap.
I'm not
sent from a phone
> On 7. Mar 2019, at 15:02, Phake Nick wrote:
>
> The route us currently operated by two different operators on coordinated
> timetable and each operator have their own ETA system. While they do not
> provide a GTFS feed for now, it can be expected that each of them will
sent from a phone
> On 7. Mar 2019, at 13:06, Paul Allen wrote:
>
> It's just that at one time the bus will have the
> livery of "Foo Brothers" and at another time it will have the livery of "Bar
> Buses." They're not variant
> routes but variant operators.
the basic options are different
Nope. For example: https://www.openstreetmap.org/relation/3352395 The route
us currently operated by two different operators on coordinated timetable
and each operator have their own ETA system. While they do not provide a
GTFS feed for now, it can be expected that each of them will provide their
On Thu, 7 Mar 2019 at 06:33, Martin Koppenhoefer
wrote:
>
> > On 5. Mar 2019, at 21:33, Paul Allen wrote:
> >
> > Routes do exist with more than one operator.
>
> wouldn’t these simply be tagged as several relations?
>
I don't know. It's the same route, with the same service number, the same
sent from a phone
> On 5. Mar 2019, at 21:33, Paul Allen wrote:
>
> Routes do exist with more than one operator.
wouldn’t these simply be tagged as several relations?
Cheers, Martin
___
Tagging mailing list
Tagging@openstreetmap.org
On Tue, 5 Mar 2019 at 19:07, Jarek Piórkowski wrote:
>
> Again, frankly - approximately zero general-purpose apps will support
> whatever scheme we could come up with in OpenStreetMap to tag the
> situation "this stop is served by a route that has two separate
> timetables that are both valid,
On Tue, 5 Mar 2019 at 13:35, Paul Allen wrote:
> But I'd prefer we have specific keys for
> timetables and GTFS data rather than rely upon either of those. Much better
> to make things clear
> with timetable=* and gtfs=* (except we have to deal with partial
> timetables/feeds from operators
>
On Tue, 5 Mar 2019 at 17:37, Jarek Piórkowski wrote:
>
> If your use case is people using the query tool on
> https://openstreetmap.org to follow links to PDFs to plan a journey,
>
Might be a PDF or a simple web page or a Web 2.0 page with funky effects
and even live
updates. Sadly, given the
Paul,
If your use case is people using the query tool on
https://openstreetmap.org to follow links to PDFs to plan a journey,
then whatever tagging specification you use doesn't really matter as
long as it's understandable to the people viewing it - a link looks
like a link so that's quite easy.
On Tue, 5 Mar 2019 at 01:41, Jarek Piórkowski wrote:
>
> On Sat, 2 Mar 2019 at 19:42, Paul Allen wrote:
> > As I said, I'd prefer not to use url=* because it could be for anything
> - a page about the history of
> > the bus stop (maybe the shelter is a listed building),
>
> That would rather be
Hello,
I've gotten paid for wrangling GTFS worldwide before - happy to tell
you some of my experiences.
On Sat, 2 Mar 2019 at 19:42, Paul Allen wrote:
> As I said, I'd prefer not to use url=* because it could be for anything - a
> page about the history of
> the bus stop (maybe the shelter is
On Sun, 3 Mar 2019 at 00:06, Graeme Fitzpatrick
wrote:
>
> On Sun, 3 Mar 2019 at 00:21, Paul Allen wrote:
>
>> On Sat, 2 Mar 2019 at 08:14, Warin <61sundow...@gmail.com> wrote:
>>
>>>
>>> So a documented way of including GTFS link in routes?
>>>
>>
>> Yep. We could just use url=*
>>
>
> When
On Sun, 3 Mar 2019 at 00:21, Paul Allen wrote:
> On Sat, 2 Mar 2019 at 08:14, Warin <61sundow...@gmail.com> wrote:
>
>>
>> So a documented way of including GTFS link in routes?
>>
>
> Yep. We could just use url=*
>
When I've been adding bus stops, I've been using timetable= linked to the
GTFS
On Sat, 2 Mar 2019 at 08:14, Warin <61sundow...@gmail.com> wrote:
>
> So a documented way of including GTFS link in routes?
>
Yep. We could just use url=* but I'd prefer to keep that available for
other things. Besides,
it would probably be a good idea to allow for a link to the operator's
Mar 2, 2019, 9:12 AM by 61sundow...@gmail.com:
> The other thing picked on it keeping it 'up to date'.
> One says a route is out of date for years (why the contributor does not up
> date it is not stated)
>
In my case: because updating it would take about half of hour, there are
multiple ones
On 02/03/19 10:27, Jarek Piórkowski wrote:
On Fri, 1 Mar 2019 at 18:02, Leif Rasmussen <354...@gmail.com> wrote:
It seems like the best way forward now is for a proposal allowing OpenStreetMap
data to be tightly integrated with outside sources (such as GTFS) to be created
by someone.
+1. To
On Fri, 1 Mar 2019 at 18:02, Leif Rasmussen <354...@gmail.com> wrote:
> It seems like the best way forward now is for a proposal allowing
> OpenStreetMap data to be tightly integrated with outside sources (such as
> GTFS) to be created by someone.
+1. To avoid lots of changes, perhaps only set
23 matches
Mail list logo
