Landmark Database Size Reduction
In two other threads http://www.waze.com/forum/viewtopic.php ... rk#p422710 and http://www.waze.com/forum/viewtopic.php ... rk#p425980, skbun discusses the very large size of some of the major landmarks due to the very high number of nodes defining the landmark.
The recommendation is to consider reducing the number of nodes for some of these landmarks by either redrawing them and deleting the old one, or deleting some (or many) of the nodes to still give the landmark its basic outline, but not have it provide meter-by-meter granularity.
I wanted to start this thread focused on this topic since there are some huge water landmarks with a high degree of detail (too many nodes) around the country. One example is the San Francisco Bay and delta areas.
1. Do we know if each time an editor moves their screen view the browser has to reload all those datapoints?
2. Are all the datapoints for a landmark loaded at once even if they are off the screen?
3. Does it reload after every save even if the screen location does not move?
The recommendation is to consider reducing the number of nodes for some of these landmarks by either redrawing them and deleting the old one, or deleting some (or many) of the nodes to still give the landmark its basic outline, but not have it provide meter-by-meter granularity.
I wanted to start this thread focused on this topic since there are some huge water landmarks with a high degree of detail (too many nodes) around the country. One example is the San Francisco Bay and delta areas.
1. Do we know if each time an editor moves their screen view the browser has to reload all those datapoints?
2. Are all the datapoints for a landmark loaded at once even if they are off the screen?
3. Does it reload after every save even if the screen location does not move?
Re: Landmark Database Size Reduction