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

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

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

Postby bz2012 » Sun Nov 18, 2012 12:56 am

Thanks for the info, AND thanks to the author for a very useful tool!
State Manager, Louisiana
bz2012
Map Raider
Map Raider
 
Posts: 1525
Joined: Wed Nov 23, 2011 4:32 pm
Location: Baton Rouge, La
Has thanked: 1418 times
Been thanked: 284 times

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

Postby bz2012 » Sat Nov 17, 2012 12:40 pm

multiple select not working properly.
I am trying to correct a bunch of 'wrong state' segments in an area.
I have 'in screen' and 'state' showing in my segment list.
I select the 'wrong state' segments.
I change them to the right state.
I save the changes.

only ONE SEGMENT gets 'fixed', not the rest.
win7, chrome, wme 1.6.5 (latest I can find).

EDIT: for some reason, it seems to have started working now!
State Manager, Louisiana
bz2012
Map Raider
Map Raider
 
Posts: 1525
Joined: Wed Nov 23, 2011 4:32 pm
Location: Baton Rouge, La
Has thanked: 1418 times
Been thanked: 284 times

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

Postby bz2012 » Thu Nov 08, 2012 4:51 pm

interesting and strange....
I opened chrome's developer tools and the segment list.

I used the segment list to select all zero way roads in the screen,
I changed them to two way and
saved successfully!

I suspect that the tool is ignoring some errors that normally cause the save to fail to save the changed data.

Perhaps this clue will help someone figure out how to fix the extensions so they work normally again.
State Manager, Louisiana
bz2012
Map Raider
Map Raider
 
Posts: 1525
Joined: Wed Nov 23, 2011 4:32 pm
Location: Baton Rouge, La
Has thanked: 1418 times
Been thanked: 284 times

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

Postby bz2012 » Wed Nov 07, 2012 7:08 pm

dave_cairns wrote:Further...

I've just downloaded the old ver: 1.2.2 and it's not mentioned in there either.. something I have noticed however is that there is an "allow all connections" shortcut key - W - listed in the keyboard shortcuts of the new editor (use shift + ? for the full list) - is that what you are referring to?

If not - do you have a copy of one of the .js files that includes it? either a GreaseMonkey version or a Chrome extension? If so could you zip it and PM me please?

Cheers,
Dave.

I think he is referring to the "Allow all drives" (4th button down) that used to change all 'unknown' to two way and set all the intersections (not connected to a 'one-way' segment) to all turns allowed.
After a couple of presses, it would change all one ways that were not locked to two way.

Handy for small towns that have no 'one way streets' and have had little or no WAZE drives, so most of the streets are still set with all turns forbidden. These seem to generate a lot of User Reports because the routing seems to be very poor in such areas.
State Manager, Louisiana
bz2012
Map Raider
Map Raider
 
Posts: 1525
Joined: Wed Nov 23, 2011 4:32 pm
Location: Baton Rouge, La
Has thanked: 1418 times
Been thanked: 284 times

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

Postby bz2012 » Wed Nov 07, 2012 6:57 pm

Aside from the things that don't work yet with the new WME, I noticed a couple of things that probably should NOT be in the Extended Tools set:
OPEN IN >
Cartouche old
...
google map

The link to Cartouche old is no longer useful and
http://www.waze.com/wiki/index.php/Map_ ... Imagery.29
make it clear that we can NOT use google maps.

The link to livemap IS useful and should be kept!
State Manager, Louisiana
bz2012
Map Raider
Map Raider
 
Posts: 1525
Joined: Wed Nov 23, 2011 4:32 pm
Location: Baton Rouge, La
Has thanked: 1418 times
Been thanked: 284 times

Re: Plugin pour Papyrus (Waze Papyrus Extended Tools) update

Postby Brshk1 » Thu Jun 07, 2012 7:35 pm

With the new 1.5.2 version and Chrome I have started to see this problem:
http://www.waze.com/forum/viewtopic.php?f=10&t=20123

I also agree that some options are just too dangerous, 'mass-misediting' tools. And others have been extremely useful, to be fair.

Haven't checked with 1.5.3.
CM Spain|| Nexus 5 / LOS 7.1.2 - rooted || Galaxy J5 (2015) / 6.0.1 Stock || Waze: latest
Image
Más info (Beti berandu!!!).
Movember 2015, por una buena causa..
Brshk1
Global Champs Localizers
Global Champs Localizers
 
Posts: 1887
Joined: Wed Mar 24, 2010 8:38 pm
Location: Durango (ES)
Has thanked: 284 times
Been thanked: 297 times

Re: Plugin pour Papyrus (Waze Papyrus Extended Tools) update

Postby bmitch3020 » Mon Jul 09, 2012 11:42 am

shawndoc wrote:A) What is the scope of segments it shows? I notice is selects a far larger area than what I am looking at (when zoomed in), but smaller that the total area (when zoomed out).


