On 16/03/2015 00:16, Rob Nickerson wrote:
Not necessarily as fixing the tag could also result in the data being
rendered therefore making it more visible for people to come in and fix
(if a local community of OSMers exists).
Other non-destructive actions might me to include key capitalisations
Hi,
On 03/16/2015 08:54 PM, Andreas Goss wrote:
I've found a dozen really incompetent imports by following up on
oddities in Taginfo. Simply fixing the tags would do nothing
but mask the bad data.
It would allow me to actually find the stuff that really wrong. As it
stands now I'm not
I've found a dozen really incompetent imports by following up on
oddities in Taginfo. Simply fixing the tags would do nothing
but mask the bad data.
It would allow me to actually find the stuff that really wrong. As it
stands now I'm not going to waste my time fixing 200 capital language
But we were never talking about such changes. We were talking about
changing Highway=footway into highway=footway.
On 3/14/15 23:32 , SomeoneElse wrote:
On 14/03/2015 21:48, Andreas Goss wrote:
Just because people some people make bad decisions when mapping, doesn't
mean that the whole
I've found a high correlation between misspelled tags and bad tagging.
The onsey twosey tags with letters transposed are usually OK.
But those where the same error appears on a dozens or more nodes usually
have other far worse problems.
Please do add case mismatched tags to something like
On Sun, Mar 15, 2015 at 2:21 AM, Andreas Goss andi...@t-online.de wrote:
But we were never talking about such changes. We were talking about
changing Highway=footway into highway=footway.
That's exactly what's under discussion.
Automated changing of tag X into Y misses something. Very often
Simply fixing the tags would do nothing but mask the bad data.
Not necessarily as fixing the tag could also result in the data being
rendered therefore making it more visible for people to come in and fix (if
a local community of OSMers exists).
There are arguments on either side but I do feel
The API could also impose some rules, and reject certain malformations at
time of upload.
This would at least alert the uploader, even if they just paper over the
problem later.
___
talk mailing list
talk@openstreetmap.org
So what about keys like this:
https://www.openstreetmap.org/relation/4223325/history
With non-English components after the colon. Should these be encouraged?
Discouraged?
___
talk mailing list
talk@openstreetmap.org
Hi,
On 03/14/2015 02:34 PM, Andreas Goss wrote:
And how many mappers would actually bother to check something if they
spot it? I think a huge majority would just change ToiletS to toilets,
so I doubt a bot would be much worse.
A bot would perhaps not be much worse, but still a bad idea; it
Changing spelling and/org cases via the API causes another entry in
the database. A history entry gets created for each change.
Changes like that should be done at the database level with a simple
update statement. Not sure how much the DBAs would hate to do this due
to tracking changes made at
Just because people some people make bad decisions when mapping, doesn't
mean that the whole project has to lower its standards.
And some people in this case are what? 99%? I seriously there are many
people who would spend a second though when changing Toilets=
__
On 14/03/2015 21:48, Andreas Goss wrote:
Just because people some people make bad decisions when mapping, doesn't
mean that the whole project has to lower its standards.
And some people in this case are what? 99%? I seriously there are many
people who would spend a second though when changing
Hi,
On 03/14/2015 10:48 PM, Andreas Goss wrote:
And some people in this case are what? 99%? I seriously there are many
people who would spend a second though when changing Toilets=
The discussion was about ToiletS, not Toilets.
As far as I am concerned, I would either not be interested (and
On 14/03/2015 5:49 PM, Jochen Topf wrote:
On Sa, Mär 14, 2015 at 09:24:20 +1100, Warin wrote:
Are not 'keys' always lower case? Thus any upper case there can be changed
into lower case without loss of data?
Tags are much more varied than you might think. And then some. See here for
some stats:
On Sa, Mär 14, 2015 at 09:24:20 +1100, Warin wrote:
Are not 'keys' always lower case? Thus any upper case there can be changed
into lower case without loss of data?
Tags are much more varied than you might think. And then some. See here for
some stats:
And how many mappers would actually bother to check something if they
spot it? I think a huge majority would just change ToiletS to toilets,
so I doubt a bot would be much worse.
At least it would encourage me to work on that key overview, because
after 10min last week I gave up, because it
On Fr, Mär 13, 2015 at 07:17:01 +, Malcolm Herring wrote:
I found several cases of a key being duplicated with various
capitalisations: instead of this they are mostly like This or THIS.
Could somebody make a bot to clean these?
Please don't. Read the end of
On 14/03/2015 2:57 AM, Jochen Topf wrote:
On Fr, Mär 13, 2015 at 07:17:01 +, Malcolm Herring wrote:
I found several cases of a key being duplicated with various
capitalisations: instead of this they are mostly like This or THIS.
Could somebody make a bot to clean these?
Please don't. Read
A case fix is perfectly safe, except when it's not.
A crummy import may have brought ToiletS=yes.
But it might not mean the same thing as toilets=yes.
On occasion there will be a Tag=foo and tag=fum the same object.
___
talk mailing list
I found several cases of a key being duplicated with various
capitalisations: instead of this they are mostly like This or THIS.
Could somebody make a bot to clean these?
___
talk mailing list
talk@openstreetmap.org
Hi!
One week after my taginfo challenge we have a visible dent in the number
of of keys as you can see here:
http://taginfo.openstreetmap.org/reports/historic_development
But it looks like the work is already stalling. Maybe it is because everybody
is at FOSSGIS conference this week? Keep up the
22 matches
Mail list logo
