Re: [josm-dev] Checking tags
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 right now they are well hidden. And as useful the autocomplete feature of JOSM is, it is also problematic. Once you have a typo in a tag, JOSM will happily autocomplete that misspelled tag again and again. There are already discussions about the order of autocompletion. I am not happy the the current state, as well. We could work with colours to give hints about the origin, e.g. for tags from default preset, gray for other presets and blue for only in data. 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... See above, validator already knows about the keys and values of presets and gives warning. The default mappaint style is not a validation layer but should only render known tags and not simply keys. Cheers colliar 0xE8F56581.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
[OSM-dev] osm2pgsql - error loading planet
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 details on my configuration:
Hardware: PC 64-bit 8-core 32 gb ram
OS: Ubuntu 14.04.2 LTS
postgresql: PostgreSQL 9.3.6 on x86_64-unknown-linux-gnu, compiled by gcc
(Ubuntu 4.8.2-19ubuntu1) 4.8.2, 64-bit
postgis: POSTGIS=2.1.2 r12389 GEOS=3.4.2-CAPI-1.8.2 r3921 PROJ=Rel.
4.8.0, 6 March 2012 GDAL=GDAL 1.10.1, released 2013/08/26 LIBXML=2.9.1
LIBJSON=UNKNOWN RASTER
osm2pgsql SVN version 0.85.0 (64bit id space)
My last command was:
osm2pgsql --create -s -v -C 28000 --cache-strategy sparse
--number-processes 6 -I --flat-nodes ./nodes.cache
--disable-parallel-indexing -l -d gio_reference -U gio -W -H localhost -P
5432 /Data/europe-latest.osm.pbf
Here is the error:
Processing: Node(1432818k 1007.6k/s) Way(65018k 27.54k/s) Relation(0
0.00/s)pgsql_ways_set - bad result during COPY, data 139191086
{1525470973,1525469649,1525469626,1525469616,1525469608,1525469597,1525469594,1525469591,1525469590,1525469586,1525469583,1525469571,1525469573,1525469588,1525469593,1525469596,1525469613,1525469617,1525469618,1525469629,1525469634,1525470940,1525469638,1525469639,678216143}
{z_order,0,highway,track} f
Error occurred, cleaning up
I think it's a bug but found no informations neither solutions on forums.
Does anybody experienced a similar issue? Does anybody solved it? Please
let me know.
Thanks, Angelo.
--
al mondo ci sono solo 10 tipi di persone: quelle che capiscono il binario e
quelle che non lo capiscono
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Re: [josm-dev] Blacklisted IP
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 with the Captcha you get. If the captcha is not enough to increase karma, then you must have multiple reason for reject. Adding some useful text in the Register comment helps also. If further tries fail, then please tell me time and username of your tries, so I can have a look in the logs. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [OSM-dev] GitHub repositories
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 authors of the tool). You can also see my contributions (over a third of the commits) here: https://github.com/openstreetmap/OSMembrane/graphs/contributors Regards, Jakob 2015-03-06 1:05 GMT+01:00 Tom Hughes t...@compton.nu: On 05/03/15 20:30, Jakob Jarosch wrote: I'm one of the original developers of the OSMembrane GUI tool for osmosis. It hadn't a real maintenance but looks like the source code is now on GitHub. I would like to give OSMembrane another try and update the GitHub repository with the latest build and a README. Is there anyone who can give me access to that repository so I can add a release? URL: https://github.com/openstreetmap/OSMembrane Well I'm not sure who added it to the openstreetmap organisation. I'm an admin for the organisation but I've never even heard of it. i suspect it has been there for a long time. In a literal sense I could given you access, but I would want the current owners (whoever they might be) to approve that before I did so, so you should probabyl start by trying to contact them. It looks like https://github.com/podolsir is the only person with access to that repo (other than the org admins) so that is probably the best person to contact in the first instance. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] osm2pgsql - error loading planet
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?
Simon
Am 16.03.2015 um 10:28 schrieb angelo de angelis:
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 details on my configuration:
Hardware: PC 64-bit 8-core 32 gb ram
OS: Ubuntu 14.04.2 LTS
postgresql: PostgreSQL 9.3.6 on x86_64-unknown-linux-gnu, compiled by
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2, 64-bit
postgis: POSTGIS=2.1.2 r12389 GEOS=3.4.2-CAPI-1.8.2 r3921 PROJ=Rel.
4.8.0, 6 March 2012 GDAL=GDAL 1.10.1, released 2013/08/26
LIBXML=2.9.1 LIBJSON=UNKNOWN RASTER
osm2pgsql SVN version 0.85.0 (64bit id space)
My last command was:
osm2pgsql --create -s -v -C 28000 --cache-strategy sparse
--number-processes 6 -I --flat-nodes ./nodes.cache
--disable-parallel-indexing -l -d gio_reference -U gio -W -H localhost
-P 5432 /Data/europe-latest.osm.pbf
Here is the error:
Processing: Node(1432818k 1007.6k/s) Way(65018k 27.54k/s) Relation(0
0.00/s)pgsql_ways_set - bad result during COPY, data 139191086
{1525470973,1525469649,1525469626,1525469616,1525469608,1525469597,1525469594,1525469591,1525469590,1525469586,1525469583,1525469571,1525469573,1525469588,1525469593,1525469596,1525469613,1525469617,1525469618,1525469629,1525469634,1525470940,1525469638,1525469639,678216143}
{z_order,0,highway,track} f
Error occurred, cleaning up
I think it's a bug but found no informations neither solutions on forums.
Does anybody experienced a similar issue? Does anybody solved it? Please
let me know.
Thanks, Angelo.
--
al mondo ci sono solo 10 tipi di persone: quelle che capiscono il
binario e quelle che non lo capiscono
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
signature.asc
Description: OpenPGP digital signature
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Re: [josm-dev] Checking tags
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 tags alerting the user that this is an unknown tag? Of course we need a list of known tags then... We already have this. It's degraded to INFO level, as it is disturbing. How are these warnings shown? Are they only shown in the validator? I almost never use the validator any more because a) it is another step to run this after I do the actual work and I tend to forget and b) it shows too many problems overwhelming me. I think any warnings should be shown in-line when editing in some way to warn immediately, otherwise they will probably be overlooked. Maybe that happens and I just have never seen it? For upload they are disabled by default. Can be enabled in validator settings (3rd/4th checkbox). A hint: You can simulate the upload validator when searching modified and then clicking the validator button. Reduces the amount of displayed stuff to anything related to your changes :-) There are just too many ways to mistype something. There are too many legitimate uses. And integrating the whole taginfo stats in JOSM is a bit much I think. The taginfo approach for quality control is a good thing, better than restrictive editors. But the idea of color coded key/value list sounds nevertheless good. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 times. Thats currently about 3500 keys. A list with all those keys is probably less than 35kBytes and should compress well. We only have to download this every so often, it doesn't change that much. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-173-7019282 ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 valid keys do not appear in JOSM's presets. However, adding to the mistake checkfile could help a little: hight denonation naem nota Along with warnings about colons greater than two, and keys length less than four, etc. -- Putting warnings inline with the tag editor could help a little. I'd also like to see that area used for warning about tags that JOSM will silently delete on upload. -- Ultimately think the problem is not really at the editor level. A buddy system where changsets are looked at by a second mapper would do far more. Mangled keys often go hand in hand with data that's also mangled. ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 already have this. It's degraded to INFO level, as it is disturbing. We also have a common mistake checkfile, which contains misspelled words. Has not been upgraded for a long time. Any ideas appreciated. I doubt this can be fixed at editor level without breaking the idea of OSM, but updating the words.cfg to catch most often current typos may improve situation a lot. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 unknown tag? Of course we need a list of known tags then... We already have this. It's degraded to INFO level, as it is disturbing. How are these warnings shown? Are they only shown in the validator? I almost never use the validator any more because a) it is another step to run this after I do the actual work and I tend to forget and b) it shows too many problems overwhelming me. I think any warnings should be shown in-line when editing in some way to warn immediately, otherwise they will probably be overlooked. Maybe that happens and I just have never seen it? We also have a common mistake checkfile, which contains misspelled words. Has not been upgraded for a long time. There are just too many ways to mistype something. I think we need some kind of positive list and warn for everything else. The positive list could be created from taginfo data, every key/tag used more than n times and/or documented on the wiki would be a good start for such a list I think. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-173-7019282 ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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, especially for large changesets. Connect new mappers to experienced mappers via the editor! ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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, say all keys that are used at least 1000 times. Thats currently about 3500 keys. A list with all those keys is probably less than 35kBytes and should compress well. We only have to download this every so often, it doesn't change that much. I could imagine something like syntax-highlighting in the tag-pane. I.e. if the key (or key=value combination) is recognized, the text becomes bold, or gets a different color. But if this is done, the whitelist should be as complete as possible and include all tags that are documented on the wiki. Do we have this data available? Paul ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 stats. Lets say to start we just make a list of keys that are okay, say all keys that are used at least 1000 times. Thats currently about 3500 keys. A list with all those keys is probably less than 35kBytes and should compress well. We only have to download this every so often, it doesn't change that much. I could imagine something like syntax-highlighting in the tag-pane. I.e. if the key (or key=value combination) is recognized, the text becomes bold, or gets a different color. That sounds very good to me. But if this is done, the whitelist should be as complete as possible and include all tags that are documented on the wiki. Do we have this data available? Yes, taginfo has that data. I'll try to create a whitelist using information like the usage count, how many people have used a tag, whether it is documented in the wiki etc. This is, of course, not perfect, but I think we can get a list that's much better than no list at all. I don't think a completely manual approach is going to work (unless we have a group of volunteers :-) Let me give this a try and we can then look at the created list and see how we like it. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-173-7019282 ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] Checking tags
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, of course, the editors. It is good that people can invent new tags, but maybe the editors could show a warning if an unusual key/tag is used? And as useful the autocomplete feature of JOSM is, it is also problematic. Once you have a typo in a tag, JOSM will happily autocomplete that misspelled tag again and again. 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... Any ideas appreciated. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-173-7019282 ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Checking tags
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 invalid characters as long as they are encoded in UTF-8: http://wiki.openstreetmap.org/wiki/Any_tags_you_like#Characters You can use any Unicode characters (utf-8) as you like. cheers, Martin ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
