Modify

Opened 13 years ago

Last modified 5 years ago

#7443 new defect

JOSM claims that there are incomplete nodes in a way when there isn't when updating

Reported by: rickmastfan67 Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: Cc:

Description

Steps to reproduce:

  1. Download a small area ( try: http://api.openstreetmap.org/api/0.6/map?bbox=-80.1377106,41.7159803,-80.1268959,41.7209775 )
  2. Select any of the ways that only have 2 nodes in the downloaded area.
  3. File > Update Selection

What happens:
Look at the Java console and notice the following message: "Way {way id here} with 2 nodes has incomplete nodes because at least one node was missing in the load data." After that, you see a request for the two nodes in the way.

What should happen:
JOSM shouldn't be telling you that there are incomplete nodes in the first place in the console because you do already have both nodes for the way downloaded and displayed on the screen as you had just downloaded that area. JOSM also shouldn't need to re-request those nodes in the first place as long as they hadn't been modified.

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2012-02-23 02:32:36
Last Changed Author: akks
Revision: 5018
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2012-02-22 19:54:15 +0100 (Wed, 22 Feb 2012)
Last Changed Rev: 5018

Identification: JOSM/1.5 (5018 en)
Memory Usage: 263 MB / 2730 MB (166 MB allocated, but free)
Java version: 1.6.0_31, Sun Microsystems Inc., Java HotSpot(TM) 64-Bit Server VM
Operating system: Windows 7
Dataset consistency test: No problems found

Plugin: OpeningHoursEditor (27852)
Plugin: buildings_tools (27865)
Plugin: imageryadjust (27865)
Plugin: licensechange (27888)
Plugin: mapdust (27884)
Plugin: measurement (27852)
Plugin: openstreetbugs (27852)
Plugin: reverter (27865)
Plugin: turnrestrictions (27891)
Plugin: undelete (27852)
Plugin: utilsplugin2 (27865)

Attachments (0)

Change History (2)

comment:1 by skyper, 13 years ago

See also #7437 and #4663.

If you run "update data", JOSM checks the whole bounding boxes for modifications , e.g. it querries all local objects. It does this cause the objects might have been changed by other users. Use "update modified" or "update selected" if you only want to update certain objects but be aware that in order to update a way its nodes have to be checked.

Last edited 13 years ago by skyper (previous) (diff)

comment:2 by mdk, 5 years ago

Actually (r15591) I couldn't reproduce the problem. In the mentioned download area are 6 vertical ways witch I can Update one by one or all together without problems.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to rickmastfan67.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.