Andy Townsend gmail.com>
writes:
> Because of the language difference I
suspect that the chance of a reply
> from this MAPS.ME user will be less than
from others (unless you try an
> address them in Korean - but that really
isn't difficult these days with
> machine translation).
>
> I've
On Wed Jun 22 14:52:40 2016 GMT+0100, Martin Koppenhoefer wrote:
> 2016-06-22 15:13 GMT+02:00 Michael Reichert :
>
> > I decided not to write a changeset comment because it seems to me to
> > be a waste of time to comment a Maps.Me user's changeset.
> >
>
>
> It is also a way
2016-06-22 15:16 GMT+02:00 Michael Reichert :
> If someone wants to import some low-/mixed quality stuff into OSM and
> suggest to add fixme=* to lots of objects, we usually refuse to give the
> import "permission" because such data usually will not be fixed. That's
> why I think
2016-06-22 15:13 GMT+02:00 Michael Reichert :
> I decided not to write a changeset comment because it seems to me to
> be a waste of time to comment a Maps.Me user's changeset.
>
It is also a way to document for your fellow mappers what you have found
out, not just a way to
On 22/06/2016 14:13, Michael Reichert wrote:
I decided not to write a changeset comment because it seems to me to
be a waste of time to comment a Maps.Me user's changeset. (There less
frequently respond to comments than iD users)
Because of the language difference I suspect that the chance of
just checked a few of the edits and deleted some nodes.
Lee Jin-Jeong did add a couple of things that were already there and in
the case of an hostel several times. In Kiev the user added a Korean
church with the name "Kiev Korean Unified Church" in Korean. The
location is a bit curious though in
Hi Martin,
Am 22.06.2016 um 15:04 schrieb Martin Koppenhoefer:
> I would add fixme tags and decide on an individual basis how to deal with
> it. Still, despite all lamentation, I admit that the amount of surveyed
> addressing information we are getting this way is great (precision to be
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Joost,
Am 22.06.2016 um 15:09 schrieb joost schouppe:
> Did you miss the ongoing thread on this subject? [1]
If read the thread but was not able to draw a conclusion regarding my
question.
> You should of course contact the mapper with the
Did you miss the ongoing thread on this subject? [1]
Max even said something about Korean names there too, though this is about
the reversed situation [2]. I have no ideas if the names in Korean in your
case are transliterations of the local name.
You should of course contact the mapper with the
2016-06-22 14:26 GMT+02:00 Michael Reichert :
> Shall I either revert his changesets in total or shall I change
> (mechanically/without local knowledge) name=* to name:ko=*?
>
In the instances of similar cases I have checked, it was mostly improbable
that the features would
On Wednesday, June 22, 2016, Michael Reichert wrote:
> by browsing the map, I have discovered the edits of user 이진영
> (Google Translator says that this is a Korean name). He added some
> POIs in serveral European countries and entered the Korean name into
> name=*.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
by browsing the map, I have discovered the edits of user 이진영
(Google Translator says that this is a Korean name). He added some
POIs in serveral European countries and entered the Korean name into
name=*.
12 matches
Mail list logo