Skip to content

Allowing remote WMS dataset to be automatically connected to existing harvesters #13381

@mattiagiupponi

Description

@mattiagiupponi

Is your feature request related to a problem? Please describe.

If we publish a resource to an existing external service, we want the ability to force the import of that resource without waiting for the scheduled harvesting. To enable this, the importer should allow us to create a remote WMS layer via an API by using a payload like the one below. This process should generate the resource and connect it to the harvester.

curl --location 'http://localhost:8000/api/v2/uploads/upload' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--header 'Cookie: Cookie_2=value; sessionid=6rzy8kf8w8ga49fixelmfhklixtkd9se' \
--data '{
    "url": "http://geoserver:8080/geoserver/ows?service=WMS&version=1.3.0&request=GetCapabilities",
    "title": "Remote Title",
    "type": "wms",
    "identifier": "geonode:boxes_with_date",
    "parse_remote_metadata": true,
    "action": "upload"
}'

Describe the solution you'd like

If the provided URL is part of an existing harvester, the importer should connect the newly created resource to the harvester to prevent it from being harvested again. The importer will create a HarvestableResource, link it with the newly imported resource, and align it with the harvester. If the harvester is unavailable, the resource will not be connected to anything and will be treated as a standard remote resource.

Metadata

Metadata

Labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions