Also, it would be very handy to be able to navigate through all the children of a Group - not just retrieve them by name.
Here you are: http://gitorious.org/fg/fgdata/commit/f ... 1aa9fd98f9
Also, it would be very handy to be able to navigate through all the children of a Group - not just retrieve them by name.
TheTom wrote in Mon Sep 17, 2012 5:48 pm:I only see again that we will need to somehow declutter the labeling as most labels are not clearly visible. Seems like a good testing environment for new features and requirements for the Canvas.
Hooray wrote in Mon Sep 17, 2012 6:45 pm:This is true, if you remember, we exchanged some related ideas a while ago
zakalawe wrote:Deciding an API for limiting symbols / databoxes is going to be very important - the NavDisplay and MapWidget already have different solutions for that. In particular there's a notion of symbol priority - basically I sort the available symbols by priority, and the display can be limited to the most important 10/50/100. This is also the approach taken by some real world map displays.
PAL labeling library is a ready-to-use C++ library providing efficient meta-heuristic algorithms for finding good placement solutions for point, line and polygon labeling.
It is released under the conditions of LGPL, GNU Lesser General Public License.
This website represents a platform with the main focus to federate and bring together an opensource community to maintain, offer support and follow innovative new developments in the field of labeling through PAL library.
Designed for multilayers and real-time labeling of maps, PAL provides impressive results, both in terms of execution time and solution quality. It uses combinatorial optimization approaches to maximize number of displayed labels (in opposition to greedy approaches). PAL is useful for polygon, line, point features labeling, and numerous options can be set for each layer to customize the labeling process.
zakalawe wrote in Wed Sep 19, 2012 1:34 pm:Deciding an API for limiting symbols / databoxes is going to be very important - the NavDisplay and MapWidget already have different solutions for that. In particular there's a notion of symbol priority - basically I sort the available symbols by priority, and the display can be limited to the most important 10/50/100. This is also the approach taken by some real world map displays.
Hooray wrote in Wed Sep 19, 2012 1:56 pm:Like we mentioned earlier, the C++ code of the Canvas system would need to be extended such that it also computes bounding box dimensions for each drawable (or just OSGText labels) and writes that info to the tree,
I'd like also to try oder variants and methods. What I think would improving is grouping together similar items and only split them based on their distance/displayed size.
Users browsing this forum: No registered users and 5 guests