I try to run with as few as possible, but ones I run with the following interchangeably :
- Chat Addon
- UR-MP tracking
- WME Geometries
- WME Road Selector (& Highlights)
- WMECH
- WME Snapshot
- URO+
- WME Speedhelper
has big problems, it is unusable.
Not the devs, and not even a representative thereof, but can you provide specifics? To use a Waze analogy, that’s a UR with no text.
Sent from my SAMSUNG-SM-G920A using Tapatalk
I know, but the problems are always the same every time…
Could not save the work, if you can, and if you refresh the page you see the old segments.
If I select a segment I see the old attribute but if I move the map and select again I see the new attribute.
If the problem is repeatable, could you provide a permalink and a description of the problem or how to reproduce it?. It will be much more helpful than just blaming the editor.
-
we could not create junction between primary and ramp: https://www.waze.com/editor/?env=row&lon=11.11757&lat=45.42069&layers=3493&zoom=7&segments=162896332,83582276&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=1&problemsFilter=true&update_requestsFilter=true
-
same here, between 2 ramps: https://www.waze.com/editor/?env=row&lon=11.51467&lat=45.05689&layers=3493&zoom=6&segments=290131315,303027737&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=1&problemsFilter=true&update_requestsFilter=true
-
private with minor e/o primary: https://www.waze.com/editor/?env=row&lon=9.78967&lat=45.68285&layers=3557&zoom=7&segments=303301693&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=1&problemsFilter=true&update_requestsFilter=true
"While you were editing, the elements you’re trying to save have been modified or deleted "
Hi. I’ve had problems with permalinks. When I try to select a lot of segments to get them locked or unlocked I’m finding that clicking the permalink doesn’t result in the segments being selected when zoomed out (e.g. zoom =1) to see the entire set of selected segments. If I alter the link to adjust the zoom level, only the segments that are within the editor window are displayed.
For example (this is in Australia and below I’ve broken the link up so you can see it in this post with *'s.)
*https://www.waze.com/editor/?env=row&lon=149.08041&lat=-35.33036&layers=901&zoom=1&segments=90332967,
*90332983,153641406,302836956,302836959,302836961,302836962,302836963,302836964,
*…
*299090608&update_requestsFilter=true&problemsFilter=true&mapProblemFilter=1&map
*UpdateRequestFilter=1&venueFilter=0
This is not a problem with WME - it is due to the way it works and has always been this way.
As you pan around the map, the segments you can see on the screen (and a little way outside) are cached locally. If you select segments as you are panning, the selected segments remain in your cache. In this way, you can make a permalink containing segments from an almost arbitrarily wide area. When you or another editor opens this permalink in a fresh WME session, the only segments available for selection will be those that are in the local cache - i.e. on-screen or very nearby. Any segments listed in the permalink but outside this area will not be selected.
A similar thing happens with zoom levels. You can select street segments when zoomed in, zoom out to zoom=1 and the streets will remain selected because of the cached data. However, if you create a permalink at zoom=1 and then someone else opens it, the segments will not be selected. This is because, at zoom=1, streets are not loaded into the Roads layer and, again, are not therefore available to be selected.
So the two keys to creating successful permalinks are:
- Only create permalinks containing selected segments that are visible on-screen
- Only create permalinks at a zoom level where the selected segments are normally selectable. This is zoom=4+ for streets
TTS Localization does not work before saving the segment.
Localization works fine once the segment is saved… or if you type in a new name on an existing segment and hit play.
New problems arised today: big black tiles in WME. Seen in France, the Netherlands, Romania, Turkey, Poland. It is so bad it makes editing impossible. Chrome as well as Firefox. It seems to be the Satellite Imagery.
Switzerland too
In Israel too.
USA too.
RIP the Satellite View.
[NOTE] THIS IS NOT MY FAULT. I DIDNT DO IT. 
I want to beleive. :lol:
I have been experiencing a very slow response from WME interface in general, which makes it kind hard to work. At first I thought it was due to my internet connection but then I checked twice and everything else was OK.
Reporting from Guatemala.
SOS message was sent to Waze staff just a minute ago.
Please give them some time to look at this issue.
This is awesome !!!
another glitch in the matrix
:mrgreen:
SOS team never dealt with the WME…hard to believe that they will ever will…