Use Back buuton on your browser to return. Otherwise click here for Foresoft Home.

Wednesday, December 23, 2015


When importing a DWG. When we come across a TIN surface represented as 3DFace we now ask whether surface is natural or design. We repeat this for each separate surface in the model. Separate surfaces are assumed to be on different layers.


When creating Trimble data files, we now support State Plane coordiantes for mainland USA and territories. If your data is in a local coordinate system you can now enter in Lat Lon of the master bench.

Wednesday, December 9, 2015


Added in option to roadworks - variable entry templates. You can now export and import the table to a csv file (ie excel).  So now for example you could:

  1. export to a csv. Do editting within excel and import back into the same table
  2. export table 1 to a csv. Create a new table 2 and import contents of table 1 to table2

Monday, November 16, 2015


When importing a DWG that contains 3d faces etc we now ask what type of surface we are using. ie whether it is as surveyed or a design surface. Point heights are set appropriately.

Have added in a utility to create a string from a contour. We now ask for a contour height.

When exporting raw data to a file; the file name edit box has been made longer. This helps those people who use lots of nested folders to keep track of there data.

When displaying a profile, we have changed the text display color when in "plot view" mode. The grey was hard to read.

Wednesday, November 4, 2015


When creating Tribmle .gps control block you now have the option to create rectangular grid array's as well as specifying a grid rotation. This means you can create control blocks that have less distance between grid points.

Friday, October 30, 2015


There were a number of issue's when creating Trimble gps control blocks when using feet. These have been fixed.

Wednesday, October 28, 2015

CDS 2.7.15

Importing LandXML was broken; now fixed.

Wednesday, October 14, 2015


Have added in the ability to create hinge links. This is a common link between sections and forces the edges to meet at the same height. Particularly useful for creating surfaces with rotating lasers.

Please note that for GPS solutions there is an option to smooth between sections which can give a similar solution


Have added in

  • option to import directly a AMW NEZ file
  • option to export a AMW FBG file

Monday, September 28, 2015

Check gps files has moved.

New link is - it has more memory and doesn't bring up unwanted spam websites that the free hosting was doing.

Thursday, September 24, 2015

Check .gps files created from Ezigrade

We have created an online viewer for displaying Trimble FMX, Field Level 2 files. Quickly check the .gps file that you have created before sending it to the land grading contractor.

Alternatively if you are the Land Grading contractor, then check the file before you bother loading it onto your tractor.

This online utility will work with files from any source; ie multiplane, optisurface, wm_form as well as Ezigrade.

Go to  and try it on your data.

Wednesday, September 23, 2015

CDS 2.7.14

CDS could crash if using icon to run "interpolate profiles and sections". When copying strings, points etc from job to job some layer information went missing if layers were non upper case.

Tuesday, September 15, 2015

Ezigrade 2.7.4

We stuffed up the Trimble .gps export a couple of updates ago. The design heights and cut/fill were way out. Now fixed.

Monday, September 14, 2015

Ezigrade 2.7.3

Have modified the Export Trimble .gps file. It now only puts the gridded data for .gps file around the points that only have valid heights. We have also added in an option to allow you to export a specific section of the job.
Have also speeded up some of the draw functions.

Thursday, September 10, 2015

CDS 2.7.13

Number of updates to help display and process larger jobs such as LIDAR data.

Includes the following updates

  1. variable ascii input. If reading in data that doesn't contain point numbers then it no longer checks for existing points numbers to avoid multiple point numbers. The numbers are allocated hence they wont clash
  2. speeded up re-indexing of chainage/offset index
  3. speeded up onscreen display. For example 2.3 million points will now render in under 10 seconds
  4. if database contains more than 200000 points then CDS automatically displays job as a point cloud. Any text for large jobs just leads to a massive blob on screen anyway

Displaying image.png

Monday, August 31, 2015

Ezigrade 2.7

Have made a number of changes.

  1. When deleting links the other fields in the job could get corrupted and you had to redefine all the sections.
  2. Trimble (.gps) file was being formed incorrectly for odd lengths eg 1.5m. Even lengths always worked.
  3. When importing gps files there is an option to thin the data if necessary.
  4. Menu items are more logical. 

CDS 2.7.02

CDS could go into an endless loop when displaying large jobs. It could happen if you already had windows "Task Manager" running at the same time. Task manager was restarting the drawing as it thought CDS had gone non-responsive. CDS now lets the OS know it is still in-fact running.

Thursday, August 13, 2015


Have added in the ability to export a 12d ascii file. If you are an existing 12D user (and are trained in there methodolgy) it can be cost effective to supplement your 12D licence by using CDS for extra licences and using it for general data pickup and processing. Pickup your data with CDS and send data to 12D using 12d ascii file.

Thursday, July 16, 2015


Bug in road works when string alignments are using long string names fixed.

Thursday, June 25, 2015

Ezigrade 2.0.49

Ezigrade now includes the option to put out strings to the Trimble Field level II controller. This is handy for Civil Engineering type as you can see on the screen edge of drains, edge of roads, ring tanks etc. At present can't put out both strings and section edges together - maybe next update. 

Monday, June 22, 2015

Ezigrade 2.0.48

When moving a node where sections intersect the section edge heights are updated automatically when you move the node and associated section edges.

Have added in the following features to display both main grade and cross grade.
  • When moving the cursor the main grade and cross grade is displayed in status pane in lower right.
  • The contour parameters - surface colors now has options to shade the grades with respect to either the main grade or the cross grade.
