<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<blockquote type="cite"
cite="mid:CACKdxBpna-=1sz8vcs-XbV4RdDNcEKjJeW1DNuZQ4YEhWOS86A@mail.gmail.com">
<div class="gmail_quote">
<div dir="ltr">On Tue, Nov 27, 2018 at 10:40 PM Pierre
Parmentier <<a href="mailto:pierrecparmentier@gmail.com"
moz-do-not-send="true">pierrecparmentier@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Hello,</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">The two
planned training sessions on the contribution to OSM
took place at EPN (Espace public numérique) in Arlon on
6 and 27 November 2018 from 9.00 to 16.00 h.<br>
<br>
A dozen people attended each of them. They came from
very different horizons, from places in the province
sometimes far from Arlon, and included members of the
Sentiers de Grande Randonnée ASBL as well as officials
of a tourism organization in the area.<br>
<br>
We approached the edition with JOSM mainly. The various
menus and some plugins were examined. Participants
created an account and some nodes and ways were added to
OSM. The GPX file creation with Graphhopper and overpass
turbo and their import into uMap were also shown.<br>
<br>
Some participants have already set to work on their
side, mainly in the localities of Aubange and Athus, in
the province of Luxembourg.<br>
<br>
But the others, perhaps more shy, were interested in
consolidating their knowledge and it was agreed with the
EPN Arlon that a monthly OSM workshop would take place
from January 2019.<br>
<br>
I hope this will help OSM grow in this part of the
country.</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Pierre
Parmentier<br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
That's great news, Pierre.<br>
Nice to hear news from the nearby province (I mapped the Luxembourg
boundaries and in Wallonia with 2 Belgian friends and a Frenchman).<br>
I especially appreciate your basing of your tutorials on JOSM and I
hope you mention PICC because:<br>
<ul>
<li>JOSM is the recognized best editor (most serious)</li>
<li>it's extremely powerful: did you show the AreaSelector plugin
that, by clicking on the PICC layer, can map a whole streetful
of houses at the rate of 1 house per 5-10 sec, complete with
street name etc. and incrementing number, at a 20 cm precision?</li>
<li>when I am mapping that way, I'm spending much time correcting
the mapping made with other editors with an imprecision of 2-5 m
and often more: when I meet precise tagging I know it was done
with JOSM+PICC and that most often checks to be true<br>
</li>
<li>JOSM is less intuitive than other editors indeed (c) but it's
not very hard to learn it after all. The problem is that someone
who has been accustomed to another editor may prefer to spend
time mapping rather than to learn JOSM. Some of my friends are
really convinced of the superiority of JOSM but just can't make
the step. To them, my best advice is to start using JOSM little
by little, using two editors at the same time and finally
settling on JOSM (that's what I did with Merkaartor but I
concluded that JOSM is better).<br>
</li>
<li>JOSM is a totally different concept than Web based solutions
that (generally) expose the user to the "an expected error
occurred" message, "please do it again" (all that was done
forgotten). JOSM loads parts of the OSM data on the PC, modifies
a part of it and then writes what it has modified back to the
OSM database. This means that:</li>
<ul>
<li>the data that JOSM loaded, or part of it, can be recorded in
a *.osm file on the PC (before being "written back" to OSM)<br>
</li>
<li>if the work to do was too much for one day, that *.osm file
can be reloaded and the work continued after a good night
sleep<br>
</li>
<li>if the user is stuck, the *.osm file can even be send to a
friend to be continued</li>
<li>the *.osm file can be edited as a text file to do very
subtle modifications</li>
<li>those kind of things are not obvious indeed but many friends
are around: I once helped to salvage a shrimp pond dikes: his
mapping had been vandalized (erased); He could not do a
"revert", I did it for him and sent him the *.osm file that
would have restored his mapping. But some nodes were moved "ad
infinity" and JOSM would crash when trying to move them. So I
edited the *.osm file to move them to a noticeable location so
that he could move them to the right place. And he succeeded
the revert and was so glad.<br>
</li>
<li>should JOSM crash, which is very rare, it will offer to
continue a saved checkpoint</li>
<li>etc. etc.</li>
</ul>
</ul>
<p>More and more geographic pages use OpenStreetMap now <br>
</p>
All the best,
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>