topic Re: Dubious Geoprocessed 3D layer behaviors in ArcGIS Pro Questions

Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Fri, 15 Jun 2018 21:52:55 GMT

I’m trying to animate a linear path. I start w/ a datafile of 8000 lat/lon/elev points.

From the tutorial, I learned to apply the following geoprocesses:

Make XY event layer
Feature class to Feature Class
Points to Line
Split line at Vertices

I don’t have any problems doing any of this in 2D. All of the geoprocessed output layers work and I can continue w/ animating the final geoprocessed (Split line at Vertices) layer. So I’ve proven sufficient competency in 2D.

But in 3D, everything goes awry. For 3D data I am using the project data from the 3D basic tutorial “Create Points on a Map” http://pro.arcgis.com/en/pro-app/get-started/create-points-on-a-map.htm

After applying a geoprocess (eg. Feature to feature, points to line, split line at vertices) the resultant layer should match exactly (and thus sit on top of) the input layer. Correct?

But many if not all the resultant output layers do not match. Many of the resultant output layers (when they’re visible, often they’re not… ☹ ) do not match the position of their input layer and thus are translated (seemingly randomly) some meters up/down/right/left (albeit the shape is retained).

I’ve exported & examined the shape file data to no avail.

I’ve deleted/updated/etc. cache settings, and project spatial index settings all to no avail.

I’ve played w/ visibility ranges.

In fact changing layer properties seems to have no positive affect nor yield any illumination on the problem.

Are these ArcGIS Pro bugs? If yes, what can I do? If no please tell me what I’m missing. At this point I have no faith in my ability to geoprocess or otherwise control my ArcGIS Pro layers. Thank you in advance for any help or advice (including anything I’ve tried before).

Background info:

Using ArcGIS Pro 2.1.3 (auto update on).

I got my info on how to do this from this quick useful demo: https://www.youtube.com/watch?v=tq4rzFPXwr4 (please note my problem/questions are not about animation per se. My problem is with the behavior/visibility of the resultant 3D geoprocessed output layers.

My data represents a single drone trajectory flight path with 8000 lat/lon/elev points in GCS WGS 1984.

Screenshot 1) Why are the layers shifted? No coordinate translation should have occurred in the above mentioned geoprocesses. One layer should be sitting on top of the other.

Screenshot 2) Zoom in 700m and the green layer starts to disintegrate and the red is stable. Why? Why don't both layers behave the same?

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Fri, 15 Jun 2018 22:10:13 GMT

during the process from Longitude/latitude to featureclass, whas the data defined as a GCS WGS84 ie a geographic coordinate system. Undefined data can behave strangely especially if you are working with web-based web Mercator data.

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Fri, 15 Jun 2018 22:42:37 GMT

Dan,

I've double checked that. The CS is the same for the input & the output = GCS_WGS_1984.

After cleaning up & re-running several times the dubious behavior is still very evident:

output layer is shifted to the south.
it disintegrates when zooming in
reintegrates when zooming out.

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Fri, 15 Jun 2018 23:09:29 GMT

You might have to show your csv with the coordinates.

recently coordinates that were converted from Degrees Decimal minutes incorrectly caused a shift... so I am leary of anything shifty these days

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 18:46:11 GMT

Sample of data:

Lon	Lat	Altmeters
174.123329	-39.3064874	39.59999847
174.1233295	-39.30648706	39.70000076
174.1233297	-39.30648681	39.70000076
174.1233294	-39.30648647	39.79999924
174.1233292	-39.30648642	39.79999924
174.1233287	-39.30648645	39.90000153
174.1233284	-39.30648645	39.90000153
174.1233282	-39.30648648	39.90000153
174.123328	-39.30648641	39.90000153
174.1233278	-39.30648647	39.90000153
174.1233276	-39.30648656	39.90000153
174.1233274	-39.30648662	39.90000153
174.1233273	-39.30648658	39.90000153
174.1233272	-39.30648663	40
174.123327	-39.30648667	40
174.1233269	-39.30648671	40
174.1233267	-39.30648665	40
174.1233267	-39.30648665	40
174.1233265	-39.3064867	40
174.1233266	-39.30648675	40
174.1233266	-39.30648717	40
174.1233267	-39.3064874	40
174.1233268	-39.30648759	40
174.1233268	-39.30648784	40
174.123327	-39.30648796	40
174.1233271	-39.30648797	39.90000153

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Mon, 18 Jun 2018 18:57:14 GMT

