Would your team be interested in sharing scouting data?

The idea is to build a shared database of scouting data that any team has the ability to submit to and view. Using an API, teams will be able to send JSON data following a set format after competitions. This allows data to be obtainable by teams that haven’t been in the same competition as a team they are facing, and allows data to be cross-referenced for higher accuracy.

  • Yes, our team would love to submit data!
  • Maybe, we’d like to see the final product first
  • No :frowning:
0 voters

Please note that this would be something that your team would submit to after a comp, not during

1 Like

Sounds a lot like with The Purple Warehouse is trying to do.

I do like the idea, but also love the xkcd: Standards that teams try to do with scouting, especially recently.

1 Like

The big difference between this and Purple Warehouse (which I’m not an expert on for reference) is that Purple Warehouse is designed as a full scouting platform, while this is designed to be platform-agnostic and just take raw JSON data.

1 Like

Apologies, I confused the platform with their data structure. They’ve been advertising The Purple Standard in order to allow anyone to add their data to TPW - GitHub - HarkerRobo/the-purple-standard: A unified, community-driven standard for FRC scouting data ( The Purple Standard Press Release (thepurplewarehouse.com))

2 Likes

Hello, I am a dev on TPW (collaborative scouting app, analyzer, and shared database) and The Purple Standard (open, customizable data format/standard for any scouting platform/interface). We will also be releasing an API to send/receive TPS formatted data into the shared database soon, but we are always looking for more feedback and community contributions on TPS. Please let me know if you have any suggestions, ideas, or if there’s some way we can work together to help make scouting data accessible and open for all!

1 Like

Hello! I’ve heard of TPW, but I haven’t seen much of the actual product. The project we are working on in its current scope is solely intended to be used as a post-competition database. For this 2024 season, we plan to have the submission and viewing system finished and ready by week 1. Work on data analysis will be happening in post-season, and it would be great to be able to collaborate on that.

Additionally, all of the backend is powered through an API that is also currently being built out during this season, and currently contains entry submissions powered by custom schemas. Maybe we can figure out a way to share data between our two databases? We would love to work with you!

1 Like

For us, the analysis and database viewing/export, etc. is hosted through TPW, and the goal of TPS is just to standardize the data format and property naming/units so that scouting entries can be shared easily through a common format. There are several other scouting apps we know of that are planning to adopt TPS, so it would be great if you could offer a TPS format import/export option for your platform. Once in the TPS format, it should be pretty straightforward to use each others’ API to cross share the data.

The overall description of how the standard is set up is at https://thepurplestandard.com and our github has all of the property information and example datasets/scouting entries. If the data points you’re storing map nicely to the existing properties in TPS then you just need to apply the TPS naming and json structure, otherwise, you can add a new property that others can also recognize. If your project has a github repo, we would also be happy to try to implement the TPS export directly there, but we are working on a js SDK to make it easy to convert any data format into TPS.

We post updates mostly through our discord and it might be easier to discuss further there in dms. Look forward to joining forces!

1 Like