Opened 12 years ago

Closed 12 years ago

#1349 closed defect (fixed)

Splitting way to add bridge deleted one segment of way

Reported by: jfuredy Owned by: Richard
Priority: major Milestone:
Component: potlatch (flash editor) Version:
Keywords: split break way Cc:


While adding bridge identifiers to a way by adding two nodes, breaking the way at the new nodes, and adding tags to the bridge segment, I noticed that Potlatch had deleted one of the legs of the way. Also, when I hit U to try to undelete, there was no deleted way shown.

A couple of examples are here:

Added bridge to W Pinnacle Peak Rd and Potlatch deleted way West of bridge segment.

Added bridge segment to southbound I-17 road over W Deer Valley Road and Potlatch deleted the segment of I-17 south of the new bridge segment.

And again, there was no way to undelete the segment of way that Potlatch deleted after splitting the way. This editing was done on November 18th, 2008 at around 16:30, according to Potlatch History data.

Hopefully someone can recover these ways, as this was a lot of data that had been updated and verified.

Change History (3)

comment:1 Changed 12 years ago by jfuredy

The problem is definitely recurring, although not 100% of the time. Today (11-19-2008 at ~17:00) I created bridges at approximately 15 locations, and two of them deleted one end of the way that was broken.

The two that were deleted after breaking were: Northbound Loop 202 as it crosses US 60.

Southbound Loop 202 as it crosses Baseline Rd.

In all cases, it appears to leave off the leading end of the way (downstream of the bridge), as defined by the way direction. The starting end (upstream end) of the way does not get deleted.

It also appears that it could have something to do with the length of the way that is being split. The ways that have been deleted have been the longer ways that were split to add bridges. For example, I added four bridges to the stacked interchange of US 60 and Loop 202, and none of the short motorway_link segments were truncated upon breaking the way.

Other places that I added bridges during this session, that did not result in the loss of any portion of the way were: Bridge on Clearview over US60 and bridge on Sossaman over US 60: Bridge on westbound onramp, and bridge on Ellsworth over US 60:

I also just noticed that on Ellsworth Rd when I tried to split the way to create a new bridge segment, Potlatch created a new way for the bridge section, but left the entire Ellsworth way intact, resulting in a duplicate way at the bridge location.

I guess that means I'm done splitting ways to add bridges until I hear that this bug is fixed.

Is there any other way to break ways to create separate segments to call out bridges?

comment:2 Changed 12 years ago by Richard

Owner: changed from richard@… to Richard
Status: newassigned

Right, I see it. In some circumstances, it seems, the split way isn't being marked as 'unclean', therefore isn't being uploaded.

I suspect this happens when you split two ways in quick succession (as you're doing with the bridge), so you're splitting a way even before its first iteration has been returned from the server. This would explain why it shows up on long ways - they take longer to return from the server. I'll fix it asap.

Two possible workarounds for now:

  • when you have split a way once, wait for the "saving data" display to clear before splitting it a second time;
  • alternatively, once you've split the way, look to see if either part retains a negative ID (i.e. isn't uploaded), and if so make some arbitrary change to it and deselect, thereby forcing an upload.

comment:3 Changed 12 years ago by Richard

Resolution: fixed
Status: assignedclosed

Will be fixed with next deployment.

Note: See TracTickets for help on using tickets.