Thank you all very much for the replies. I finally found out that the jrc validator is checking 2 things, the view service capabilities response and the metadata file, which location is found in the inspire extended capabilities geoserver provides.
So I just created an inspire compliant services metadata file with the inspire editor (instead of creating it with a harvester) and I imported it in geonetwork (which actually cannot validate it neither can I view it in inspire view but anyway...). This solution is giving me 100% compliance with inspire. The problem is that every time I add a layer in geoserver I have to manually add the MetadataURL (coupled resource metadata element) in the service metadata file but that is a minor task :-) -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Set-up-an-INSPIRE-compliant-view-network-service-using-Geoserver-and-Geonetwork-tp5322233p5323150.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
