Leica VIVA (Azimuths to Right Angles)

Do you need the .raw in right angle format, or just want a hardcopy in right angle format?

For the latter the end run would prob be to dump the points in a drawing and get a cogo stakeout report in right angles, but it would only be a paper copy. Let me know if you find a way to get the DC to do it please.

Which format are you exporting? If you choose for example
Jobs & Data / Export & copy data / Export fbk/rw5 data / Under Data Format select TDS RAW, you can select "Config" on the soft menu and select "Use angle right"

Whoops, I just re-read your post, are you saying you found this setting but are wanting to convert your previously exported data to angle right? If the jobs are not deleted you could re-export, otherwise I would think a manual conversion is probably your best solution, unless someone has written a script for that. I would be looking at MS Excel probably. I have written some handy Python scripts for use in Notepad++ for similar cases, that could potentially be another solution. Effort vs. benefit in that scenario.

Jacob

another possibility. push the dbx files back into the controller, change the output type to angle right (in your config set), then export the job again to the pc

Yeah, we haven't figured that out yet.

The process for collecting sets spits out azimuths, but the topo (single angle shots), come out fine in AR. I just reduce the Direct-Reverse in Carlson raw editor, and it gives the AR.

> Like the Hardware...hate viva. :good:

Jacob Wall, post: 269918, member: 1674 wrote: Which format are you exporting? If you choose for example
Jobs & Data / Export & copy data / Export fbk/rw5 data / Under Data Format select TDS RAW, you can select "Config" on the soft menu and select "Use angle right"

Whoops, I just re-read your post, are you saying you found this setting but are wanting to convert your previously exported data to angle right? If the jobs are not deleted you could re-export, otherwise I would think a manual conversion is probably your best solution, unless someone has written a script for that. I would be looking at MS Excel probably. I have written some handy Python scripts for use in Notepad++ for similar cases, that could potentially be another solution. Effort vs. benefit in that scenario.

Jacob

##"I have written some handy Python scripts for use in Notepad++ for similar cases, that could potentially be another solution. Effort vs. benefit in that scenario."

Have recently revived an interest in programming after a zillion yrs. Python seems very adaptable. Not a natural in this. More like an old guy exercising what's left of his brain. Would be very interested in any Python modules you would be willing to share re cogo, stuff we use on a daily basis in land surveying. Afraid I'm at noob level. For instance, here's code I was butchering the other day.##

import ui
import math

class Survey:
def __init__(self, brng, dist,lat,dep): #bearing to be entered like this:
self.brng = brng. # 'S45.2341E'
self.dist = dist
self.lat = lat
self.dep = dep

def course(self):
b = self.brng
quad = b[0] + b[-1]
decpoint = b.find('.') #find the decimal point
deg = int(b[1:decpoint]) #convert dms to decimal degrees
mins = int(b[decpoint+1:-3])/60.
sec = int(b[-3:-1])/3600.
az = (deg+mins+sec)
if quad == 'NE':
az = az
elif quad == 'SE':
az = 180 - az
elif quad == 'SW':
az = 180 + az
elif quad == 'NW':
az = 360 - az #need to convert to radians
lat = math.cos(az*math.pi/180)*self.dist #lat - change in north-south
dep = math.sin(az*math.pi/180)*self.dist #dep - change in east-west
return az, lat, dep

def store_az_lat_dep():
#brng = input('Input bearing: ')
#dist = input('Input distance: ') #--> eventually for user input
#xy = Survey(brng, dist, 10000, 10000) #ignore the 10000,10000
xy = Survey('45.0000E', 100, 10000, 10000) #-->for example
corDict = {xy.course()[0] : xy.course()[1:]}
print corDict

store_az_lat_dep()

##I was looking for a way to iterate the process and add to the dictionary. Ant help would be greatly appreciated.##

fieldguy, post: 331224, member: 2298 wrote: ##"I have written some handy Python scripts for use in Notepad++ for similar cases, that could potentially be another solution. Effort vs. benefit in that scenario."

Have recently revived an interest in programming after a zillion yrs. Python seems very adaptable. Not a natural in this. More like an old guy exercising what's left of his brain. Would be very interested in any Python modules you would be willing to share re cogo, stuff we use on a daily basis in land surveying. Afraid I'm at noob level. For instance, here's code I was butchering the other day.##

import ui
import math

class Survey:
def __init__(self, brng, dist,lat,dep): #bearing to be entered like this:
self.brng = brng. # 'S45.2341E'
self.dist = dist
self.lat = lat
self.dep = dep

def course(self):
b = self.brng
quad = b[0] + b[-1]
decpoint = b.find('.') #find the decimal point
deg = int(b[1:decpoint]) #convert dms to decimal degrees
mins = int(b[decpoint+1:-3])/60.
sec = int(b[-3:-1])/3600.
az = (deg+mins+sec)
if quad == 'NE':
az = az
elif quad == 'SE':
az = 180 - az
elif quad == 'SW':
az = 180 + az
elif quad == 'NW':
az = 360 - az #need to convert to radians
lat = math.cos(az*math.pi/180)*self.dist #lat - change in north-south
dep = math.sin(az*math.pi/180)*self.dist #dep - change in east-west
return az, lat, dep

def store_az_lat_dep():
#brng = input('Input bearing: ')
#dist = input('Input distance: ') #--> eventually for user input
#xy = Survey(brng, dist, 10000, 10000) #ignore the 10000,10000
xy = Survey('45.0000E', 100, 10000, 10000) #-->for example
corDict = {xy.course()[0] : xy.course()[1:]}
print corDict

store_az_lat_dep()

##I was looking for a way to iterate the process and add to the dictionary. Ant help would be greatly appreciated.##

Python is certainly a great way to get back into programming. I love the Python Script Plugin for Notepad++, since it really gives you a lot of power to work with ASCII files, and also binary files as well. Everything I've done with Notepad++ and Python has been limited to processing file contents, nothing much in the way of UI stuff, at least so far. It sounds interesting though and might give me a reason to explore other possibilities within that environment. Email me directly if you want to discuss what you have in mind.