And, TO THEM, it may not matter.qwaletee wrote:I mention this one specifically, because I remember a thread where someone had spoken to Dev, and claimed that Waze said not to worry about it.doctorkb wrote:If you want a reason that really impacts you, then let's say the more geonodes on the screen, the more intensive it is for TB or WMECH to provide highlights in the editor.
The datapoint for the geonode must be stored on the server, so it absolutely takes up space, but that is not an impact on the efficiency of the server (in any significant way).
Rendering, once the tiles have been loaded, they are loaded. "Smoothing" eliminates the majority of geonodes from the app. Again, no significant impact on operation.
Routing, the routing server is simply looking at transit speed/time from endpoint to endpoint as well as junction entry/exit. Geonodes have ZERO impact on the routing server efficiency. The only impact is forced turn instructions produced using micro-doglegs.
*BUT*
The Devs are not editors. Oh, some may do some editing, but I can't imagine one being a very active editor in their spare time when they already spend 10-12 hours a day actually working for Waze.
So no... Geonodes have no impact from a typical Dev's perspective, but that doesn't mean that they have no impact at all.
Re: Toolbox Permissions USA