EICA.csv File Description and Field Mapping: Description: The EICA.csv file (Everything I Care About) is created by the JCapper 2025 Main Module during Build Database routines. It contains more than 2500 columns. The objective is to facilitate importing large amounts of JCapper data into third party data tools such as Microsoft SQL Server, Python etc. for statisical analysis. Field Mapping: --Section 1. Column names: "pps" (without the quotes) followed by column number. Data Source: JCapper JCP Past Performance Data File (1435 Cols) Description: Raw Past Performance Data Field mapping: http://www.jcapper.com/MessageBoard/Reports/JCPFieldMap_03302020.txt --Section 2. Column names: "res" (without the quotes) followed by column number. Data Source: HDW F Text Chart Results File (255 Cols) Description: Raw Chart Results Data Field mapping: http://www.jcapper.com/messageboard/reports/Comma_Delimited_Charts_Spec.pdf --Secton 3. Column names: "tkw_" followed by the 39 TrackWeather Column Names from the ChartRaces Table Data Source: ChartRaces Table in the JCapperSDK.mdb File (Cols 0-38) Description: Weather Observations from the JCapper TrackWeather API Field mapping: http://www.jcapper.com/messageboard/reports/TKW_ChartRacesFieldMapping.txt --Section 4. Column names: "ply" (without the quotes) followed by column number. Data Source: Pl_Profile.txt File (550 to 600 Cols)(currently 573 Cols) Description: Factors (numeric value, rank, and gap) and output generated by JCapper in Playlist File Mode Field mapping: http://www.jcapper.com/messageboard/pdfs/fieldmap_dec012011.pdf --Section 5. Column names: Actual Factor Names of TDX_, NCALL_ NRM_, Implied_, and Bucket_ factors (900 Cols) (with Cols 639 to 900 slated for future use) Data Source: TDx_, Nrm_, Implied_, and Bucket_ factors generated by the Platinum program Field mapping: I don't have formal field mapping for these factors yet. However you can glean what most of these factors are from this JCapper Release Notes PDF: http://www.jcapper.com/helpdocs/JCapperPlatinumBuild198_02012021.pdf --Section 6. Column names: Actual Column Names from the StarterHistory or StarterHistory2025 Table Data Source: StarterHistory Table in c:\JCapper\Exe\JCapper2.mdb file (253 Cols) -or- Data Source: StarterHistory2025 Table in c:\JCapper\Exe\JCapper2.mdb file (255 Cols) Description: Factors (numeric value, rank, and gap) and output generated by JCapper in SQL Mode StarterHistory Table Field Mapping: http://www.jcapper.com/messageboard/reports/JCapperStarterHistoryFieldMapping01272024.txt StarterHistory2025 Table Field Mapping: http://www.jcapper.com/messageboard/reports/StarterHistory2025-FieldMapping.txt --Notes: StarterHistory Table Column Reassignments: 1. Scratched horses are included in the data. Scratched horses are designated with a Y in Column 97 (res97) of the HDW Text Chart Results (Section B.) 2. Dates formatted as: Section A: yyyymmdd -- example: 20240126 Section B: mm/dd/yyyy -- example 1/26/2024 Section c: mm/dd/yyyy -- 1/26/2024 Section D: #yyyy-mm-dd# -- example: #2024-01-26# 3. Track Codes: a. JCP FileNames always have 3 char track code, example: AQU (Aqueduct) b. For 2 char Equibase Track Codes an X char is added, example: SAX (Santa Anita) c. Track for past running line data in Section A cols pps286-pps295 for 2 char track codes contains a 2 char track code. d. Lone exception is Fairmont Park which is FPK (to avoid confusion with Fairplex (FPX) which is no longer running. e. HDW Text Chart Result FileNames are 2 Chars for 2 char Equibase Track Codes, example: SA (Santa Anita) f. Track Code in Section D StarterHistory Table always 3 chars, example: SAX (Santa Anita) 4. User Defined Enhanced Settings: a. Miltary Post Times are set -8 hrs GMT Pacific (US) b. Data Trasformations togled ON (Gap transformed to pct of race total) 5. UserFactors, As the name implies these are factors created by the user (max of 8.) a. UserFactors 1-5 are included in Section C columns ply498-ply512. 6. SQL Factor Setup for Section 6 above: a. SQLDataBits reassigned to SIRESSIRE Column in the StarterHistory Table. ---See Doc #23 on the Help Docs page at http://www.JCapper.com ---Link, here: http://www.jcapper.com/SQLDataBits.html b. Factors I chose for User Defined SQL Factor Setup in Slot #'s F01-F35: ---See Doc #22 on the Help Docs page at http://www.JCapper.com ---Link, here: http://www.jcapper.com/Article_AddJRating.html 01. NRM_MLPROB 02. PED_TURF 03. TDX_ODDSHIST_CX10 04. PED_WET 05. NCALL_TDX_FIN_BEST10 06. NCALL_TDX_FIN_CX10 07. _SIRE-PERIPH-12 08. TDX_SURF_CX10 09. TDX_WOFAST_BEST10 10. TDX_WOFAST_CX10 11. BUCKET_A_ODDSPROXY 12. TDX_WOPCT_CX10 13. TDX_WOFIT_BEST10 14. TDX_WOFIT_CX10 15. NRM_TDX_RACERATING_CX10 16. TNR 17. RDR 18. TDX_LATE_SURF_CX10 19. TDX_PACE_SURF_CX10 20. PEDIGREE 21. TDX_PACE_TRACK_CX10 22. TDX_PACE_DIST_CX10 23. TDX_LATE_TRACK_CX10 24. TDX_LATE_WETDRY_CX10 25. TDX_LATE_DIST_CX10 26. _TRAINER-PERIPH-12 27. _RIDER-PERIPH-12 28. TDX_PACE_WETDRY_CX10 29. TDX_DIST_CX10 30. TDX_WETDRY_BEST10 31. TDX_WETDRY_CX10 32. TDX_TRACK_BEST10 33. TDX_TRACK_CX10 34. TDX_FINAL_BEST10 35. TDX_FINAL_CX10 c. Names for Rider, Trainer, and Owner in StarterHistory table formatted as one name, upper case, with punctuation chars removed (so as not to interfere with sql expressions.) d. HorseName in StarterHistory table formatted as upper case with punctuation chars removed (so as not to interfere with sql expressions.) 7. Also, I should probably clarify the Prob Expressions that score Rider, Trainer, and Sire in columns F27, F26, and F07 in the StarterHistory2025 section of the file. Data in the columns for Prob Expressions is generated by an algorithm that executes a sql expression that fetches the most recent 120 days of data from the Starterhistory table and scores the returned query results. (For example, the scores in the F26 columns for trainer reflect finish position given field size for today's trainer at today's track-surface-distance over a small number of recent starts.) When you start a new database, there is scant history data to query. As a result, the values in the Prob Expression Columns will have little if any significance. But after few weeks of data (eventually) there's enough of a history in the returned query results - that the scores for rider, trainer, and (most) sires can (often) serve as useful inputs in a model. Expanding on that a little, some of the thoroughbred distances - for example 1 Mile and 3/16ths or 2090 yards (the distance of The Preakness) are very seldom run. (Maybe a handful of races at that distance each year.) But for common distances like 6f (1320 yards) there is plenty of data. Hope I managed to type most that out in a way that makes sense. -jp .