Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-09 Thread LeeE
On Wednesday 09 January 2008 00:24, Adam Dershowitz wrote: On Jan 7, 2008, at 7:15 PM, LeeE wrote: On Monday 07 January 2008 22:28, Curtis Olson wrote: On Jan 7, 2008 3:51 PM, Frederic Bouvier wrote: If we keep the same triangle budget for every tile, we will have sparse data and

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-08 Thread Curtis Olson
On Jan 8, 2008 1:22 AM, Frederic Bouvier wrote: I was thinking about the parameter we pass to Terra to simplify the initial grid. IIRC, this parameter is always the same, leaving all *.arr.gz files with the same number of vertices. Yes, that's a good point, and something definitely to

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-08 Thread Adam Dershowitz
On Jan 7, 2008, at 7:15 PM, LeeE wrote: On Monday 07 January 2008 22:28, Curtis Olson wrote: On Jan 7, 2008 3:51 PM, Frederic Bouvier wrote: If we keep the same triangle budget for every tile, we will have sparse data and features at the equator and much more than what is really needed at

[Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-07 Thread Ralf Gerlich
Hi again! Thinking a bit more about it, the grid could be made consistent if we would define that 180W and 180E are tile borders instead of enforcing the Greenwich Meridian to be a tile border at all ranges of latitude. Find attached my proposed patch. That would change the arrangement of tiles

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-07 Thread Curtis Olson
On Jan 7, 2008 5:10 AM, Ralf Gerlich [EMAIL PROTECTED] wrote: Thinking a bit more about it, the grid could be made consistent if we would define that 180W and 180E are tile borders instead of enforcing the Greenwich Meridian to be a tile border at all ranges of latitude. Find attached my

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-07 Thread Frederic Bouvier
Selon Curtis Olson : I've been wondering about dispensing with the variable subdivision scheme and just having a fixed number of divisions per 1 degree of longitude. Perhaps having 4 subdivisions. This would double the tile width at the equator, but would preserve the same tile widths in the

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-07 Thread Curtis Olson
On Jan 7, 2008 3:51 PM, Frederic Bouvier wrote: If we keep the same triangle budget for every tile, we will have sparse data and features at the equator and much more than what is really needed at the poles, just because the area covered by each tile will vary greatly ( proportional to

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-07 Thread LeeE
On Monday 07 January 2008 22:28, Curtis Olson wrote: On Jan 7, 2008 3:51 PM, Frederic Bouvier wrote: If we keep the same triangle budget for every tile, we will have sparse data and features at the equator and much more than what is really needed at the poles, just because the area

Re: [Flightgear-devel] RFC: Fixing the tile numbering scheme (was: Re: Problems found in world scenery and SGBucket class)

2008-01-07 Thread Frederic Bouvier
Selon Curtis Olson : On Jan 7, 2008 3:51 PM, Frederic Bouvier wrote: If we keep the same triangle budget for every tile, we will have sparse data and features at the equator and much more than what is really needed at the poles, just because the area covered by each tile will vary