Problem with precise sections, processed profile is way too short.

[raschagas]

I've been trying to create a surface profile for this path.

But after creating the surface profile, it results in a 2 meter in length section. It seem it is redistributing all the 25726 length to a 600x2m line. You can see in the red polygon how it is plotted. It seems to match the DEM, but not the lenght.

I'd appreciate if you could give me some light on this one. Thanks in advance.

[ethoms-usgs]

The tool measures the length of the line in the units of the line's spatial reference so I think this is somehow a unit mismatch problem. Is the cross section line maybe being projected from geographic decimal degrees to a meter-based SR? Check that X, Y, and Z of the dem are all in meters and that the spatial references of the line of cross section and the dem are the same. Lastly, although it's possible to zoom to a surface profile in your map data frame, the values, of course, don't make sense according to a plan-view map projection. Create a new empty data frame and put the surface profile there. The spatial reference will be 'Unknown.

One thing you can do to troubleshoot the problem is to open an edit session on the surface profile line and view the table of coordinates of the vertices. The X values should go from 0 to whatever value SHAPE_LENGTH of the original, map-view, cross section line is.

Also, you can measure the line of cross section manually with the Create Routes tool (specifying length) and then check the coordinates of the vertices of that route. There will be a column, M, with the distances along the line that should make sense.

Of course, be sure the vertical exaggeration is set to something reasonable.

[raschagas]

Different projections for the DEM was causing this, so it's solved, thanks! The problem now is I'm having some trouble with the "map points to cross-section points" tool.

If you have the time I'd be happy. Thanks.

[ethoms-usgs]

Good! Glad that worked out.

For your next question, can you tell me what the spatial reference of TESTE_PERFIL_Events is? Looking back through my code I can see a possible source of error depending on that. You get the error you are seeing when, for instance, you try to move features too far away from the area on earth where they are appropriate. If your spatial reference is only built to handle a certain set of XY values, my code will fail because it re-writes the X and Y coordinate to be the M and Z values and tries to ignore the real-world coordinate system of the feature class in map-view.