On Wed, Jan 2, 2013 at 11:15 AM, Ákos Maróy <[email protected]> wrote: > On 01/01/13 17:51, Andrea Aime wrote: > > > SLD is not CSS, and the default do make sense within the limits of the > standard specification, what's causing troubles is the extension that > we are discussing. > But I agree that the documentation should point out about possible issues. > > That said, if the current list of units: > http://www.opengeospatial.org/se/units/metre > http://www.opengeospatial.org/se/units/foot > http://www.opengeospatial.org/se/units/pixel > > is extended with the following two: > http://www.opengeospatial.org/se/x-units/target/mm > http://www.opengeospatial.org/se/x-units/target/inch > > I guess the current defaults are still going to be reasonable (ok, one > inch > is too large, but the issue is easily fixed, it's not going to give you a > fully > black map like using 1m) > > yes, I see this as an easy-to-achieve goal > > I've created a ticket in jira, and attached a patch with the > implementation to it, here: https://jira.codehaus.org/browse/GEOT-4360 > yes, it does include updated unit tests as well. >
Had a quick look at the patch, one thing stand out: - the UomRescaleStyleVisitor constructor has been modified in a backwards incompatible way, please also add a constructor that only takes the scale and assumes the dpi is the default one to avoid breaking the API > Right, CSS is a better fit for styling than SLD in many respects, and > GeoServer > > comes with its own example here: > http://docs.geoserver.org/stable/en/user/community/css/index.html > and in particular here: > http://docs.geoserver.org/stable/en/user/community/css/values.html > > That said, the above still has to map do the internal model which is > based 1-1 > on SLD 1.0/SE 1.1, it just makes things easier to write and then the CSS > is translated on the fly in an eventually very large equivalent SLD. > > interesting. > > and how are instances solved when the unit of measurement is different for > different parts of the same feature? for example, if a font size would be > in target-device mm, but the halo radius would be in pixels? > I did not write that code so don't know how it works, but what you are citing above should be.. hum... impossible? Well, unless the code is doing the uom -> pixel transformation while turning the CSS into SLD in order to make the unit uniform. Which of course would not work in your case. Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it 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 -------------------------------------------------------
------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612
_______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
