> That is, you can specify meters as the uom, and then you can add px to a > measure > to specify it's meant to be pixels. However the override is available only > for pixels, > which is a bit weird. > > How about we implement this override support to be SE 1.1 compliant in this > respect, > but allow people to also add m and ft to override the unit to be meters and > feet respectively?
Agreed, obey the standard, but do not be held back by the standard. > Some properties would be rather "fun", think of dasharray, it could end up > looking like: > 2m 3px 10ft 1m That looks suitably awkward. > The possible alternatives could be to search the uom in the first or last > number, which > would help in the common case where the dasharray is all expressed in one > unit: > 2m 3 10 1 > or > 2 3 10 1m > > Opinions? Sadly I think the first example is more consistent with the spirit of SE 1.1 you quoted. The "2 3 10 1 m" allows you no ability to "fall back" to the symboliser default. Jody ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
