Map Editor major ver (Nov 5, 2012) Official Feedback

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: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby wroadd » Sun Nov 11, 2012 10:08 am

The gas station's brand field is fixed...
wroadd
 
Posts: 1839
Joined: Mon Oct 04, 2010 4:35 pm
Location: Szeged,Hungary
Has thanked: 7 times
Been thanked: 24 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby davipt » Sun Nov 11, 2012 9:34 am

AlanOfTheBerg wrote:
davipt wrote:It would be quite heavy on the browser to draw all segments, including the direction arrows, and more importantly the road names and their position on the segment and the angle in vectorial mode. Not impossible though. It's still easier and cheaper to do it once on the server side.

The browser essentially does this now, though it doesn't actually produce the images for the visible road layer. But every road object is loaded from the server which allows us to manipulate that object. The browser is tracking it, panning it, zooming it, etc., with every movement of the map.

I would think we are closer to having the visible road layer rendered completely in the browser that we think. At least, I hope so! :)


No it doesn't, you didn't read me completely ;) Drawing dozens even hundreds of lines is easy. It's the text and the effects (direction arrowst, node circles) hat would not scale. But mainly the text. Unless you want to see most of the road nameless and directionless until you click on it, like the client does now.
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2794
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 287 times
Been thanked: 606 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby bgodette » Sun Nov 11, 2012 7:38 am

There does seem to be a bug in updateModel in the current 771 public version on NA. It will, for causes yet to be determined, decide not to request segment data from the features server.

It's all my phone's fault for using Tapatalk.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3436
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 116 times
Been thanked: 538 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby AlanOfTheBerg » Sun Nov 11, 2012 5:57 am

invented wrote:the app doesn't even update a tile until you route over it so it's pretty moot.

1/2 true. There is also a date associated with tiles and the app is supposed to download nearby tiles even when not routing if they have "expired."
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23614
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4822 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby invented » Sun Nov 11, 2012 5:30 am

AlanOfTheBerg wrote:
mike-bronner wrote:If we're speaking of graphically drawing things out, the browser is already doing this. The server just sends the raw data about the objects (coordinates, basically), then the browser renders everything through SVG data. The selectable road object is actually separate from the road that you see. It is an invisible vector object that gets manipulated as you select it or hover over it.
Because all objects are essentially data, and not graphics, we can create nifty add-ons, like timbones' color hightlights script, that can manipulate segments. :)
The only graphics that the server servers up is the Bing imagery, which comes from Bing servers, so it doesn't present an additional load on the Waze servers.

We are saying the same thing I think. What we see visually for the road layer, is a png, aligned with the actual SVG layer. What I'd like to see is the SVG layer only to be loaded, and have the browser draw the actual visible layer too.

In terms of the browser save causing a tile refresh, that is a capability of the current infrastructure and was one of the major features of the upgrade the US got a few months ago, and the World got this past week.

However, we do not want it to happen this quickly, at least, not so the app can download it right away or by default. Can you imagine a tile being saved 20 times in 5 minutes and the app downloading the tile 20 times? That would crush both the infrastrucutre network bandwidth and kill our data plan limits. :) It may be able to do that, but before we do, we need better, more restrictive default app tile download behavior.
the app doesn't even update a tile until you route over it so it's pretty moot.
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby AlanOfTheBerg » Sun Nov 11, 2012 5:15 am

mike-bronner wrote:If we're speaking of graphically drawing things out, the browser is already doing this. The server just sends the raw data about the objects (coordinates, basically), then the browser renders everything through SVG data. The selectable road object is actually separate from the road that you see. It is an invisible vector object that gets manipulated as you select it or hover over it.
Because all objects are essentially data, and not graphics, we can create nifty add-ons, like timbones' color hightlights script, that can manipulate segments. :)
The only graphics that the server servers up is the Bing imagery, which comes from Bing servers, so it doesn't present an additional load on the Waze servers.

We are saying the same thing I think. What we see visually for the road layer, is a png, aligned with the actual SVG layer. What I'd like to see is the SVG layer only to be loaded, and have the browser draw the actual visible layer too.

