Changes between Version 1 and Version 2 of Ticket #10955


Ignore:
Timestamp:
2015-01-09T22:31:22+01:00 (11 years ago)
Author:
Don-vip
Comment:

JOSM does not know all required info about this node. If you delete this node from JOSM and save your data to an .osm file you will have this output:

<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.6' upload='true' generator='JOSM'>
  <node id='1409407267' action='delete' timestamp='2011-09-07T22:22:05Z' uid='355242' user='Bryce C Nesbitt' visible='true' version='2' changeset='9241456' lat='37.779177' lon='-122.418272'>
    <tag k='amenity' v='car_sharing' />
    <tag k='capacity' v='1' />
    <tag k='description' v='56 Dr Carlton B Goodlett Place with Toyota Prius Plugin Hybrid' />
    <tag k='name' v='San Francisco/Civic Center: Polk &amp; Grove (Green Vehicle Showcase)' />
    <tag k='operator' v='City CarShare' />
    <tag k='source' v='osmsync:ccs' />
    <tag k='source:pkey' v='192' />
    <tag k='website' v='http://www.citycarshare.org/pod_192.do' />
  </node>
</osm>

The tags might be optional (TBC, I did not test), but the lat, lon and visible attributes are required to make JOSM consider this node as complete.

So you need to update the "Osmsync_CCS" generator to comply with format expected by JOSM.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10955

    • Property Resolutioninvalid
    • Property Status newclosed
  • Ticket #10955 – Description

    v1 v2  
    11The following file when uploaded via JOSM results in an empty change set:
    22{{{
     3#!xml
    34<?xml version='1.0' encoding='UTF-8'?>
    45<osm version='0.6' generator='Osmsync_CCS'>