WME - Extended Tools (fka Plugin pour Papyrus) - English

[invented]

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

[alcolo47]

Chrome have change its security policy.
I'm looking for a solution.

But, This pluging have problems with chrome, use Firefox with greasemonkey instead.

[alcolo47]

Google chrome have changed its extensions installation right policies, then now, to install the plugging for Chrome, you have to give authorization.

For windows add the regitry key:
HKEY_CURRENT_USER\Software\Policies\Google\Chrome\ExtensionInstallSources\1 = "https://waze-papyrus-extended-tools.googlecode.com/svn/ChromeInstall/*"

or use this .reg file:
https://waze-papyrus-extended-tools.googlecode.com/svn/ChromeInstall/WME-extended-tools%20-%20Windows%20Chrome%20autorization.reg

For other platforms, take a look at: http://www.chromium.org/administrators/policy-list-3#ExtensionInstallSources

The other solution is to integrated this extension into the goggle store. But I don't want this.

[khaytsus]

I'm sure there's some correct sauce of filenames and paths to make this work on Linux but I gave up after trying several times...

Download the crx file (svn, view file, raw view, it should download) then display the Chrome Extensions page, launch a file manager like Thunar and drag the crx file into the Extensions window.

If someone figures out how to make a proper json file to allow this, please post the info.

[harling]

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.

[scruffy151]

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.

I agree, splitting/unsplitting should be difficult so that borderline roads don't get changed back and forth continually.

[tgfathergoose]

I just had to add the tools to Chrome. What I did was to save the file using Firefox. Once done, select the wrench, go to Tools Extensions. Drag and drop the file in there.

That said, though, I'm going to have to look this over (once the server comes back) to see what the tools actually do. I may resort to Firefox if the tools don't work in Chrome.

[alcolo47]

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.

Yes I know this method, I'm speaking here only of geometry point of view. For the average speed, I have to implement the serial/join method, and after I have to change the geometry of the result according to my previous conversation.

I just had to add the tools to Chrome. What I did was to save the file using Firefox. Once done, select the wrench, go to Tools Extensions. Drag and drop the file in there.

That's works, but not the auto-update.
You can save the file with Chrome itself (without FF), just go to the directory of the file, right-click on WME-extended-tools.crx file and save the link under ...

[LittlestLou]

So, after reading all 18 pages w/o success, can someone just explain each tool or send me to where this info is already available? I primarily use the Segment List to identify problems with missing/incorrect city/state names but still update each segment individually. I am not interested in "mass-editing" but would like these items explained in plain English (not a slight to French, just mean non-technical). Thanks!

[foxitrot]

"Segment list": it is not possible to sort according to the first (i.e. the leftmost) column (it actually never was, IIRC), other text columns sort correctly.

If I change the column order (using "Choose displayed columns"), again the new leftmost column does not allow to sort the list, other columns work fine.