Thanks for the feedback, @JB! What I'm wondering most though is, "Does each ride need this much detail? Do I need to hunt down every variable that can be identified or should I just focus on the easily obtained data to get through it faster?" Each of the 3 rides in my first version of the Index of Tracked Ride Data took 2 days to find. Given the fact that there are 53 more Tracked Rides and 65 Coasters, that's 8 months of work before it's complete. (likely much longer since I can't devote 85% of my time to this task for that long like I did over the past week)
What I'm thinking of doing is just get the most critical data for each ride which takes much less time. For example, focus on getting the Reliability, Display Price, Peep Attractiveness, Entry Fee, Running Cost, and essential stat data... letting things like Price per Segment and complex stat data go by the wayside unless specifically requested. Basically trying to keep the data down to 1 or 2 lines per ride instead of 2-7 lines as seen in my 3 completed examples.
I guess what it comes down to is this question: "Is a totally complete data set actually useful to anyone or is it just button sorting?"
Thanks again for the comment! :^)