[Talk-transit] [OSM-talk-be] identifier in ref:xOperatorx=y0yyyy to url=http://mijnlijn.be/y0yyyy

[Jo]

Frank,

url wasn't used yet on the bus stops, so no conflict there.

Pieter, good to hear De Lijn plans such deep links. I think it will be good
to have them on our route_master relations. The route relations are for the
longest variations in itinerary, not sure if they fit there.

For the stops, I tend to like the mijnlijn.be/ form, as that is the
information printed on each of the paper schedules on the stops. So if De
Lijn is not planning to abolish those in the medium term, I'd prefer to use
them. I'll hold off with preparing the data and launching the Project of
the Month though.

Pieter, is De Lijn planning to introduce uic identifiers we could put in
uic_ref?

We don't have anything that corresponds to the zones in OSM. I'm curious to
find out what will be behind those urls. I painstakinglly added the zone
information on the stops, but now that a ticket has a time limitation
instead of a zone dependent one, they became less relevant.

Marc, we can leave the ref:De_Lijn tags. I'm not strongly against keeping
them, but I doubt anyone uses them (except me in my integraton scripts). If
anyone wants to use them, it's trivial to extract the identifiers from the
url tag values.

There is another tag I'd like to introduce. While reviewing the import of
bus stops around Finland, they added a direction tag.

My first reflex was to remove it after reviewing the stop, but now I start
to see value in knowing in which direction the bus will leave. I plan to
add functionality to PT_Assistant to calculate it automatically based on
the segment of the way the stop is adjacent to. And in a second stage a
validator rule that checks whether the stop is (still) on the correct side
of the road (right or left, depending on the side of the road vehicles
drive on)

Polyglot





El dom., 18 nov. 2018 a las 11:19, Pieter Colpaert (<pieter at openknowledge.be>)
escribió:

> Hi Polyglot,
>
> We are in a Linked Data project with De Lijn and we’re going to have
> official persistent identifiers (HTTP URIs) soon for stops (but also for
> things like the routes and zones). It might be interesting to integrate
> these in OSM rather than the mijnlijn.be one?
>
>  From the moment we have an official URI strategy, I will get back to
> this list in each case.
>
> Kind regards,
>
> Pieter
>
> On 18/11/18 11:10, Jakka wrote:
> > Using key as "url=" not comming in conflict with already other keys
> > that use short key url ?
> >
> > Op 18/11/2018 om 10:51 schreef Jo:
> >> Our bus stops in Flanders have unique identifiers visible to the public
> >> on the flags of the stop poles.
> >>
> >> I started by entering those in the ref tag, then later decided to use
> >> ref:De_Lijn=y0yyyy, as some of those stops are served by other operators
> >> as well.
> >>
> >> For several years now itt's possible to obtain real-time information
> >> about the buses on a url+identifier, so I want to add that to those
> >> stops. As i don't like to duplicate information I'd prefer to drop the
> >> ref:De_Lijn though.
> >>
> >> So all of those stops would have:
> >> url=http://mijnlijn.be/303079    (<- you can test this, the url is
> >> expanded/translated to a url on www.delijn.be <http://www.delijn.be>)
> >>
> >> For the conversion, I'd like to launch a Belgian "Project of the month",
> >> so the position of the stops can be verified once more by locals, but
> >> also shelters and bus_bays can be added and if cycle ways split off to
> >> go around those bus bays, that detail can be added as well.
> >>
> >> I know that that is what we have been doing for the past 5+ years, but
> >> now it would get some more dedicated focus.
> >>
> >> For several years I thought having the identifier n a dedicated ref:X
> >> tag and then telling everyone about how to turn it into such a url was
> >> the way to go,. That doesn't actually work though. Nobody knows how to
> >> get from the identifer to the url. Giving potential passengers a url
> >> they can simply click through on, seems to be the better way of doing
> >> this for this use case.
> >>
> >> Polyglot
> >>
> >>
> >> _______________________________________________
> >> Talk-be mailing list
> >> Talk-be at openstreetmap.org
> >> https://lists.openstreetmap.org/listinfo/talk-be
> >>
> >
> >
> >
> > _______________________________________________
> > Talk-be mailing list
> > Talk-be at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-be
>
> --
> +32486747122
>
>
> _______________________________________________
> Talk-be mailing list
> Talk-be at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-transit/attachments/20181118/fe27b2a1/attachment.html>