Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
No change to the script (yet), but thanks to a tip-off from Iain I've now identified and fixed a problem in the way I was processing the raw OS data which could cause loss of name data for a whole 1km grid block...

I also took the opportunity to pull in the latest updates from the OS, so as of about 5 minutes ago the server was updated with April 2020 data, all processed using the fixed parsing tool, which 2.60 will start using automatically (though note that you may need to clear your browser caches first to remove any locally cached copies of the older data).
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
Ooh, a new major version... One of the positive side-effects of having to fix the parsing tool last month was that it also allowed me to identify a few performance improvements which significantly reduced the time required to parse the data. In turn, this gave me the opportunity to seriously start investigating an idea I've been sitting on pretty much since WMEOD gained the ability to highlight the primary road network nigh on 6 years ago.

Which was to remove the ability to highlight the primary road network...






...and replace it with the ability to render any of the roads defined in the Open Roads dataset ;) This may be of use when trying to figure out exactly (or at least within the spatial accuracy limits of the OS->WME coordinate system conversion) which path a road takes through a heavily wooded area, or whether that empty field on the edge of a town now contains a new housing estate.

Roads are rendered by their OS classification, which is broadly the same as the segment types in WME.

Caveats:

Whilst Open Roads is comprehensive, it isn't complete - partly due to its half-yearly update cycle and partly by design - so roads which have been recently completed, as well as some access roads/tracks, may not be shown.

Due to the comprehensive nature of the dataset, many of the lesser classification roads (particularly Restricted Access) are not currently present in the Waze map data. Whilst some are genuine omissions (hence why I've made them available in WMEOD), the majority are roads which really don't need to be, or shouldn't be, included in the map data. If someone goes off on a mad mapping spree just because WMEOD suggests there's a bunch of missing roads out there, on their own head be it...

Due to the way the OS data is segmented into 1KM chunks and dynamically loaded/unloaded as you move around the map within WME, there may be occasions when roads fail to render at all - not dissimilar to how WME itself sometimes fails to load a segment tile. It is also likely that segments which span multiple 1KM chunks between junction nodes (e.g. motorways) will sometimes fail to render. Given that the roads where this most often occurs are the ones that are pretty much guaranteed to already be mapped correctly in WME, this isn't a big deal.

Asking WMEOD to render the full gamut of classifications whilst WME is zoomed all the way out in areas with lots of roads will, unsurprisingly, be painfully slow. Though it looks rather nice once it's finished, so it's not all bad...


Oh yes, 3.00 also fixes a long-standing bug in the way altnames are applied to segments without city names (another good spot from Iain).


https://greasyfork.org/scripts/1941-wme-to-os-link
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
atrophicshiner wrote:As always thanks for the massive effort you put into this script.... you can guess what's coming next...

When working on my laptop with the limited screen size of 1440x900, I have previous had issue when WMEOD lists a large number of name suggestions, but this update kinda makes it happen with only a couple of names.
https://i.ibb.co/JrfDgQH/Screenshot-202 ... -53-27.png

The issue being the WMEOD window gets shoved off the top of my map window and I can no longer minimise it. It appears the the bottom of WMEOD has a hard limit of the bottom of the map screen rather than overrunning it. Would it be possible to change this behaviour so the top bar of WMEOD always stays where you drag it and the bottom overruns off the visible screen :?:

This doesn't seem to happen you select a segment for name lookup, but if you minimise WMEOD and then expand again. Still trying to figure out a repeatable procedure.

EDIT: Now with video to show behaviour - download link [2.8MB MOV]
This has also been noted by Iain, and the next update will have some changes to address it. I fear I'm starting to fall into the same trap the WME devs have regarding designing UIs for higher resolution screens and forgetting about users on smaller screened systems, so I'll have to start testing with my browser window reduced in size a bit from now on...
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
Kkervinjones wrote:Very nice change, thank you.

A slight bug that may become an irritant. If you do something that might refresh the map, and with the OSOpenData dropdown closed, the visible map will load in a misaligned version of the Open Roads map, just for the visible view. I've found this mostly happens when you open up street view:



Question, is the overlay supposed to be showing when the OSOpenData dropdown is closed (and the Highlight by Classification is ticked), or are they supposed to show at all times (when it's ticked)?
Yeah, that bug is caused by the Open Roads renderer not paying attention to the minimised state of the WMEOD window and just re-rendering each time the map view changes... That's now been fixed.

Minimising the window has always been treated by the rest of the script as a disable switch, so the Open Roads overlay (or underlay depending on which of the WME layers you're using as a reference point!) is indeed also intended to disappear until the window is maximised again.
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
3.01 brings a bumper crop of fixes and enhancements based on the user feedback obtained in the few days that 3.00 had been available - hadn't realised just how much interest there still was in this script!
  • User preferences storage updated to support the new options/UI state selections.
  • UI rendering now prevents window from being pushed off the top of the WME window.
  • All sections of the UI can now be individually expanded/collapsed to save space when not being used.
  • OpenRoads highlighting now allows the use of bounding boxes instead of polylines. Purple boxes indicate the presence of roads where name/number data is available, cyan boxes indicate the presence of unnamed/numbered roads.
  • Option to enhance the visibility of OpenRoads polylines when underneath the WME road layer.
  • Rendering of lower classification roads is now only made available to L3+ editors to reduce the risk of newbies going on a mad mapping spree...
  • Rendering is now inhibited as expected when the main UI is minimised and the WME view then changes.

Regarding the preferences storage, I've made the deliberate decision not to restore the state of the master enable "Highlight by Classification" checkbox for Open Roads rendering, although the settings of all the other checkboxes within that section will be restored.

The reasoning behind this is to avoid the script being rendered unusable for a potentially extended period of time on startup, if you've selected all the classification filters whilst working on a smaller part of the map, and then reloaded WME into a view which has far more roads needing to be rendered... Forcing users to manually re-enable rendering whenever they reload WME gives them the chance, and the responsibility, to decide for themselves whether they *really* want to ask WMEOD to render all the selected road types within the map area currently visible in WME.


https://greasyfork.org/scripts/1941-wme-to-os-link
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
3.02 allows NameCheck to be enabled without it clearing the road name matches, and the OpenRoads layer now remains visible during map pans, and also when dragging nodes on existing segments.

https://greasyfork.org/scripts/1941-wme-to-os-link
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Post by Twister-UK
3.03 uses dashed lines to display tunnels in polyline mode, no longer omits some polylines/bounding boxes in the corners of the screen, and renders around 30% faster than 3.02.

https://greasyfork.org/scripts/1941-wme-to-os-link
Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png

Twister-UK
Waze Local Champs
Waze Local Champs
Posts: 4671
Answers: 2
Has thanked: 736 times
Been thanked: 4685 times
Send a message
Chris (not to be confused with Chris or Chris, or even Tim, Stu, or any of the other champs team...)
AM SE England & Shetland Islands, UK Local Champ, WME Beta Tester & ScriptMangler
WME/Livemap enhancement scripts @ GreasyFork


https://chizzum.com/greasemonkey/images/beta.pnghttps://chizzum.com/greasemonkey/images/s0400.pnghttps://chizzum.com/greasemonkey/images/c5s.png