Queries to Helioviewer's Feature/Event Web-service return a list of "Event" objects each of which include a set of known/required parameters (catalogId, startTime, endTime,etc), as well as a list of catalog-specific parameters which are encapsulated in a "properties" subarray.
The "coordinates" portion of the main event object, however, still varies from catalog to catalog. For some catalogs the events include "hlat" and "hlong," for others: "polarCpa" and "polarWidth."
I propose that we create a new parameter "coordinates" which could encapsulate the variable aspect of the coordinate system. The types of parameters to expect could still be fully-determined based off the coordinateSystem property of associated catalog object, and the individual Event object parameters would now be uniform.
I was planning on doing something like that. Creating a seperate coordinates parameter seems like a good idea to me.
As this is a change to the interface, which leads to multiple changes in the implementations, I would like to get it right the first time, so if there are any more feature requests to the interface, please tell me in advance.
Also, are there any suggestions for improving the naming of coordinates? "hlat", "hlong", "polarCpa", "polarWidth" etc. are simply the designations used in the first data sources we used (NOAA and CACTus I think). Maybe "latitude", "longitude", "principalAngle", "paWidth" are better understandable?