Support for v3.1+ HAPI servers about bleeding_edge HOT 3 OPEN

HTML docs here:

https://github.com/hapi-server/data-specification/blob/master/hapi-3.1.0/HAPI-data-access-spec-3.1.0.md

from bleeding_edge.

Just a heads up - Scott Boardsen has an official IDL client for accessing HAPI data:

https://github.com/hapi-server/client-idl

Perhaps we should update our HAPI routine in IDL to use Scott's tools instead of duplicating the effort (and perhaps contributing the updates directly to his client if needed). Using Bob Weigel's HAPI client in Python has made our job very easy (since we get all of the HAPI spec updates that he implements, and we're not duplicating effort).

from bleeding_edge.

At this point, I think no SPEDAS changes are needed. First, I don't know of any production HAPI server that uses the 3.1 specification, so any changes will be hard to test. Furthermore, the HAPI version 3 specification says that no changes are necessary because HAPI 3.1 servers should also accept version 2 commands. So, everything SPEDAS is doing should also work with 3.1 servers. Changes will be needed only when we implement some functionality that exists in version 3 and does not exist in version 2.

For reference, the version 3.1.0 specification says:

"HAPI 3 servers must accept both the old and these new parameter names"
https://github.com/hapi-server/data-specification/blob/master/hapi-3.1.0/HAPI-data-access-spec-3.1.0.md

In a future specification, some of the version 2 parameters may be deprecated and in that case, it will be necessary to change some of the SPEDAS code.

from bleeding_edge.