Good morning,
I recently noticed that some elevation expressions I put on one of my hosted feature layers is no longer working properly. The expression is "Round(Geometry($feature).Z, 2)" & "Round(Geometry($feature).Z*3.28084, 2)". I found that expression online through one of the ESRI sites. It used to show in meters so i created a second one that multiplies the value by 3.28084 to convert it to feet. It worked great for a long time, but just a couple days ago the values popped up as "--" on Field Maps. Later that afternoon I checked AGOL and the values that were showing up as "--" on Field Maps are showing up as "748,417.04" six or seven digit values. The previously collected data also shows up in the same manner. I also noticed that it happened after updating Field Maps, but whatever happened somehow affected AGOL pop-ups too. Any idea what could've caused this? Thanks
Okay so I just figured it out. I set the base map back to an ESRI imagery base map to test it and the expressions are no longer in 6 digit format and displaying correctly on AGOL Web Viewer now (see screenshots below). So I'm guessing something got fixed/modified in the background that has to do with base map configurations.
My initial idea of using our web service URL as a base map was to keep everything consistent to our local datum. It worked great up until now that I noticed this change.
Something else got fixed that was a insignificant issue that I pretty much ignored, and never asked about on the forums, that I'll share. When I first added those Z expressions, they would display backwards on AGOL Map Viewer for some reason. The MSL(ft) conversion expression would show up as meters and the MSL(m) expression would show up in ft on the AGOL Map Viewer pop ups. However, it wasn't too much of a big deal because on Field Maps the ft values displayed on the correct MSL(ft) field and meter values on the MSL(m) field, which was more important to me being able to see the elevations in real time in the field. When I would get back to the office and briefly review the elevations on AGOL Map Viewer, I knew the ft elevations were on my MSL(m) expressions and not the MSL(ft), that's why I left both MSL(m) and MSL(ft) fields on the pop-up.
Like I said, it wasn't too big a deal because my priorities was to be able to see the Z values in the field, then if I had to process the data to create a map, I would export the features into a shapefile and process the data in ArcMap. We are migrating to ArcGIS Pro soon, so that'll be a whole knew experience when it comes.
Good morning Colin,
The Z-values are now displaying correctly on AGOL Map Viewer, 6-digit values are no longer showing. However, that small discrepancy/bug I mentioned on my last "solution" comment about the Z-value expressions on pop-ups displaying backwards is there again. This is not a big deal at all as mentioned above, since I know about the bug, but I'll just share it since we're on this topic.
Now that I think about it, the reason they show up backwards is because of my base map URL web service. I noticed on AGOL Web Map the 'MSL(m)' field shows correctly as ft since the base map is in our local datum, and the 'MSL(ft)' field is the ft value multiplied by 3.28084. Somehow Field Maps displays it correctly and I'll have to investigate my coordinate system configurations/profile on Field Maps or even my Trimble R2 app to find out where the discrepancy is at or just leave it as is since it's worked great. See the pop-up screenshots. Thanks for the help! Have a great weekend.
Best regards,
Frank
@fjramos wrote: My initial idea of using our web service URL as a base map was to keep everything consistent to our local datum. It worked great up until now that I noticed this change.
This would be the best practice when working with high accuracy, its just unfortunate you were running into this issue. Have you tried again with your original map in your original coordinate system? I happened to see there were some patches that went out on AGOL recently that could possible impact this.
Hi tikola,
The issue was my web service url base map. I changed the base map to an ESRI imagery base map to test it out and the expression Z fields on the pop up display correctly now. Thanks for the help! Now a fix for those Z value expressions labels would be great, ha!
Another quick update, the Trimble TDC600 mobile device is now displaying the expressions correctly, all mobile devices are displaying Z values correctly as before. AGOL Web Map is still displaying Z values as 6 digit integers.
A few more bits of information to add as I keep investigating, nothing has changed in our datum web service base map. The Trimble TDC600 is locked to Android version 10, and our Samsung S24 are Android version 16 which was done Feb 2, 2026. I'm starting to lean into the Field Maps display issue is outdated hardware related to the TDC600, but I can't be 100% sure. However, I still don't know what would've caused the AGOL Z expressions to display into 6 digit integers.
No difference in adding a new expression, they still display as 6 digit values for the Z field. The screenshot of the mobile phone I shared on the original post was from my Samsung S24, which was displaying as "--" at first, but after the update I think it got fixed? I don't recall exactly, I just remember seeing it on both devices, then only on the TDC600 which I use to collect data. The only device still displaying "--" is the Trimble TDC600.
I did not make any changes, however this morning upon more inspection I did notice that it is device specific when the expression attributes display as "--". On our mobile work phones, Samsung S24+, the expression attributes display correctly. On my Trimble TDC600 (Android), they display as "--", might be a outdated hardware issue? Let me try erasing the expressions and creating new ones and I will update you with the result.
As a add to my previous post - if you open the link to my map it labels Z to 0 but if you go editing the labeling function in that map and click Run on that it gives you nicely the correct height. So even the feature(geometry).Z function works - it just fails to write that value to label.
I tried some coordinate system variants but no success - so I have not find a way to make this work yet. I will keep on trying to isolate the issue better. In nutshell - my variant is just that labeling height from geometry fails.
And my variant can be defined also a bit more. It happens only in AGOL MapViewer and it does not happen anywhere else in Esri ecosystem - that matches with Franks's case latest version above. FieldMaps, ArcGIS Pro, (old Classic Map Viewer if possible) etc. in any of those my issue does not exist. I have never tested it in Enterprise as I have no such server in hands. Other coordinate labels (X&Y) in my variant are done with exactly same function except there is of course a feature(geometry).X function instead of Z. In past also X&Y was effected but that got fixed a year ago which solved my need.
Now when remembering my case a year ago more it had something to do with projections. It happens if features and basemap are not in same projection or then it had something to do with local projections we use in Finland. When moving data to same projection as the basemap issue disappeared.
Need to refresh my memory a bit and test some data variants as currently my case seems that issue exist even if both data and basemap are in WebMercator - it was somehow projection related and I need to test bit more to refresh my memory.
Issue has nothing to do with external GPS devices as I have repeated it with hand drawn points in past. Currently though my points are from Leica FLX100 as the test was originally made for GNSS mapping needs.
Colin what happens on your computer if you open my link: https://arcg.is/1z8O544 ? I have tried it be open to anyone as it just contains basemap and two points.
As a comment to Frank I see no point of sticking ArcMAP for this issue as this thing easily works in ArcGIS Pro without issues.
Odd, did you make any changes to the map? I also tried this out with a Trimble R1 and the expressions are working correctly. I also see the expected formatting in Map Viewer.
Are your values "0"? because they're showing up as 0 when I open the map.
Hi Colin,
Disregard my previous message, the Field Maps side is now working properly. However, on AGOL, the expression is still showing up as 6 digit (74xxxx.00) values. That's not a big deal, since we export the layers into shapefiles, then process/label them outside of AGOL. Thanks!
Thanks Colin, that's interesting. I am on NAD83 South Texas Plane 4205 coordinate system and GEOID18. The real time corrections is a local RTK service from our State Transportation Department TXDOT. The antenna is a Trimble R2 cm unit. I have not attempted to reproduce with internal GPS, however a coworker collected some points earlier with a Bad Elf Extreme cm antenna unit and the results identical, showing Z values in 6 digits (74xxxx.00) The map is editable, as it is the map we use on a daily basis to collect data.
I will also add something I noticed, but can't confirm cause I can't remember if this is how it happened. I remember noticing the expression attributes as "--" first on my mobile work phone. I use Field Maps simultaneously on my mobile work phone (Android) and on my Trimble TDC600 paired with R2. I think I had just done a full app update on my Trimble TDC600 unit that included Field Maps, when I first noticed the expressions "--" after collecting a point. When I noticed that discrepancy, I checked the expression fields on my mobile work phone, which did not have Field Maps updated yet and I could've sworn that on previous points the expression elevation data was correct, with the exception of that recent point collected on the TDC600 unit. I later updated Field Maps on my mobile work phone and now all points with the expression show up as "--". Not sure if that has anything to do with it, but it was an observation I made, leading up to it.
We are still in the process of migrating into ArcGIS Pro, so we are still using ArcMap. I exported my points to ArcMap to process and get the Z values. Fortunately, the elevation data is correct when processed through ArcMap. The only issue is that it does not display correctly on AGOL or Field Maps. Let me know if you need anymore information, thank you for your time.
Regards,
Hey @fjramos thanks for posting about this. I have some existing expressions that calculate Z values and they are working for me. I also copied what you have above and they seem to be working for me as well in both Field Maps and Map Viewer. Could you provide some additional details? For example, what is the coordinate system (horizontal and vertical) on this feature service? Are you using a correction service with your Trimble? Do you reproduce this just using the internal GPS on the device? Is the map you see this in editable or are you reviewing existing data in a read only map? Thanks again!
Based on your post I got inspired to test my case in Field Maps - there is no issue. So my variant is such that it fails only in AGOL but in all other places in Esri ecosystem it works without issues. So it might be that our versions are slightly different but most likely we are still seeing the variations of the same issue.
My variant can be seen on this map: https://arcg.is/1110Du
Open that in browser and check Z in label - and then open exactly same map with ArcGIS Pro and check Z value in label and you should see the difference. I have not thought the issue in Field Maps perspective as my need was related on AGOL sewer upelev and downelev visualization according pipe flowing (=digitizing) direction. There actually just finding correct X value is enough in my script.
It can be that autumn major Field Maps update changed the FieldMaps visualization engine closer to new AGOL MapViewer and we got the same issue there with that update..
Interesting,
I did notice a couple years ago that I wasn't able to label those expressions I mentioned above, it wasn't too big of a deal for me since I would go back to the office, process the data and create/label a map from there. Seeing them on the attribute list/pop-up was good enough for me just to confirm my elevations in real time. The expression worked great this way for years, but just a couple days ago with the recent Field Maps update, the expression does not display Z values, nor X & Y values on Field Maps anymore. I can see X & Y value expressions on AGOL Map viewer, but the Z value expression is way off, it's showing Z values in 6 digit integers.
Good evening
Known issue and I have been strugling with same one. The Z is the issue so if you do same function with X or Y it works but Z fails. Also if you do this same function in ArcGIS Pro it works and most likely also in Classic Map Viewer but not in current AGOL Map viewer. Of course as Classic viewer does not exist it is no option but that was a case while it existed it worked there.
This is the variant where I worked the case out:
https://community.esri.com/t5/arcgis-online-questions/arcade-labels-work-in-map-viewer-classic-but-not/m-p/1619891#M64934
My case was related in labeling so function might work in other Arcade needs also in AGOL but in labeling it has an issue. My solution is now that I label Height from attributes but I also have in future some needs to show geometry based height values so I have exact same need to get fixed. So contact your local Esri support and push the case through them. With this information you should have enough input for support story.
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
