Dubious Geoprocessed 3D layer behaviors

994
29
06-15-2018 02:52 PM
JOHNDONALDSON4
New Contributor III

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:

  1. Make XY event layer
  2. Feature class to Feature Class
  3. Points to Line
  4. 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.

 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?

Zoom in ~700m and the green layer starts to disintegrate and the red is stable. Why?

0 Kudos
29 Replies
DanPatterson_Retired
MVP Esteemed Contributor

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.  

JOHNDONALDSON4
New Contributor III

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.

Feature to Feature geoprocessing: Please note "Output CS"

0 Kudos
DanPatterson_Retired
MVP Esteemed Contributor

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

JOHNDONALDSON4
New Contributor III

Sample of data:

LonLatAltmeters
174.123329-39.306487439.59999847
174.1233295-39.3064870639.70000076
174.1233297-39.3064868139.70000076
174.1233294-39.3064864739.79999924
174.1233292-39.3064864239.79999924
174.1233287-39.3064864539.90000153
174.1233284-39.3064864539.90000153
174.1233282-39.3064864839.90000153
174.123328-39.3064864139.90000153
174.1233278-39.3064864739.90000153
174.1233276-39.3064865639.90000153
174.1233274-39.3064866239.90000153
174.1233273-39.3064865839.90000153
174.1233272-39.3064866340
174.123327-39.3064866740
174.1233269-39.3064867140
174.1233267-39.3064866540
174.1233267-39.3064866540
174.1233265-39.306486740
174.1233266-39.3064867540
174.1233266-39.3064871740
174.1233267-39.306487440
174.1233268-39.3064875940
174.1233268-39.3064878440
174.123327-39.3064879640
174.1233271-39.3064879739.90000153
0 Kudos
DanPatterson_Retired
MVP Esteemed Contributor

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

JOHNDONALDSON4
New Contributor III

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

0 Kudos
JOHNDONALDSON4
New Contributor III

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

0 Kudos
DanPatterson_Retired
MVP Esteemed Contributor

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

process and result setting Map to the same GCS

Does this look OK?

JOHNDONALDSON4
New Contributor III

YES.

0 Kudos