First step define your service points. You don’t need to specially format your data, just make sure it includes latitude and longitude columns. Just tell RouteXL which column means what and you are set to go.
Next define your fleet. This is also user formatted data, just tell RouteXL where to get the capacities, shift times, start and end points.
Now you need to build your matrix, which pre calculates all times and distances between the points to be used later in optimization. RouteXL can calculate millions of these pairs in minutes.
If you add new points to your point set, RouteXL only calculates the distances and times for the new points to save you time.
All this data is saved in a QVRW file, a project file for your routing exercise.
Now you are ready to segment your points and allocate trucks.
All you do is choose the “Dynamic optimize” option. RouteXL automatically plots your points and lets you select points.
Immediately after points are added or removed from the selection, RouteXL calculates the trucks needed and their routes. You can even have RouteXL display the routes, or just straight lines for clarity if needed.
If your selection has no solution, you can click the previous button to go back to the last working selection and try another.
When you are ready you can add these points to a cluster, say for example “Monday shift”
You can do what ifs, by selecting points and then adjusting truck capacities and shift times and clicking “Refresh routes” to calculate the best truck allocation and routes.
Once all clusters have been created you can recalculate all clusters and generate an output report in graphics and spreadsheet showing all the truck allocations, travel times shift times etc.
You can save your routes to any spatial format: shape files etc.
You can perform any spatial analysis on the results using themes and heat maps etcetera.
It is completely customizable and allows storing your geological data in almost any database or data format.
Supported databases include:
SQL Server (All versions including Express)
Oracle (All versions from 9 up)
GeologXL allows offline operation. Before leaving for the field, download the data you wish to work with. This includes your own custom metadata. Then while out you can modify, delete and add new geological data. When you return to the office just click on the synchronize button and your data is uploaded and synchronized with the server database.
GeologXL allows total freedom over the fields captured. It allows defining custom lookups, validation rules etcetera.
The geological data is stored as native 3D spatial data in the database. Thus in Oracle it supports Oracle Spatial. In SQL server it supports the native SQL 2d geometries, and using our SpatialBase it supports any 3d data. If you don’t need to manipulate the 3d data inside Sql server then the data is stored in binary form on the database and can be manipulated in the GeologXL front end.
Relations can be defined between geological data tables allowing for capture of master detail data.
Data can be exported to almost any graphic format including:
ESRI shape files
Mapinfo TAB files
Modelmaker TOT files
and many other lesser known formats
Any external spatial data can be loaded and overlaid. Data can be loaded from the following sources:
ESRI shape files
Mapinfo TAB files
Whittle block models
All image file formats
ModelMaker TOT files
and many more
Data can be coordinated by placement of tapes and construction points.
Data can be captured in freehand as well as needed.
MineModeller Version 4.0 allows Microstation Levels to store data from an external spatial database.
The data in the levels can be synchronised with the database after either database changes have been made or elements have been added, updated or deleted in Microstation.
When the level is synchronised, its data with all attributes is stored inside the Microstation design file, allowing it to be inspected and browsed offline from the database.
The grid can be sorted, filtered and grouped and then selected rows can be selected in graphics.
Also selected elements in Microstation can be filtered in any open data grids for easy location of data spatially.
Each level can be individually configured to link to its own database and table.
A query and link column is specified per level to link the tabular data with the Microstation elements.
It is possible to link to Oracle native spatial columns, Oracle OGC Well Known Binary columns (WKB), as well as SQL Server native and WKB columns. Finally you can link to our famous full 3D spatial extension to SQL Server SpatialBase.
This is an excellent solution for doing Geological modelling in Microstation. You can filter your geological data with complex attribute filters, and then spatially operate to build surfaces or model structures as needed. All the data can be stored in a central spatial database and thus securely shared within your organisation.
Also it is then possible to work offline and when ready then publish your results to the central database.