[Script] WMEOpenData v4.1 (20250803)

Looks like WME v2.206 has broken WME OpenData :frowning:

3.30 restores operation following the latest WME update. As usual whenever WME updates require significant script rewriting, no guarantees are made that everything is working as expected, merely that nothing is obviously broken any more…

https://greasyfork.org/en/scripts/1941-wme-opendata

Frustratingly, over the weekend I became aware of a problem applying names to segments - no idea what’s changed behind the scenes in that part of the native WME UI, but the end result is that when WMEOD tries to alter a segment name, it’ll start off by being able to change the street name but leaves the city name blank, and then if you try to reapply the change it blanks the street name but manages to get the city name set, and then each time you try to reapply thereafter it cycles between these two states of almost but not quite correctness…

There also appears to be some odd interaction between WMEOD and the MTE UI, such that if you try to apply a new segment name after you’ve done any editing of a MTE, WMEOD may end up reopening the MTE UI and trying to alter its address details, rather than opening the segment edit UI as expected. TBH, I’ve no idea if this behaviour is new or has been around for a while without being noticed by anyone, but now I know it’s there I’m going to have to do something about it, providing I can first fix the more pressing issue noted above.

HI Chris, to be honest, the first issue isn’t a recent issue. It’s been going on for a few months. I generally just refresh, and then I’m able to do it (which is the reason I’ve not reported it to you).

Hmm, interesting - I’ve genuinely only noticed it since getting the script up and running again, and for me it doesn’t seem to matter how many times I try coaxing it into applying both names at the same time, it always gets stuck in that one or the other cycle.

3.31 restricts Waze place name suggestions to those within 10km of the present map location, improves the accuracy of gazetteer comparisons, ignores address fields in other parts of the UI (e.g. MTE panel), improves reliability of street name changes, and blocks the script from running within WME Beta.

https://greasyfork.org/en/scripts/1941-wme-opendata

3.32 works again following the latest WME update…

https://greasyfork.org/en/scripts/1941-wme-opendata

It seems it doesn’t work on beta.

None of Twister’s scripts work on Beta now, by design.

:cry:

but I understand why :wink:

Looks like One.Network have had a website re-vamp, now the WMEOpenData link doesn’t take you to the correct location (for me anyway) :frowning:

3.33 restores the one.network integration features…

https://greasyfork.org/en/scripts/1941-wme-opendata

Anyone else finding that WMEOpenData is no longer loading?

3.34 stops the user profile page detection check from being triggered by references to the userscripts tab in the new-style WME URLs…

https://greasyfork.org/en/scripts/1941-wme-opendata

The link to the OS OpenData maps doesn’t seem to load for me anymore :cry:

Working OK for me. I guess it must be system related. I am using Chrome and the current prod WME.

3.35 restores the OS mapping link…

https://greasyfork.org/en/scripts/1941-wme-opendata

Thank you. The benefit of using this .gov.uk website is that clicking on the map gives you the address under he cursor.

I do quite like the new map, but it doesn’t have as many coloured roads as the previous version did. Specifically yellow ones which give a good indication as to whether a road should be a primary street. Has that gone from all existence or have we lost access? If it’s still available, could we have a secondary link on there to take you right to where you are in WME?

That’s one of the 3 display options for sites that embed the OS map, however it’s up to the site designer to choose a) which one they want to use by default and b) whether to make the others available as options.

The previous site I used was essentially set up by the OS themselves as a “this is what you can do with our API” demo, so understandably it made all 3 render modes available. HMG have opted however only to use the mode you see here in their embedded map - for their needs, having the mode which looks more like an OS map isn’t needed, and despite a fair bit of time digging around behind the scenes, I’ve not found a way to coerce it into using it anyway.

So unless we can find another “donor site” that uses/exposes that mode, then this is as good as it gets for now…