Maybe this is a well known limitation, but I'm looking for solution in easy fixing soft turns on segments 1km+. Toolbox now perfectly identifies and fixes shorter segments with soft turns (Q+W). But as WME Validator identifies (example) also larger segments with soft turns, it would be nice for the same solution in this case. Thanks!
https://i59.tinypic.com/wre1ad.png[img]https:///F30V6O[/img][img]https:///MV4Na6[/img]
CM: Latvia; beta editor; Android beta tester.
LV community: Operācija "Meži" - saraujam!
Other communities: Take the challenge! Go green!
CM: Latvia; beta editor; Android beta tester.
LV community: Operācija "Meži" - saraujam!
Other communities: Take the challenge! Go green!
Of course - I can zoom in for every road segment and click on the arrows. But in WME arrows shows only at the first zoom levels. Junction node fixer and now WME Toolbox allows to fix them at higher zoom levels and save time.AlanOfTheBerg wrote:Why don't you just click on the turn arrows when the purple ? icon shows? We've always been able to fix soft turns manually in WME, no need for a script.Atuuu wrote:Maybe this is a well known limitation, but I'm looking for solution in easy fixing soft turns on segments 1km+.
https://i59.tinypic.com/wre1ad.png[img]https:///F30V6O[/img][img]https:///MV4Na6[/img]
CM: Latvia; beta editor; Android beta tester.
LV community: Operācija "Meži" - saraujam!
Other communities: Take the challenge! Go green!
CM: Latvia; beta editor; Android beta tester.
LV community: Operācija "Meži" - saraujam!
Other communities: Take the challenge! Go green!
Checked on widescreen - it works! Thanks!Arnoniem wrote: It's not the length that's limiting, it's just that the entire segment should be on your screen. So if you select one of the nodes, and then zoom out a bit, you can use the good old Q.
https://i59.tinypic.com/wre1ad.png[img]https:///F30V6O[/img][img]https:///MV4Na6[/img]
CM: Latvia; beta editor; Android beta tester.
LV community: Operācija "Meži" - saraujam!
Other communities: Take the challenge! Go green!
CM: Latvia; beta editor; Android beta tester.
LV community: Operācija "Meži" - saraujam!
Other communities: Take the challenge! Go green!
X2. I don't understand why these were taken away when it is a VERY useful tool, and there are so few CMs around since it isn't an automatic upgrade anymore.s18slider wrote:Ok, my next questions is can we make fixing unconfirmed turns and loops features available to something lower then CM? These are issues that all editors deals with. Fixing loops is the feature I miss the most as it is a headache to fix them manually.OyyoDams wrote:Because more and more L5 is not linked to CM, and this is a nonsense to enable CM features based on a level.
Now I have to select EVERY node I want to fix, instead of clicking one button.
MAR LAM (W DC Suburbs)
MS/AR/Atlanta Metro AM
MS/AR/Atlanta Metro AM
I'd still like to see the unconfirmed turn auto fix tool come back for AMs as well. Or go back to the way it was before and make it a L5+ tool.
MAR LAM (W DC Suburbs)
MS/AR/Atlanta Metro AM
MS/AR/Atlanta Metro AM
Bug report: Openstreetmap permalink doesn't work.
The OSM url contains /?lat=<ok>&lon=<ok>&zoom=NaN&layers=M (both beta and stable versions).
With <ok> I mean the proper values.
In WME I'm here while trying: https://www.waze.com/editor/?env=row&lo ... 389&zoom=8
Thanks again for this wonderful tool!
The OSM url contains /?lat=<ok>&lon=<ok>&zoom=NaN&layers=M (both beta and stable versions).
With <ok> I mean the proper values.
In WME I'm here while trying: https://www.waze.com/editor/?env=row&lo ... 389&zoom=8
Thanks again for this wonderful tool!
Francesco
https://i.ibb.co/19CTPvM/f.png
Script: Street Vector Layer (SVL)
"Slack volant, forum manent"
https://i.ibb.co/19CTPvM/f.png
Script: Street Vector Layer (SVL)
"Slack volant, forum manent"
Hi, all the links to external maps (at least G Maps) that I tried are not working at the moment. Tell me if it is reproduceable or you need more details.
Francesco
https://i.ibb.co/19CTPvM/f.png
Script: Street Vector Layer (SVL)
"Slack volant, forum manent"
https://i.ibb.co/19CTPvM/f.png
Script: Street Vector Layer (SVL)
"Slack volant, forum manent"
Hi, I found out that it "collides" with some of my scripts mostly used by the italian community. With the new editor I had to "prepend" instead of "append" something to the permalink bar to make the link visibile, so toolbox doesn't find the permalink where it expects it to be (at the first position).OyyoDams wrote:Hi,bedo2991 wrote:Hi, all the links to external maps (at least G Maps) that I tried are not working at the moment. Tell me if it is reproduceable or you need more details.
They work for me...
Could you change your code to this to retrieve the permalink? It should be equivalent and maybe more robust.
Code: Select all
$('.WazeControlPermalink a.icon-link')[0].href;
Francesco
https://i.ibb.co/19CTPvM/f.png
Script: Street Vector Layer (SVL)
"Slack volant, forum manent"
https://i.ibb.co/19CTPvM/f.png
Script: Street Vector Layer (SVL)
"Slack volant, forum manent"
This error message comes when there are 2 identical city names in a country. This will look something like this:velezss wrote:In the image you can see the message.OyyoDams wrote:
Are you sure of the message ? Toolbox should NOT generate a "WME Toolbox abort" message...
Thanks,
https://www.bellinghausen-online.de/own ... 2&download
You will also get a double proposal when manually entering the city name in WME:
https://www.bellinghausen-online.de/own ... 4&download
Before you ask: no, the two city names are absolutely identical, no extra whitespaces.
This can be solved by either manually changing the city entries of one of the city names, or by requesting for a "Merge city" with the support, using the same current and new city name.
So it's not a Toolbox bug, it's a feature!
In the Toolbox Configuration Panel, I think this caption needs an update:
https://www.bellinghausen-online.de/own ... a&download
https://www.bellinghausen-online.de/own ... a&download
Re: [Script] WME Toolbox (>1.4.2.8)