It's whatever Waze has temporarily cached in a javascript object on your browser. At wider zoom levels, only major streets are loaded into this cache. And closer levels, Waze seems to be retrieving tiles of segments. I believe Waze is loading these tiles when you see the "Loading road data..." message.

shawndoc wrote:B) Is there a way to limit the segment list to just those segments that are currently in the window/zoom level? It would be real handy to update some bad neighborhoods, but I don't need to be selecting things way across town. I've set to show "Screen" which gives me 0, 1, or .5 in the screen window.


Create a new landmark over the area you're interested in selecting, highlight the landmark, and then click the "select in landmark" button from the plugin tools. This isn't limiting the segment list, but I think it covers most usage cases for fixing a bad neighborhood.
Brandon
Northern Virginia Area Manager
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

Re: Plugin pour Papyrus (Waze Papyrus Extended Tools) update

Postby bmitch3020 » Wed May 16, 2012 5:39 pm

I'm getting an error where the segment list will stop displaying in various locations. The offending code is on waze.user.js line 683. Apparently seg.getCountry() is now returning undefined for some segments (maybe for the unconfigured segments) so seg.getCountry().name is throwing an exception.
Brandon
Northern Virginia Area Manager
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

Re: Plugin pour Papyrus (Waze Papyrus Extended Tools) update

Postby bmitch3020 » Wed Apr 18, 2012 2:00 pm

alcolo47 wrote:My limits are:
  • Don't interact with server.
  • For edition, change internal datas with Waze functions (or with modified waze function like I done with applySegmentEditDetails)


Alcolo47: Here's a diff of waze.user.js with the new functionality following your limits (which I agree with) for your review:

Code: Select all
waze-plugin$ diff -c waze.user.js  waze.user.bmitch.js
*** waze.user.js   2012-04-18 08:51:05.601002298 -0400
--- waze.user.bmitch.js   2012-04-18 09:53:16.121002764 -0400
***************
*** 500,505 ****
--- 500,521 ----
      return street;
    };
 
+   this.getStreetAlt = function() {
+     var streetAlt;
+     var sids = seg.attributes.streetIDs;
+     var streetAlts = [];
+     if (sids instanceof Array) {
+       for (var i = 0, l = sids.length; i < l; ++i) {
+         if (wazeModel.streets.objects[sids[i]].name) {
+           streetAlts.push(wazeModel.streets.objects[sids[i]].name);
+         }
+       }
+     }
+     streetAlt = streetAlts.join(", ");
+     this.getStreetAlt = returnIt(streetAlt);
+     return streetAlt;
+   };
+
    this.getCity = function() {
      var city;
      var street = this.getStreet();
***************
*** 695,700 ****
--- 711,721 ----
      this.getValue = function(seg) { return seg.getStreet() ? seg.getStreet().name : ""; };
    },
 
+   StreetAlt: function() {
+     this.getName = function() { return "Street Alt"; };
+     this.getValue = function(seg) { return seg.getStreetAlt() ? seg.getStreetAlt() : ""; };
+   },
+
    StreetId: function() {
      this.getName = function() { return "Street id"; };
      this.getValue = function(seg) { return seg.getStreetIdPart() ? seg.getStreetIdPart() : ""; };
***************
*** 805,811 ****
 
  with(ListSegColumns) {
    ListSegColumns.Available = [
!       Country, State, City, Street, StreetId, StreetName,
        Length, Locked, Separator, Level, RoadType, CreatedBy, UpdatedBy, InLndMark,
        NbWays, RoundAbout, AllowNoDirection, FwdSpeed, RevSpeed,
        Select];
--- 826,832 ----
 
  with(ListSegColumns) {
    ListSegColumns.Available = [
!       Country, State, City, Street, StreetAlt, StreetId, StreetName,
        Length, Locked, Separator, Level, RoadType, CreatedBy, UpdatedBy, InLndMark,
        NbWays, RoundAbout, AllowNoDirection, FwdSpeed, RevSpeed,
        Select];
Brandon
Northern Virginia Area Manager
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

Re: Plugin pour Papyrus (Waze Papyrus Extended Tools) update

Postby bmitch3020 » Wed Apr 18, 2012 11:58 am

foxitrot wrote:Would it be possible to add one more column, which would display the segments' "Alt. names:" row (as it is being displayed in WME editor, a.k.a. the Cartouche's concatenated list of the "Alt street:" names)?

You're asking to be able to display this in the "segment list", correct? I think alcolo47 is answering in reference to the "edit properties" box. This may be a relatively easy change since the data should be in the cache to view. Out of curiosity, I'll take a look through the javascript to see if this looks doable.
Brandon
Northern Virginia Area Manager
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: Google Feedfetcher, jm6087, Mattressburn