Exporting elevation points

[marklcc]

Has anyone come up with a way to export elevation data (xyx points) to a for example CSV file so I can load it in my survey gear.

I have been asking Chief for 10 years to create an export tool for this, still nothing!

 

 

[SHCanada2]

you have them in a schedule?

[JiAngelo]

When you select the table there is an "export text" icon (circled green below) that is also on the right-click menu.  selecting the icon opens up options for TXT, CSV and XML exports.  For CSV I normally check "open in default spreadsheet editor" and it automatically opens in XLS after export.  You can then resave in XLS format or keep it as CSV.

 

When I save it in XLS format, I can add columns to the right that calculate on the data in the imported columns.  On subsequent exports to a new CSV filename, I can cut and paste the new imported data over the old imported columns in my XLS format and the calculations will update themselves based on the new data provided. 

 

 

[marklcc]

it doesn't work i got this from a guy years ago who made this macro for me but it wont export.

He made special point markers and a special schedule, but they no longer work.

I was hoping chief had created a tool to do this by now, but I guess not.

Thanks

 

[Alaskan_Son]

4 hours ago, marklcc said:

it doesn't work i got this from a guy years ago who made this macro for me but it wont export.

He made special point markers and a special schedule, but they no longer work.

 

Not sure who you got that from, but I would just do a little troubleshooting to try and find out why it stopped working.  If you have the values in a schedule, you should be able to export quite easily.  Must just be a slight formatting or export issue you need to straighten out.  Might be something as simple as getting rid of the unit indicator even.  

Edited 9 hours ago by Alaskan_Son

[JiAngelo]

Would have taken less time if you'd posted your plan.

I agree Chief could provide a simpler way to create a CSV table of elevation points.  

I used a Plot Plan Note, added custom fields to match yours, and added some custom macros that /12 and round(4) decimal places for macro values elevationf, x_position & y_position.

The Plan Notes Schedule allows you to specify 4 trailing zeros.

Everything is now shown in feet, so I didn't bother to call that out.

 

Each Note has an arrow to read an elevation point's data.  Once you have one created and showing the correct values, you can copy & paste/move the note+arrow to the next point and it will auto populate the schedule if you uncheck "group similar objects".  They will incrementally number themselves with each copy/paste, then on the schedule you can drag them into the order you want and they will renumber again automatically.  (I actually added an extra field to know which was #1, #2, etc. which made it easier to order the POINTNO field.

 

After I exported to CSV, I added some calculations to the right to get perimeter distances between the points 1-4 and doublecheck everything..

 

If your macro is 10 years old, it probably needs adjusted like @Alaskan_Son indicated above.

 

[Alaskan_Son]

41 minutes ago, JiAngelo said:

Would have taken less time if you'd posted your plan.

I agree Chief could provide a simpler way to create a CSV table of elevation points.  

I used a Plot Plan Note, added custom fields to match yours, and added some custom macros that /12 and round(4) decimal places for macro values elevationf, x_position & y_position.

The Plan Notes Schedule allows you to specify 4 trailing zeros.

Everything is now shown in feet, so I didn't bother to call that out.

 

Each Note has an arrow to read an elevation point's data.  Once you have one created and showing the correct values, you can copy & paste/move the note+arrow to the next point and it will auto populate the schedule if you uncheck "group similar objects".  They will incrementally number themselves with each copy/paste, then on the schedule you can drag them into the order you want and they will renumber again automatically.  (I actually added an extra field to know which was #1, #2, etc. which made it easier to order the POINTNO field.

 

After I exported to CSV, I added some calculations to the right to get perimeter distances between the points 1-4 and doublecheck everything..

 

If your macro is 10 years old, it probably needs adjusted like @Alaskan_Son indicated above.

 

 

I created a similar system, but rather than using referencing defined elevation points, it can actually pick up on underlying elevation data.  In other words, drop the point wherever you want, and it will simply report whatever the terrain is doing at that location.