Agreed, I always found myself blindly clicking places with the duplicate Google Linked Place after checking the PLAs
They are highlighted, I am usually finding that they are stacked on top of each other.
I assume you mean a linked Google place. It does highlight, in orange, the Places with a duplicate link.
I found the stacked one after the reply above, but it was also highlighting a completely different venue a considerable distance away as well until I got rid of the stacked duplicate.
I think the point is that all the other places with duplicate Google Place links are also highlighted with the same color (also same color is used for places without address). So if you click one place it tells you it’s duplicate, but you don’t know which place it’s because they’re all highlighted. I think the more specific feature request would be when a duplicate Google Place is selected, highlight the offending duplicate, either by changing the duplicate entry’s color to make it more visually obvious, or possibly providing a link in the error message.
I found the real problem, yes, there were two places with duplicated google places, but when I fixed the first one, it removed the highlight from the second one until I reloaded the editor. Simply saving the changes does not appear to update the status of the place.
My first reaction was that there should be a link in the duplicated link message to the Place with the duplicated link. If dbcm doesn’t get to it, I’ll look into this after I wrap up the changelog enhancements.
If I recall, you should be able to just move around on the screen a little bit which will reload the layers or refresh the layers. You shouldn’t have to reload WME.
It does the same thing for multiple issues, like junction issues that have other segment problems.
Not at my computer right now, but I believe it does. Click on the “+” in the left panel I think.
I would like to ask for set up for Czech republic in the “country based config”. We started debate in our local champ group about the WMEMagic configuration. Thanks.
This is an amazing script. Thanks so much for the work on this!
It’s an amazing script, but there’s still place for improvements.
The script tends to mark segments on the map’s edges as “City with only 1 segment”. In all cases that I met there was no problem, as those were segments of a neighbor city. I think the script shouldn’t apply this rule to segments that aren’t completely on screen.
Suggestion: mark places with a street or city name for which either there’re no segments on the map or the segments are far away.
I just lost all my settings. Is this a side effect of version updates?
Sent from my SM-G935P using Tapatalk
Can you confirm the Version Number right now? I have Ω1.0.0.3107126.1498899051 and it shows last updated 6 days ago after I force update in TM. I ask because I was told that the state lock levels for the US should have been released in the last couple days but mine doesn’t seem to be updating and they are not highlighting correct lock levels yet.
I don’t have the correct lock levels showing either.
Mine is also running on the same version you are showing (updated 7 days ago), yet it appears to be highlighting lock levels correctly now, even for roundabouts. I’m wondering if the regional updates are happening behind the scenes, independent of the main script.
EDIT: Well, that’s strange. The mH roundabouts show up as protected (no highlight), yet the MH and PS roundabouts are shown as unprotected (highlighted).
I see Ω1.0.0.3107126.1498899051 updated 6 days ago.
The country configurations are only pulled when there is a new build. A new beta was built this morning and, pending any issues, we are planning a production release tomorrow. When the production release is built, the new configurations will go into effect (enable/disable some options, correct lock levels per state, etc.).
Thanks for the update