When displaying the job in CDS2 the triangles are displayed as by color. The color being set in Ezigrade. This is because CDS doesn't know about grades and cross grades. Update CDS2 from members page as well.

When displaying grades the surface colors dialog puts in more appropriate default grades.

The picture below shows the cross grades.

Friday, May 22, 2015

CDS and Ezigrade

Feature added that allows one to switch seamlessly between running a job in CDS and then running the job in Ezigrade. If you are in running a job in CDS2 then from "file menu - close and open in ezigrade" then job is opened within Ezigrade. If Ezigrade is not running then it is started up. If it is already running the job is opened with the current instance of Ezigrade. This also works when going from Ezigrade to CDS2.

Ezigrade 2.0.46

When creating Trimble Field Level FMX .gps file the benchmark points were incorrect.

Thursday, May 14, 2015

Ezigrade 2.0.45

Fixups with Trimble .gps import and export.

The .gps file contains two blocks of data. The first one contains design heights. The min and max limits along X and Y axis were not always correct and was leading to a mismatch with the total number of points in the array.

The second array contains the amount of cut and fill in an array. The total number of points for this array was not always correct. We were also putting out this data reversed. ie cut was being put out as a fill value and vice versa. On Trimble FMX display this was showing with the colours reversed from what was expected. The grading still works OK though as bucket is driven from current GPS height and design value in the design array.

When exporting the Field Level 2 file we have added in a progress bar so that user knows something is still happening.

Wednesday, May 13, 2015


When creating short line / short arc tables the reference number was doubled up in the shortline and the short arc table. For example if there were three arcs there defining reference numbers were 1,2 and 3. The first three short lines were the same. This has been fixed.

Tuesday, May 5, 2015


When exporting to Leica instruments / machines etc via dbx file the strings went missing. Leica road runner expects strings to be exported to the intermediate landxml file as a "planfeature". We had changed them to alignments.

Monday, May 4, 2015


When creating route curves (Cogo - Curves - route curves) the software would put out transition spiral's even if the transition length was zero. This is now fixed.

Thursday, April 2, 2015

Ezigrade 2.0.44

Problem in Trimble GPS control files when they contain extra bench mark points; now fixed.

Monday, March 30, 2015

Ezigrade 2.0.43

Following update is for grade constrained sections, not planar designs.

When designing furrows that change direction the existing design methodology was leading to slight problems at the section edges. When designing sections individually the edges never match exactly. The smoothing will create a nice interface but for furrow design applications we want finer control.

For this type of application we have added in an option to do the design for all the sections at once. This fix's up section edges but can lead to longer design times.

To run this option use the menu item under   Tools  -  Grade Entire Job (LP)

Thursday, March 19, 2015


Problem setting background bitmaps. Was only happening fro long skinny bitmaps.
When running Autoroad, calculating new design heights. Natural surface heights were being picked up.

Wednesday, March 18, 2015

Ezigrade 2.0.42

Added in routine to convert files in a local system onto UTM based grid system. Find in the Tools - Local To UTM menu item.

Use this when you wish to grade field using LevelGuide system or other UTM based systems.

Wednesday, March 4, 2015

Ezigrade 2.0.41

When running smoothing, bug with smoothing across section boundaries. We could have the joining link set to disallow smoothing across the boundary but was doing it anyway. Fixed.

Have added in an option when exporting to Google Earth to correct points received from Trimble GPS. The Trimble GPS picks up points in a local coordinate system. However Google Earth uses a global  UTM grid. It often shows up as the field swung around the master bench point.

Tick the box as below. You need to have a master bench defined in the job. A point with a code of "mb".

Monday, March 2, 2015

Ezigrade 2.0.40

Ezigrade - multiplane txt file that uses E,N,S,W etc and was placed West of Greenwich was creating the Longitude of the master bench in the wrong position.

Thursday, February 26, 2015

Ezigrade 2.0.39

When importing a trimble multiplane txt file the master bench point was not being stored; now fixed.

Friday, February 20, 2015

Ezigrade 2.0.38

Now color coding height difference when displaying. Easier to pick cut and fill area's.
When creating levelguide .ezigrade file, ignoring some predefined descriptions.

Thursday, February 12, 2015

Ezigrade 2.0.37

Creating Trimble control file .gps for tractor. Now supports putting out field rotation. If you select option of field to be rotated then the rotation is picked up from the field grid that is being used.

Wednesday, February 11, 2015


Problem with strings losing there layers after using the strings - sort option, now fixed.

Tuesday, February 3, 2015


Query dialog. The description and code box's have been made wider so that full description or code is visible.

Ezigrade 2.0.36

Support for Trimble Field Level 11.

We have added in the ability to import a .gps file into Ezigrade. This allows you to import jobs created in Multiplane or Optisurface. You can modify the data or redesign and export in the appropriate format.

We have added in the ability to export a .gps which is compatible with Trimble Field Level 11 and can also be used as a method of importing data into multiplane.

Please note that both import and export are still in Beta and may not yet support all the .gps functionality. Please email us your .gps file if it contains something that needs to be supported.

Wednesday, January 28, 2015


CDS was giving an error message when calculating the join/invert between two points that are selected by pointing to a string segment. It would occur if there was an incorrectly formed string that ends in an arc mid-point. Now fixed.