Quote:
Originally Posted by vegasone
Admittedly, the parsing technique I am using is tedious. A different technique is faster to write code for but is slower in execution. I have yet to strictly determine the format. I am leaning towards tagging the start of each entry, pp, workout…
You may want to check out the single and multiple file formats available for past performance data from Bris. That may give you some ideas.
|
I currently use and process Brisnet files which are zipped csv files with data partitioned into separate files. Being that the files are partitioned by data types, no start of fields is required. If single lines are desired, field tagging will be required. Does not really matter to me which type people want, as I take the data and save it in a Microsoft Server database. Therefore, if properly designed, telling the server date, track and race number is trivial to fill up a dataframe or C/C++ structure. With no input, I'll place the data in a Brisnet's type files. The thing about Brisnet files is, you must keep track of the mapping of the data. Brisnet fully documents the mapping.
