SS3 Field books and Datasets
| Product(s): | InRoads, MX, GEOPAK |
| Version(s): | 08.11.09+ |
| Area: | Survey |
- Data in the same fieldbooks is all connected, data in separate fieldbooks is disconnected from one to another.
- Separate field books are recommended when the data needs to be separate such as stockpiles or other disconnected data.
- Data in separate field books does not need to be unique while data in the same field book is required to have unique names.
- Data that needs to be connected should be in the same fieldbook, each separated imported data from the field will be classified on a different “Datafile”. Two,three…etc… different datasets should be processed within the same fieldbook, each one taken as a different datafile.
- If you have two chains with the same name within the same field book (but different datafiles), the name of the second chain will be automatically upgraded. This will not happen if the chains are in separate field books which may cause name conflict problems later if the user wants to export to GPK. We always stated that duplicate named data could and would exists in separate field books.
- To perform editing across data files, all of the data files must be in the same field book.
