CDS 2.5.40

Bearing and Distance Table was not working properly when input inputs were set differently to those units stored in the database.

Stadia entry could lead to a doubling up of "0" layers.

New Number

Our new number is  0437684617

PS Telstra still sucks.

Telstra Sucks.

Telstra in there wisdom has ported (ie taken it away) our phone number without letting us know. We will probably need to get a new one. In the meantime please email or use web form on the contact page and we can phone you back.
Sorry for the inconvenience!

Ezigrade 2.0.34

Have added in an option to help create parallel bay/sections. From the Fields menu click on "Insert Parallel Sections/Bays".
This brings up a dialog where you can enter the number of bays, the length and the width. The function uses the currently defined grid to set the origin and the bearing along the bay. You also have the option of removing existing sections or adding to existing.
If adding to existing by moving around grid and then running this function you can define multi "parallel layouts".

Ezigrade 2.0.33

1. Max cross grade could be wrongly reported when grades are calculated. 
2. Haulage Index/Distance was not being updated

CDS 2.5.39

Fixed up an issue with merging breaklines for combined surfaces.

CDS 2.5.38

When doing join/invert sometimes rounding down to nearest second while should have been rounding up.

Some Cogo routines modified,

•  bear dist / radiate
• 2 bearing intersect
• bearing and distance intersect

If you click in the bearing by either using P command and typing two numbers or clicking on a string link then the actual bearing is used, not the value displayed to the nearest second in the edit box.

However if you type in the value then uses value to nearest second.