Implementing Open Geospatial Data Portals with CKAN, pycsw and PublicaMundi: the geodata.gov.gr case
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Tzotsos, Angelos (OSGeo)
PublicaMundi is a successfully completed EU FP7-ICT project aiming to make open geospatial data easier to discover, reuse, and share by fully supporting their complete publishing lifecycle in open data catalogues. PublicaMundi extends and integrates leading open source software for open data publishing and geospatial data management. In particular, PublicaMundi extends CKAN, the leading open data catalogue, into treating geospatial data as “first-class citizens” and providing automatic OGC- and INSPIRE-compliant access to geospatial data, through integration with pycsw, rasdaman, ZOO-Project, GeoServer, MapServer, PostGIS and GDAL. PublicaMundi was recently deployed to geodata.gov.gr to serve as the main open geospatial data catalogue of the Greek government. The production system provides multilingual data access to data publishers, open data users, and developers through the main catalogue, an integrated mapping application, and various APIs (CKAN, data, mapping and OGC APIs). This presentation will provide an overview of the production system, the cloud infrastructure used and future developments.
 We're starting? Okay. So I'm back here. So welcome again. I'm going to present the new geodata.gov.gr, which is actually based on work that has been done with C-CAN, PyCSW, and a new project called PublicanMundi. So this is the outline of this speech. We are going to make an introduction in PublicanMundi project on C-CAN. I'm going to skip PyCSW because I already said that before. And then we are going to see a couple of applications like what was the data.gov and how it differs from geodata.gov.gr. And I hope we have some time to show you a demo. So okay, this is a very generic introduction. Like this is the definition of open data, the idea that some data should be freely available to everyone to use in the republics. The open data movement is similar to open movements as open source and open hardware and et cetera and open science. So data.gov is the home of US government open data. It was done several years ago. It was revised three years ago and ported to open source software completely through C-CAN. And it is open source. It's on GitHub. You can find the source code there. So in Portland in 2003, I gave this presentation about data.gov. So now you'll see the difference and how this evolved to something newer. So actually geodata.gov.gr is something that existed since 2010. It was actually one of the five first national open data portals. So it is a geospatial data infrastructure and it is serving as a national open data catalog. It's inspired compliant and it is maintained by Athena Research Center, which is responsible to maintain it and provide support and anything else on this platform. So the old geodata.gov.gr was based on some customized version of open source software. And it was based also, the map components were built upon map fish. So at some point where C-CAN came along and C-CAN is a software from OKFN, the Open Knowledge Foundation. It's a web platform for publishing and sharing open data. And it has really been very, very popular in the open data community and it is also very, very popular in national portals. So right now C-CAN powers the European open data portal, the open data portal and the European data portal. Actually this was six months ago. The USA Open Data portal, the UK portal, the Australia now, the Greek one and many others. If you go to the side you'll see like hundreds of them. It is a powerful system, it's built on Python and Pylons actually. It provides tools to streamline publishing and sharing and finding and using open data. And it was designed aiming to help publishers actually. And this is probably why it was such a success. So instead of asking for like 50 metadata fields, C-CAN said, OK, just upload your data and give me some minimal information and it will be available. Although not very compliant to standards, but it was a success because publishers could just go there and publish their data. So it was a success story for them. So these are the main features of C-CAN. They can publish and find data sets, store and manage data, do federation nodes, harvesting and it has an excellent API and some extension. So somebody with Python knowledge can extend C-CAN. And these are some screenshots of how things are done in C-CAN. This is like a search result and discovery and many other features which I will also talk about later. So I'm going to skip the PyCSW slides. I'm just going to say that it's an OGCCSW server implementation in Python. It's open source and it's an OSGO project. Now let's move to Publica Mundi. So Publica Mundi was a funded European Union FP7 project which was, the goal was to be able to extend C-CAN in some nice ways regarding open geospatial data. So we wanted to research and develop new methodologies and to make C-CAN more scalable, more data to be more reasonable and to offer to facilitate publication discovery and reuse of data. So the main idea was that we wanted to add the OSGO stack on top of C-CAN because C-CAN had already some spatial extensions but it didn't provide direct publication, for example, of WMS, WFS. So what we thought is that we should bring OSGO stack directly and integrate with C-CAN in order to make it more easy for the users to publish their data. So we extended C-CAN using the OGCC standards, the source code is on GitHub, the links are here, also the presentation is online on PublicaMundi.eu. So what kind of standards did we implement? We implemented, we tried to use the inspire directives for discovery services, view services, download services and we added the processing services there because we think that using also the data now online is important. Also we integrated some new technologies like we went for the Earth observation community and we integrated Razdaman for WCPS and WCS for raster data and also we integrated Zoo WPS project on C-CAN. Also the known players of OSGO are here, Grass, Overfill Toolbox, Saga, those were also used in order to create processes that Zoo was offering on top of them through WPS support. So these are our contributions during the project. We implemented the OGCC Open Search, as I already said through Pisces W. WPS2 was also implemented by Zoo project, OGCC transactional coverage service was a new specification that derived from the project through work being done by the Razdaman group. Also CSW3 was implemented even though it was released half a year later and we also were involved in the GeoDCAT discussions and we contributed as much as we could. And this is the consortium of the FP7 project. So just a little flashback on how data.gov was in 2003 and 2013. So it first started in 2009 and then it switched to OKFN's platform with C-CAN in 2012 and then it was integrated with Pisces W in 2013 and 2014 later and many updates since then. So this is the architecture, C-CAN with the data.gov extensions using the C-CAN API and open layers and leaflet as data visualization tools but also solar as a search engine and Pisces W for CSW and that's more or less how data.gov is also today. This is how it looks. They change the look and feel of C-CAN completely in order to be able to search through specific organizations so somebody can just look for USGS data and get specific results. And it now has 2 million records in there so it's like I think the biggest open data portal so far. There are some specific features I don't have the time to go through but they support many end points. Somebody can publish a WMS and they can harvest from many sources. The main idea of data.gov is similar to Inspire but it was forced from top to bottom. So instead of expecting many organizations to support the standard they went and said okay we are going to do data.gov and we are going to harvest everyone else to one portal. So if you are not compliant with what we want you are not going to be on data.gov and all the organizations and government agencies in US responded to that by providing C-CAN installations and CSW end points and then suddenly the catalog was made by itself. Data.gov does not have any data on site. It harvests everything. Only harvests data. So let's move on to geodata.gov.gr. So this is the architecture as it became after we did the project. So here we have like we integrated the web services like map server, geo server, Razzdaman, zoo. Of course GDAL and PROD is there because it's used everywhere in the OSGO stack. Also we are based on C-CAN with PyCW and solar but also we did some extra special extensions. We added some analytics there, we are able to monitor the usage of web services through our servers and also we did some more extensions like we provided processing and data API directly over the data that we host and we did some new additions to C-CAN like raster stores, vector stores and some new metadata editor. I will show them on the way. So now how we do integration. We have a better deployment software portal which is labs.geodata.gov.gr. We have the servers in the Ministry of Education because it's a government site and we are using a Greek cloud stack called Cinefo which is on top of GANETI. We deployed on several clusters which is from database to C-CAN, geo server and we are using tiles and everything that's supposed to be on an SDI in order for it to be efficient. We are doing clustering for geo server but we are also doing things like using map proxy and map server to also do tiles. So this is like we try to bring everything into one environment. We have monitoring tools to be able to see if some servers stop responding and be able to spin off new servers. And all the installation because there are too many components in the new system, we did everything with Hans Sible which is an excellent tool to be able to create, to deploy software in many servers and to be able to do DevOps work in this case. So this is the new theme. This is how we changed C-CAN and we provided also some new extra features which I'm going to go through now. Well the look and feel of the search page is not much different from what you can find in C-CAN but there are some hidden features like now we are doing automatic generation of WMS and WFS for example if somebody uploads some vector data. So here we redesigned the dataset page and now when somebody uploads a shape file we have like sorry this is the Greek, I will show you later the English page but this is the data and these are the services and these are the metadata so we now have all of them in one page and somebody can just upload the shape file and what happens is when you upload a shape file to C-CAN for example it will identify that it's a shape file, okay that's easy and then it will get you through some steps in order to complete how you publish your data. So initially C-CAN just asks for a title, a description, a license and an organization. That's all the four elements that C-CAN used to ask so you can still do that but we added a full inspire metadata editor to C-CAN so if you can, if you will, if you change the schema here and you say I don't want C-CAN, I want to inspire or ISO then you get the next page which is a full metadata editor inspired by the inspired geoportals so you can add things like linears and spatial resolution and conformity and all this stuff. So if you go into that trouble, well which is required for EU organizations then you have a full XML representation of inspire metadata and then you're able to directly sorry this is wrong, then you're able to directly publish them through CSW. So then we implemented a new dashboard within C-CAN, C-CAN was not able, when you uploaded the geospatial file it was not able to do anything with it, it just was there only download, nothing more. So now we made a new dashboard where when you upload the file, let's say a save file, it will identify what it is and it will provide you with some options so you can ingest the resource to a database which is post-GIS or you can just ignore it or you can do just some copy of data if you want to but the main idea is that you upload the save file and then you go to the administration site and you publish, you ingest your data to post-GIS. So after you do that immediately the dataset page will automatically create you an endpoint through Geo server or Map server for WMS and WFS and then it will be available on a map directly. So you can regenerate the endpoints by linking to the post-GIS page and then we have previews. So if you go into a dataset and you hit the preview and the map you just get the WMS, you get a URL how to link to another application using WMS or you get support for WFS right out of the box. And we do that also with raster data. So once you provide a T file or an hcdf file, well obviously you are not going to upload the big T file on your browser, right? So instead you can add the link to it. So if you add the link to it, the server will download it, it will ingest it to Rastaman and then it will provide WCS endpoint and WMS based on this dataset. Of course it will try to guess what type of data that is and we provide also previews. I'm going to go really fast now because there's not enough time and there are many features. So in the metadata, once you get your metadata there or when you want to upload the file and create a dataset from that, you directly have PiscesW there to help you. So you have your metadata and your page and you can just download whatever other profile you want based on PiscesW. We also took some time to provide some tools for developers. So we did our own test of providing a mapping API and we did it both with leaflet and open layers. So you have similar code with our API, almost identical. I mean only one line changes and you have the same result either on leaflet or on open layers. Now also we provide a data API, since we have all the data now directly in post-GIS, we created an API with a JavaScript API, sorry, where you can do queries to the data directly. And of course because it's a national portal, we created a new client, a new map application directly with open layers with features like when you see a layer here, you can just select a part of the layer and you can download it through the data API and you can get the file. So somebody just doesn't know how to use a WebGIS, you can just click and download the data through the map directly. So also I don't have enough time, sorry, it's too many slides, too many features, we added multilingual support. So we kind of did a UI where somebody can translate data and metadata directly through the through SICAN. So if you have an English data set and you want to translate it to Greek or to French or anything else, there is a UI where you can do the translation, it will store the different revisions and then you will get your data set in a different language in the data set page. That's about it, no time for a demo if you want, I can demonstrate outside. So thank you. Thank you, Angulos, are there any questions? Thank you for presenting this, it's impressive. And my question is, I see many similarities to GeoNode and how did you consider it also at the beginning or how you see the differences? Yes, this is a good question. So actually I'm a GeoNode developer myself, but sometimes you have requirements that are given to you by somebody, right? And sometimes you are working with different communities, as Paul said. And the open data community has SICAN as a reference, let's say implementation, everybody is using SICAN, so most open data portals will use SICAN. Well, GeoNode is becoming a very strong player, but the difference is that GeoNode is even more focused on Geospatial than SICAN. But SICAN is more, I mean, for example, you can upload any kind of data on SICAN and it will do its work, its extensions will work. So it's a platform for open data. Well, GeoNode is also a very good platform, but it is more focused into providing Geospatial features. And actually SICAN was missing those features, but they were needed. So we had to do it on SICAN. It's a matter also of preference, it's open source, right? Variety matters in this aspect. And also GeoNode is improving the SICAN connection. Yes, there are SICAN connections, they both use PICSW so you can harvest each other now. But it's also a vibrant community, SICAN is also moving, but this project was a two-year project only. So we went as far as we could. Thank you. A very excellent product, I think. So can we get virtual environment? So for example, the Baygrunt or Docker, for example, can we get to the Docker? It is all the software is on GitHub. If you go to public Amundi organization, we don't use Docker yet. We are now porting it to Docker, but we have all the uncivil scripts. So if you get the uncivil scripts, you will run them on one VM. It will create a very big VM and very heavy VM, but it will work. But also we also provide the actual production uncivil scripts. If you have 10 or 15 VMs available, you can set up the whole thing by yourself. I think we spend a lot of time on uncivil to be able to reproduce it because failure happens and we used to do lots of work to set up new servers, so uncivil was a lifesaver for us. And now Docker, so it will be available soon also. So one last question. Someone? So you mentioned it will be available soon, but the public Amundi project finished? Are there still organizations in that community? Is this? Yeah, so, all right. Athena Research Center maintains the catalog. So it's a national catalog. The project has ended, but maintenance is still going. We are not implementing right now new features. Maybe if we get some funding, if somebody is interested, we can also do some new project. But we do maintenance. So everything that is needed to work, it will continue to be supported for many, many years because the government is behind it, even a bit broke at the moment. But anyway, yeah, it's still there. So yeah, and contributions are always welcome. The development team is also doing other stuff, but it's an open source. It's there. Anybody can pick it up and continue or ask us to help. Okay. Well, then I want to close this session. Thanks.eters again. Thank you. Thank you. Thank you.
 We're starting?  Okay.  So I'm back here.  So welcome again.  I'm going to present the new geodata.gov.gr, which is actually based on work that has been  done with C-CAN, PyCSW, and a new project called PublicanMundi.  So this is the outline of this speech.  We are going to make an introduction in PublicanMundi project on C-CAN.  I'm going to skip PyCSW because I already said that before.  And then we are going to see a couple of applications like what was the data.gov and  how it differs from geodata.gov.gr.  And I hope we have some time to show you a demo.  So okay, this is a very generic introduction.  Like this is the definition of open data, the idea that some data should be freely available  to everyone to use in the republics.  The open data movement is similar to open movements as open source and open hardware  and et cetera and open science.  So data.gov is the home of US government open data.  It was done several years ago.  It was revised three years ago and ported to open source software completely through  C-CAN.  And it is open source.  It's on GitHub.  You can find the source code there.  So in Portland in 2003, I gave this presentation about data.gov.  So now you'll see the difference and how this evolved to something newer.  So actually geodata.gov.gr is something that existed since 2010.  It was actually one of the five first national open data portals.  So it is a geospatial data infrastructure and it is serving as a national open data  catalog.  It's inspired compliant and it is maintained by Athena Research Center, which is responsible  to maintain it and provide support and anything else on this platform.  So the old geodata.gov.gr was based on some customized version of open source software.  And it was based also, the map components were built upon map fish.  So at some point where C-CAN came along and C-CAN is a software from OKFN, the Open Knowledge  Foundation.  It's a web platform for publishing and sharing open data.  And it has really been very, very popular in the open data community and it is also  very, very popular in national portals.  So right now C-CAN powers the European open data portal, the open data portal and the  European data portal.  Actually this was six months ago.  The USA Open Data portal, the UK portal, the Australia now, the Greek one and many others.  If you go to the side you'll see like hundreds of them.  It is a powerful system, it's built on Python and Pylons actually.  It provides tools to streamline publishing and sharing and finding and using open data.  And it was designed aiming to help publishers actually.  And this is probably why it was such a success.  So instead of asking for like 50 metadata fields, C-CAN said, OK, just upload your data  and give me some minimal information and it will be available.  Although not very compliant to standards, but it was a success because publishers could  just go there and publish their data.  So it was a success story for them.  So these are the main features of C-CAN.  They can publish and find data sets, store and manage data, do federation nodes, harvesting  and it has an excellent API and some extension.  So somebody with Python knowledge can extend C-CAN.  And these are some screenshots of how things are done in C-CAN.  This is like a search result and discovery and many other features which I will also  talk about later.  So I'm going to skip the PyCSW slides.  I'm just going to say that it's an OGCCSW server implementation in Python.  It's open source and it's an OSGO project.  Now let's move to Publica Mundi.  So Publica Mundi was a funded European Union FP7 project which was, the goal was to be  able to extend C-CAN in some nice ways regarding open geospatial data.  So we wanted to research and develop new methodologies and to make C-CAN more scalable, more data  to be more reasonable and to offer to facilitate publication discovery and reuse of data.  So the main idea was that we wanted to add the OSGO stack on top of C-CAN because C-CAN  had already some spatial extensions but it didn't provide direct publication, for example,  of WMS, WFS.  So what we thought is that we should bring OSGO stack directly and integrate with C-CAN  in order to make it more easy for the users to publish their data.  So we extended C-CAN using the OGCC standards, the source code is on GitHub, the links are  here, also the presentation is online on PublicaMundi.eu.  So what kind of standards did we implement?  We implemented, we tried to use the inspire directives for discovery services, view services,  download services and we added the processing services there because we think that using  also the data now online is important.  Also we integrated some new technologies like we went for the Earth observation community  and we integrated Razdaman for WCPS and WCS for raster data and also we integrated Zoo  WPS project on C-CAN.  Also the known players of OSGO are here, Grass, Overfill Toolbox, Saga, those were also used  in order to create processes that Zoo was offering on top of them through WPS support.  So these are our contributions during the project.  We implemented the OGCC Open Search, as I already said through Pisces W. WPS2 was also  implemented by Zoo project, OGCC transactional coverage service was a new specification that  derived from the project through work being done by the Razdaman group.  Also CSW3 was implemented even though it was released half a year later and we also were  involved in the GeoDCAT discussions and we contributed as much as we could.  And this is the consortium of the FP7 project.  So just a little flashback on how data.gov was in 2003 and 2013.  So it first started in 2009 and then it switched to OKFN's platform with C-CAN in 2012 and  then it was integrated with Pisces W in 2013 and 2014 later and many updates since then.  So this is the architecture, C-CAN with the data.gov extensions using the C-CAN API and  open layers and leaflet as data visualization tools but also solar as a search engine and  Pisces W for CSW and that's more or less how data.gov is also today.  This is how it looks.  They change the look and feel of C-CAN completely in order to be able to search through specific  organizations so somebody can just look for USGS data and get specific results.  And it now has 2 million records in there so it's like I think the biggest open data  portal so far.  There are some specific features I don't have the time to go through but they support many  end points.  Somebody can publish a WMS and they can harvest from many sources.  The main idea of data.gov is similar to Inspire but it was forced from top to bottom.  So instead of expecting many organizations to support the standard they went and said  okay we are going to do data.gov and we are going to harvest everyone else to one portal.  So if you are not compliant with what we want you are not going to be on data.gov and all  the organizations and government agencies in US responded to that by providing C-CAN  installations and CSW end points and then suddenly the catalog was made by itself.  Data.gov does not have any data on site.  It harvests everything.  Only harvests data.  So let's move on to geodata.gov.gr.  So this is the architecture as it became after we did the project.  So here we have like we integrated the web services like map server, geo server, Razzdaman,  zoo.  Of course GDAL and PROD is there because it's used everywhere in the OSGO stack.  Also we are based on C-CAN with PyCW and solar but also we did some extra special extensions.  We added some analytics there, we are able to monitor the usage of web services through  our servers and also we did some more extensions like we provided processing and data API directly  over the data that we host and we did some new additions to C-CAN like raster stores,  vector stores and some new metadata editor.  I will show them on the way.  So now how we do integration.  We have a better deployment software portal which is labs.geodata.gov.gr.  We have the servers in the Ministry of Education because it's a government site and we are  using a Greek cloud stack called Cinefo which is on top of GANETI.  We deployed on several clusters which is from database to C-CAN, geo server and we are using  tiles and everything that's supposed to be on an SDI in order for it to be efficient.  We are doing clustering for geo server but we are also doing things like using map proxy  and map server to also do tiles.  So this is like we try to bring everything into one environment.  We have monitoring tools to be able to see if some servers stop responding and be able  to spin off new servers.  And all the installation because there are too many components in the new system, we  did everything with Hans Sible which is an excellent tool to be able to create, to deploy  software in many servers and to be able to do DevOps work in this case.  So this is the new theme.  This is how we changed C-CAN and we provided also some new extra features which I'm going  to go through now.  Well the look and feel of the search page is not much different from what you can find  in C-CAN but there are some hidden features like now we are doing automatic generation  of WMS and WFS for example if somebody uploads some vector data.  So here we redesigned the dataset page and now when somebody uploads a shape file we  have like sorry this is the Greek, I will show you later the English page but this is  the data and these are the services and these are the metadata so we now have all of them  in one page and somebody can just upload the shape file and what happens is when you  upload a shape file to C-CAN for example it will identify that it's a shape file, okay  that's easy and then it will get you through some steps in order to complete how you publish  your data.  So initially C-CAN just asks for a title, a description, a license and an organization.  That's all the four elements that C-CAN used to ask so you can still do that but we added  a full inspire metadata editor to C-CAN so if you can, if you will, if you change the  schema here and you say I don't want C-CAN, I want to inspire or ISO then you get the  next page which is a full metadata editor inspired by the inspired geoportals so you  can add things like linears and spatial resolution and conformity and all this stuff.  So if you go into that trouble, well which is required for EU organizations then you  have a full XML representation of inspire metadata and then you're able to directly  sorry this is wrong, then you're able to directly publish them through CSW.  So then we implemented a new dashboard within C-CAN, C-CAN was not able, when you uploaded  the geospatial file it was not able to do anything with it, it just was there only download,  nothing more.  So now we made a new dashboard where when you upload the file, let's say a save file,  it will identify what it is and it will provide you with some options so you can ingest the  resource to a database which is post-GIS or you can just ignore it or you can do just  some copy of data if you want to but the main idea is that you upload the save file and  then you go to the administration site and you publish, you ingest your data to post-GIS.  So after you do that immediately the dataset page will automatically create you an endpoint  through Geo server or Map server for WMS and WFS and then it will be available on a map  directly.  So you can regenerate the endpoints by linking to the post-GIS page and then we have previews.  So if you go into a dataset and you hit the preview and the map you just get the WMS,  you get a URL how to link to another application using WMS or you get support for WFS right  out of the box.  And we do that also with raster data.  So once you provide a T file or an hcdf file, well obviously you are not going to upload  the big T file on your browser, right?  So instead you can add the link to it.  So if you add the link to it, the server will download it, it will ingest it to Rastaman  and then it will provide WCS endpoint and WMS based on this dataset.  Of course it will try to guess what type of data that is and we provide also previews.  I'm going to go really fast now because there's not enough time and there are many features.  So in the metadata, once you get your metadata there or when you want to upload the file  and create a dataset from that, you directly have PiscesW there to help you.  So you have your metadata and your page and you can just download whatever other profile  you want based on PiscesW.  We also took some time to provide some tools for developers.  So we did our own test of providing a mapping API and we did it both with leaflet and open  layers.  So you have similar code with our API, almost identical.  I mean only one line changes and you have the same result either on leaflet or on open  layers.  Now also we provide a data API, since we have all the data now directly in post-GIS, we  created an API with a JavaScript API, sorry, where you can do queries to the data directly.  And of course because it's a national portal, we created a new client, a new map application  directly with open layers with features like when you see a layer here, you can just select  a part of the layer and you can download it through the data API and you can get the file.  So somebody just doesn't know how to use a WebGIS, you can just click and download the  data through the map directly.  So also I don't have enough time, sorry, it's too many slides, too many features, we added  multilingual support.  So we kind of did a UI where somebody can translate data and metadata directly through  the through SICAN.  So if you have an English data set and you want to translate it to Greek or to French  or anything else, there is a UI where you can do the translation, it will store the different  revisions and then you will get your data set in a different language in the data set  page.  That's about it, no time for a demo if you want, I can demonstrate outside.  So thank you.  Thank you, Angulos, are there any questions?  Thank you for presenting this, it's impressive.  And my question is, I see many similarities to GeoNode and how did you consider it also  at the beginning or how you see the differences?  Yes, this is a good question.  So actually I'm a GeoNode developer myself, but sometimes you have requirements that are  given to you by somebody, right?  And sometimes you are working with different communities, as Paul said.  And the open data community has SICAN as a reference, let's say implementation, everybody  is using SICAN, so most open data portals will use SICAN.  Well, GeoNode is becoming a very strong player, but the difference is that GeoNode is even  more focused on Geospatial than SICAN.  But SICAN is more, I mean, for example, you can upload any kind of data on SICAN and it  will do its work, its extensions will work.  So it's a platform for open data.  Well, GeoNode is also a very good platform, but it is more focused into providing Geospatial  features.  And actually SICAN was missing those features, but they were needed.  So we had to do it on SICAN.  It's a matter also of preference, it's open source, right?  Variety matters in this aspect.  And also GeoNode is improving the SICAN connection.  Yes, there are SICAN connections, they both use PICSW so you can harvest each other now.  But it's also a vibrant community, SICAN is also moving, but this project was a two-year  project only.  So we went as far as we could.  Thank you.  A very excellent product, I think.  So can we get virtual environment?  So for example, the Baygrunt or Docker, for example, can we get to the Docker?  It is all the software is on GitHub.  If you go to public Amundi organization, we don't use Docker yet.  We are now porting it to Docker, but we have all the uncivil scripts.  So if you get the uncivil scripts, you will run them on one VM.  It will create a very big VM and very heavy VM, but it will work.  But also we also provide the actual production uncivil scripts.  If you have 10 or 15 VMs available, you can set up the whole thing by yourself.  I think we spend a lot of time on uncivil to be able to reproduce it because failure  happens and we used to do lots of work to set up new servers, so uncivil was a lifesaver  for us.  And now Docker, so it will be available soon also.  So one last question.  Someone?  So you mentioned it will be available soon, but the public Amundi project finished?  Are there still organizations in that community?  Is this?  Yeah, so, all right.  Athena Research Center maintains the catalog.  So it's a national catalog.  The project has ended, but maintenance is still going.  We are not implementing right now new features.  Maybe if we get some funding, if somebody is interested, we can also do some new project.  But we do maintenance.  So everything that is needed to work, it will continue to be supported for many, many years  because the government is behind it, even a bit broke at the moment.  But anyway, yeah, it's still there.  So yeah, and contributions are always welcome.  The development team is also doing other stuff, but it's an open source.  It's there.  Anybody can pick it up and continue or ask us to help.  Okay.  Well, then I want to close this session.  Thanks. eters again.  Thank you.  Thank you.  Thank you.
foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_0_407.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_408_2123.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_2124_5567.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_5568_7451.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_7452_7595.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_7596_7703.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_7704_8231.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_8232_8459.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_8460_8879.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_8880_10403.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_10404_10547.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_10548_10607.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_10608_12923.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_12924_14171.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_14172_20375.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_20376_20903.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_20904_22715.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_22716_24623.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_24624_28223.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_28224_29819.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_29820_30551.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_30552_30659.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_30660_31175.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_31176_31607.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_31608_32375.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_32376_33347.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_33348_35579.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_35580_36575.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_36576_37511.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_37512_37895.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_37896_38039.png foss4g-2016-1169-implementing_open_geospatial_data_portals_with_ckan_pycsw_and_publicamundi_the_geod_38040_38514.png