nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Popup info is adding many numbers behind decimal point?

ReedDavis

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?

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

rzufelt

I thought he had tried changing it to double a few posts back, with no luck. So thought it might be elsewhere.

R_

RobertScheitlin__GISP

Yep,

The original problem is very specific to a SINGLE (type) field it always worked fine with a double.

rzufelt

This is working just fine for me.

    <fields>
        <field name="Shape_Area" alias="Area of Feature" visible="true">
             <format precision="2" usethousandsseparator="true"/>
        </field> 
        
    </fields>

Of course, if I set it to "-1" I get the default, which is a whole ton of zeros.

so, with it set to -1
37,441.89976562478

Set to "2":
37,441.90

R_

Works with my other numeric fields also. Just figured everyone can come up with a Shape_Area field to test.

Though, I'm not using the description tag, so have not tested that part.

Ok, just tested using the description tag. still working as expected.

ReedDavis

Stew,

No, unfortunately the project that I was working on was a temporary contract and the customer did not require this issue to be resolved. It still bothers when I check on the product; However no one is paying me to fix it so there it stays. Please post here if you find out any more...

StewartGalloway

Reed,
Did you ever come up with a solution to this?
Thank you.
Stew
Stewart.c.galloway.nfg@mail.mil

ReedDavis

Yeah, the Flex Viewer and I have come to an understanding, I don't input any data with decimals(rounded them all off, its not critical for what I'm doing) and it doesn't display bogus numbers behind them. Problem Solved, well not really, but I'm moving on for now.

RobertScheitlin__GISP

RD,

Have you cleared your browsers cache? Have you tried to access the Viewer from a different machine? Short of that, it is time to call esri tech support.

ReedDavis

Yes to all, I believe the cache is cleared automatically in 10.1 and the server is displaying:

PercentUNE ( type: esriFieldTypeDouble , alias: Percent Unemployment )

and now even though I left the precision and scale set to 0,0 they are showing 38,8 respectively in my workspace.

RobertScheitlin__GISP

Reed,

Did you overwrite your MSD as well as saving your MXD changes? Did you restart your Map Service? Did you clear your REST Cache by using the REST Service directory admin page? Have you verified that the REST Service directory is reporting the existence of the new double field for that map service? Have you updated the popup xml to use that field instead of the old single field?

ReedDavis

Correct, now that I have been able to edit those records I am still having the same issue, the addition of numbers behind the decimal. To elaborate: the only field not returning the error was double, so I add a double field, populate it with the same data as was in the float field(that was returning the error) and it still gives me the error.

RobertScheitlin__GISP

RD,

So once your data is versioned you can add a field (When NOT Editing) and then when you are editing you can perform a field calculation.

ReedDavis

Well, the field calculator is still being moody but I can now manually edit at least, one problem was the source data was not versioned.

RobertScheitlin__GISP

RD and Michael,

It is a copy (sometimes) in 10.1. Are you using 10.1 for ArcGIS Server? I use SDE and FGDB data for my map services and performing a schema change require an exclusive lock on the data and can not be a shared lock. So when I want to add a field to a FC in one of my GDBs that is included in a Map Service I always have to stop that map service, make the change, save the mxd, overwrite the MSD, restart the map service, clear the REST cache.

ReedDavis

Tried anyway, just to be thorough. Still no field calculator for me.

ReedDavis

Shouldn't matter because the data I am editing is not the same instance, I have been overwriting my service each time I make an update, the data I am attempting to edit is local, the service is on my server. It is my understanding that the service is a copy of the data not a reference to it. Maybe I am misunderstanding the environment?

mvolz47

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?

RobertScheitlin__GISP

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?

ReedDavis

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. ?

RobertScheitlin__GISP

RD,

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

ReedDavis

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

RobertScheitlin__GISP

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.

ReedDavis

PECENT_UNE ( type: esriFieldTypeSingle , alias: Percent Unemployment )

RobertScheitlin__GISP

RD,

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

ReedDavis

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%

RobertScheitlin__GISP

RD,

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

ReedDavis

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

RobertScheitlin__GISP

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>

ReedDavis

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.

RobertScheitlin__GISP

RD,

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

TomMagdaleno

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.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.