Hi Eric,
Thank you for your questions. I will address them one by one:

> Match results times:
You are correct, we don't have an indication. It happens to be that all of the times are based on the timestamp of the 
truck for the event, which means it is usually the local time of the event. If you are willing, please open a tracker 
for this so that we can investigate how to most effectively communicate this portion of the response data.

> Events location:
Unfortunately, for the location field, all the API is doing is passing you information from the official FIRST database 
about events. In that database, the "official" location of an event happens to have the venue name pegged to the front, 
which is why it shows in the location. What I would recommend, if your use case requires location to not have venue, is 
to use the venue to do a "search and replace" in your selected language, followed by a "trim" to end up with a string 
with purely the city, state, etc.

For district codes, the intention is to have them be null, not empty strings like the documentation shows. However, the 
district portion of the API has not yet been implemented, so the examples do not reflect that in the documentation. If 
you wish, feel free to open a tracker so that we can keep you abreast of the changes, but it is our intention to have 
this be null in the production environment.

>Team Listings
The name short, name full and name nick fields are all fields set by the team through TIMS (or derived from information 
they enter, like sponsors). Most every team has full and nick names, but not all teams will have a short name. It just 
depends on what they have entered in their team profile in TIMS. Most changes to TIMS will be reflected in the API 
within 24 hours (once in production, not during beta or pre-beta).

As for ID, it may have been on an earlier version of the documentation, but it is no longer an available field.