Geometry point in WME between starting and ending node

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

Geometry point in WME between starting and ending node

Postby AndyLaode » Sun Apr 05, 2015 11:07 am

Dear all

I would like to ask, is the road geometry, I mean the little dot between the start and ending node, has any connection with the amount of data downloaded in the app?

My meaning is like this. If the road is curvy between starting and ending node, we have to add “the little dot” to make the segment curvy. However my friend said, as an editor, do not add too many “little dot” because later the app will download more data to display the road into their gadget (phone, tablet, etc)

Appreciate if someone can answer this and bring light to me..

Warmest regards
Andy.
andylaode (andylaode@outlook.com)
okay, mate, see you on the road and on the map too, cheers
AndyLaode
Waze Local Champs
Waze Local Champs
 
Posts: 756
Joined: Mon May 19, 2014 9:04 am
Location: on my way from my house to insanity
Has thanked: 13 times
Been thanked: 246 times

Re: Geometry point in WME between starting and ending node

Postby citeman » Sun Apr 05, 2015 5:10 pm

Andy,
Yes more geometry nodes, technically make the Waze servers and mobile devices work harder. Think of it this way: the code to describe a single line only takes two end points; but by adding a geometry node in the middle, you need to code three points (each end and the middle). Therefore, it is best practice to limit the use of geometry nodes when practical.


Sent from my iPhone using Tapatalk
- CITEMAN
Remember to keep Wazing!

[ img ] [ img ]
Closure & Restrictions Fanatic
citeman
State Manager
State Manager
 
Posts: 730
Joined: Tue Dec 03, 2013 3:02 am
Location: Long Beach, CA
Has thanked: 916 times
Been thanked: 308 times

Re: Geometry point in WME between starting and ending node

Postby AlanOfTheBerg » Mon Apr 06, 2015 4:38 pm

That doesn't mean to make roads look chunky and clunky, but to describe a nice curve on a 45mph you don't need a geometry node every meter.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
 
Posts: 23622
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1109 times
Been thanked: 4853 times

Re: Geometry point in WME between starting and ending node

Postby AndyLaode » Mon Apr 06, 2015 5:25 pm

I agree with Alan, I can’t have the road look chunky on the app.

I get citeman point also

The things I want to ask is, is the geometry point makes a different so much in term of data downloaded? Because as I recall, round about consist of a lot geometry point to make it look round.

In the road that span for let say 50 meter in some village in Indonesia, the road is curvy. The things is: 1. Internet connection is poor (EDGE or GPRS), 2. The road is curvy.

I need to have a curvy road to let the driver know where are they now when they are driving, chunky is not an option, but my friend warn me about data consumption as I disagree with him. In my opinion, to load the road with a lot of or only a few geometry point, it is not so much different in data. Any opinion?
andylaode (andylaode@outlook.com)
okay, mate, see you on the road and on the map too, cheers
AndyLaode
Waze Local Champs
Waze Local Champs
 
Posts: 756
Joined: Mon May 19, 2014 9:04 am
Location: on my way from my house to insanity
Has thanked: 13 times
Been thanked: 246 times

Re: Geometry point in WME between starting and ending node

Postby AlanOfTheBerg » Mon Apr 06, 2015 5:54 pm

andylaode wrote:Any opinion?

Keep in mind, we are also talking about storage space in the database as well as image rendering optimization. Fewer is better, as long as you are adequately showing the curve. Here's a local I example I found with too many geometry points. This is a 278m segment.

In WME, it looks nice:
[ img ]

Here's how many geometry nodes are used:
[ img ]

In my opinion, that is too many. You can still get a good image of the curve with fewer nodes:
[ img ]

In WME, it still looks pretty good with almost 1/2 the number of nodes:
[ img ]


The final curve is still truly curved and will clearly show as such in the app.

I would like to see a screenshot from you of a "50m" segment which has such curves the driver needs to be aware of.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
 
Posts: 23622
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1109 times
Been thanked: 4853 times

Re: Geometry point in WME between starting and ending node

Postby AndyLaode » Tue Apr 07, 2015 7:39 am

