topic Re: Using Arcade to calculate xy geometry. in ArcGIS Pro Questions

Using Arcade to calculate xy geometry.

AbiDhakal — Thu, 21 Nov 2019 18:36:11 GMT

Hello GIS friends,

Is there an arcade expression I can use to calculate xy values for a point feature? I am using this (return Round(Geometry($feature)x, 6) expression, but it is not doing the work. My field name is Point_X and Point_Y.

Thank you very much,

Abi

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Thu, 21 Nov 2019 19:09:08 GMT

Hello GIS friends,

This expression worked for me, but it is in meters. How can is change it to WKID 3857 from within the expression?

Thank you.

Abi

Re: Using Arcade to calculate xy geometry.

XanderBakker — Fri, 22 Nov 2019 15:48:19 GMT

Hi Abi Dhakal ,

You are missing a dot "." in the expression, It should be:

Round(Geometry($feature).X, 6)‍

... but if it is working for you, then I assume it is just a typo.

You are mentioning WKID 3857 (Web Mercator Auxiliary Sphere) and that you want it in meters. However, this is a spatial reference that already return the coordinate in meters. If you want to obtain decimal degrees (WGS 1984) you can use a conversion to get that. See example here: https://community.esri.com/message/806053-re-latlong-unit-conversion-with-arcade?commentID=806053#comment-806053

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Fri, 22 Nov 2019 19:48:23 GMT

Sorry. I meant to say I have it in NAD_1983_UTM_Zone_16N and like you mentioned I want to obtain decimal degrees (WGS 1948). Would the same expression work with the OriginalShift and all? I'm actually trying to create an attribute rule for the xy fields to auto populate.

Once again I'm sorry for the confusion.

Abi

Re: Using Arcade to calculate xy geometry.

XanderBakker — Mon, 25 Nov 2019 13:02:07 GMT

Hi Abi Dhakal ,

Unfortunately in Arcade you do not have access to any projection library (yet?). For this in ArcGIS Pro, you can use Python to do the job. Using a projection in a field calculation on a feature basis, might not be very fast. Depending the number of features you have, you might first want to project the featureclass, calculate the X and Y of the geometry and than join back those fields to the original featureclass.

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Mon, 25 Nov 2019 14:03:15 GMT

Hey Xander,

Morning!

What I am trying to do is create an attribute rule where by any point collected automatically also has its xy calculated in decimal degrees. Is that possible?

Thank you.

Abi

Re: Using Arcade to calculate xy geometry.

XanderBakker — Mon, 25 Nov 2019 14:24:49 GMT

Hi AlabamaForest ,

Currently, that is not possible if it requires a projection of coordinates.

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Mon, 25 Nov 2019 14:27:32 GMT

Thank you very much Xander!

Re: Using Arcade to calculate xy geometry.

ScottKichman — Mon, 29 Mar 2021 19:44:15 GMT

I do these attribute rules for a federated service

Coordinates

//Latitude

var y = Centroid($feature).y

var originShift = 2.0 * PI * 6378137.0 / 2.0;

var lat = (y / originShift) * 180.0;

lat = 180.0 / PI * (2.0 * Atan( Exp( lat * PI / 180.0)) - PI / 2.0);

return lat

//Longitude

var x = Centroid($feature).x

var originShift = 2.0 * PI * 6378137.0 / 2.0;

var lon = (x / originShift) * 180.0;

return lon

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Thu, 23 Feb 2023 15:50:03 GMT

@Scott

Hey Scott,

I also have a federated service in UTM NAD83 Zone16. I would like to automatically populate x and y fields in decimal degrees as the points are dropped. Would it be possible for us to communicate with emails? Here is my email address: abi.dhakal@forestry.alabama.gov

Thank you,
Abi

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Fri, 24 Feb 2023 17:26:53 GMT

@ScottKichman

Hey Scott,

I tried your expression. The calculation for Latitude is coming out in decimal degrees which is what I want, but it is not converting right for my original service in UTM NAD83 Zone16. The calculation for Longitude is giving me in meters not in decimal degrees. Please see below the expression I used exactly copying what you had. If you know the modification for what I have to have I will greately apprecite it.

Coordinates

//Latitude

var y = Centroid($feature).y

var originShift = 2.0 * PI * 6378137.0 / 2.0;

var lat = (y / originShift) * 180.0;

lat = 180.0 / PI * (2.0 * Atan( Exp( lat * PI / 180.0)) - PI / 2.0);

return lat

//Longitude

var x = Centroid($feature).x

var originShift = 2.0 * PI * 6378137.0 / 2.0;

var lon = (x / originShift) * 180.0;

return lon

Re: Using Arcade to calculate xy geometry.

ScottKichman — Fri, 24 Feb 2023 21:24:58 GMT

Hi Abi!

I am not sure why its not working. I just tested it and it worked fine. I also used each individual component(lat) and (Lon) separately in a field calculation using the form builder in the (new) Map Viewer. I created a Latitude Field and a Longitude Field and then applied each section as a field calculation in the form.

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Tue, 28 Feb 2023 19:11:55 GMT

@ScottKichman I'll keep trying, Scott. Also, the difference in mine is I'm trying to convert UTM NAD83 Zone16 to WGS84.
Thank you for your support.
Abi

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Tue, 28 Feb 2023 19:37:58 GMT

@ScottKichman

Hey Scott,

Earlier, I didn't explain it to you properly. First of all, I'm trying to get Lat/Lon values in NAD 1983 UTM Zone 16N for a point feature and within the same attribute rule trying to convert that to WGS84.

The second one is I'm trying to get lat/Lon values in USA Contiguous Albers Equal Area Conic USGS and then convert that to WGS84.

Thank you,
Abi

Re: Using Arcade to calculate xy geometry.

AbiDhakal — Tue, 28 Feb 2023 21:19:31 GMT

@XanderBakker

I'm sorry Xander, please accept my apology for not clearly stating what I'm looking for.

1. I'm trying to get WGS84 values in decimal degrees for a feature service that is in NAD 1983 UTM Zone16N .

2. I'm also trying to get WGS84 values in decimal degrees for a feature service that is in USA Contiguous Albers Equal Area Conic USGS.

So those are two different calculation for two toally different situations.

Thak you,
Abi