topic Unresolved in ArcGIS Viewer for Flex Questions

Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 18:37:21 GMT

I have configured my popup to show percent unemployment for the county that is clicked, the popup displays the information but adds about ten bogus numbers after the decimal on some counties. The source data is configured as follows: The percent unemployment field is float with precision of 6 scale of 2, number of decimal places 2. The same is occurring in the search tool which leads me to believe it is a source data formatting issue. Any Ideas?

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Wed, 26 Sep 2012 18:40:04 GMT

RD,

Sure look at the help documentation for configuring popups on this page:

http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Pop_up_configuration_files/01m30000002q000000/

Look for fields and format and then precision.

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 18:56:20 GMT

It is saying I can disable precision by setting it to -1, here is my popup

<configuration>
<title>{CONAME} County Percent Unemployment</title>
<description><![CDATA[Percent Unemployment: {PECENT_UNE}%]]></description>
</configuration>

Where would I add the precision-1 ?

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Sat, 11 Dec 2021 15:30:15 GMT

RD,

In the fields tag that you have yet to add:

<configuration>
    <title>{CONAME} County Percent Unemployment</title>
    <fields>
        <field name="PECENT_UNE">
            <format precision="-1" />
        </field>
    </fields>
    <description><=!=[=C=D=A=T=A=[Percent Unemployment: {PECENT_UNE}%]=]=></description>
</configuration>

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 19:21:28 GMT

Coping it directly does not seem to work, tried a couple variations with no luck, still the same issue?

Re: Popup info is adding many numbers behind decimal point?

TomMagdaleno — Wed, 26 Sep 2012 19:27:30 GMT

Can you create a new text field in the raw data and copy the data over as text? Then you can format exactly like you want.

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Wed, 26 Sep 2012 19:29:40 GMT

RD,

The description tag go messed up in the forum post replace that with what you already had.

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 19:53:24 GMT

Replaced, still no luck. The strange thing is when I use the Identify tool the correct percentage shows ex: 15.3%, in popups and search widget I get 15.300000890034003 or some other random string of numbers!?!? Whats even more strange a couple of my counties don't seem to have the issue at all, even though all data is sourced from the same field and table.

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Sat, 11 Dec 2021 15:30:18 GMT

RD,

So your config looks like this?

<configuration>
    <title>{CONAME} County Percent Unemployment</title>
    <fields>
        <field name="PECENT_UNE">
            <format precision="-1" />
        </field>
    </fields>
    <description><![CDATA[Percent Unemployment: {PECENT_UNE}%]]></description>
</configuration>

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 20:05:04 GMT

Identical. I also tried different values for the "-1" just for kicks with no luck.

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Wed, 26 Sep 2012 20:08:47 GMT

RD,

Do you even get the rest of the description text (i.e. Percent Unemployment:)?

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 20:14:32 GMT

Example of a popup return:

Newton County
Percent Unemployment: 9.399999618530273

Actual Value(as given by your identify tool): 9.4%
Value in table: 9.4%

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Wed, 26 Sep 2012 20:20:05 GMT

RD,

What is the actual field type reported by the REST Service directory?

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 20:38:40 GMT

PECENT_UNE ( type: esriFieldTypeSingle , alias: Percent Unemployment )

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Wed, 26 Sep 2012 20:44:07 GMT

RD,

OK that is what I figured. There is a known bug with the field type esriFieldTypeSingle coming from ArcGIS Server 10.0.x. I don't have the bug number though.

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Wed, 26 Sep 2012 20:48:25 GMT

Could it help to change from float to double in the source?

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Wed, 26 Sep 2012 20:50:14 GMT

RD,

Absolutely, the single field type is the only one with the issue.

Re: Popup info is adding many numbers behind decimal point?

ReedDavis — Thu, 27 Sep 2012 13:17:17 GMT

Can you create a new text field in the raw data and copy the data over as text? Then you can format exactly like you want.

Same thing I was thinking, however my field calculator is greyed out, any thoughts on this? Tried it in and out of editing session, no luck. Tried creating a duplicate of the data and adding a field to it, field calculator still greyed. ?

Re: Popup info is adding many numbers behind decimal point?

RobertScheitlin__GISP — Thu, 27 Sep 2012 13:19:28 GMT

RD,

Did you stop your map service and make sure that there is no one else using the data, so that any data locks will be removed?

Re: Popup info is adding many numbers behind decimal point?

MichaelVolz — Thu, 27 Sep 2012 13:35:22 GMT

Robert:

I do not mean to hijack this post, but I have a question directly related to the scenario that Reed is experiencing.

Would the locks that you are speaking about in regards to the ArcGIS Server mapservices apply to both the source data originating from a file geodatabases and SDE geodatabases? Are the locks handled differently in each geodatabase?