<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-06-16 01:58, Jo wrote :<br>
</div>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi,<br>
<br>
</div>
The conversion is done. Municipality names are converted
to lower case, restoring the accents. Route_ref is
calculated.<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Many thanks Jo!<br>
A few remarks.<br>
<br>
As there were as usual no replies on this list to my remarks about
missing bus line numbers and accent-less uppercased place names, I
wrote to the TEC myself. They recognized my remarks as valid points
and they said that they will fix these problems, but no sooner than
September. I'll cc: you.<br>
<br>
I wonder if it wouldn't be wiser to "let's start !" in September
with that data rather than do it twice.<br>
<br>
Whatever I try, I see accent-less uppercased place names in your
file.<br>
<br>
I thought that you had found the line numbers, but I don't see them.<br>
<br>
My file was displaying the lines (without number). Yours not. Here
is an additional layer to display them.<br>
<pre class="help-code"><a href="https://dl.dropboxusercontent.com/s/ty49nmfdb2vfz4m/TEC_2014_04-Lignes.2.osm.bz2">https://dl.dropboxusercontent.com/s/ty49nmfdb2vfz4m/TEC_2014_04-Lignes.2.osm.bz2</a></pre>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>All that's missing at the moment is comparison with
existing data already present in OSM. I'm already doing
that for the stops of De Lijn, so the process exists. It
merely needs to be adapted a bit in the scripts I created.<br>
<br>
I'm not adding source on the objects anymore. Instead I
add source tags on the changeset as a whole.<br>
</div>
</div>
</div>
</div>
</blockquote>
On one hand, using a source= tag is highly recommended in the bus
stops and lines, if not required.<br>
On the other, you must of course be able to tell data that was added
by copying the elements of your file from OSM.org data that existed
before your publication and that must be updated.<br>
It's not a matter of how <b>you</b> make updates and tag
change-sets, but of how <b>the mappers</b> will do it.<br>
They'll File>Upload those updates the normal way, without your
change-sets tags, I don't know how to do it.<br>
If you use <b>source=survey 2014-06 TEC 2014-04</b> in bus stops
as I recommend, you will both comply with the source requirement and
be sure to find the indication that they contain your file's data
and can be deleted from the remaining-to-be-updated file.<br>
If an existing element does not contain <b>source=survey 2014-06</b><b>
TEC 2014-04</b> or later, it will be kept in the
remaining-to-be-updated file. If a mapper further updates the data,
he is kindly requested to use a new date such as <b>source=survey
2014-07</b> or <b>source=survey 2014-06-21</b> .<br>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>As for the operator, I prefer to use simply TEC.<br>
</div>
</div>
</div>
</blockquote>
No problem for me with <b>operator</b>, but (Sorry Julien, fourth
time) if you use <b>network</b>=tec-wl.be that's not an URL and <a
moz-do-not-send="true"
href="http://www.openstreetmap.org/node/857875464" target="_blank">that
is not clickable here</a> although we agreed using an URL (<b>network</b>=<a
moz-do-not-send="true" href="http://tec-wl.be" rel="nofollow"
target="_blank">http://tec-wl.be</a> <a moz-do-not-send="true"
href="http://www.openstreetmap.org/node/1645537259"
target="_blank">which is clickable here</a>) then please add
website=<a moz-do-not-send="true" href="http://tec-wl.be"
rel="nofollow" target="_blank">http://tec-wl.be</a>.<br>
<br>
The OSM file with all the stops in Wallonia can be found here:<br>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><a moz-do-not-send="true"
href="https://dl.dropboxusercontent.com/u/42418402/TEC.osm.zip">https://dl.dropboxusercontent.com/u/42418402/TEC.osm.zip</a><br>
</div>
</div>
</blockquote>
<br>
I think you should say that it must not be used for updates right
now.<br>
<br>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>What we still need to discuss:<br>
</div>
</div>
</blockquote>
The topics mentioned above and<br>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Is it OK to keep the zones as 4 digits? For me it's better,
as it makes them unique. It's not what can be read at the
stops in the streets though (There you'll find the last 2
digits).<br>
</div>
</div>
</blockquote>
I find the 4 digits all-right because if you don't want to see the
first two you just close your left eye but if they weren't there and
if you wanted to see them it wouldn't be possible ;-)<br>
What do the left two digits mean? Wouldn't that be the place for
the line number? Following "be.wa."?<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<blockquote
cite="mid:CAJ6DwMA_z47UkV2keRfUL_-Q-MTO9rtQjA9AWmgoPnZqDjjm0w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Polyglot<br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-06-16 1:38 GMT+02:00 André Pirard
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:A.Pirard.Papou@gmail.com" target="_blank">A.Pirard.Papou@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi,<br>
<br>
I'm conducting an offline TEC conversation business with
Jo and I'm impressed.<br>
You will soon be able to confidently buy TEC tickets and
use the OSM transport map ;-)<br>
<br>
I have just two tag remarks.<br>
<br>
For the third time (Julien), if we want to use URLs, we'd
better use URLs.<br>
network=<a moz-do-not-send="true" href="http://tec-wl.be"
target="_blank">tec-wl.be</a> is not an URL as you can
see by <a moz-do-not-send="true"
href="http://www.openstreetmap.org/node/857875464"
target="_blank">not being able to click on it here</a>.<br>
network=<a moz-do-not-send="true" href="http://tec-wl.be"
rel="nofollow" target="_blank">http://tec-wl.be</a> is
one as you can see by <a moz-do-not-send="true"
href="http://www.openstreetmap.org/node/1645537259"
target="_blank">being able to click on it here</a>.<br>
<br>
I recommend adding <b>source=survey 2014-06 TEC
2014-04</b><br>
Much like <a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/Key:source"
title="Key:source" target="_blank">Key:<span>source</span></a>
indicates and I am presently proposing to amend slightly
as shown below.<br>
<br>
The bulk import scenario was clearly written with in mind
the idea to maintain a remaining-to do TEC file.<br>
<br>
Suppose an *.osm file is built from an imported source.
The map contributors are requested to move/update the map
elements to <a moz-do-not-send="true"
href="http://osm.org" target="_blank">osm.org</a> after
verifications such as coordinates. If the *.osm map
elements contain a survey value such as source=survey
<import-date>, then a program can find out by
checking for an equal or later survey date what map
elements have been moved/updated to <a
moz-do-not-send="true" href="http://osm.org"
target="_blank">osm.org</a> and hence build a
remaining.osm file containing what remains to be done. A
FIXME can be added at import time to already existing <a
moz-do-not-send="true" href="http://osm.org"
target="_blank">osm.org</a> elements to warn about the
ongoing import. <br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<blockquote type="cite">Following this discussion here is
a proposed clarification to <a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/Key:source"
title="Key:source" target="_blank">Key:<span>source</span></a>.<br>
The goal is to define the word, make date mandatory, use
ISO format, define per source tag meaning.<br>
Is there any objection or suggestion for changes?<br>
<br>
<b>survey</b> yyyy-mm[-dd] (with one blank and an <a
moz-do-not-send="true"
href="http://www.google.be/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&sqi=2&ved=0CDAQFjAC&url=http%3A%2F%2Fwww.iso.org%2Fiso%2Ffr%2Fhome%2Fstandards%2Fiso8601.htm&ei=X3qZU_CEPNHR4QT34YGwCg&usg=AFQjCNHMm5_cA8CzTjEvrWYQc5GZ9K1wLg&sig2=m6xdSXuaBGqt6Qlj0tCfTw&bvm=bv.68911936,d.bGE"
target="_blank"><em>ISO</em> 8601</a> format date) can
be used within the data of any source.KEY=* or source=*
tag to indicate that, on that date, the source(s) of KEY
were the most recent and the data was verified to be
correct for that KEY. In source=*, survey means the
same for all possible (required) keys (even those absent
by default), but it can be overridden by survey in some
source.KEY tags. survey helps to avoid making already
done verifications, especially because a source
publication date is not a verification date. survey can
contain the date of dateless sources like visual or
knowledge. It can help humanly assisted bulk imports.
Please update the survey date of what you verify (a
substantial time later), even if you don't add survey
dates yourself.<br>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>