1.37 supports the new-style WME URLs, sets the correct zoom parameter in the Livemap link, and reduces the script startup time...

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: http://crx.chizzum.com/WMEOpenData.crx

dknight212 wrote:Don't know if this is possible...

...sadly it's all too possible, which means I'm still one impossible task short of earning breakfast at Milliways


1.38 now remembers its minimised/maximised state between sessions

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: http://crx.chizzum.com/WMEOpenData.crx

1.39 uses the November 2013 streetname data, and the June 2013 gazetteer data...

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: http://crx.chizzum.com/WMEOpenData.crx

Bit of an odd one this, took a while before I figured out how to reliably replicate it...

First off, and a bit surprisingly given all the hassles Chrome has given me previously with weird script behaviour, this problem is not Chrome-specific...

Secondly, although performing a streetname lookup changes the script UI in a way which makes it more likely to trigger the problem, the problem can occur with no lookup having been performed.


What's happening is that, if the bottom edge of the WMEOD window is off the bottom edge of the WME viewport when the Send button is clicked, the WME viewport redraw initiated by the send operation causes the view to be shifted vertically by however many pixels are required to bring the bottom edge of WMEOD back into view.

Since the WMEOD window gets taller whenever a streetname lookup is performed, this makes the problem more readily apparent following a lookup, but it can also be forced to occur by manually dragging the window down until it falls off the bottom of the screen even in its smallest state.

What I've also observed is that, if you then drag the WMEOD window back up the screen, or use the minimise icon to collapse it into its titlebar, the WME view automatically realigns itself.


Now I know how to consistently replicate the problem, a fix should hopefully be not too far away...

That's pretty much up to the relevant mapping authorities - if they provide the same quality of data with the same sort of open-use licence as the OS have done for England, Wales and Scotland, then I'd certainly be interested in integrating it into WMEOD.

Version 2.0 integrates the OpenData FullHeight and Canaries Map Tracker helper scripts, fixes a lat/lon problem with the Canaries mapping site, and eliminates an illegal data access problem when editing outside of the UK.

It also marks the debut of WMEOD on the Chrome Web Store. Users who've got an earlier CRX version installed should remove that before installing 2.0.

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: https://chrome.google.com/webstore/deta ... mdbdnmcfei

Good point, forgot to mention that anyone who's got the OpenDataFullHeight and/or Canaries Map Tracker scripts installed should remove those when upgrading to WMEOD 2.0. Chrome users should also remove the main script and replace it with the webstore version, whereas Firefox users can do an in-place update.

CTCNetwork wrote:Had some contact the the Irish equivalent of OS and there is a cost implication for access. They are working on public release but don't anticipate anything before a couple of years!

Thanks for the info. Was this OSNI or the equivalent in the Republic?

The latest WME Beta seems to be causing problems with positioning of the WMEOD UI, trapping it in the narrow band across the top of the screen rather than allowing it the freedom of the whole WME viewport, and as with URO+ I'll be rolling out a fix for this soon...

I wonder if the checklist for each beta release goes something like this:

• Add snazzy new features that we think are indispensable
• Leave out features everyone has been begging us to include since the dawn of time
• Tweak the UI once again so all the wiki screengrabs have to be redone
• Randomly alter the code/page structure in such a way to break Twister-UK's scripts without actually changing how WME itself behaves
• (Optional extra) Add in extra changes to the internal beta version and then promote it directly to production status without first releasing it for public beta testing, or indeed without apparently performing even the most trivial of in-house testing either...

2.1 restores compatibility with WME beta, and fixes various UI styling/layout glitches caused by the latest CSS tweaks across all of the Waze site...

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: https://chrome.google.com/webstore/deta ... mdbdnmcfei