Difference between revisions of "How to programmatically publishing a spatial dataset and the associated metadata by the gCube SDI"

From Gcube Wiki
Jump to: navigation, search
(Created page with "Category:Developer's Guide Category: gCube Spatial Data Infrastructure Publishing a spatial dataset in the gCube Spatial Data Infrastructure Features|gCube Spatial...")
 
 
(3 intermediate revisions by one other user not shown)
Line 4: Line 4:
 
Publishing a spatial dataset in the [[gCube Spatial Data Infrastructure Features|gCube Spatial Data Infrastructure]] implies that:
 
Publishing a spatial dataset in the [[gCube Spatial Data Infrastructure Features|gCube Spatial Data Infrastructure]] implies that:
 
* the dataset metadata (including a reference to the actual dataset stored into a repository) are registered in the CSW-compliant Catalogue;  
 
* the dataset metadata (including a reference to the actual dataset stored into a repository) are registered in the CSW-compliant Catalogue;  
The actual dataset must be stored in a repository, the infrastructure offers at least two types of Repositories: GeoServer and THREDDS DS.
+
The actual dataset must be stored in a repository, the infrastructure offers at least two types of Repositories: GeoServer and THREDDS DS (see [[Spatial Data Storage and Publishing]] for further details).
  
 
In order to publish a dataset by the [[gCube Spatial Data Infrastructure Features|gCube Spatial Data Infrastructure]], the following approaches are possible:
 
In order to publish a dataset by the [[gCube Spatial Data Infrastructure Features|gCube Spatial Data Infrastructure]], the following approaches are possible:
 
* use the [[GIS Interface]] to publish both the dataset (in a GeoServer Repository) and the associated metadata (in the catalogue);
 
* use the [[GIS Interface]] to publish both the dataset (in a GeoServer Repository) and the associated metadata (in the catalogue);
 +
** Metadata shall be produced by using a [[Legacy_ISO_Metadata_Publishing#Metadata_generation_facilities | GcubeISOMetadata]] object;
 
* use the [[GeoNetwork library]] to publish the metadata only into the Catalogue;  
 
* use the [[GeoNetwork library]] to publish the metadata only into the Catalogue;  
* use the [[GIS Publisher Service]] (not released yet);
+
** Metadata shall be produced by using a [[Legacy_ISO_Metadata_Publishing#Metadata_generation_facilities | GcubeISOMetadata]] object;
 +
<!-- Commenting GIS Publisher. Actual service is sdi-service
 +
* use the [[GIS Publisher Service]] (not released yet); -->
 +
* use [[Data Transfer 2]] to publish geospatial datasets in Thredds;
 +
** Metadata can be extracted by dataset and published into GeoNEtwork Catalogue;
 +
* use the [[SDI-Service]] to interact with the SDI via REST;
 +
** Retrieve geo-services endpoints and authorized accounts;
 +
** Initialize catalogues and policies on a VRE-basis
 +
* directly interact to [[GCube-Enabled geo-services]] declaring a gCube token;
 +
** [[GCube-Enabled geo-services]] shell automatically authorize caller with its token privileges;

Latest revision as of 11:30, 9 June 2017


Publishing a spatial dataset in the gCube Spatial Data Infrastructure implies that:

  • the dataset metadata (including a reference to the actual dataset stored into a repository) are registered in the CSW-compliant Catalogue;

The actual dataset must be stored in a repository, the infrastructure offers at least two types of Repositories: GeoServer and THREDDS DS (see Spatial Data Storage and Publishing for further details).

In order to publish a dataset by the gCube Spatial Data Infrastructure, the following approaches are possible:

  • use the GIS Interface to publish both the dataset (in a GeoServer Repository) and the associated metadata (in the catalogue);
  • use the GeoNetwork library to publish the metadata only into the Catalogue;
  • use Data Transfer 2 to publish geospatial datasets in Thredds;
    • Metadata can be extracted by dataset and published into GeoNEtwork Catalogue;
  • use the SDI-Service to interact with the SDI via REST;
    • Retrieve geo-services endpoints and authorized accounts;
    • Initialize catalogues and policies on a VRE-basis
  • directly interact to GCube-Enabled geo-services declaring a gCube token;