John when you made that map, a base layer was added first is my guess.

Assuming you defined the coordinate system correctly (seems like an ok assumption), did you try adding the data to a new Map without!!! a default basemap... nothing... just the data and define the Map's coordinate system appropriately. I just want to rule out some projection-on-the-fly issue. Add your other 2d point data next and see if it aligns properly after... then the 3d line

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 19:03:14 GMT

Link to the datafile (it is ~4000 points and not 8000 as originally stated): https://drive.google.com/file/d/1q7MhjVh81a522EEc-J4xmdRmSbWXlCfq/view?usp=sharing

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Mon, 18 Jun 2018 19:11:50 GMT

John... downloaded and before I go further..

process and result setting Map to the same GCS

Does this look OK?

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 19:16:39 GMT

YES.

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 19:18:17 GMT

Thank you.
The above is a big bite for this Noob. Please give me time to grasp/investigate.

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 19:19:45 GMT

FYI: I don't think the aforementioned New Zealand tutorial is using GCS_WGS_1984.

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Mon, 18 Jun 2018 19:21:37 GMT

Next step.... I am assuming you are following along so that no step is missed

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Mon, 18 Jun 2018 19:30:42 GMT

Ok.. got to get the mail.. so I will give you the next 3 steps

back soon, but let me know if this is what you were/are doing and check the results.

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 19:45:01 GMT

I've never used "Copy Features" tool. Only "Feature Class to Feature Class" (because that's what the tutorial said to use).
I believe you're suggesting that I use Copy Features tool instead of Feat.Class to Feat.Class.
Thank you. I will try this but not sure why it would make it a difference.

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 19:47:51 GMT

FYI: The problem occurs immediately after the Feature Class to Feature Class geoprocess.
So, I first import the datafile using Make XY Event Layer which creates the first layer to compare.
After I run Feat.to Feat. against it, the 2nd layer is created and doesn't match it's input layer. I don't understand why a straight copy (ie. Feat. to Feat) would translate the coordinates...?

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Mon, 18 Jun 2018 20:25:45 GMT

hmmm. my experience is all I can say … actually, your event layer is not a featureclass, whereas it has features, hence when you copy features from 'whatever', it copies them to a featureclass.... I just never use featureclass to featureclass for some reason

So in summary

make an event layer
make a featureclass from the event layer
points to line
line to vertices

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 20:33:32 GMT

Yes, correct. this is all what I did in 2D (as stated earlier). It's in the 3D tutorial that all heck breaks loose.

Re: Dubious Geoprocessed 3D layer behaviors

DanPatterson_Retired — Mon, 18 Jun 2018 20:40:39 GMT

Well... now you learned an 'alternate method' and have something that works... so the tutorial wasn't a complete failure

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 20:43:24 GMT

Perhaps my question is obfuscated by all the detail.
My basic question is "Why is the output layer shifted south of the input layer?"
I would think after a Feature Class to Feature Class operation the output layer should sit nicely on top of its input layer. That is what happens in 2D. But in 3D, using the 3D tutorial as a base, the output layer is shifted unexpectedly.

Re: Dubious Geoprocessed 3D layer behaviors

JOHNDONALDSON4 — Mon, 18 Jun 2018 20:46:49 GMT

alright. I'll give that a shot and get back to you. I was following the ESRI youtube video faithfully though. I had to slow it down various places to get its exact instructions.