OpenAPI spec is incorrect for certain endpoints

[John-Boccio]

Can the OpenAPI spec please be updated? It seems certain fields are incorrect, such as the coordinates on the get photos API.

[njbrake]

To add to this: I ran into two more spec/API mismatches while building a CompanyCam integration:

1. Photo.coordinates - Spec declares type: array, items: Coordinate but the API returns a single Coordinate object {"lat": 0.0, "lon": 0.0}, not an array.

2. Photo.description - Spec declares type: string but the API returns a Description object:
   {"id": "39647164", "html": "...", "text": "..."}

Both of these cause validation failures when generating typed clients from the spec. We're working around them with a normalizer, but it would be great to get the spec updated to match the actual API behavior. Thanks!