As usual, when new version is released, scripts will go haywire.
With this new version of WME, seems like my favorite script here can’t import any KML or geoJSON files anymore (KML/JSON format not supported ). I don’t like importing WKTs because it lacks ability to show actual useful information on the screen.
Will the script be fixed to incorporate the new WME changes?
Waze had updated WME to use a newer version of OpenLayers (to 2.13.1), so this script was refusing to patch in the extra functionality it needs (copied from 2.12).
I’ve updated WME Geometries to v1.4 so it loads the appropriate functions from Cloudflare CDN, for whichever version of OpenLayers WME is using.
This should mean that you should be able to load KML, GML and GPX files again.
I feel like I’m missing something, but I’m not seeing it. I have a .kml file and in the Areas tab, I can upload it and it shows in blue font. However, nothing is showing in WME. I am indeed at the location of the .kml. What am I missing?
Hello,
I have the problem that there is nothing showing up for upload a file…
I am using Firefox 60.0.1 with Greasemonkey and version 1.4 from WME Geometries…
My waze url is… https://www.waze.com/de/editor?lon=…
Any idea how to fix this ?
EDIT: Well with Tampermonkey it seems to work…a notice at the first page of the thread would be good for all script neewbies…
Isn’t working for me in Chrome. Nothing has changed since I first tried back in March.
I’ve turned off all other scripts and Toolbox and reinstalled the script with TamperMonkey several times with no change.
The KML file is imported, but no lines appear on the map, and no new layers are added to the menu.
I have two that I’m trying to use. I had to modify the longitude from the -248° my tracker recorded. :x
Does this script not do gx:Tracks? My file is formatted like this:
...
<gx:Track>
<altitudeMode>absolute</altitudeMode>
<when>2018-03-04T00:04:28Z</when><gx:coord>-248.92865 45.693047 1448.1</gx:coord>
<when>2018-03-04T00:04:29Z</when><gx:coord>-248.92844 45.693047 1448.5</gx:coord>
...
They both work fine in Google Earth after fixing the coordinates to
Should I reformat the coordinates into LineStrings or something?
I mention layers because the (ancient) image on GreasyFork shows each file getting a checkbox in the layers menu. Waze may have broken this at some point but I have a few functional scripts that still manage to make it work.