sorry for late reply..

yeah allan, i follow your suggestion..

take a look at this example

https://www.waze.com/editor/?env=row&lo ... ,276463928

this one more curvy
andylaode (andylaode@outlook.com)
okay, mate, see you on the road and on the map too, cheers
AndyLaode
Waze Local Champs
Waze Local Champs
 
Posts: 756
Joined: Mon May 19, 2014 9:04 am
Location: on my way from my house to insanity
Has thanked: 13 times
Been thanked: 246 times

Re: Geometry point in WME between starting and ending node

Postby mikupoiss » Sun Apr 12, 2015 7:17 pm

Late bump, but... during a Waze Cafe few months ago we were told that the middle node's have almost zero effect on connection or server load.
mikupoiss
Area Manager
Area Manager
 
Posts: 844
Joined: Mon Aug 11, 2014 8:09 am
Location: Tallinn, Estonia
Has thanked: 172 times
Been thanked: 110 times

Re: Geometry point in WME between starting and ending node

Postby AlanOfTheBerg » Mon Apr 13, 2015 12:52 am

mikupoiss wrote:Late bump, but... during a Waze Cafe few months ago we were told that the middle node's have almost zero effect on connection or server load.

You believe them?

The following segments are the same length. One has four geometry nodes. The other, 260.
Screen Shot 2015-04-12 at 5.48.43 PM.png
(30.21 KiB) Downloaded 888 times


Screen Shot 2015-04-12 at 6.00.51 PM.png
(40.02 KiB) Downloaded 887 times


They both are basically the same. Except how much data the 260-node one uses in the database. The following list of geometry nodes is used in the 260-node version. Each geometry node must be fully described to order to create the segment. The last geometry point at the bottom I opened up to show the data required inside each one.

There is no way that I will believe that there is zero performance impact of trying to draw or simplify one versus the other.

So, this is an extreme example, but the impact of 10,000 extra geometry nodes across 5000 segments can be a lot. This is just 256 extra geometry nodes.

