Ssshhh I need sleep!
Sent from my GT-N7100 using Tapatalk
Actually, thatās probably one of the same problems I fixed in the latest URO release - Iād forgotten WMEOD plays with the livemap linkā¦ Iām guessing you saw this in the beta?
Iāve not been using the beta for a while, mainly as Iām trying to do some intense work and all the fudges keep getting in the way.
The IP for my shared server was changed yesterday, so now we just have to wait for that change to propagate across the DNS serversā¦ Everything should be up and runnng again āsoonā (and hopefully thatās a real-world soon as opposed to a Waze-type soon 
)
The best tools are those that are almost impossible to live without.
Hi,
Is it me? This doesnāt seem to be working for me atm. Al I have is āLoading new OS dataā¦ā
I have added both:
https://www.waze.com/en-GB/editor/* and
https://www.waze.com/editor/*
as included pagesā¦
Des. . .
No not just you. I was a little premature in saying it was fixed (about 8 posts up).
Sent from my GT-N7100 using Tapatalk
This is getting tediousā¦ 24 hours after being told itād take a couple of hours to resolve, routing to my domain is still borked, and a follow-up ticket has been raised. Oh well, at least they didnāt say itād be fixed āsoonā.
The delay will be your computerās cache or the DNS server of your ISP
Iāve prodded opendns for you so anyone using that service for DNS will get routed ok.
On your PC you can start > run > cmd > ipconfig /flushdns
For Ubuntu Linux some help is here:
http://ubuntuhandbook.org/index.php/2013/07/flush-dns-cache-ubuntu-13-04-12-10/
I think you should also close your browser first.
Iād been checking the routing via Virgin cable and EE mobile, plus via a handful of online traceroutes around the world, and all of them were failing in the same way, so whatever was causing the delay doesnāt appear to have been my local DNS cache (which Iād wiped as part of this testing anywayā¦).
Anyhoo, whether it was the result of prodding my hosting company again or purely coincidental, routing now seems to be up again - I can reach my server both from my phone and from my work PC, and the online traceroutes are also able to find it OK. So fingers crossed weāre back in business.
All is now right with the world again.
Now that the production WME is using the same codebase as the recent beta, 2.2 is required to allow the livemap link to be updated according to the current editing locationā¦
Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: https://chrome.google.com/webstore/detail/wme-opendata/hjkehljinhkehammgkkhabmdbdnmcfei
Thanks Chris. Chrome WS is offering v2.1 currently
I just downloaded 2.2 from the Web Store - although it did say I already had it installed. I had to delete 2.1 from the extensions tab and then re-add from the WS.
Thanks. Took a couple of mins to sync I suppose (āDetailsā tab on WS shows the version)
2.3 restores operation in the latest WME Beta
Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: https://chrome.google.com/webstore/detail/wme-opendata/hjkehljinhkehammgkkhabmdbdnmcfei
Itās that time of the year againā¦ the OS have just released the latest update to their streetname dataset, so expect a corresponding WMEOD update āsoonā (i.e. just as soon as I get the raw data downloaded, pummelled into shape, and copied onto my server)
Could you elaborate in newbie language haha
Sent from my GT-I9505 using Tapatalk
WMEOD is a script I wrote to search the Ordnance Survey street and place name data for possible matches when a road segment is selected in WME. Every 6 months the OS release an updated copy of the street name data, and the latest update arrived at some point in the last few daysā¦ In order for WMEOD to use the data, it first needs to be processed to chop up the single UK-wide data file into smaller chunks that the script can handle, then uploaded to my server so the chunks can be accessed by the script.