Putting notes on every object armcahir mappers: keep away is just as
redundant and less informative than a source tag. I don't like all those
source tags, but it addresses a real problem.
I meant to say: add a note=* tag explaining the situation. Otherwise it
indeed wouldn't help, but when
2014-06-30 23:17 GMT+02:00 Tod Fitch t...@fitchdesign.com:
My issue with source:whatever=* tags is that you need one for every tag to
avoid confusion about what the source for a specific tag is and it is a
manual entry prone to error.
+1, and one for every node (e.g. of a way). Many mappers
2014-07-01 0:11 GMT+02:00 John Packer john.pack...@gmail.com:
(I'm not sure if OSM Messaging is built-in in JOSM, but it could be useful
for quick messaging in this kind of case).
there is a link: if you hit ctrl+h you'll get the versions of the selected
object with clickable usernames.
Hi,
Let us notice that, unlike my message, your replies do not comment the
*reasons* for source tags location.
I say:
* the wiki instructions say to put sources in the objects
* it needs fumbling to see changeset sources (is it fair to the author?)
* only source in objects can be used in
Just like everybody else I started several years ago by adding source tags
on the objects themselves.
The whole reason why the imports list says source tags belong on the
changeset has something to do with an import of millions of buildings in
France, each and every one with:
On Mon, Jun 30, 2014 at 06:40:47PM +0200, Jo wrote:
Just like everybody else I started several years ago by adding source tags
on the objects themselves.
I changed to putting the source on to change sets, but hit a problem
with armchair-mappers.
I found armchair mappers overwriting carefully
If the tagging of the object is tricky or not obvious, or it is prone to be
miscorrected by armchair mappers, it's useful to add a note in the
appropriate language with the key note=*.
For example, I have added it to part of a street that is used only for
parking, and doesn't legally lead
On 30/06/2014 22:17, Tod Fitch wrote:
At least in JOSM if you do a ctrl-h on a selected object it shows you the
source entry text that given on the change set (if it exists which it usually
doesn't on older change sets). If the other editors don't show that, then they
should be fixed.
For
gt; I'm not sure if OSM Messaging is built-in in JOSM, but it could be useful
for quick messaging in this kind of case
No, due to missing API features. All that could be done is checking for unread
messages.
___
Tagging mailing list
Hi, I wonder if this phrase without an explanation link
http://wiki.openstreetmap.org/wiki/Key:source contains appropriate
instructions (or just press news):
*Since the introduction of changesets these tags are often added as
changeset http://wiki.openstreetmap.org/wiki/Changeset tags rather
2014-06-26 12:44 GMT+01:00 André Pirard a.pirard.pa...@gmail.com:
Hi, I wonder if this phrase without an explanation link
http://wiki.openstreetmap.org/wiki/Key:source contains appropriate
instructions (or just press news):
*Since the introduction of changesets these tags are often added
I've been reading import proposals on the imports list for a while now and
the recommendation I keep seeing there is to add source tags on the
changesets, which is what I started since several months now. So now that
I'm preparing the osm file for BusCo, I'd prefer to simply add the
instruction to
2014-06-26 14:21 GMT+02:00 Dan S danstowell+...@gmail.com:
When I do edits using multiple sources, it makes a lot of sense to put the
source tags on the objects.
I have also occasionally used source-tags on the objects in the past, but I
have stopped doing it in favour of source-tags on
13 matches
Mail list logo
