Bounded textures support (not spanning the whole globe)
Review Request #123304 - Created April 9, 2015 and submitted
Before this patch, there is an assumption that every texture layer spans the whole globe. Tiles are searched on all previous levels in TileLoader for each geo texture, while it can be the case that the texture layer only spans in certain area (like aerial photos of a certain city). It is both ineffective and unnecessary.
The patch allows for textures that are bounded by a specified latlon box. With these patch, bounding box can be set for dynamic textures. Additional support and coding for dgml tags parsing should follow.
Displayed a bounded texture, tested for backwards compability.
Are there any reasons not to call this:
for reasons of naming consistency?
I guess we should pick GeoDataLatLonBox over GeoDataLatLonAltBox since the latter inherits from the former but since we don't take the altitude into account for rendering - or are there chances that we ever will? and might it be possible that we get hard to track bugs if we allow for specifying the altitude range while not properly evaluating it?)
GeoDataLatLonBox latLonBox() const
Changed names as suggested in review
Revision 2 (+28 -1)