geonetwork / geonetwork/core-geonetwork

Difficulties for integrating/linking WFS/WMS geoservices into metadata record (slowness)

Open
#8,501 9 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
521
Forks
514
Avg merge
6d 13h
Merged PRs (30d)
19

Description

With GeoNetwork 4.2.3, I'm facing difficulties regarding one record. I don't notice this problem for all records, just this one. The problem is for integrating/linking WFS/WMS within the metadata record. I succeed without problem in loading the data (postgis layer) into QGIS (WFS/WMS).For information, the WFS/WMS geoservices are published thanks to GeoServer.
So when editing the metadata record and trying to link/integrate the WMS/WFS the page becomes really slow :

![image](https://github.com/user-attachments/assets/8df35785-4b18-4952-9569-7708118c9153)

![souci_edition_stations_groix](https://github.com/user-attachments/assets/3a07f84b-817f-4871-bf86-436d1e1cc5b4)

And I assume that the geoservices are not functional if integrated into the record. I tried to reindexed this record but that didn't change anything.

Moreover, When I authenticate (admin) on the catalog, I can't access the record editing interface. There is a message saying 'An error occurred while calling the service':

![SS_groix_prmb_connect_edit](https://github.com/user-attachments/assets/dbd63704-763c-4eb9-839e-ac1608a081c4)

For information, there are several spatial reference systems : for the PostGIS layer (EPSG:2154 - RGF93 v1 / Lambert-93 - Projected), the WMS (not projected in EPSG:4326 - WGS 84) and WFS (not projected in EPSG:3857 - WGS 84 / Pseudo-Mercator).

If needed, I can share catalina.out log file.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported record-editing flow for the affected WFS/WMS services and review the available catalina.out log. Check the behavior with the stated PostGIS and EPSG configurations; done means the metadata editor loads normally, the record can be edited, and the linked geoservices work.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.