iainhouse wrote:You're probably aware, but OpenData isn't working too well since the WME update.
I'm surprised you're getting any sort of functionality out of it at the moment, because it's not working at all for me since the update... Given the relative sizes of their userbases, fixing URO+ is my priority at the moment, so fixing WMEOD is likely to start at some point over the weekend.
iainhouse wrote:I'm seeing several errors in the console like "WMEOpenData: Current name was set 140m away from segment location". I've tried experimenting with relative positioning of the OpenData window and the segment and the segment within the WME window, without coming to any conclusions.
That's diagnostics data, not an error message - WMEOD requires you to reselect the city name once you start editing a segment more than 1000 metres away from the point at which you last selected it, those messages are indicating how far away the currently selected segment is from that point.
iainhouse wrote:I also hate to resurrect an old problem, but I'm still experiencing considerable performance issues with OpenData when editing in dense urban areas - to the extent that I find I'm regularly having to disable/enable it from the Extensions tab. Might it be possible to add an on/off switch so I can turn it off without checking extensions & then permalinking/refreshing?
Once I get it back into a fully operational state I'll have a look at performance again.