Civil 3D and Coordinate Datums
Quote from cturlington on October 29, 2024, 2:36 pmAll,
I have questioned the need to set the coordinate datum in Civil 3d for point import and export. So decided to perform my own test by:
I am importing and exporting points using different datums, with the intent to reproduce coordinate errors based on the datums used. However, I am not experiencing any coordinate changes between the different trials, comparing nothing and eating values imported and exported. This makes me ask if it is even necessary to set the coordinates in a CAD file for just importing and exporting points. I can imagine that coordinates would be necessary for transformations but not for exporting or importing point data.
If it proves necessary to set coordinates in CAD, is there a best way to demonstrate this, so my hard head can understand it better?
Can someone shed some light on this topic?
All,
I have questioned the need to set the coordinate datum in Civil 3d for point import and export. So decided to perform my own test by:
I am importing and exporting points using different datums, with the intent to reproduce coordinate errors based on the datums used. However, I am not experiencing any coordinate changes between the different trials, comparing nothing and eating values imported and exported. This makes me ask if it is even necessary to set the coordinates in a CAD file for just importing and exporting points. I can imagine that coordinates would be necessary for transformations but not for exporting or importing point data.
If it proves necessary to set coordinates in CAD, is there a best way to demonstrate this, so my hard head can understand it better?
Can someone shed some light on this topic?
Quote from MightyMoe on October 29, 2024, 3:15 pmThe reason is to allow the XY coordinate to convert easily in CAD to LAT, LONG. If you change the projection but insert the same XY coordinate, it should show a different L,L #. Depending on the change it could be a very small number change or a huge one if you're changing zones. So by importing the same XY value, all you're doing is moving the position in the real world. N1,000,000 E1,000,000 In Wyoming state plane will be in a way different location than the same number in a Colorado zone., but it will still be 1,000,000x1,000,000.
Check the lat long on each point, they should change with the different datum.
The reason is to allow the XY coordinate to convert easily in CAD to LAT, LONG. If you change the projection but insert the same XY coordinate, it should show a different L,L #. Depending on the change it could be a very small number change or a huge one if you're changing zones. So by importing the same XY value, all you're doing is moving the position in the real world. N1,000,000 E1,000,000 In Wyoming state plane will be in a way different location than the same number in a Colorado zone., but it will still be 1,000,000x1,000,000.
Check the lat long on each point, they should change with the different datum.
Quote from Norman_Oklahoma on October 29, 2024, 3:37 pmIf your drawings are all simple and isolated you can just use "No Datum, No Projection" and get along just fine. But if you start mixing and matching external references or aerial imagery that is in this projection and that projection - as you might if employing GIS data - you will want to pay close attention to those settings.
If your drawings are all simple and isolated you can just use "No Datum, No Projection" and get along just fine. But if you start mixing and matching external references or aerial imagery that is in this projection and that projection - as you might if employing GIS data - you will want to pay close attention to those settings.
Quote from cturlington on October 29, 2024, 5:45 pmAll,
Thank you for that feedback. I will test the recommendations.
Concerning lat-long locations, I thought they were mostly used to measure on a 3D geographic datum, but I see this also in the Civil 3D prospector as point location data. So, the lat-long must be interpolated on the projected grid surface. Is my understanding correct?
All,
Thank you for that feedback. I will test the recommendations.
Concerning lat-long locations, I thought they were mostly used to measure on a 3D geographic datum, but I see this also in the Civil 3D prospector as point location data. So, the lat-long must be interpolated on the projected grid surface. Is my understanding correct?
Quote from jimcox on October 29, 2024, 6:25 pm@cturlington Yes, you are correct
Latitude and Longitude of a given point tends not to change - other than physical movement - it takes a change of spheroid model
Northing and Easting coordinates depend on the projection - change the projection and you will see those numbers change, sometimes quite significantly
@cturlington Yes, you are correct
Latitude and Longitude of a given point tends not to change - other than physical movement - it takes a change of spheroid model
Northing and Easting coordinates depend on the projection - change the projection and you will see those numbers change, sometimes quite significantly
Quote from cturlington on October 29, 2024, 7:45 pmAll,
Thanks a million for all your feedback.
I have experienced the change in lat-long values but have been unable to force a change in the Northing-Easting values by changing the datums/projections and even units. My guess is that because the coordinate systems are grid-based in Civil 3D, the units from the origin are already fixed. So, changing the datum will not change the distance to the origin unless I move the points in the file. However, I would think exporting the points with an odd datum should create a CSV point file with distances relative to the odd datum. Does that sound correct?
All,
Thanks a million for all your feedback.
I have experienced the change in lat-long values but have been unable to force a change in the Northing-Easting values by changing the datums/projections and even units. My guess is that because the coordinate systems are grid-based in Civil 3D, the units from the origin are already fixed. So, changing the datum will not change the distance to the origin unless I move the points in the file. However, I would think exporting the points with an odd datum should create a CSV point file with distances relative to the odd datum. Does that sound correct?
Quote from jimcox on October 29, 2024, 9:30 pmMost cad systems store their data as XYZ, not Lat/Long.
What you are experiencing is a side effect of this.
When the projection gets changed, the coordinate XYZ's do not. This is lazy behaviour in my opinion, tends to introduce errors, but not necessarily wrong.
Then any lat / long is calculated in terms of the projection in use at that particular time - so they DO change.
GIS software is often better behaved - if you really want to play in this area I would recommend QGis
Best practice is to
- know and understand your software
- get your coord system/projection etc set right from the very start
- write down / record what it is
- and DONT go changing it
Most cad systems store their data as XYZ, not Lat/Long.
What you are experiencing is a side effect of this.
When the projection gets changed, the coordinate XYZ's do not. This is lazy behaviour in my opinion, tends to introduce errors, but not necessarily wrong.
Then any lat / long is calculated in terms of the projection in use at that particular time - so they DO change.
GIS software is often better behaved - if you really want to play in this area I would recommend QGis
Best practice is to
- know and understand your software
- get your coord system/projection etc set right from the very start
- write down / record what it is
- and DONT go changing it
Quote from land_odse on October 30, 2024, 12:07 amAnd pay special attention to the transformation algorithms in C3D. We have encountered that the transformation of coordinates from rectangular coordinate system to geographic (or any other) coordinate system in C3D differs from the transformation algorithm in (TBC) Trimble Business Center, for example. In (TBC) there is a separate utility for updating coordinate system parameters, frankly speaking, I trust Trimble more.
And pay special attention to the transformation algorithms in C3D. We have encountered that the transformation of coordinates from rectangular coordinate system to geographic (or any other) coordinate system in C3D differs from the transformation algorithm in (TBC) Trimble Business Center, for example. In (TBC) there is a separate utility for updating coordinate system parameters, frankly speaking, I trust Trimble more.
Quote from cturlington on October 30, 2024, 7:32 amThank you all for sharing your expertise with me.
Does anyone know if there is a certification program or similar geared toward engineers and CAD people that teaches these concepts? I am familiar with NGS, NOAA, etc., but there is always some fundamental lack of knowledge, like what we have discussed here, which leaves the question about confident transformations, real software understanding, etc.
Thank you all for sharing your expertise with me.
Does anyone know if there is a certification program or similar geared toward engineers and CAD people that teaches these concepts? I am familiar with NGS, NOAA, etc., but there is always some fundamental lack of knowledge, like what we have discussed here, which leaves the question about confident transformations, real software understanding, etc.
Quote from BStrand on October 30, 2024, 7:46 amI assumed the main purpose of setting the coordinate system in Civil 3D was to get the google earth background to come in on the right spot. heh
This makes me ask if it is even necessary to set the coordinates in a CAD file for just importing and exporting points. I can imagine that coordinates would be necessary for transformations but not for exporting or importing point data.
If all you're doing is connecting some dots then who cares where in the world they're sitting. 😎
I assumed the main purpose of setting the coordinate system in Civil 3D was to get the google earth background to come in on the right spot. heh
This makes me ask if it is even necessary to set the coordinates in a CAD file for just importing and exporting points. I can imagine that coordinates would be necessary for transformations but not for exporting or importing point data.
If all you're doing is connecting some dots then who cares where in the world they're sitting. 😎