Basic Usage Details:
For additional information please refer to the FITS homepage.
- Conventions Used In Examples:
Below are the conventions we will be using within the examples given.
- /fits
- The context root is assumed to be /fits. Your context root may be different depending on installation
- HOST
- Refers to your server where fits has been installed.
- PORT
- Refers to the port on which fits is running.
- REMOTEFILE
- Refers to the filename with full path on the FITS server to examine
- LOCALFILE
- Refers to a file which you will upload to FITS with full path
- Endpoint:
/examine
Examining a file and returing the corresponding metadata containing both FITS output and standard schema output in XML
format. (See FITS for more information.)
- GET (using curl):
curl --get -k --data-binary file=REMOTEFILE http://HOST:PORT/fits/examine
- GET (using browser):
http://HOST:PORT/fits/examine?file=REMOTEFILE
- POST (using curl):
curl -k -F datafile=LOCALFILE http://HOST:PORT/fits/examine
- POST (using browser):
http://HOST:PORT/fits/index.html Use the upload form.
- Endpoint:
/version
Obtaining the version information for FITS being used to examine the input files returned in plain text format. (GET request only)
- GET (using curl):
curl --get http://HOST:PORT/fits/version
- GET (using browser)
http://HOST:PORT/fits/version
- Information
The return of any fits call will be a structured XML. If the file is properly identified this will be the FITS output, if there is an issue with the uploaded file an XML error response.