Quantcast
Channel: OpenRoads | OpenSite Forum - Recent Threads
Viewing all articles
Browse latest Browse all 15596

Latitude Longitude Annotation with InRoads

$
0
0

MicroStation version 08.11.09.292

InRoads version 08.11.07.566

With  particular geographic  coordinate systems assigned, the Auxiliary Coordinate System and InRoads compute latitude and longitude differently and display different results (see table below).  The Auxiliary Coordinate System uses the units of the assigned geographic coordinate system and the design file working units to calculate the Lat/Long.  InRoads reads the units of the active design file only for its latitude/longitude computations and does not apparently read the coordinate system units, leading to a possibility of an incorrect display or annotation of the Lat/Long using InRoads.

Perhaps the best way to assure that InRoads performs its Lat/Long computations correctly would be for it to use both the design file working units AND the coordinate system units like ACS does - CR?

 A method for achieving the correct latitude/longitude annotation from InRoads requires that the design file working units match the units of the assigned geographic coordinate system.  InRoads "reads" the design file units at launch and at MicroStation File>Open - so, you can't just change them in the design file on the fly.  You can match the working units to the coordinate system units, save settings, and reopen the DGN file - and then InRoads will compute the correct latitude and longitude.  Then you can use InRoads Tracking or Place Drafting Note to annotate the Latitude and Longitude correctly.

GCS/ACS

GCS units

DGN working units

ACS Position (Lat, Long)

InRoads Lat/Long

OR83-N

Meter

Feet

45°44'54.4314",  -120°1'12.0172"

28^48'4.0037"N,  56^35'3.0897"W

OR83-N

Meter

Meters

45°44'54.4314",  -120°1'12.0172"

45^44'54.4314"N, 120^1'12.0172"W


Viewing all articles
Browse latest Browse all 15596

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>