Rail3D*

   

 

Spot Log Database Fields


SpotLog uses an SQL database to store data and records.

You can use the SQL columns with the reporting feature to specifiy a custom selection clause.

Spotlog also has a DB tab which allows you to query and update the database using SQL.  The DB tab is not normally visible, you can enable the DB tab in the app's settings.

Database Tables and Columns

 

full size image

 

Comp Table

The "comp" table contains data for companies (or railways),

CompName TEXT Full text of company/Railway name eg "Belgium Railways"
CompCode TEXT Code for the company eg "SNCB"
Note TEXT A text note if set  
Country TEXT Country for the code eg "BE"
DoNoMatch INTEGER 0 or 1 if set to not match  

 

Class Table

The "class" table contains data for classes

ClassCode TEXT The class code eg "4MT"
Comp TEXT The CompCode of the company this class applies to (see Comp table) eg "UKP"
SubComp TEXT A comp subcode, as used to group the BR/GWR etc classes in the  UKP set eg "GWR"
Note TEXT A note for the class  
Desc TEXT Description text for the class  
Num0 TEXT Lowest number in the class eg "75014"
Num1 TEXT Highest number in the class  
Seen INTEGER Number of class members seen  
Total INTEGER Total number of members in the class  
Photo TEXT Path of class photo (if present)  

 

Loco Table

The "Loco" table contains data for loco records

Number TEXT Number of the loco/unit eg "09106"
Name TEXT Name eg "Hurricane"
AltNumber TEXT Alternative number(s) eg "D4013, 08759"
Note TEXT Note, if applicable  
Form TEXT Numbers of individual cars in a unit eg "802 830-0|802-632-0| etc
Seen INTEGER 1 if seen  
Photo INTEGER 1 if photo taken  
Livery TEXT Livery  
Owner TEXT Owner code  
Status TEXT Status code (see codes)  
Depot TEXT Depot code (see codes)  
Base TEXT Base (eg for preserved locos)  
webID INTEGER The unique ID of this loco recod in the spotlog data.  
SyncID TEXT A reference for this record used in Syncing  
       

 Note, the "Class" field is no longer used (SpotLog v2.6 onwards), instead Loco's are related to a Class through the Link table.  If your installed the app before v2.6 you will have the class column in the table, but it is not used by the app.

Record Table

The "Record" table contains data for records of loco's seen

Loco INTEGER The index of the loco in question in the Loco table (above)

 Important:  This changes in v3.2 of the app.

In v3.2 this links to the webID in the Loco table, instead of the _id in the Loco table

Note TEXT Any note added with the record eg "train 2C23"
Date TEXT The date of the record eg "2014-12-31 12:31"
Number TEXT The actual number entered (may be a previous number or the number of a car in a unit) eg "52889"  (car number)
Location TEXT The location of the record eg "Bath"
Photo INTEGER 1 if photo taken  
First INTEGER 1 if this is the first record for this unit  
Haul INTEGER    
SyncID TEXT Unique ID of this row, used in syncing  
Del INTEGER 1 if row deleted, used in syncing  
Mod TEXT Timestamp of when the row last updated, used in Syncing  

 Link Table

 The "Link" table links loco's to classes, thus allowing a single loco record to appear in multiple datasets (Eg UK, UK70, UKP)

Class INTEGER _id of class

Important:  This changes in v3.2 of the app.

In v3.2 this links to the webID in the Loco table, instead of the _id in the Loco table

Loco INTEGER _id of loco  
pNumber TEXT Number used in this dataset  

NB, some other columns used by the app internally are not listed above


 

Manual 

 


MRG 14/04/2016 07:26:09