GizmoGuy411 wrote:Noticed tonight that the select when using a landmark did not select everything correctly within the landmark.

Jenn, would you be so kind to pass these issues along?

You can report it via the project page here. (I just reported the bug about the "open in" functions.)

RallyChris wrote:Where do you download the current version? The project page has the only download listed as depreciated and has an upload date of October.

Here.

jenncard wrote:New version and new link to Chrome extension...

And the "open in..." functions work again. Laissez les bon temps rouler!

harling wrote:

jenncard wrote:New version and new link to Chrome extension...

Hey, the "open in..." functions work again. Laissez les bon temps rouler!

Rats: the road segment table wouldn't open in FF9/Linux. It opened on the first try in FF10/Win7--and I haven't been able to get it to reappear since. And now the tools don't even show in FF10/WIn7 any more, only in FF9/Linux. Why is this script so unstable?!

alcolo47 wrote:For merging: because geometry the two one-way segments may be different (different path-point numbers), its very difficult to compute the "average segment", then the simpler is to use one of them as e result segment.

Or use one of the merging strategies posted elsewhere on the Waze forum, that reportedly preserve road speed data for both directions.

For spliting: I can compute the global axis vector (between the two extremity) and create another one-way segment with a translation perpendicularly to the global axis of 5 meters.

Please, for the sake of all that is good, right and just, do not implement a splitting feature! If ever there were a feature that would reward editors with massive amounts of points for seriously degrading the Waze map, that would be it.

Swap steps 5 & 6.

Once the Edit Properties box has appeared, you have to de-select the segments before changing their properties.

I don't think the JavaScript version works in Chrome - at least for the later versions of the script. There was a .crx download, which is, I think, a packaged version for Chrome, but the very latest version of the Extended Tools wasn't available like that.

Musical Chairs is useful - inasmuch as it gives a visual representation of Ordnance Survey OpenData (which is allowable) over the top of OSM (which isn't). This means you can use it - as long as you ignore the OSM part of the display.

Twister_UK's WME to OS link script is more useful, because it overlays the OS OpenData boundary boxes directly over the WME map.

However I stongly suspect none of the OS data will be of much use to you down under. I don't think Ordnance Survey does much mapping down your way! The OS OpenData viewer won't zoom out further than England & Northern Ireland

WME Ext. tools V1.3.6.1

Tells me under 'Segment List' that Canadian roads are set to "USA" under "Cntry". This is not the case.

When i try to install WME tools now, Chrome pops up a warning saying that extensions can only be added through the Chrome store??