Re: [josm-dev] Invisible way
Thanks Dirk and Jochen (again). We fixed the incomplete ways bug in our output so the display bug no longer appears. This thread has given me some more clarity about the file format definition. I will try and capture that in the JXML wiki page also. (Oh and yes the extraneous tags like `foo` and `lastUser` would never make it into any file we'd ever release - like I said these are still fairly early experiments.) On Mon, Mar 9, 2015 at 9:30 AM, Jochen Topf joc...@remote.org wrote: On Mo, Mär 09, 2015 at 09:10:55 -0600, Martijn van Exel wrote: If the file is really incomplete, I don't think JOSM should accept it - or at least not without some kind of warning. The current behavior is ambiguous: it loads the file without any warning or error, and merges with another layer just fine, but it does not display the file (because obviously it does not have enough information.) Or is this because the JOSM file format is not well enough defined? There is nothing on the wiki suggesting a JXML file should contain all existing nodes in a way, or what happens if it doesn't. Should I write a clarification? JOSM does report those problems, but on STDOUT, maybe you didn't see it. JOSM being a GUI program should probably report it through the GUI though... And it should be obvious that you have to have all nodes needed for a way in the data if you want it to show up properly. Thats just standard OSM format, nothing special about JOSM that way. Of course it would be nice if JOSM documented what it does if thats not the case. Another issue I just noticed in the changes.osm file: You timestamps are probably not conforming. Please don't use microseconds and always use timezone Z. Some programs will, no doubt, parse your file correctly, but others will not. And I hope all those tags are just for experimenting. Tags lastUser and foo make no sense and tag source these days belongs on the changeset, not on the objects. Jochen -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-173-7019282 -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Invisible way
On Mon, 9 Mar 2015, Martijn van Exel wrote: If the file is really incomplete, I don't think JOSM should accept it - or at least not without some kind of warning. The current behavior is ambiguous: it loads the file without any warning or error, and merges with another layer just fine, but it does not display the file (because obviously it does not have enough information.) Or is this because the JOSM file format is not well enough defined? There is nothing on the wiki suggesting a JXML file should contain all existing nodes in a way, or what happens if it doesn't. Should I write a clarification? JOSM can also handle incomplete data sets, where referenced objects are missing. For relations this is obvious. For other types not so much. Anyway that's a feature. :-) But usually it is not recommended to use that feature unless you really know what you are doing. That's why most suggested XAPI/Overpass/API requests include the referenced objects to reduce trouble, but it works without. 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] Invisible way
On Mo, Mär 09, 2015 at 09:10:55 -0600, Martijn van Exel wrote: If the file is really incomplete, I don't think JOSM should accept it - or at least not without some kind of warning. The current behavior is ambiguous: it loads the file without any warning or error, and merges with another layer just fine, but it does not display the file (because obviously it does not have enough information.) Or is this because the JOSM file format is not well enough defined? There is nothing on the wiki suggesting a JXML file should contain all existing nodes in a way, or what happens if it doesn't. Should I write a clarification? JOSM does report those problems, but on STDOUT, maybe you didn't see it. JOSM being a GUI program should probably report it through the GUI though... And it should be obvious that you have to have all nodes needed for a way in the data if you want it to show up properly. Thats just standard OSM format, nothing special about JOSM that way. Of course it would be nice if JOSM documented what it does if thats not the case. Another issue I just noticed in the changes.osm file: You timestamps are probably not conforming. Please don't use microseconds and always use timezone Z. Some programs will, no doubt, parse your file correctly, but others will not. And I hope all those tags are just for experimenting. Tags lastUser and foo make no sense and tag source these days belongs on the changeset, not on the objects. 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] Invisible way
Hey Tod, Vincent and Jochen, Thanks for looking at this also. If the file is really incomplete, I don't think JOSM should accept it - or at least not without some kind of warning. The current behavior is ambiguous: it loads the file without any warning or error, and merges with another layer just fine, but it does not display the file (because obviously it does not have enough information.) Or is this because the JOSM file format is not well enough defined? There is nothing on the wiki suggesting a JXML file should contain all existing nodes in a way, or what happens if it doesn't. Should I write a clarification? 'GraphEnhancer' is our own tool-in-development so consider the bug reported. We will investigate further on our end. On Mon, Mar 9, 2015 at 1:37 AM, Vincent Privat vincent.pri...@gmail.com wrote: This is rather a bug of the software that produces the .osm file (GraphEnhancer 1.0.0), not JOSM. Half the nodes are missing in your file. Please report the bug to them. 2015-03-09 8:25 GMT+01:00 Jochen Topf joc...@remote.org: On So, Mär 08, 2015 at 11:11:15 -0600, Martijn van Exel wrote: I just had a weird experience with a JOSM XML file where some ways are present but not visible on the map. I described the issue in some detail in my diary: https://www.openstreetmap.org/user/mvexel/diary/34521 Before I open a ticket I just want to make sure I am not missing something? I see two problems: 1. Not sure how you generated that base.osm.pbf, but it contains a way without any attributes. If I convert this with osmium to XML I get: way id=813/ with Osmosis I get: way id=813 version=0 timestamp=1970-01-01T00:00:00Z/ 2. My JOSM reports these: INFO: Way -1 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -72 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -65 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -66 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -67 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -68 with 5 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -20 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -22 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -21 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -24 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -36 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -40 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -37 with 4 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -43 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -44 with 7 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -41 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -51 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -50 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -54 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -53 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -64 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -63 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -62 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. I haven't looked farther than this. Not sure any of this explains your problems, but fix them first and we'll see then. 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 -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Invisible way
On So, Mär 08, 2015 at 11:11:15 -0600, Martijn van Exel wrote: I just had a weird experience with a JOSM XML file where some ways are present but not visible on the map. I described the issue in some detail in my diary: https://www.openstreetmap.org/user/mvexel/diary/34521 Before I open a ticket I just want to make sure I am not missing something? I see two problems: 1. Not sure how you generated that base.osm.pbf, but it contains a way without any attributes. If I convert this with osmium to XML I get: way id=813/ with Osmosis I get: way id=813 version=0 timestamp=1970-01-01T00:00:00Z/ 2. My JOSM reports these: INFO: Way -1 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -72 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -65 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -66 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -67 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -68 with 5 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -20 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -22 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -21 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -24 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -36 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -40 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -37 with 4 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -43 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -44 with 7 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -41 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -51 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -50 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -54 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -53 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -64 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -63 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -62 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. I haven't looked farther than this. Not sure any of this explains your problems, but fix them first and we'll see then. 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] Invisible way
This is rather a bug of the software that produces the .osm file (GraphEnhancer 1.0.0), not JOSM. Half the nodes are missing in your file. Please report the bug to them. 2015-03-09 8:25 GMT+01:00 Jochen Topf joc...@remote.org: On So, Mär 08, 2015 at 11:11:15 -0600, Martijn van Exel wrote: I just had a weird experience with a JOSM XML file where some ways are present but not visible on the map. I described the issue in some detail in my diary: https://www.openstreetmap.org/user/mvexel/diary/34521 Before I open a ticket I just want to make sure I am not missing something? I see two problems: 1. Not sure how you generated that base.osm.pbf, but it contains a way without any attributes. If I convert this with osmium to XML I get: way id=813/ with Osmosis I get: way id=813 version=0 timestamp=1970-01-01T00:00:00Z/ 2. My JOSM reports these: INFO: Way -1 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -72 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -65 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -66 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -67 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -68 with 5 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -20 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -22 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -21 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -24 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -36 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -40 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -37 with 4 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -43 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -44 with 7 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -41 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -51 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -50 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -54 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -53 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -64 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -63 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. INFO: Way -62 with 2 nodes has incomplete nodes because at least one node was missing in the loaded data. I haven't looked farther than this. Not sure any of this explains your problems, but fix them first and we'll see then. 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 ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Invisible way
Interesting. You don't even need to load the OSM base layer, just open your change file and play around with it to see what displays and what you can select. Looks like it happens on several different viewing styles, so probably not an issue with a specific display style as such. To make things more confusing to me, when you open the .osm file JOSM seems to renumber all the nodes and ways so when I select something and get info on it and then look at the OSM XML they don't match so it is hard to line up what I see in JOSM with what I see in a text editor. Just loading the change OSM XML file then selecting an area with no data shows a bunch of different values in the tags implying multiple objects selected. But doesn't show which nodes or ways it actually selected. And using the 3 to zoom to selection doesn't work for whatever was selected. I'm not an expert on the OSM XML file format but I've written some scripts that generate that type of file for some of my local (non-OSM) data and your file looks reasonable to me. Looks to me like a couple of bugs in JOSM (display and select). -Tod On Mar 8, 2015, at 10:11 PM, Martijn van Exel wrote: Hey all, I just had a weird experience with a JOSM XML file where some ways are present but not visible on the map. I described the issue in some detail in my diary: https://www.openstreetmap.org/user/mvexel/diary/34521 Before I open a ticket I just want to make sure I am not missing something? Thanks! -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
