The source code is available on a public repository on Github. This means that you can clone, fork and propose pushes of your custom changes. If you are not familiar with repositories of code or git, you should check this quick manual.
Maven and Java
It is built using mavenversion 3+. Therefore, it is written on Java and requires version 7 or more. Can be run both with OpenJDK or the Oracle version.You will need git and maven installed on your local machine to work. There are several ways to install this on your local machine; for example if you have a Debian based OS (like Ubuntu), you can install them with just this command:
Remember that this will also install java on your system. You can check that the version is the right one with the following command:
So, the very first step once you have your environment set up is clone the repository on your local machine. That can be done on the command line using the following command inside an empty folder where the source code will be populated:
As you can see, all the source code shown on github is also available on your local machine now.
Internal Structure of GeoNetwork
The source code is split on several smaller maven projects. To run it, you have to build all of them and run the project named “web“.
If you are familiar to maven, you will probably have guessed that you have to run a package install command on the root folder of the source code. But if you try that, maven will warn you that for building it you need more memory than the default memory provided to maven.
So, you will have to export the maven options to increase the memory like this:
export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=256M"
At this point we are not interested in running the tests, so you can skip them using the parameter “-DskipTests”:
mvn package install -DskipTests
At the end of this build (which can take long, depending on your network connection, as it has many third party libraries), you will see something like this:
[INFO] BUILD SUCCESS
[INFO] Total time: 02:19 min (Wall Clock)
[INFO] Finished at: 2015-07-17T10:36:43+01:00
[INFO] Final Memory: 232M/441M
This will generate a war file you can use in any Java Application Container (server) like Tomcat on web/target/geonetwork.war
Congratulations! You are ready to run it. To do this, just go to the web folder and run jetty in there:
Last week I had the privilege to attend the main osgeo conference: the FOSS4G. This time it took place on Seoul, Korea. Exotic place I strongly recommend to visit, but better to focus on non-cultural surprises on this post.
It’s impossible to write everything on a single blog post, as it was impossible to assist to all the interesting parallel threads that run on those short five days. But let me guide you through my steps so I can share part of my experience until we get access to the full videos of that awesome week.
First there were the workshops. I have to confess something: my first options for workshops were cancelled. But it doesn’t matter, as I had problems deciding on first place. So, I started with the WS02 workshop:
Exploring the Sensor Observation Service Standard Enhanced by IstSOS Special Features
Let me summarize it: if you want to work with sensors, take a very close look at IstSOS. Combining PostGIS, Python, GDAL and Apache you get not only a complete sensor service, but a complete sensor data management system. Easy to use, easy to install, easy to everything!
Quality Assurance is integrated on IstSOS to make sure the sensor doesn’t go mad. This process are sometimes done asynchronously to conflate your own sensor data with other sources. It doesn’t just return a basic boolean, but a statistic value of confidence based on previous data.
Another interesting feature is the virtual sensors, which allows you to create your “own” “sensors” based on data from real physical sensors. Useful to conflate data and offer it on a unique endpoint as sensor.
As if this workshop wasn’t good enough, we got some real arduino and sensors to play with them.
WS08 Build your own data portal using GeoNetwork 3
Besides some Windows issues (surprise!), I think that the workshop was very successful. Assistants not only built their own user interface style for GeoNetwork, but asked us about advanced features and how to implement them.
As Florent said: “We are the experts of GeoNetwork, so if you have any questions, it is now or never.” And we had questions asked.
Jet-lagged day finished after this workshop. So we went to the hotel to try to rest a bit more and start with renewed strength the following day, which I started with:
WS19 Beyond GeoServer Basics
If you already run a GeoServer, most of this workshop is already known to you. But if you don’t… bad you missed it! There were a lot of fancy features to play with, like regexp on parameters for sql layers (surprised that very few knew what regexp meant!).
And, of course, WPS already useful in production now. You can even use WPS inside SLD definitions!
After refreshing knowledge on GeoServer, I went for the last workshop:
WS21 OpenSource 3D GIS
Yes, you are right, 3D GIS has too much hype right now. But Oslandia did a great job on this workshop. If you don’t have experience with 3D, I strongly advise you to try to follow the workshop, posted on github.
We even had some docker introduction. And the second day was finished, but we still had energy to went for the last one. Or some more beers:
I was already on the first slot of the FOSS4G conference, during the Opening Ceremony, when I first noticed that we talked too much about open instead of free.
Besides that, Venkatesh made very clear that we need more Geo4All, specially on developing countries.
Very interesting the national SDI of Korea presentation about the workflow of open source. While I don’t fully agree with their vision, it is always refreshing to see new perspectives on this subject. Maybe we should make more clear that free software can have a professional customer support as good as any closed source software. Probably even better in most cases, as there are more companies that can offer it.
Now the conference divided on so many threads at the same time that it was impossible to follow them all. QGIS (new useful plugins to develop) and MapServer (now faster than ever) before lunch and the sensor and crowdsourcing session after lunch. There, between the ISA server for indoor spatial data, Apache Spark, Ontologies and CartoDB, we presented Cobweb. The day couldn’t finish without a very productive and promising BOFH session about crowdsourcing… and more!
Thursday was a hard day: jet lag started to go away, but taking #geobeers every night does not help much.
Alysa Wright started with a cool presentation about why and how did she start on the spatial world. We should never forget that, as a community, we come from very different places and perspectives. And still, we share a common view about freedom.
On the last session of the day, I learned about OpenDroneMap. I couldn’t stop asking myself why didn’t I knew about this incredible project before. Where drone software is even more awesome than the drone hardware.
Finally, Paul Ramsey talked about sustainability of free and open software and why we should care about who maintains it.
Last day of conference is here. Friday tastes bitterweet. And not because of the food! María Brovelli starts with a keynote about crowdsourcing and VGI and how they can change our community. Because even if we don’t deal directly with the data, the software is also affected by all this. The next keynote was from Marco Hugentobler, talking about the qGis community from a developer’s perspective. Because, yes, “developers are human and not everyone is aware of that”. What a surprise! In any case, never trust someone with the “expert” label, just trust the community. After the coffee break, I attended a very instructive presentation from Henrik Lund Pedersen about caching fresh data. Is it possible to have a cached and updated server for GIS data?
Jody Garnett talked about documentation and why we should be very careful when writing it: not only to help advanced developers but also to not scare newbies. Never use the word “easy”, for example. If you use it and the reader don’t find it easy, he will go away to look for something easier for him. And maybe the original documentation was easy, it’s just that it hasn’t been updated with new features.
Then we had another Cobweb session on the main grand ballroom, this time by Panos, talking about the mobile part of the framework.