Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
image80 opened this issue Nov 15, 2024 · 9 comments

Comments

@image80
Copy link

image80 commented Nov 15, 2024

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

souci_edition_stations_groix

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

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.

@jahow
Copy link
Contributor

jahow commented Nov 15, 2024

Could you please share any error that appears in the browser console (accessed using F12)? Thanks!

@image80
Copy link
Author

image80 commented Nov 20, 2024

Thanks so much for your help. So i'm taking the liberty to share the screen shot showing the error message and the browser console interface (Google chrome F12) when i try to edit the record.
image.
So, moreover, i paste the SS showing the network menu of the F12 interface.
The error could come from the fact that the request for editing the file is made in type "json" instead of "xml" normally but I don't understand why.
image

If needed, I can share catalina.out log file (server side).
Thanks so much for your help.

@jahow
Copy link
Contributor

jahow commented Nov 21, 2024

This error does not ring a bell for me, unfortunately. Could you maybe share the response of the GET request that fails with a 400 code?

@image80
Copy link
Author

image80 commented Nov 26, 2024

Hello. Thanks so much for your message. Please find attached a screen shot more detailed regarding the replies (console -> reply).
image

@jahow
Copy link
Contributor

jahow commented Nov 28, 2024

It looks like your record is causing an XSL error. Could you share the record XML so that it can be investigated further? thanks!

Also, it would be interesting to try out with a more recent version of GN, as these errors are usually corrected regularly when they appear.

@image80
Copy link
Author

image80 commented Nov 28, 2024

Hello. Thanks for your help. Please find attached the XML file (.zip). For information, our GN version is : 4.2.3.
81158646-5a3f-4724-8339-1ae726b82e09.zip

@jahow
Copy link
Contributor

jahow commented Nov 28, 2024

This record has two mdb:identificationInfo blocks, and some fields were present in both (title and abstract) which was causing an error. I've quickly merged both blocks and removed the extra empty title and abstract and it seems to work:

81158646-5a3f-4724-8339-1ae726b82e09 fixed.zip

@image80
Copy link
Author

image80 commented Nov 28, 2024

Thank you for your usefull help

@jahow
Copy link
Contributor

jahow commented Nov 29, 2024

If the issue is fixed on your side please feel free to close this ticket, thanks ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants