I don't have access to SDE on my home box but will in a few days when I'm
back to work... SDE uses the function msDoubleToString in mapstring.c to
convert values (MapServer holds all attribute values as strings). The
conversion uses the %g conversion specifier. That must be the problem.
If you're
I'm not building from source because the environment is windows and I
don't have a way (and knowledge ) configure all compile environment.
But thank you for the explanation I understand the problem, it's
probably that because labels with big numbers are converted to
scientific notation.
The
Hello Mario,
Mario Franco mario.fra...@ydreams.com, [20110720 - 16:29:16]
I'm not building from source because the environment is windows and I
don't have a way (and knowledge ) configure all compile environment.
But thank you for the explanation I understand the problem, it's
probably
I don't have access to SDE on my home box but will in a few days when I'm
back to work... SDE uses the function msDoubleToString in mapstring.c to
convert values (MapServer holds all attribute values as strings). The
conversion uses the %g conversion specifier. That must be the problem.
If you're
Can anyone that uses mapserver with sde reproduce the label and
expression issue that I'm having?
On 15-07-2011 15:38, Mario Franco wrote:
The version is Mapserver 5.6.3 and using the attribute as label was
how find out the values were being rounded.
For example the attribute has values
On issue one, what version are you using? MapServer shouldn't be rounding the
value. The comparison should be being done as a double. It might be helpful to
see a sample dataset although if this is SDE I can't test on my end. One thing
to try to help diagnose the problem would be to create a
The version is Mapserver 5.6.3 and using the attribute as label was how
find out the values were being rounded.
For example the attribute has values from 1000 to 17 and if the
value is smaller than 10 rounds the value with one decimal but above
10
rounds to and integer.
I'm using
