Quote:
Originally Posted by Eugene Fang
I've wrote something that gets more granular data and it's used for "Search Nearby," but we don't store it anywhere else yet and thus can't serve it in the API. I'm working on making use of it elsewhere in the site and will expose it in the API.
For those curious, to get granular location data I make guesses of what a team's location could be by combining city/state/zip/country with different parts of a team's full name (which usually starts or ends with the high school or title sponsor), hitting Google's Maps API to check for validity, and then making sure the results Google gives back have the same city, state, zip, etc. as what FIRST says the team's location is. Then the best result is normalized (To fix CA vs. California, typos in FIRST's database, etc.) by hitting Google again.
TLDR: Yes TBA will expose an API for detailed street-level addresses for most teams. Hopefully within the month.
|
Cool, glad to know I'm not the only one that is finding dealing with the location data painful.
I've been using Mapzen to do it and ended up slicing up the location data TBA does return to remove the country from the end. Due to a quirk in how Mapzen does location searches Flint, MI will return weird stuff but Flint, MI, will return exactly what you'd assume. I've also started experimenting with restricting to the country that is reported for team. I've not had much luck with that yet though.
I'm using it to generate geojson files for team travel to events such as
https://github.com/schreiaj/frc-team...7mimid.geojson (they exist for all events, some of them just render funky because teams got coded to the wrong place)