topic Re: Why is the location tracking layer in WGS84? in ArcGIS Tracker Questions

Why is the location tracking layer in WGS84?

JakeJacobs — Tue, 28 Jan 2020 20:02:59 GMT

We're implementing Tracker for ArcGIS on our ArcGIS Online organization. Why is the location tracking hosted feature service created as WKID 4326 (WGS84) when everything else on AGOL defaults to WKID 102100 (web mercator)?

Re: Why is the location tracking layer in WGS84?

Anonymous User — Tue, 28 Jan 2020 20:16:00 GMT

That's a good question. The underlying location tracks data store in ArcGIS Online always stores it in GeoJSON format (WGS-84). In most cases, the data will be projected to Web Mercator when a client queries it so it would be projected regardless of the default spatial reference.

When it's uploaded from Tracker we use WGS84 so there's no projection required prior to inserting the features.

Re: Why is the location tracking layer in WGS84?

JamesCrandall — Tue, 18 Feb 2020 21:35:00 GMT

Of note: if you plan to use input geometry from another feature service to query the tracker feature service then it's important to have input geometry the same as the tracker service in that query. For example, we have a polygon feature service (WKID 102100/3857) and loop thru each feature and query the ESRI Tracker service with that geometry but when we initially query the polygon service we set the output SR to WKID 4326 so that the geometries will align.

Re: Why is the location tracking layer in WGS84?

Anonymous User — Mon, 09 Mar 2020 17:36:50 GMT

You should be able to set the inSR parameter, when querying, to specify the spatial reference of your polygon. The feature service should project it correctly prior to executing the geometry operation.

Re: Why is the location tracking layer in WGS84?

JamesCrandall — Mon, 09 Mar 2020 18:31:55 GMT

Absolutely!