Code: Select all
OL.Class.initialize {attributes: Object, type: "segment", model: OpenLayers.Class.initialize, nested: Object, initialize: function…}
attributes: Object
geometry: n
bounds: OpenLayers.Bounds.OpenLayers.Class.initializecomponents: Array[260][0 … 99]0: OpenLayers.Geometry.Point.OpenLayers.Class.initializebounds: OpenLayers.Bounds.OpenLayers.Class.initializeid: "OpenLayers.Geometry.Point_528"parent: nx: -12712693.833959y: 5249619.753600899__proto__: i1: OpenLayers.Geometry.Point.OpenLayers.Class.initialize2: OpenLayers.Geometry.Point.OpenLayers.Class.initialize3: OpenLayers.Geometry.Point.OpenLayers.Class.initialize4: OpenLayers.Geometry.Point.OpenLayers.Class.initialize5: OpenLayers.Geometry.Point.OpenLayers.Class.initialize6: OpenLayers.Geometry.Point.OpenLayers.Class.initialize7: OpenLayers.Geometry.Point.OpenLayers.Class.initialize8: OpenLayers.Geometry.Point.OpenLayers.Class.initialize9: OpenLayers.Geometry.Point.OpenLayers.Class.initialize10: OpenLayers.Geometry.Point.OpenLayers.Class.initialize11: OpenLayers.Geometry.Point.OpenLayers.Class.initialize12: OpenLayers.Geometry.Point.OpenLayers.Class.initialize13: OpenLayers.Geometry.Point.OpenLayers.Class.initialize14: OpenLayers.Geometry.Point.OpenLayers.Class.initialize15: OpenLayers.Geometry.Point.OpenLayers.Class.initialize16: OpenLayers.Geometry.Point.OpenLayers.Class.initialize17: OpenLayers.Geometry.Point.OpenLayers.Class.initialize18: OpenLayers.Geometry.Point.OpenLayers.Class.initialize19: OpenLayers.Geometry.Point.OpenLayers.Class.initialize20: OpenLayers.Geometry.Point.OpenLayers.Class.initialize21: OpenLayers.Geometry.Point.OpenLayers.Class.initialize22: OpenLayers.Geometry.Point.OpenLayers.Class.initialize23: OpenLayers.Geometry.Point.OpenLayers.Class.initialize24: OpenLayers.Geometry.Point.OpenLayers.Class.initialize25: OpenLayers.Geometry.Point.OpenLayers.Class.initialize26: OpenLayers.Geometry.Point.OpenLayers.Class.initialize27: OpenLayers.Geometry.Point.OpenLayers.Class.initialize28: OpenLayers.Geometry.Point.OpenLayers.Class.initialize29: OpenLayers.Geometry.Point.OpenLayers.Class.initialize30: OpenLayers.Geometry.Point.OpenLayers.Class.initialize31: OpenLayers.Geometry.Point.OpenLayers.Class.initialize32: OpenLayers.Geometry.Point.OpenLayers.Class.initialize33: OpenLayers.Geometry.Point.OpenLayers.Class.initialize34: OpenLayers.Geometry.Point.OpenLayers.Class.initialize35: OpenLayers.Geometry.Point.OpenLayers.Class.initialize36: OpenLayers.Geometry.Point.OpenLayers.Class.initialize37: OpenLayers.Geometry.Point.OpenLayers.Class.initialize38: OpenLayers.Geometry.Point.OpenLayers.Class.initialize39: OpenLayers.Geometry.Point.OpenLayers.Class.initialize40: OpenLayers.Geometry.Point.OpenLayers.Class.initialize41: OpenLayers.Geometry.Point.OpenLayers.Class.initialize42: OpenLayers.Geometry.Point.OpenLayers.Class.initialize43: OpenLayers.Geometry.Point.OpenLayers.Class.initialize44: OpenLayers.Geometry.Point.OpenLayers.Class.initialize45: OpenLayers.Geometry.Point.OpenLayers.Class.initializebounds: OpenLayers.Bounds.OpenLayers.Class.initializeid: "OpenLayers.Geometry.Point_573"parent: nx: -12712502.592097014y: 5249619.081791053__proto__: i46: OpenLayers.Geometry.Point.OpenLayers.Class.initialize47: OpenLayers.Geometry.Point.OpenLayers.Class.initialize48: OpenLayers.Geometry.Point.OpenLayers.Class.initialize49: OpenLayers.Geometry.Point.OpenLayers.Class.initializebounds: OpenLayers.Bounds.OpenLayers.Class.initializeid: "OpenLayers.Geometry.Point_577"parent: nx: -12712492.841523953y: 5249618.591929724__proto__: i50: OpenLayers.Geometry.Point.OpenLayers.Class.initialize51: OpenLayers.Geometry.Point.OpenLayers.Class.initialize52: OpenLayers.Geometry.Point.OpenLayers.Class.initialize53: OpenLayers.Geometry.Point.OpenLayers.Class.initialize54: OpenLayers.Geometry.Point.OpenLayers.Class.initialize55: OpenLayers.Geometry.Point.OpenLayers.Class.initialize56: OpenLayers.Geometry.Point.OpenLayers.Class.initialize57: OpenLayers.Geometry.Point.OpenLayers.Class.initialize58: OpenLayers.Geometry.Point.OpenLayers.Class.initialize59: OpenLayers.Geometry.Point.OpenLayers.Class.initialize60: OpenLayers.Geometry.Point.OpenLayers.Class.initialize61: OpenLayers.Geometry.Point.OpenLayers.Class.initialize62: OpenLayers.Geometry.Point.OpenLayers.Class.initialize63: OpenLayers.Geometry.Point.OpenLayers.Class.initialize64: OpenLayers.Geometry.Point.OpenLayers.Class.initialize65: OpenLayers.Geometry.Point.OpenLayers.Class.initialize66: OpenLayers.Geometry.Point.OpenLayers.Class.initialize67: OpenLayers.Geometry.Point.OpenLayers.Class.initialize68: OpenLayers.Geometry.Point.OpenLayers.Class.initialize69: OpenLayers.Geometry.Point.OpenLayers.Class.initialize70: OpenLayers.Geometry.Point.OpenLayers.Class.initialize71: OpenLayers.Geometry.Point.OpenLayers.Class.initialize72: OpenLayers.Geometry.Point.OpenLayers.Class.initialize73: OpenLayers.Geometry.Point.OpenLayers.Class.initialize74: OpenLayers.Geometry.Point.OpenLayers.Class.initialize75: OpenLayers.Geometry.Point.OpenLayers.Class.initialize76: OpenLayers.Geometry.Point.OpenLayers.Class.initialize77: OpenLayers.Geometry.Point.OpenLayers.Class.initialize78: OpenLayers.Geometry.Point.OpenLayers.Class.initialize79: OpenLayers.Geometry.Point.OpenLayers.Class.initialize80: OpenLayers.Geometry.Point.OpenLayers.Class.initialize81: OpenLayers.Geometry.Point.OpenLayers.Class.initialize82: OpenLayers.Geometry.Point.OpenLayers.Class.initialize83: OpenLayers.Geometry.Point.OpenLayers.Class.initialize84: OpenLayers.Geometry.Point.OpenLayers.Class.initialize85: OpenLayers.Geometry.Point.OpenLayers.Class.initialize86: OpenLayers.Geometry.Point.OpenLayers.Class.initialize87: OpenLayers.Geometry.Point.OpenLayers.Class.initialize88: OpenLayers.Geometry.Point.OpenLayers.Class.initialize89: OpenLayers.Geometry.Point.OpenLayers.Class.initialize90: OpenLayers.Geometry.Point.OpenLayers.Class.initialize91: OpenLayers.Geometry.Point.OpenLayers.Class.initialize92: OpenLayers.Geometry.Point.OpenLayers.Class.initialize93: OpenLayers.Geometry.Point.OpenLayers.Class.initialize94: OpenLayers.Geometry.Point.OpenLayers.Class.initialize95: OpenLayers.Geometry.Point.OpenLayers.Class.initialize96: OpenLayers.Geometry.Point.OpenLayers.Class.initialize97: OpenLayers.Geometry.Point.OpenLayers.Class.initialize98: OpenLayers.Geometry.Point.OpenLayers.Class.initialize99: OpenLayers.Geometry.Point.OpenLayers.Class.initialize[100 … 199]100: OpenLayers.Geometry.Point.OpenLayers.Class.initialize101: OpenLayers.Geometry.Point.OpenLayers.Class.initialize102: OpenLayers.Geometry.Point.OpenLayers.Class.initialize103: OpenLayers.Geometry.Point.OpenLayers.Class.initialize104: OpenLayers.Geometry.Point.OpenLayers.Class.initialize105: OpenLayers.Geometry.Point.OpenLayers.Class.initialize106: OpenLayers.Geometry.Point.OpenLayers.Class.initialize107: OpenLayers.Geometry.Point.OpenLayers.Class.initialize108: OpenLayers.Geometry.Point.OpenLayers.Class.initialize109: OpenLayers.Geometry.Point.OpenLayers.Class.initialize110: OpenLayers.Geometry.Point.OpenLayers.Class.initialize111: OpenLayers.Geometry.Point.OpenLayers.Class.initialize112: OpenLayers.Geometry.Point.OpenLayers.Class.initialize113: OpenLayers.Geometry.Point.OpenLayers.Class.initialize114: OpenLayers.Geometry.Point.OpenLayers.Class.initialize115: OpenLayers.Geometry.Point.OpenLayers.Class.initialize116: OpenLayers.Geometry.Point.OpenLayers.Class.initialize117: OpenLayers.Geometry.Point.OpenLayers.Class.initialize118: OpenLayers.Geometry.Point.OpenLayers.Class.initialize119: OpenLayers.Geometry.Point.OpenLayers.Class.initialize120: OpenLayers.Geometry.Point.OpenLayers.Class.initialize121: OpenLayers.Geometry.Point.OpenLayers.Class.initialize122: OpenLayers.Geometry.Point.OpenLayers.Class.initialize123: OpenLayers.Geometry.Point.OpenLayers.Class.initialize124: OpenLayers.Geometry.Point.OpenLayers.Class.initialize125: OpenLayers.Geometry.Point.OpenLayers.Class.initialize126: OpenLayers.Geometry.Point.OpenLayers.Class.initialize127: OpenLayers.Geometry.Point.OpenLayers.Class.initialize128: OpenLayers.Geometry.Point.OpenLayers.Class.initialize129: OpenLayers.Geometry.Point.OpenLayers.Class.initialize130: OpenLayers.Geometry.Point.OpenLayers.Class.initialize131: OpenLayers.Geometry.Point.OpenLayers.Class.initialize132: OpenLayers.Geometry.Point.OpenLayers.Class.initialize133: OpenLayers.Geometry.Point.OpenLayers.Class.initialize134: OpenLayers.Geometry.Point.OpenLayers.Class.initialize135: OpenLayers.Geometry.Point.OpenLayers.Class.initialize136: OpenLayers.Geometry.Point.OpenLayers.Class.initialize137: OpenLayers.Geometry.Point.OpenLayers.Class.initialize138: OpenLayers.Geometry.Point.OpenLayers.Class.initialize139: OpenLayers.Geometry.Point.OpenLayers.Class.initialize140: OpenLayers.Geometry.Point.OpenLayers.Class.initialize141: OpenLayers.Geometry.Point.OpenLayers.Class.initialize142: OpenLayers.Geometry.Point.OpenLayers.Class.initialize143: OpenLayers.Geometry.Point.OpenLayers.Class.initialize144: OpenLayers.Geometry.Point.OpenLayers.Class.initialize145: OpenLayers.Geometry.Point.OpenLayers.Class.initialize146: OpenLayers.Geometry.Point.OpenLayers.Class.initialize147: OpenLayers.Geometry.Point.OpenLayers.Class.initialize148: OpenLayers.Geometry.Point.OpenLayers.Class.initialize149: OpenLayers.Geometry.Point.OpenLayers.Class.initialize150: OpenLayers.Geometry.Point.OpenLayers.Class.initialize151: OpenLayers.Geometry.Point.OpenLayers.Class.initialize152: OpenLayers.Geometry.Point.OpenLayers.Class.initialize153: OpenLayers.Geometry.Point.OpenLayers.Class.initialize154: OpenLayers.Geometry.Point.OpenLayers.Class.initialize155: OpenLayers.Geometry.Point.OpenLayers.Class.initialize156: OpenLayers.Geometry.Point.OpenLayers.Class.initialize157: OpenLayers.Geometry.Point.OpenLayers.Class.initialize158: OpenLayers.Geometry.Point.OpenLayers.Class.initialize159: OpenLayers.Geometry.Point.OpenLayers.Class.initialize160: OpenLayers.Geometry.Point.OpenLayers.Class.initialize161: OpenLayers.Geometry.Point.OpenLayers.Class.initialize162: OpenLayers.Geometry.Point.OpenLayers.Class.initialize163: OpenLayers.Geometry.Point.OpenLayers.Class.initialize164: OpenLayers.Geometry.Point.OpenLayers.Class.initialize165: OpenLayers.Geometry.Point.OpenLayers.Class.initialize166: OpenLayers.Geometry.Point.OpenLayers.Class.initialize167: OpenLayers.Geometry.Point.OpenLayers.Class.initialize168: OpenLayers.Geometry.Point.OpenLayers.Class.initialize169: OpenLayers.Geometry.Point.OpenLayers.Class.initialize170: OpenLayers.Geometry.Point.OpenLayers.Class.initialize171: OpenLayers.Geometry.Point.OpenLayers.Class.initialize172: OpenLayers.Geometry.Point.OpenLayers.Class.initialize173: OpenLayers.Geometry.Point.OpenLayers.Class.initialize174: OpenLayers.Geometry.Point.OpenLayers.Class.initialize175: OpenLayers.Geometry.Point.OpenLayers.Class.initialize176: OpenLayers.Geometry.Point.OpenLayers.Class.initialize177: OpenLayers.Geometry.Point.OpenLayers.Class.initialize178: OpenLayers.Geometry.Point.OpenLayers.Class.initialize179: OpenLayers.Geometry.Point.OpenLayers.Class.initialize180: OpenLayers.Geometry.Point.OpenLayers.Class.initialize181: OpenLayers.Geometry.Point.OpenLayers.Class.initialize182: OpenLayers.Geometry.Point.OpenLayers.Class.initialize183: OpenLayers.Geometry.Point.OpenLayers.Class.initialize184: OpenLayers.Geometry.Point.OpenLayers.Class.initialize185: OpenLayers.Geometry.Point.OpenLayers.Class.initialize186: OpenLayers.Geometry.Point.OpenLayers.Class.initialize187: OpenLayers.Geometry.Point.OpenLayers.Class.initialize188: OpenLayers.Geometry.Point.OpenLayers.Class.initialize189: OpenLayers.Geometry.Point.OpenLayers.Class.initialize190: OpenLayers.Geometry.Point.OpenLayers.Class.initialize191: OpenLayers.Geometry.Point.OpenLayers.Class.initialize192: OpenLayers.Geometry.Point.OpenLayers.Class.initialize193: OpenLayers.Geometry.Point.OpenLayers.Class.initialize194: OpenLayers.Geometry.Point.OpenLayers.Class.initialize195: OpenLayers.Geometry.Point.OpenLayers.Class.initialize196: OpenLayers.Geometry.Point.OpenLayers.Class.initialize197: OpenLayers.Geometry.Point.OpenLayers.Class.initialize198: OpenLayers.Geometry.Point.OpenLayers.Class.initialize199: OpenLayers.Geometry.Point.OpenLayers.Class.initialize[200 … 259]200: OpenLayers.Geometry.Point.OpenLayers.Class.initialize201: OpenLayers.Geometry.Point.OpenLayers.Class.initialize202: OpenLayers.Geometry.Point.OpenLayers.Class.initialize203: OpenLayers.Geometry.Point.OpenLayers.Class.initialize204: OpenLayers.Geometry.Point.OpenLayers.Class.initialize205: OpenLayers.Geometry.Point.OpenLayers.Class.initialize206: OpenLayers.Geometry.Point.OpenLayers.Class.initialize207: OpenLayers.Geometry.Point.OpenLayers.Class.initialize208: OpenLayers.Geometry.Point.OpenLayers.Class.initialize209: OpenLayers.Geometry.Point.OpenLayers.Class.initialize210: OpenLayers.Geometry.Point.OpenLayers.Class.initialize211: OpenLayers.Geometry.Point.OpenLayers.Class.initialize212: OpenLayers.Geometry.Point.OpenLayers.Class.initialize213: OpenLayers.Geometry.Point.OpenLayers.Class.initialize214: OpenLayers.Geometry.Point.OpenLayers.Class.initialize215: OpenLayers.Geometry.Point.OpenLayers.Class.initialize216: OpenLayers.Geometry.Point.OpenLayers.Class.initialize217: OpenLayers.Geometry.Point.OpenLayers.Class.initialize218: OpenLayers.Geometry.Point.OpenLayers.Class.initialize219: OpenLayers.Geometry.Point.OpenLayers.Class.initialize220: OpenLayers.Geometry.Point.OpenLayers.Class.initialize221: OpenLayers.Geometry.Point.OpenLayers.Class.initialize222: OpenLayers.Geometry.Point.OpenLayers.Class.initialize223: OpenLayers.Geometry.Point.OpenLayers.Class.initialize224: OpenLayers.Geometry.Point.OpenLayers.Class.initialize225: OpenLayers.Geometry.Point.OpenLayers.Class.initialize226: OpenLayers.Geometry.Point.OpenLayers.Class.initialize227: OpenLayers.Geometry.Point.OpenLayers.Class.initialize228: OpenLayers.Geometry.Point.OpenLayers.Class.initialize229: OpenLayers.Geometry.Point.OpenLayers.Class.initialize230: OpenLayers.Geometry.Point.OpenLayers.Class.initialize231: OpenLayers.Geometry.Point.OpenLayers.Class.initialize232: OpenLayers.Geometry.Point.OpenLayers.Class.initialize233: OpenLayers.Geometry.Point.OpenLayers.Class.initialize234: OpenLayers.Geometry.Point.OpenLayers.Class.initialize235: OpenLayers.Geometry.Point.OpenLayers.Class.initialize236: OpenLayers.Geometry.Point.OpenLayers.Class.initialize237: OpenLayers.Geometry.Point.OpenLayers.Class.initialize238: OpenLayers.Geometry.Point.OpenLayers.Class.initialize239: OpenLayers.Geometry.Point.OpenLayers.Class.initialize240: OpenLayers.Geometry.Point.OpenLayers.Class.initialize241: OpenLayers.Geometry.Point.OpenLayers.Class.initialize242: OpenLayers.Geometry.Point.OpenLayers.Class.initialize243: OpenLayers.Geometry.Point.OpenLayers.Class.initialize244: OpenLayers.Geometry.Point.OpenLayers.Class.initialize245: OpenLayers.Geometry.Point.OpenLayers.Class.initialize246: OpenLayers.Geometry.Point.OpenLayers.Class.initialize247: OpenLayers.Geometry.Point.OpenLayers.Class.initialize248: OpenLayers.Geometry.Point.OpenLayers.Class.initialize249: OpenLayers.Geometry.Point.OpenLayers.Class.initialize250: OpenLayers.Geometry.Point.OpenLayers.Class.initialize251: OpenLayers.Geometry.Point.OpenLayers.Class.initialize252: OpenLayers.Geometry.Point.OpenLayers.Class.initialize253: OpenLayers.Geometry.Point.OpenLayers.Class.initialize254: OpenLayers.Geometry.Point.OpenLayers.Class.initialize255: OpenLayers.Geometry.Point.OpenLayers.Class.initialize256: OpenLayers.Geometry.Point.OpenLayers.Class.initialize257: OpenLayers.Geometry.Point.OpenLayers.Class.initialize258: OpenLayers.Geometry.Point.OpenLayers.Class.initialize259: OpenLayers.Geometry.Point.OpenLayers.Class.initializebounds: OpenLayers.Bounds.OpenLayers.Class.initialize
bottom: 5249525.7748719
left: -12712079.07199
right: -12712079.07199
top: 5249525.7748719
__proto__: Objectid: "OpenLayers.Geometry.Point_787"
parent: n
bounds: OpenLayers.Bounds.OpenLayers.Class.initialize
components: Array[260]id: "OpenLayers.Geometry.LineString_788"
__proto__: i
x: -12712079.07199049y
: 5249525.774871918
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
 
