Am 16.03.2015 um 09:21 schrieb Jochen Topf:
It is good that people can invent new tags, but maybe the editors could show
a warning if an unusual key/tag is used?
There is already the info level warning about keys or values not in
presets. Maybe a new category for these warnings could help as
On Mon, Mar 16, 2015 at 2:11 AM, Martin Koppenhoefer dieterdre...@gmail.com
wrote:
2015-03-16 10:01 GMT+01:00 Bryce Nesbitt bry...@obviously.com:
You can use any Unicode characters (utf-8) as you like.
Is now,
need not be forever.
___
josm-dev
Dear members,
it's many weeks that i'm trying to import the latest versione of the
planet-latest.osm.pbf into postgresql/postgis using osm2pgsql without
success.
After many many attempts i tried to import a smaller version of the dataset
(europe-latest.osm.pbf), same bad result.
Just some
On Mon, 16 Mar 2015, Harvey Sama wrote:
I tried to register to the tickets tracker and my IP got blacklisted as my
registration was considered a spam. How can I solve this?
Be careful to read the rejection messages. An IP blacklist is only one
point to the score. Usually that can be solved
Hi,
thanks for your reply. I tried to contact Igor (podolsir) but he did not
respond to my mail.
Looking and the last commit date I think he is not really up to do some
changes in the next time.
So in my opinion it shouldn't be a problem to give me access to the
repository (as one of the original
Do you have enough disk space?
I believe we have seen similar errors due to running out of space (the
COPY command is essentially bulk loading data in to tables and seems to
not give particularly helpful messages when things go wrong).
Have you tried something really small, say Luxembourg or so?
On Mon, 16 Mar 2015, Jochen Topf wrote:
On Mo, Mär 16, 2015 at 03:56:53 +0100, Dirk Stöcker wrote:
On Mon, 16 Mar 2015, Jochen Topf wrote:
I am not sure myself how best to solve this. More warnings that people have
to click through are not ideal either. Maybe little warning icons next to
On Mo, Mär 16, 2015 at 05:13:51 +0100, Dirk Stöcker wrote:
There are too many legitimate uses. And integrating the whole taginfo stats
in JOSM is a bit much I think.
We don't need all stats. Lets say to start we just make a list of keys that are
okay, say all keys that are used at least 1000
On Mon, Mar 16, 2015 at 7:02 AM, colliar colliar4e...@aol.com wrote:
There is already the info level warning about keys or values not in
presets. Maybe a new category for these warnings could help as right now
they are well hidden.
The INFO level is essentially unusable, because too many
On Mon, 16 Mar 2015, Jochen Topf wrote:
I am not sure myself how best to solve this. More warnings that people have
to click through are not ideal either. Maybe little warning icons next to
tags alerting the user that this is an unknown tag? Of course we need a list
of known tags then...
We
On Mo, Mär 16, 2015 at 03:56:53 +0100, Dirk Stöcker wrote:
On Mon, 16 Mar 2015, Jochen Topf wrote:
I am not sure myself how best to solve this. More warnings that people have
to click through are not ideal either. Maybe little warning icons next to
tags alerting the user that this is an
I don't like the 1000 uses approach.
Some really terrible tags are used more than 1000 times,
and some really great ones less.
---
I think it far more useful to have editors offer guidance to new mappers.
JOSM can know how many changesets a person has uploaded, and turn on
extra guidance,
On 16.03.2015 18:02, Jochen Topf wrote:
On Mo, Mär 16, 2015 at 05:13:51 +0100, Dirk Stöcker wrote:
There are too many legitimate uses. And integrating the whole taginfo stats
in JOSM is a bit much I think.
We don't need all stats. Lets say to start we just make a list of keys that are
okay,
On Mon, Mar 16, 2015 at 06:36:09PM +0100, Paul Hartmann wrote:
On 16.03.2015 18:02, Jochen Topf wrote:
On Mo, Mär 16, 2015 at 05:13:51 +0100, Dirk Stöcker wrote:
There are too many legitimate uses. And integrating the whole taginfo stats
in JOSM is a bit much I think.
We don't need all
Am 16.03.2015 um 19:22 schrieb Jochen Topf joc...@remote.org:
unless we have a group of volunteers :-)
I volunteer to help with this task if I'm not the only one doing it (is
generally better to have more eyes on this because of the risk to be biased)
Cheers
Martin
Hi!
With my new Similar keys feature in taginfo presented here
http://blog.jochentopf.com/2015-03-05-new-taginfo-features-and-a-challenge.html
I started discussions how to fix those cases and then how to avoid the many
misspelled keys/tags in the first place. One point where we could start are,
On 16/03/2015 08:21, Jochen Topf wrote:
Any ideas appreciated.
A start would be to flag unusual characters in tag keys: Capital
letters, non-Latin characters, non-alphanumerics other than colon,
underscore, etc.
___
josm-dev mailing list
At some level I feel it's the API's job to reject changesets with invalid
key/value lengths or characters.
JOSM should perhaps have a matching validator rule.
___
josm-dev mailing list
josm-dev@openstreetmap.org
2015-03-16 10:01 GMT+01:00 Bryce Nesbitt bry...@obviously.com:
At some level I feel it's the API's job to reject changesets with invalid
key/value lengths or characters.
not sure what happens if you try to upload k/v with more than 255 chars
length, but according to the wiki there are no
19 matches
Mail list logo
