Geonetwork/Geoserver compatibility

Added by Trumpy Eugenio over 2 years ago

Hello,

I installed easySDI on an already running joomla website in the version 3.4.1
The website is on an Ubuntu server 12.04 LTS, with tomcat6.

Up to now I was able to configure monitor and proxy. Now is the moment to
configure my already running webservices: a geonetwork CSW catalogue and WMS/WFS geoserver.

My CSW catalogue is a geonetwork at version 2.10.3, whilst geoserver is at version 2.3.2
The easySDI installed is the last version 4.3.0

What do you think?

best

Eugenio


Replies (7)

RE: Geonetwork/Geoserver compatibility - Added by Blatti Yves over 2 years ago

Hi Eugenio !

For your versions concerns:
  • Joomla! 3.4.1 : is currently not officially supported, but I'm currently running on it for tests and haven't found any problem yet. Should be good.
  • Ubuntu 12.04 : I don't think we have any OS limitations ....
  • Tomcat 6 : I haven't tried the esaySDI 4.x series on this platform, but I think it should be OK. Minimum java version is JDK6 (but I currently test JDK7 only)
  • GeoServer : I'm not aware of any version limitations. (easySDI communicate with OGC services, and GeoServer is quite good with OGC compliance)
  • GeoNetwork : GeoNetwork version should be <= 2.6.3 (2.6.4 can be used, but must be customized). GeoNetwork 2.8.+ is not compatible with easySDI since all CSW interfaces have changed.
    • Is your geonetwork a fresh install or a production server? Is it possible for you to downgrade ?

RE: Geonetwork/Geoserver compatibility - Added by Trumpy Eugenio over 2 years ago

Hi Yves,

I proposed this question because I got problem on physical service configuration as I inserted
in the forum:

https://forge.easysdi.org/boards/42/topics/575?r=619#message-619

I guess that problem occurs because of geonetwork version.

I'm using geonetwork 2.10.3 in production mode/server, so I'm afraid
I think is not possible to do a downgrade. In addiction I think
I can't add a GN lower version in my tomcat container since another
GN instance is already running.

Do you think does not exist any other solution to use GN 2.10.3?

best

Eugenio

RE: Geonetwork/Geoserver compatibility - Added by Blatti Yves over 2 years ago

It's a know issue of easySDI 4.x (feature #629).
CSW connector have changed in GeoNetwork 2.8+ and there was no current user of easySDI that presented the need to extend easySDI for the new CSW connectors.
Plus GeoNetwork 3.x is about to be released, and I don't know if 2.8.x and 3.x connectors are the same.

So, as far as I know, easySDI has currently no sponsor for this feature :(

Maybe someone else on the board can give you some more precise informations about this subject.

RE: Geonetwork/Geoserver compatibility - Added by Trumpy Eugenio over 2 years ago

Hi,

I argue the only solution is the GN downgrade, since the easySDI compliance to GN 2.10.x or 3.0
is not foreseen.

My only solution could be to deploy a GN 2.6.3 who harvests my running GN 2.10.3,
am I right?

best

Eugenio

RE: Geonetwork/Geoserver compatibility - Added by Blatti Yves over 2 years ago

That depends on your needs ...

What is the purpose of your easySDI installation ?

  • Consulting (read only) metadata ?
  • Editing metadata ?
  • Use advanced features of easySDI objects like:
    • Linking and or nesting metadata ?
    • Distribute (download, extract or sell) geodata/datasets described in easySDI (SHOP features) ?
    • Using easySDI MAP with easySDI objects (preview with services)?
    • Manging users, organisms and rights ?
  • Using MONITOR ?
  • Using PROXY (to secure OGC services)?
I'm asking this because:
  • You cannot edit an harvested metadata in easySDI (at least to my knowledge, personally, I don't use harvesting)
  • But easySDI to display haversted metadata is not a problem, many do this (see APEM , SI17 , TIGEO doing it)
  • And your easySDI edited metadata can be harvested by another server !
  • I think advanced features like SHOP or previewing data cannot be enabled on harvested metadata (but that needs confirmation)

Tell us more about your planned usage of easySDI ! ;-)

Best regards

Yves

RE: Geonetwork/Geoserver compatibility - Added by Trumpy Eugenio over 2 years ago

Hi Yves,

thank you for your answer, actually my aims could be useful to solve my problem.

I already have a running geonetwork (2.10.3) with some metadata(about 50-60 up to now),
and a running geoserver (2.3.2) providing WFS and WMS services.
For a pilot project I have a running webportal who describes the data presented
in geonetwork (GN) and provided by geoserver (GS).
The application are not completely integrated, of course I can link GN and GS
in my joomla webportal, however I was looking for something more integrated
and easySDI seemed to be a good solution, that's why I would like to test it.
Truly I tested even other tools (e.g., geonode or ckan-spatial, mapstore)
but I wanted to try something new.

I don't want edit metadata neither use the shop facilities, since my geonetwork
already harvests metadata from others geonetworks. I would like only to show
all metadata harvested by my GN (that is the main) as well as show some maps
and documents.

hope to have clarify better my point

best

Eugenio

RE: Geonetwork/Geoserver compatibility - Added by Mérour Xavier over 2 years ago

Hello Eugenio,

Thanks for sharing your needs.

I confirm what Yves said about GN compatiblity (here https://forge.easysdi.org/boards/15/topics/617?r=622#message-622).
There is currently no aim to move to GN 2.8 or upper version since GN 3.0 is about to be released and the Steering Comittee decided to wait for this release before doing any move in that direction.

After reading your last post, I guess easySDI can fill your needs. I am not technical enough to give you a complete guideline on the "how-to" but I can tell you the following things :

1. concerning "showing some maps", I guess the MAP component will cover your needs.
2. concerning "showing harvested metadata", I know it's done in others easySDI's instances installed, here for example : http://bit.ly/1HvMGcM
You can create a CATALOG in backend, then you could harvest your current 2.10 GN with easySDI and then describe the search fields you want to show up in frontend.

I guess others will be able to show you the way to achieve what you are looking for.

All the best,

Xavier

(1-7/7)