Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
vlkb-soda
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ViaLactea
vlkb-soda
Commits
c0b5d489
Commit
c0b5d489
authored
11 months ago
by
Robert Butora
Browse files
Options
Downloads
Patches
Plain Diff
README update SODA-pure
parent
36a8f79e
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+9
-5
9 additions, 5 deletions
README.md
with
9 additions
and
5 deletions
README.md
+
9
−
5
View file @
c0b5d489
...
@@ -3,7 +3,7 @@
...
@@ -3,7 +3,7 @@
is a web-application to access astronomical data stored in FITS-files.
is a web-application to access astronomical data stored in FITS-files.
It implements SODA IVOA recommendation v1.0 (https://ivoa.net/documents/SODA/20170517/index.html).
It implements SODA IVOA recommendation v1.0 (https://ivoa.net/documents/SODA/20170517/index.html).
Docker image is available in this repository and may be launched by
the following
**compose.yaml**
.
Docker image is available in this repository and may be launched by
an
**compose.yaml**
as in this example:
```
yaml
```
yaml
version
:
'
3'
version
:
'
3'
...
@@ -23,15 +23,19 @@ services:
...
@@ -23,15 +23,19 @@ services:
```
```
The above configuaration assumes:
The port number, ACCESS_CONTEXT_ROOT and directory to FITS-files must be adjusted for the given instance.
The above configuration example assumes:
*
'SKA' project holds FITS-files in sub-directories under:
`/srv/ska/surveys`
*
'SKA' project holds FITS-files in sub-directories under:
`/srv/ska/surveys`
*
will be accessed remotely by URL: http://
<server>
/ska/datasets/soda
*
will be accessed remotely by URL:
`
http://<server>/ska/datasets/soda
`
*
identified by SODA-param ID which is
**IVOID**
of the form:
*
identified by SODA-param ID which is
an
**IVOID**
of the form:
`ID=ivo://<authority>/resource-key?<relative-pathname>#extnum`
`ID=ivo://<authority>/
<
resource-key
>
?<relative-pathname>#extnum`
Note that the service apends
**soda**
to ACCESS_CONTEXT_ROOT.
Note that the service apends
**soda**
to ACCESS_CONTEXT_ROOT.
The pathname in the ID is relative to the path in compose.yaml volume-mapping (e.g. '/srv/ska/surveys').
The pathname in the ID is relative to the path in compose.yaml volume-mapping (e.g. '/srv/ska/surveys').
The FITS extension number
`#extnum`
is optional. Default is the primary HDU.
The FITS extension number
`#extnum`
is optional. Default is the primary HDU.
Data access example:
Data access example:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment