[OSM-talk-be] replace ref on stops De Lijn with mijnlijn.be/x0xxxx
Sander Deryckere
sanderd17 at gmail.com
Sun Mar 3 09:57:48 UTC 2013
That mol error is interesting, I'll show it to Alexander
2013/3/3 Gilbert Hersschens <ghersschens at gmail.com>
> Nice program, but every now and then it hangs. I have not yet figured out
> how to reproduce it in a predictable way, but it seems to be related to
> opening more than one bubble and eventually the oldest one does not respond
> to the close button (x). I also saw occurences where all bubbles are clodes
> when I close the most recently opened bubble. Program seems to have a
> problem keeping track of mutiple bubbles.
> On one line I saw a strange warning message. Maybe you know what's causing
> it ? It's bus stop Perron 2 on the railway station in Mol.
>
> Warning: Illegal offset type in /home/www/sites/
> 194.245.35.149/site/api/functions.php on line 1248
> *Mol Station Perron 2*
> Operator: De Lijn
>
> Gilbert
>
> On 2 March 2013 19:25, Jo <winfixit at gmail.com> wrote:
>
>> Alexander implemented Sander's suggestion on Openlinkmap.org:
>>
>> Go to:
>>
>> http://www.openlinkmap.org/?zoom=18&lat=50.8819&lon=4.71503&layers=BFTTTTT
>>
>> Make sure the public transport layer is in view
>>
>> Click on one of the stops.
>>
>> Click on the link after timetables and get the passages of buses at that
>> stop in real time.
>>
>> This only works for stops where operator contains De Lijn and ref is
>> (already) set to the six digit number found on all the stops.
>>
>> Thanks to Alexander and Sander!
>>
>> Jo
>>
>> 2013/1/31 Sander Deryckere <sanderd17 at gmail.com>
>>
>>>
>>>
>>> 2013/1/31 Jo <winfixit at gmail.com>
>>>
>>>> Hi,
>>>>
>>>> I like that proposal, but I don't know how to implement it for
>>>> openlinkmap. The developer is accepting patches, but he doesn't have time
>>>> to code stuff himself anymore.
>>>>
>>>
>>> That's a pity.
>>>
>>>>
>>>> My initial proposal had the advantage of instant gratification. It
>>>> would work with the current tagging habits. It's true that it has the
>>>> disadvantage of being dependent on the continued use of that url domain by
>>>> De Lijn and it's more verbose than I would like.
>>>>
>>>
>>> I agree with the advantage it has, but it creates other difficulties
>>> like maintainability of the database. It's like the "Don't tag for the
>>> renderer", only, a bit different.
>>>
>>> It's not because openlinkmap displays a certain tag, that we should tag
>>> everything this way.
>>>
>>>>
>>>> One small remark. The way I understand it we are moving to replacing
>>>> highway=bus_stop with public_transport=platform. So it should work for that
>>>> combination of tags as well.
>>>>
>>>> And it should be enough that a node contains De Lijn. Some stops are
>>>> shared with MIVB/STIB, TEC and VEOLIA.
>>>>
>>>
>>> These are valid remarks, and show why the configuration file should be
>>> crowd sourced. A single developer can never come up with all these
>>> exceptions for all these different nations.
>>>
>>>>
>>>> Jo
>>>>
>>>>
>>> I looked at the openlinkmap code, and it seems that he's filtering a lot
>>> of tags before the file gets imported in a database. The filtering also
>>> happens with a program that doesn't allow regex, only wildcards. So reading
>>> such a configuration file would be a hell of a job.
>>>
>>> I think I found something better. We could use the osmosis tagtransform
>>> plugin (http://wiki.osm.org/Osmosis/TagTransform). Where we could use
>>> a configuration file to transform tags to an url:*= tag. Like the example
>>> from De Lijn could be as following: http://pastebin.com/4G4FPyEq(currently writing to url:delijn, but we could also check for the existence
>>> of an url tag, and write to that if it's not present).
>>>
>>> The disadvantages of this tool are that an url tag can only be created
>>> from a single other tag (as the discussion page on the wiki says), And a
>>> key needs to stay a key, and a value needs to stay a value.
>>>
>>> Another drawback might be the installation of an extra plugin. It
>>> doesn't seem so easy as it should be (version conflicts etc). But it should
>>> be very straightforward to use the file afterwards, and to have this file
>>> crowd sourced. And, on the positive side, the osmosis team is looking into
>>> making this task part of the standard installation. In which case you won't
>>> have to install anything new at all.
>>>
>>> Regards,
>>> Sander
>>>
>>
>>
>> _______________________________________________
>> Talk-be mailing list
>> Talk-be at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>
> _______________________________________________
> Talk-be mailing list
> Talk-be at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-be
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20130303/ca7bc6ee/attachment.htm>
More information about the Talk-be
mailing list