Use NEZ. Don't be afraid, just use it.
Unlike the Civil3D workspace, the Planning and Analysis workspace is smart enough to know when you feed it an NEZ file formatted as csv, it will treat the 1st column as latitude, the 2nd column as longitude and the 3rd column as elevation. You are afraid it won't know, that it's not smart enough to condsider the northing in the csv as Lat and the Easting as Long, but it is smart enough. It does know. It will treat the nothing column as Lat and treat the easting column as Long. And do it despite the absence of a format labeled 'latitude and longitude.'
Q: How does it know? How does it acquire the smarts to do this?
A: Because you clicked the WORLD button and manually selected LL84 as the georeference for the csv's coordinates.
This is in sharp contrast to Civil3D where the csv itself must be formatted with specialize columns in point file.On the other hand, Planning and Analysis only needs to know the SOURCE of your coordinates, or where you start, and where you want your points to end up, which in your case is UTM84-29N for Ballyhaunis.
Chicagolooper
