tag:blogger.com,1999:blog-21167013.post1402341458390584873..comments2007-09-17T12:10:23.936-07:00Matt Gigerhttp://www.blogger.com/profile/08948284981378368476noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-21167013.post-49264754839623105782007-09-17T12:10:00.000-07:002007-09-17T12:10:00.000-07:00Yes, I agree that a coordinate list should be an array of numbers, but not an array of arrays of numbers. [1,2,3,4,5,6,7,8] rather than [[1,2],[3,4],[5,6],[7,8]]. Sure, each coordinate only adds 2 extra characters to the data stream and can be compressed down. However, when loaded, there is a memory storage overhead for each coordinate list, also there is a processing overhead to extract say 10,000 lists with 2 points each versus 1 list with 20,000 points. I'd guess it is significant too.matt_gigerhttp://www.blogger.com/profile/08948284981378368476noreply@blogger.comtag:blogger.com,1999:blog-21167013.post-47693515618987970372007-09-17T11:45:00.000-07:002007-09-17T11:45:00.000-07:00A JSON array of numbers is only fractionally longer (in bytes) than the equivalent GML posList. After you compress them, the difference is going to be very slight. With XML you have to put the coordinates in a text node because there is no capacity for arrays. JSON has arrays, and it's natural and appropriate to use them.Seanhttp://www.blogger.com/profile/04892958878143369551noreply@blogger.com