We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

GeoNetwork Opensource - The Geospatial Metadata Catalogue

00:00

Formal Metadata

Title
GeoNetwork Opensource - The Geospatial Metadata Catalogue
Title of Series
Number of Parts
95
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language
Production PlaceNottingham

Content Metadata

Subject Area
Genre
Abstract
The presentation will provide an insight of the new functionality available in the latest release of the software. Publishing and managing spatial metadata using GeoNetwork opensource has become main stream in many Spatial Data Infrastructures. The project developers have made big progress on INSPIRE support, performance, scalability, usability, workflow, metadata profile plugins and catalogue services compliance. Examples of implementations of the software will be given, highlighting several national European SDI portals developed in the context of the INSPIRE directive as well as work for Environment Canada.
GeometryIntegral domainCore dumpSoftware developerSoftwareMetadataWater vaporOpen sourceDigital rights managementWordGoodness of fitMetadataSlide ruleWeb 2.0Physical systemBitSoftwareSoftware developerMereologyPosition operatorEmulatorSemiconductor memoryComputerProgram slicingQuicksortMusical ensembleComputer animation
MetadataDigital rights managementStandard deviationBuildingBlock (periodic table)Open setPhysical systemDigital rights managementStandard deviationSoftwareBlock (periodic table)BuildingMetadataInstance (computer science)Open setTheory of relativityElectronic mailing listComputer animation
ImplementationE-learningOpen setGeometryExtension (kinesiology)SynchronizationMetadataLibrary catalogMetadataDescriptive statisticsPropagatorLibrary (computing)Physical systemSynchronizationService (economics)Extension (kinesiology)GeometrySoftwareInstance (computer science)Utility softwareLocal ringMultilaterationOrder (biology)Point (geometry)Web browserLibrary catalogOpen setRule of inferenceCache (computing)Type theoryInterface (computing)CuboidWeb 2.0Computer animation
Spatial data infrastructureService (economics)Descriptive statisticsLevel (video gaming)Web 2.0XML
Uniform resource namePhysical lawDirected setNewton's law of universal gravitationRaw image formatInformation managementLie groupLimit (category theory)Hill differential equationDenial-of-service attackGeometryOpen sourceWindows RegistryWechselseitige InformationBuildingWeb 2.0Service (economics)Execution unitInstance (computer science)Musical ensembleInfinite conjugacy class propertyBasis <Mathematik>Plane (geometry)Convex hullServer (computing)Cartesian coordinate systemTouchscreenSoftwareLibrary catalogMetadataTask (computing)User interfaceFront and back endsRevision controlLevel (video gaming)Interface (computing)Computer animation
Library catalogMetadataMereologyComplex systemWeb portalSoftwarePhysical systemOffice suiteNumberLevel (video gaming)Disk read-and-write headComplex (psychology)Form (programming)
ArmGAUSS (software)Motion blurMoving averageFingerprintValue-added networkEmulationMenu (computing)Pointer (computer programming)Level (video gaming)Wide area networkDrill commandsLocal ringOpen setGeometryComputer networkOpen sourceInclusion mapStandard deviationLocal GroupUniform resource nameMaxima and minimaPhysical lawMetropolitan area networkColor managementWebDAVConditional-access moduleRule of inferenceLibrary catalogConfiguration spaceMIDIFreewareWorld Wide Web ConsortiumHand fanAnalogyComputerStorage area networkSpecial unitary groupProjective planeLattice (order)BuildingLatent heatRight angleSubject indexingElectric fieldBlock (periodic table)Computer animation
ArmSoftware developerElectronic mailing listEmulationChi-squared distributionSummierbarkeitLaceDisintegrationContinuous functionInformation technology consultingSoftware testingGeometryElectronic mailing listStability theoryMetadataVector spaceEmailSoftware developerTable (information)Raster graphicsSoftware testingPhysical systemAddress spaceSolid geometryRange (statistics)Projective planeNumberLimit (category theory)Type theoryDesign by contractProfil (magazine)Line (geometry)Client (computing)Logical constantHeegaard splittingLattice (order)System callDifferent (Kate Ryan album)INTEGRALOpen sourceGroup actionCollaborationismRevision controlDisk read-and-write headFigurate numberChaos (cosmogony)Field (computer science)Electronic program guideContext awarenessComputer animation
Revision controlFunction (mathematics)User interfaceGUI widgetPlug-in (computing)MetadataGraphical user interfaceText editorArchitectureClient (computing)Server (computing)Manufacturing execution systemStandard deviationVarianceInternet forumDirected setRouter (computing)Computer configurationInterior (topology)SummierbarkeitValue-added networkUniform resource nameDialectSpecial unitary groupSheaf (mathematics)Service (economics)Data typeFormal languageMereologyGamma functionRange (statistics)Menu (computing)Metropolitan area networkType theoryWide area networkDedekind cutExecution unitFAQDot productPhysical lawSample (statistics)InformationTemporal logicHidden Markov modelZoom lensVisualization (computer graphics)Hill differential equationMaxima and minimaDrill commandsCAN busConvex hullMetadataProfil (magazine)View (database)InformationAsynchronous Transfer ModeFunctional (mathematics)Type theoryValidity (statistics)Level (video gaming)Web pageInstance (computer science)Set (mathematics)WebsiteSampling (statistics)Plug-in (computing)Service (economics)Source codeDefault (computer science)Computer fileSoftware maintenanceLibrary catalogLink (knot theory)Inheritance (object-oriented programming)Extension (kinesiology)Theory of relativityThumbnailResultantRevision controlText editorSoftwareScaling (geometry)Template (C++)MathematicsStructural loadRow (database)Point (geometry)Traffic reportingComponent-based software engineeringDifferent (Kate Ryan album)User interfaceInstallation artPresentation of a groupHeegaard splittingWeb 2.0Physical systemSystem administratorComputer configurationSoftware developerConfiguration spaceInternet service providerMultiplicationWordNumbering schemeRight angleJava appletInterface (computing)Online helpAdditionVotingPhase transitionBuildingMereologyLetterpress printingContext awarenessWeb serviceBitOpen sourceEvent horizonAreaBus (computing)Computer animation
Server (computing)GeometryService (economics)Level (video gaming)Physical systemRepresentational state transferWeb 2.0Set (mathematics)Instance (computer science)Different (Kate Ryan album)Shape (magazine)Computer animation
MetadataPlug-in (computing)Open sourceUniform resource locatorRow (database)Local ringMathematicsCollaborationismRepository (publishing)SoftwareVideo game consolePhysical systemSummierbarkeitDatabasePrice indexWechselseitige InformationLibrary catalogSupremumArtificial neural networkArmMetropolitan area networkSoftware engineeringStatisticsDimensional analysisSpecial unitary groupPhysical lawSharewareExecution unitContent (media)Abelian categoryConfiguration spaceBroadcast programmingComputer configurationMaxima and minimaLie groupUser interfacePhysical systemInstance (computer science)System administratorMetadataDatabaseTerm (mathematics)SoftwareProfil (magazine)Group actionSelf-organizationPresentation of a groupPlug-in (computing)Interface (computing)InformationDifferent (Kate Ryan album)Validity (statistics)Type theoryRule of inferenceProjective planeBootstrap aggregatingConfiguration spaceLibrary catalogSampling (statistics)Connected spaceSubject indexingStatisticsVideo game consoleUniform resource locatorGame controllerSharewareService (economics)Multiplication signCentralizer and normalizerTouchscreenRepository (publishing)Set (mathematics)BackupFigurate numberNumbering schemeWebsiteCommunications protocolMoment (mathematics)Category of beingSoftware developerDependent and independent variablesMusical ensembleProgram flowchart
Transcript: English(auto-generated)
Yeah, I'm here alone now, but maybe Francois Brunet will join me later on to present some of the stuff live, but he is doing a workshop now. So I'm Jeroen Tichler, founder and chair of the GeoNetwork Open Source software, which we started developing over 10 years ago, now 12 years ago, I think.
Yeah, I'll get the microphone, if that works. Yeah, that's recording, yes. Let me see. Does this work?
Well, I'll try to speak up then. Drink some water.
There was sparkling water, so now my voice is going completely. I'm Jeroen Tichler. I founded the GeoNetwork project, I think, 12 years ago now. I've been working at the United Nations Food and Agriculture Organization.
I left FAO five years ago to start my own company, GeoCAD. And, yeah, GeoNetwork has been developing ever since with quite a good team of developers and a very broad network of users.
So what I'll do is I'll discuss a little bit of what is GeoNetwork, how we develop, and then have a couple of slides on what's new and how you can use it.
So it's been two years that we have not presented this obviously in Phospho-G, so a lot of things happened. Basically, what GeoNetwork is is a software to publish your data through metadata. And it's really all about properly describing your data and making it findable on the web.
Is that findable? Is that a good word? Searchable? Discoverable probably is the word. So it provides you with a very comprehensive metadata editing and management system. And I'm surprised in 12 years how much you can actually add to a metadata system
and still not be done with it. But the basic building blocks that we build the software on are standards coming out of the ISO Technical Committee 211. So it's the metadata standard 19115, for instance,
and there's a whole list of related standards to that. There's the Open Geospatial Consortium standards that we use a lot. And those are used, for instance, on the catalog interoperability. So we have descriptions of metadata in the system.
We make those searchable. But then you don't want to only access this through a website. In fact, most people don't really want to access this through the main entry point, but want to have that metadata propagate through systems in a network and then discover it at all different places.
So we have support for Inspire, for instance, in Europe, which is important. But we also then support, and then we support all kind of catalog services interfaces, like the OGC catalog service for the web interface, Open Archive, which is an interface used at libraries mainly.
We have RSS news feeds, Atom feeds, and we have open geo, sorry, open search extension that is, for instance, when you type something in your browser in the search,
small search box in your browser, so you could actually connect that to search into a catalog, a geo network catalog. Then we have a whole system of metadata harvesting and synchronization, so you can connect one catalog to a whole lot of other catalogs that use those kind of interfaces.
And so you can get that metadata out of the other catalogs and kind of cache it locally. So we say harvesting, synchronization, duplication, whatever. You store it locally, so you make your search local in that catalog, and you can do your ordering also across the whole lot of metadata
that is in your catalog at that point. It doesn't pollute the metadata that you store in it, so the things are kept. You know, you remove some catalog from your harvesting scheme, and then metadata is removed from your catalog, et cetera.
So I think that catalogs, in a way, are the glue in the spatial data infrastructure, and they then describe data sets. They describe data services, web map services, feature services, download services, whatever you call them. But without the proper descriptions, they become really hard to find
and know what you're actually dealing with. So, yeah, that's all what GeoNetwork does, basically. Then it has a user interface, and we've been building a new front-end on it that was released in version 2.10 just a couple of months ago.
And that we'll also work with tomorrow. Tomorrow there's a workshop I'll give on how to set up and manage a GeoNetwork catalog. It's a free workshop. I think it's in the other building tomorrow morning. And we'll look at this interface, and we'll start configuring a harvesting task.
We'll start configuring some map services with the metadata, get it into the catalog, and edit metadata inside this web, multilingual metadata, which is supported. So, yeah, you're welcome to join the workshop tomorrow.
But then the application itself is just the basis for setting up your own catalog. So this is the software release, and it looks kind of nice and fancy. But then you build your own interface. Or you build a new application at the top of the server that will just use a catalog service for the web, for instance, to interact with it.
Or you use the out-of-the-box user interfaces that are available. And currently we have, I think there's three different applications that you could use as user interface that come directly with GeoNetwork. Plain HTML-based, XJavaScript-based,
and now we're working on a new bootstrap, and the other one, Angular-based. But I'll have some screenshots of that. So where is that used in Europe?
These are countries that I know of that use it at the national level for their Inspire portals in some form. So that is in Europe is quite significant number of the countries that use the software for the publishing of metadata for the Inspire.
And then it's also used in Canada, Australia, US, Africa, all over the world. But quite often in quite complex systems. I know the Met Office here is using it as part of a bigger system.
So a big user base. So how do we develop that? It's a community-driven project. In there we try to get people, to get users together
and kind of define what is needed in next releases. So we had a meeting, I think this was two or three years ago, with European countries for Inspire, and we'll have a similar meeting again end of November. And then we start defining big building blocks that we want to tackle
and kind of get the funding right and the specifications right. We currently have about 800 people on the user mailing list. That's the English one. There's a French mailing list with 200 subscribers and a Spanish one as well.
400 people on the developer mailing list, that's the most active list. And then there's a commit list and there's about 10 active software developers working on it. This is kind of a graphic of the downloads. It's kind of stable over the last couple of years.
Between 1,500 and 2,000 downloads per month, which I absolutely don't understand who's downloading all this stuff, but at least we know it's downloaded. So how do we collaborate? As I said, community driven.
So we have proposals coming in, proposals that come through the developers usually. We discuss it, we sit together, or we sit together online on Skype. We vote on the mailing lists and once it has been implemented,
we accept it for integration into Trunk. So we use Skype, conference calls. I don't think we've used Google Hangout yet, but likely do at some point. And we have face-to-face meetings.
So we meet here, we usually meet for a week in Italy every year and sit together and kind of go through all the issues. Split the work in smaller packages. And as I said, we're basically in constant contact
between user and developer as well as developers. So what I try to do in Geocat is have the developers directly communicate with the client on what are their needs and so try to get the lines very short.
We also provide support contracts. So if you want your system, if you want that phone number you can call or that email address you can ask your questions. We provide the type of support and then try to resolve your problem as soon as we can.
So the benefits, we support common requirements of a very large group. It's very, very different also in type of users. So there's people that deal mostly with vector data, but there's people that deal with raster data, tabular data,
huge quantities of data, but their requirements are to describe and make findable. And that then is sometimes described in metadata that is focused on vector data, but you also have metadata focused on raster data and so on.
So there's different metadata profiles are supported and you can add your own profiles to the system. It makes the testing and compliance easier because of all this cross testing within the community and we share the cost.
So that's actually quite a big deal. By just distributing the cost among a whole range of countries, each country just pays a pretty limited amount of money and we have a big, big improvement in the system. So preventing the vendor lock-in, the obvious open source things,
and innovation because we have researchers that do research projects all around the world. In the EU, FP7 projects, I know research projects a lot in Australia. They come with new things and then they get into the system pretty quickly.
First testing and then later embedded. So you can follow the project. This is also kind of a trademark for the sustainability of the project.
There's a solid user and developer community behind it. So on the new version, 2.10, I think the last one I presented at Phosphor-G was 2.6. There's been 2.8 and now we're 2.10.
As I said, it was released with a lot of new functionality. It's way too much to actually discuss here. But there's a page on our developer website that lists all the proposals and functions that have gone into the system. Obviously, there's release notes you can read and I'll just show a couple of things.
So there was a widgets-based user interface design that was done mainly for the Dutch National GeoRegistry and that has been ported into, also the Swiss one actually, and that has been ported and is now the default user interface when you download and install.
There's a support for metadata profile plugins. So while in earlier versions we were implementing a profile directly in the software and if you needed North America profile to be in it, it would need to be built in.
Now those are plugins. So they're kind of zip files that contain all the stuff you need for validation, schema-to-run validation, schema validation. So they define what your editor looks like, how it's presented. All of that is fitted into a metadata profile plugin
and you can load your own profiles and also develop them separately and I'll come back to that. We've been splitting up the software in smaller components
that in the end you still download one installer, but if you go to the source code you can actually see the different components in Git. So we've also made the move from subversion to Git at some point over a year ago. So this is kind of the entry point, the website, if you install the software now.
If you install, there's nothing yet. So here I've loaded metadata templates and I've loaded some sample data. When you do a search we have filtering on the left.
So you can filter by organization, for instance, by keyword, by type of data, type of service, scale the data is available in, so all the information coming out of the metadata. And then you'll get your results.
You can display your results like this, but also with just the thumbnails. When you go over with your mouse you'll see the extent of your data set on the small map on the side. You can immediately filter to see only web services, for instance. There's a new presentation layer using this X JavaScript layout.
We're now working on the new layout again, but you have different view modes there. There's a default view mode. There's an inspire view mode.
You can view your metadata by metadata package. You can see the XML. You can edit the XML. You can edit it in all these different view modes. And in the system configuration, so the administrator can define which view modes are available to your end user.
So if you only want to have default view to your end user, you can make sure that they only see that view mode option and not all the other ones. In the editor, as well as in the results, you can use the right click and the contextual menus to edit,
to duplicate your metadata, to set the privileges. So who has access to what parts of metadata, maybe to what kind of services. Print, export, so you can export the whole sets of metadata and data.
And the editor, this is the editor when started. And this is in the view mode with all the packages. So you have a tab view. When you go over, you get help on what exactly you're looking at on the right.
There's a validation report on the right. So you can see where your metadata is invalid. It also has suggestions. So if you added the keywords comma separated, the suggestion would be to split it up in separate keywords.
And then you could actually apply such a change. So you could select a suggestion and click apply. And then it will do that work for you. You can relate records in related resources. So you can have a parent child relationship between metadata of services
and then all the individual layers, for instance, to go up and down through your data set. So this data is used in that and that and that service. Or that service uses this and this and this data. And the links are all in the catalog and maintained.
And a lot more. For instance, a feature to upload the data set as a zip file, as a shape, and then instantly deploy it on the GeoServer. So it then uses the GeoServer REST API and deploys a web map service for you.
So you don't have to go through different systems. You select your GeoServer and launch your map service instantly. As I said, the schema, metadata schema plug-in is quite important. If you have, if you're working with a marine profile,
you have your own validation rules, your own requirements, and you can basically develop a schema plug-in and maintain that yourself and then load it into the system when you need it. What we're working on and where I hope Europe with the Inspire project
will support us is developing a metadata 101 kind of organization. And it's also a Git repository where we will store these kind of profiles. So this will allow people to collaborate on the profiles
and have a central place where we maintain them and actually the people that are responsible for a marine profile can update their marine profile. And the one responsible for North America profile can maintain his. And so that would kind of be a central location of metadata profiles.
They could be used in whatever system. We will use them in GeoNetwork, but obviously you can use them in other software as well. And what we want to do is kind of put a permissive license on that so that it can be incorporated in both open source as well as proprietary software
to make sure that there's a lot of systems that validate against the same schema as the schematron rules. So what I mentioned, Francois, and I don't see him here, so I'll just go through some screenshots and we won't have a live demo.
He's working on a new administration interface at this moment. OK, so this is very quick. That's based on Angular JavaScript, D3, and Bootstrap. And it's probably very likely that we use the same also for the end user user interface in the future.
So just a couple of screenshots. This is then the new admin console where you can update metadata and templates, import, export data, set up harvesting, see statistics and status information on your catalog instance.
And so you can see what type of terms are searched. And if your database connections are fine, et cetera, et cetera. User and group administration, controlled vocabularies, and a whole lot more. And it's really a lot, so I will just show very limited things on it.
But here's a database status, for instance. It says that your indexes are OK, that your database connections are OK, that your catalog service get capabilities document is OK. Information on what kind of services are used for the search.
So is my CSW very popular, or is it the user interface that is used most? And so you kind of get an idea of where people search. And you can see this in all kind of different ways.
This is search statistics. So again, based on services as far as I see it. Very quick. So search terms that I used. So what's the most popular type of search terms used?
And you can start filtering by category, et cetera, et cetera. Harvesting configuration has been changed, so the user interface for that becomes much more transparent. You select your catalog you want to harvest from, and all the settings are in the same screen.
And you can update quickly. So I think that's it. I have some sample implementations, but I'll leave it at that. Thank you. So we've got time for some quick questions before we switch over to the next presentation.