I am trying to generate elevation data along lines and I have followed the process below:
- Vertices to Points for both start and end points and deleted fields that will not have any impact
- Add Surface Information to calculate the z-value for the points based off my raster data
- Added fields to my line feature for start and end z-values
- Near to calculate the nearest line for both the start and end points
Here is where everything gets messed up. When I do my Join based on the IDs it locating both a start and an end point on the same line with the same distance and is throwing off the tool by giving me an identical elevation. It ends up with my section of 1 intersection of 3 lines looking like this:
Lines
| OBJECTID | StartZ | EndZ | START_FID | END_FID |
| 3 | 181.1 | 181.1 | 4 | 3 |
| 19 | 199.6 | 199.6 | 19 | 247 |
| 21 | 171.1 | 171.1 | 3 | 19 |
Start_Point
| OBJECTID | ORIG_FID | StartZ |
| 19 | 19 | 171.1 |
End_Point
| OBJECTID | ORIG_FID | StartZ |
| 3 | 3 | 171.1 |
| 21 | 3 | 171.1 |
So what I am seeing is that Line 21 is getting both its StartZ and EndZ from the same spatial location even though it should only be getting one or the other. How can I prevent this from happening?
