Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#3568 closed defect (duplicate)

Give visual indication of an exisitng no_u_turn restriction with a way "via" member

Reported by: ponzu Owned by: potlatch-dev@…
Priority: major Milestone:
Component: potlatch2 Version:
Keywords: turn_restrictions, rendering, no_u_turn Cc:

Description

Currently, Potlatch 2 marks a node that's involved in any turn restriction relation with a white circle with a red line. If a turn restriction (specifically, no_u_turn) is created with way as the "via" member, there is currently no visual indication.

I could see it done in one of two ways:

  1. Place the same white circle with read line in the middle of the way that the "via" member (these ways are usually very short).
  1. Place a slightly modified (or even unmodified) circle with red line on the node where "from" way intersects the "via" way.

Either way would be a great improvement over the current situation.

Change History (5)

comment:1 Changed 7 years ago by stevage

If you're interested in helping, you could have a look at the potlatch.css file, and have a go at defining the required style. Also, the 'modified circle' you want should probably be an icon - perhaps you want to have a go at drawing one?

comment:2 follow-up: Changed 7 years ago by Richard

  • Resolution set to duplicate
  • Status changed from new to closed

Essentially the same issue as #3567 so closing as a duplicate.

comment:3 in reply to: ↑ 2 Changed 7 years ago by ponzu

  • Resolution duplicate deleted
  • Status changed from closed to reopened

Replying to Richard:

Essentially the same issue as #3567 so closing as a duplicate.

Not at all a duplicate. #3567 asks to add the editor feature to easily create turn restrictions of a particular kind. This ticket asks to add a visual indicator that a restriction exists. The restrictions can already be created today, though it's not as easy or intuitive as it can be. But there is no visual indication that the restriction is there. The resolution for #3567 and #3568 is different. One can be implemented without the other. As stevage suggested above, the resolution for this ticket most likely lies with the CSS.

comment:4 follow-up: Changed 7 years ago by Richard

  • Resolution set to duplicate
  • Status changed from reopened to closed

Erm, trying to remain polite here, but I am the person implementing this (and am already working on it), so I will be the one who chooses how it is filed. The two will be implemented as one. Please don't reopen this ticket as it will adversely affect the speed with which your issue is resolved. Thank you very much.

comment:5 in reply to: ↑ 4 Changed 7 years ago by ponzu

Replying to Richard:
My apologies. I thought I was being helpful.

Note: See TracTickets for help on using tickets.