limiting significant digits on labels

[Steve Lime]

That RFC is related to template presentation only. It was only later
that I thought
about it's use elsewhere. Performance in a template setting is fine,
labeling a 1000
features is another matter.

This is another case where your data adapter concept might be of use.
There's nothing
that says it has to be limited to the spatial component of a feature.
Any progress to
that end?

Steve

>>> "Tamas Szekeres" <szekerest at gmail.com> 12/15/2006 5:32:42 PM >>>
Steve,

This RFC has escaped my notice a bit because the title does not
reflect this behaviour exactly, apologies. Could you confirm that the
performance of this issue is sufficient in most cases?

With regard to the bug mentioned, I've been considering this problem
was unintentional and seemed to be trivial how to fix it. And even the
code could have been much straightforward.
(Maybe Frank can explain us why is it more appealing as it stands?)


Best Regards,


Tamas



2006/12/16, Steve Lime <Steve.Lime at dnr.state.mn.us>:
> My idea at the moment would be to extend the [item...] tag that
already
> is supported (see RFC 9)
> so it can be used in the TEXT element of a class. Besides setting
> significant digits you can also
> commify numbers, and we could add to it. In the end you could do:
>
>   TEXT '[item name=area precision=2 commify=true] acres'
>
> This would work for all providers.
>
> Steve
>
> >>> Tamas Szekeres <szekerest at GMAIL.COM> 12/15/2006 4:41:12 PM >>>
> Jim,
>
> This problem also applies to the OGR data provider and that's why
the
> following bug:
>
> http://bugzilla.remotesensing.org/show_bug.cgi?id=1053 
>
> was posted.
>
>
> Best Regards,
>
> Tamas Szekeres
>
>
>
> 2006/12/15, Jim Manning <jmanning at whsun1.wh.whoi.edu>:
> > My numeric labels appear as, for example, "5.40000000000". How do
I
> > specify a format so they look like "5.4"?
> > My first post ever to a listserv.  I hope it is ok.
> > -JiM.
> >
>