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

Prepolutate server addresses in catalogue interface #13

Open
christianbraun opened this issue Jan 21, 2025 · 5 comments
Open

Prepolutate server addresses in catalogue interface #13

christianbraun opened this issue Jan 21, 2025 · 5 comments
Labels
help wanted Extra attention is needed

Comments

@christianbraun
Copy link

Dear all,
I am looking for help to modify basic settings in our GeoNode deployment.
Specifically, I am interested in prefilling some server addresses for external CSW servers.
I understood that I should modify _geonode_config.html to extend localConfig parameters. I found this documentation of MapStore where the corresponding tags are given.
Anyhow, my mods are not reflected. Any help is appreciated.
Many thanks in advance,
Christian

@christianbraun christianbraun converted this from a draft issue Jan 21, 2025
@christianbraun christianbraun added the help wanted Extra attention is needed label Jan 21, 2025
@ridoo
Copy link
Member

ridoo commented Jan 30, 2025

@christianbraun I guess you are referring to the Catalog Tool configuration section. To be honest, I am unsure how such configuration affects the geonode-mapstore-client. Be aware, that the MapStore2 documentation is about MapStore2. geonode-mapstore-client is based on MapStore2, but not all components are available/used in GeoNode.

Remote services are harvested in GeoNode. However, you cannot harvest a CSW instance. Only WMS, other GeoNode instances, and ArcGIS MapServer/ImageServer can be harvested.

What is you actually use case?

@christianbraun
Copy link
Author

Hi Henning, thanks for your answer.
It seems to be possible to fill the defaults of the Catalog Tool. In this example it's there.

The harvesting of WMS is very limited and with big catalogues (several 100s of layers) it's just a pain and not very flexible. Its fails to search in multilingual WMS instances and a lot of GeoNetwork catalogues are not able to be parsed and thus not searchable.

Christian

@ridoo
Copy link
Member

ridoo commented Feb 5, 2025

What makes you think, that these resources are from an external catalogue? I picked a random dataset and even the data is hosted from the same instance. A remote filter do not list any resources.

Perhaps we are talking past each other?!

@christianbraun
Copy link
Author

Probably a bad example that it links to its own catalogue, but nothing stops to you to use your own CSW ;-).
The remote filter just works on the internal harvesters by design. Data from the Catalog Tool doesn't show up there.

I am using now an empty "map template" with some addresses prefilled which is owned by the Admin user. Luckily those get taken over when you clone the template to your own user. Not the best solution but somehow it's working...

@ridoo
Copy link
Member

ridoo commented Feb 6, 2025

@christianbraun To be clear: GeoNode itself is a catalogue. The documentation link you shared is of MapStore2 which is NOT a catalogue but a Web client/framework from where your are able access OGC service including CSW. Therefore, I am still unsure, what you are actually after :-).

However, I am happy that you found a solution to your problem. In any case, just share your thoughts if you think there's something more to discuss. Feel free to close this issue, if feel your issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Status: GN development
Development

No branches or pull requests

2 participants