From: Stuart B. <stu...@gm...> - 2014-08-07 06:42:54
|
On 7 Aug 2014, at 06:30, Renk Thorsten wrote: > That sounds rather neat and looks as if will sure help to clean up the file structure - thanks! I guess testing for the region before a whole area definition rather than before each material will also reduce the computational load in looking up materials. > > Some questions still: Does this still utilize aircraft position at loading time, or did you switch to tile position now? It's now based on the lat/lon of the center of the tile, so we now longer have different behaviour on Hawaii depending on which direction you approach from. The materials for a tile (and any <condition> block) are evaluated once for the entire tile for efficiency. I'm not planning to provide sub-tile granularity. > I also remember we discussed allowing for irregular polygons to be used to define a region - do you have plans on that as well? I'm not planning to support irregular polygons, though it should be fairly straightforward and computationally cheap if there is a need for them. I'm hoping that being able to define multiple <area> blocks will be sufficient. I've now migrated at regional, default and DDS definitions. I need to do a little more testing but expect to commit this before Sunday night. -Stuart |