On Tue, Aug 4, 2015 at 8:39 PM, Jody Garnett <[email protected]> wrote:
> Thanks Andrea, It is a mad concept to try and implement - but I expect > users will love it as it is more inuitive than the use of feature type > style to control z-order. > > Feedback (i.e. suggestions feel free to say no)... > > *Single layer z-ordering* > > For the sorting within a feature type style change - can we represent that > explicitly as a SortBy object (the vendor-option only has to be used for > the XML representation right?). This would make easier (and more object > oriented) for java developers ... > Well... we have been using string based vendor options for such a long time, besides priority I cannot remember anything else done with subclasses/objects. Maybe we could make a API change and relax the vendor option map from Map<String,String> to Map<String,Object>? Not sure I have time to work that though. > > The rest of the workflow/tradeoffs here makes sense and you have explained > it very clearly. > > *Cross layer z-ordering* > > For point 2 changing from the painter model - which seems to be the > difficult part. > > Is it possible to review the data and process the style into the painter > model? Would require some kind of histogram of the data in question, and > would only work in a few narrow cases I guess ... > I don't understand what you mean here? The sorting algorithm should be stable, so it will pick features in layer(s) order in case they are equal sorting wise, but will respect sorting otherwise. > > Is it possible to break out a new StreamingRenderer (or subclass) in order > to avoid making streaming renderer more complicated. guess this is an > implementation detail and not really the subject of the proposal. > No, I don't think so, not fully at least because we have to move to a StremingRenderer that receives a flow of features of different types (no more a feature collection). But I will definitely put the sort/merge logic in its own class so that the StreamingRenderer can get a iterator of features. > > The sortByGroup makes sense, and thanks for noting the CSS representation > of this stuff. > > aside: I hurt my head trying to picture the interaction between this idea > and the composite / composite base vendor extension. > Well... they don't mix. If you are grouping, all the feature type styles in the group are flattening to one, so any compositing in the middle of the mix will go the way of the dodo > > *Timeframe* > > Given that we are nearing the code freeze I wanted to check if this > proposal is a race before August 18th? > Indeed it is, finishing it after is not an option. Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -------------------------------------------------------
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