In terms of the browser save causing a tile refresh, that is a capability of the current infrastructure and was one of the major features of the upgrade the US got a few months ago, and the World got this past week.

However, we do not want it to happen this quickly, at least, not so the app can download it right away or by default. Can you imagine a tile being saved 20 times in 5 minutes and the app downloading the tile 20 times? That would crush both the infrastrucutre network bandwidth and kill our data plan limits. :) It may be able to do that, but before we do, we need better, more restrictive default app tile download behavior.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23614
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4822 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby mike-bronner » Sun Nov 11, 2012 3:34 am

AlanOfTheBerg wrote:
davipt wrote:.....

It would be quite heavy on the browser to draw all segments, including the direction arrows, and more importantly the road names and their position on the segment and the angle in vectorial mode. Not impossible though. It's still easier and cheaper to do it once on the server side.

The browser essentially does this now, though it doesn't actually produce the images for the visible road layer. But every road object is loaded from the server which allows us to manipulate that object. The browser is tracking it, panning it, zooming it, etc., with every movement of the map.

I would think we are closer to having the visible road layer rendered completely in the browser that we think. At least, I hope so! :)


If we're speaking of graphically drawing things out, the browser is already doing this. The server just sends the raw data about the objects (coordinates, basically), then the browser renders everything through SVG data. The selectable road object is actually separate from the road that you see. It is an invisible vector object that gets manipulated as you select it or hover over it.
Because all objects are essentially data, and not graphics, we can create nifty add-ons, like timbones' color hightlights script, that can manipulate segments. :)
The only graphics that the server servers up is the Bing imagery, which comes from Bing servers, so it doesn't present an additional load on the Waze servers.
mike-bronner
 
Posts: 292
Joined: Tue May 24, 2011 12:21 am
Location: Sheridan, Montana, USA
Has thanked: 0 time
Been thanked: 1 time

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby mssusa » Sun Nov 11, 2012 3:22 am

Loading road images and not the road objects, or vice versa is not a new behavior at all. It has been there for a long time before the last upgrade.
I believe it is a server load problem as I've seen UK editors always complaining about unresponsiveness or missing layers while the editor is working perfectly for me. I've never paid much attention to see if I'm served by the same servers as the UK editors (both before and after the UK got their own servers).

Sent from my GT-I9100 using Tapatalk 2
mssusa
Area Manager
Area Manager
 
Posts: 308
Joined: Wed Jul 27, 2011 7:27 am
Location: Riyadh, Saudi Arabia
Has thanked: 10 times
Been thanked: 2 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby floppyrod84 » Sun Nov 11, 2012 2:36 am

I hope so too.
Sorry if those newer editors are a little peeved, but non-loading images really is nothing new to most of us, and it does seem to happen during high server load and during the tile building process for that same reason.

I look forward to the day that the browser updates the tile image itself when Save is clicked, and the resulting pngs sent back to the server for redistribution to others. Distributed computing is still the way forward imho.

Sent from my GT-I9100P using Tapatalk 2
floppyrod84
 
Posts: 2569
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby AlanOfTheBerg » Sun Nov 11, 2012 1:47 am

davipt wrote:
bz2012 wrote:
davipt wrote:...
"mouse-over shows the roads" data is vectorial data retrieved as json from waze.com/descartes/features. If this fails, you'll get roads images but none will be selectable. And no radars, no problems, none of those.
...


Hm... interesting point that I didn't bring up is that the WME color highlight extension DOES work.

That implies to me that WME could be made more efficient by dispensing entirely with the ROAD images and just using a method similar to the way the WME color highlight extension works.

That could dispense with the need for a LOT network traffic.


It would be quite heavy on the browser to draw all segments, including the direction arrows, and more importantly the road names and their position on the segment and the angle in vectorial mode. Not impossible though. It's still easier and cheaper to do it once on the server side.

The browser essentially does this now, though it doesn't actually produce the images for the visible road layer. But every road object is loaded from the server which allows us to manipulate that object. The browser is tracking it, panning it, zooming it, etc., with every movement of the map.

I would think we are closer to having the visible road layer rendered completely in the browser that we think. At least, I hope so! :)
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23614
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4822 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: vghlycos, WelshJon