Changes between Initial Version and Version 6 of Ticket #6653


Ignore:
Timestamp:
2011-07-30T06:02:32+02:00 (14 years ago)
Author:
rickmastfan67
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6653

    • Property Resolution → othersoftware
    • Property Status new → closed

  • Ticket #6653 – Description

    initial v6  
    11Alright, I have this older (from February) *.osm file that a friend made for me out of the 2010 TIGER data so I could use it to replace/fix/add roads to OSM where necessary locally.
    22
    3 Well, I had been able to open the file with no problems in JOSM up until recently.  It last opened in r4164.  Every release after that, it refuses to open.  When I try to open it in r4172 or r4174, the following message shows up:
     3Well, I had been able to open the file with no problems in JOSM up until recently.  It last opened in r4264.  Every release after that, it refuses to open.  When I try to open it in r4272 or r4274, the following message shows up:
    44{{{
    55Could not read file 'TIGER2010_Allegheny_PA.osm'.
    … …  
    88}}}
    99
    10 Back in r4164 and previous versions, I did notice this when I opened the file in the CL:
     10Back in r4264 and previous versions, I did notice this when I opened the file in the CL:
    1111{{{
    1212Undefined element: 'osmChange' found in input stream. Skipping.
    … …  
    1515But I didn't pay attention to it since it was "skipped".
    1616
    17 Is this something that can be fixed in JOSM to have the file work again, or is there something I should fix in the osm file so that it can be loaded in JOSM versions later than r4164?
     17Is this something that can be fixed in JOSM to have the file work again, or is there something I should fix in the osm file so that it can be loaded in JOSM versions later than r4264?