Posts: 23622
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1109 times
Been thanked: 4853 times

Re: Geometry point in WME between starting and ending node

Postby AndyLaode » Tue Apr 14, 2015 9:53 am

mikupoiss wrote:Late bump, but... during a Waze Cafe few months ago we were told that the middle node's have almost zero effect on connection or server load.


who told you at the waze cafe?


@alan: alan example is extreme but it is make sense...
andylaode (andylaode@outlook.com)
okay, mate, see you on the road and on the map too, cheers
AndyLaode
Waze Local Champs
Waze Local Champs
 
Posts: 756
Joined: Mon May 19, 2014 9:04 am
Location: on my way from my house to insanity
Has thanked: 13 times
Been thanked: 246 times

Re: Geometry point in WME between starting and ending node

Postby DangerDaneDK » Tue Apr 14, 2015 11:35 am

Can you delete geonodes?, or would you have to delete and redo the road?
Flemming J., Denmark
Area Manager: Region of Southern Denmark / Region Syddanmark
Phone: Samsung Galaxy S9+ SM-G965F, Android 8.0 Waze: Newest

[ img ][ img ]
DangerDaneDK
Area Manager
Area Manager
 
Posts: 293
Joined: Mon Feb 28, 2011 1:04 pm
Location: Fredericia
Has thanked: 7 times
Been thanked: 11 times

Next

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users