- From: Harry Prevor <habs@sdf.org>
- Date: Tue, 13 Mar 2018 14:33:42 -0400
- To: public-opentrack@w3.org
Hi all, On 03/13/2018 01:42 PM, Andy Robinson wrote: > Can anyone think of anything else, or criticize the above? I'm Harry, and I'm really hoping I can help both specifically with respect to U.S.-based data and in general with OpenTrack. I spoke with Andy about the project briefly last week, and I'm hopeful that I can help contribute. I'll do my best to be on the call Wednesday to discuss all these ideas. I had some time last week so I made a little program to parse USATF's meets directory (~2700 upcoming meets) and output JSON in a format similar to this one (I used <http://opentrack.run/athlib/build/html/schemas.html#competitions> as a reference). Of course, although much of the information gathered is basic we hesitate to include them in the OpenTrack directory until we get permission from USATF, which I don't think will be much of an issue once we reach out to them. I have worked for USATF on the association but not the national level and could maybe help with this. The code is here: https://gitlab.com/hapre/usatfmeets And more specifically the JSON is here: https://gitlab.com/hapre/usatfmeets/tree/master/out You can see some of the extra fields (description, meet director info, USATF certification, etc.) I've added and event code modifications (1-hour-runs, mountain runs) I changed to match all of the USATF data. I'll try to provide some more detail as to the specific changes I made and feedback on the proposed spec before the meeting. Let me know if there's anything else I can do to help or clarify. Harry -- Harry Prevor
Received on Tuesday, 13 March 2018 20:03:34 UTC