Hi,
I used the Vincenty syntax created by Austin Nichols as indicated in this link: https://ideas.repec.org/c/boc/bocode/s456815.html
To measure the geodesic distance between my GPS points of households and specific health facilities, I used GPS coordinated in the form of (Latitude, Longitude), formatted in a Decimal Degree formate.
The syntax run fine with me and I estimated the distances in kilometers
The help file of Vincenty does cite the Javascript used I believe to construct the syntax.
I would like to disclose that Javascripts, Geography, ArcGIS...etc is not the area of my strength, and I am building my knowledge. I would appreciate an explanation in easy-to-understand language, please.
My questions:
- While constructing the "vincenty" syntax, was an appropriate and complete "projection" for the geographical coordinate system (GCS) of the (Lat, Long) points incorporated? to allow estimating the geodesic distance in kilometers or miles linear units, instead of having the output distance in decimal degree format, as it would be expected from a module estimating the geodesic distance?
or no projection was considered for the coordinates of (Lat, Long)?
- If a projection was considered, what projection coordinate system (PCS) was used/incorporated?
- If no projection was considered, what was done in the construction of this syntax to allow it to yield the distance in a linear unit like kilometers? instead of a decimal degree GPS formate? (Main inquiry)
- And what was done to assure the claimed accuracy of this syntax output of few millimeters?
-My understanding is that in software like ArcGIS, and QGIS, the projection of the Geographic coordinate system (Lat, Long) is possible. As, it allows the software to understand that the Earth is ellipsoidal in shape, not flat like the two-dimensional computer screen nor a perfect sphere. Thus, allowing the distance to be more accurately measured. How does STATA as a statical software compensate for the projection feature? or does it allow an alternative feature? or does it works entirely differently when it estimates a distance like the geodesic one on the Earth's ellipsoidal surface?
- a brief explanation of geographic vs projected coordinate systems is explained here: https://www.esri.com/arcgis-blog/pro...ng/gcs_vs_pcs/
Thank you in advance for sharing your knowledge and explanations for my inquiry.
I used the Vincenty syntax created by Austin Nichols as indicated in this link: https://ideas.repec.org/c/boc/bocode/s456815.html
To measure the geodesic distance between my GPS points of households and specific health facilities, I used GPS coordinated in the form of (Latitude, Longitude), formatted in a Decimal Degree formate.
The syntax run fine with me and I estimated the distances in kilometers
The help file of Vincenty does cite the Javascript used I believe to construct the syntax.
I would like to disclose that Javascripts, Geography, ArcGIS...etc is not the area of my strength, and I am building my knowledge. I would appreciate an explanation in easy-to-understand language, please.
My questions:
- While constructing the "vincenty" syntax, was an appropriate and complete "projection" for the geographical coordinate system (GCS) of the (Lat, Long) points incorporated? to allow estimating the geodesic distance in kilometers or miles linear units, instead of having the output distance in decimal degree format, as it would be expected from a module estimating the geodesic distance?
or no projection was considered for the coordinates of (Lat, Long)?
- If a projection was considered, what projection coordinate system (PCS) was used/incorporated?
- If no projection was considered, what was done in the construction of this syntax to allow it to yield the distance in a linear unit like kilometers? instead of a decimal degree GPS formate? (Main inquiry)
- And what was done to assure the claimed accuracy of this syntax output of few millimeters?
-My understanding is that in software like ArcGIS, and QGIS, the projection of the Geographic coordinate system (Lat, Long) is possible. As, it allows the software to understand that the Earth is ellipsoidal in shape, not flat like the two-dimensional computer screen nor a perfect sphere. Thus, allowing the distance to be more accurately measured. How does STATA as a statical software compensate for the projection feature? or does it allow an alternative feature? or does it works entirely differently when it estimates a distance like the geodesic one on the Earth's ellipsoidal surface?
- a brief explanation of geographic vs projected coordinate systems is explained here: https://www.esri.com/arcgis-blog/pro...ng/gcs_vs_pcs/
Thank you in advance for sharing your knowledge and explanations for my inquiry.
Comment