On 2018-11-18 13:47, Jo wrote:
Frank,
url wasn't used yet on the bus stops, so no conflict there.
Jakka's point is not that "url" is used but that it could be wanted
and that this usage would prevent it.
To prevent the
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,
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
I would not drop the ref. The ref is visible on the signs, so it is a
"real thing". I have no problem that people add the URL as well. The
same is done for heritage sites. There is both a ref
(refLOnroerendErfgoed and a heritage:website.)
m.
On Sun, Nov 18, 2018 at 10:52 AM Jo wrote:
>
> Our bus
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
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=y0, as some of those stops are served by other operators as
well.
For several years now itt's possible to
