Hello everybody Wow, this is *old* (1 month already!): but only now am I catching up with these messages on the list..
Too bad I missed this discussion: down here we've been playing with similar ideas for some time (wasn't sure how useful they were though). Similar points are: - One common "Layer" interface that can be added to a "Map". Specialized layers include Feature-based layers (we call them "FeatureMapLayers") and other things - The idea of a "DirectLayer" which can draw itself. We implemented a WMS layer as one of those. We anticipate using this to enable an application to render anything it may want to, and map decorations also. - The difficulty of choosing a damn name for "Map": we ended up with "CartographicMap" (just to differentiate from the Java one), but MapContext or MapContent sound simpler :P Different points that may be of interest (maybe too late, but anyway, worth talking about): - We consider this "Map" structure as metadata to be used for all kinds of purposes, not just rendering. - Our "Map" has the concept of an internal structure (rather than a list). This allows us to use a tree structure, placing layers inside layers, etc (the structure can then be translated into a nice legend) - We refused to add a "visibility" property to the Layer interface. After many years experimenting with this kind of issue, we came to the conclusion that this is a higher level of information and should be placed elsewhere (as is "active layer", "selected layer", and whatever other concept an application may have - rendering is just one of them) - We also have a wider concept of a "MapEntity", which is "whatever is a constituent part of a Map": MapLayers are specific MapEntities that are to be rendered. This wider concept allows us to specify groups and other customized structure elements into the mix. - We do have the concept of a "GridReaderLayer", but we figured that with a few tricks we could spare everybody the trouble of differentiating between raster and vector at this level: we use GridCoverageReaders wrapped in FeatureSources and treat them as regular FeatureMapLayers. This was also motivated by the fact that the GeoTools renderer did this wrapping anyway in the end. That's it then! Cheers Milton Michael Bedward wrote: > Hi Jody, > > Sorry to be absent for the last few days. I'm sure you were assuming > +1 from me :) > > Thanks again for this great improvement. > > Michael > > On 15 June 2010 15:20, Jody Garnett <[email protected]> wrote: >> So I have a few votes in - and a few reviews (thanks!) >> >> • Andrea Aime >> • +1 Ben Caradoc-Davies >> • Christian Mueller >> • Ian Turton >> • Justin Deoliveira >> • +1 Jody Garnett >> • Michael Bedward >> • +0 Simone Giannecchini >> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > -- Milton Jonathan Grupo GIS e Meio Ambiente Tecgraf/PUC-Rio Tel: +55-21-3527-2502 ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
