...
- Mandatory :
processing_level -mandatory
publisher -mandatory
service_title –mandatory - Optional - TBC
spatial_coordinate_description (implicitly body-fixed or J2000)
spatial_origin (implicitly body center or SS barycenter? Or observer location)
time_origin (implicitly: observer)
time_scale (implicitly : UTC – no other values allowed in data services? [only in computational services, e.g. ephemeris])
Same values to be used in registry declaration
• All floating point parameters are now in double precision – this prevents stupid errors…
Example of V1 to V2 conversion with APIS database:
EPNcore Table v1
(was not really compliant…)
| index | resource_type | dataset_id | access_url | access_format | preview_url | native_access_url | native_access_format |
|---|---|---|---|---|---|---|---|
| 23801 | granule | original_data | o5g202x4q_x2d.jpg | jpg | o5g202x4q_x2d_small.jpg | fits | |
| 23802 | granule | processed_data | o5g202x4q_proc.jpg | jpg | o5g202x4q_proc_small.jpg | o5g202x4q_proc.fits | fits |
| 23803 | granule | cylindric_proj | o5g202x4q_cyl.jpg | jpg | o5g202x4q_cyl_small.jpg | ||
| 23804 | granule | polar_proj_north | o5g202x4q_pol_n.jpg | jpg | o5g202x4q_pol_n_small.jpg | ||
| 23805 | granule | polar_proj_south | o5g202x4q_pol_s.jpg | jpg | o5g202x4q_pol_s_small.jpg |
...