QGis as a platform: transforming the desktop QGis for tablet use in Flanders fields
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.
Huybrechts, Roel
In this talk we'll take the off-the-shelf QGis you've come to know and love on your desktop and search the limits of customization. We'll transform the standard desktop application to a version tailored for tablet use including a finger-friendly interface, camera integration and full offline editing support with data synchronisation. Taking QGis where no QGis has gone before, we take the theory into Flanders fields. We demonstrate the possibilities of the technology with a use case where QGis is used in the field to assess soil erosion in the hills of Flanders. Thanks to a strong foundation and simple yet powerful customization options, we learn that Qgis can really outperform your expectations, even outside of its (or your?) comfort zone. Bring your boots!
 Okay, we are going to the second presentation in this QGIS sessions. This time it's also about taking QGIS out into the field. This time it's from Belgium, a Royal Hoi Bricks. Who is going to tell us how you can transform the QGIS desktop into a tablet? Yes, I will. Alright, welcome everyone. Let me start by thanking you. Now you're still here. Thanks to your organization for having me and thanks to you all for being here and listening. So a very short introduction about me. My name is Roulou Hoi Bricks. This is the way it's pronounced. I'm a GS consultant at Real Dolmen, which is a Belgian-based IT consultancy firm. I primarily work for the Flemish government, which is the northern part of Belgium, at the department DOV, which stands for Data Bank on the Grundvladen. We manage and publish all the data about the soil and the subsoil of Flanders. We do so primarily using open source GIS products, mostly post-GIS and geo-server, added to its spatial IT QGIS, etc. I do some scripting in between to glue these things together in a more or less efficient way. And yeah, the maps, I love the maps. As do you, I suspect. So what will we talk about today? I'll start with a very short introduction about soil erosion, just enough so you can follow the case. And then we'll jump right into the cool stuff, using QGIS as a platform, making it into the tablet user experience. And I will talk a little bit about data synchronization to keep it all working. And I hope there's some time at the end to do a little demo. So soil erosion, what is it? Basically it's when your field ends up on the road, which is not what we want. So it causes a variety of problems, so measures are needed to limit it. How do we go about it? Each year the Flemish government makes a map, which classifies each agricultural plot based on its potential soil erosion. This is calculated from a model based on digital elevation model, et cetera. So every plot gets a classification from negligible to very high, which is color coded, so it goes from green to purple, basically. So each plot gets a color. And based on the classification, the farmer has appropriate measures that need to be taken. For example, the direction of plowing, et cetera. Now we wouldn't be in a democracy if the farmer could not file an objection. So if he finds his purple parcel really should be orange instead. He files an objection. And these end up on the desk in Brussels. And they all need to be checked on the field whether they're legit or not. And this is where the application comes into play. So the tablets. Why did we end up with the tablets? Because previously everything was printed out on paper, basically, in the morning, annotated in the field, and then re-digitized afterwards, which works if there are 50 fields to check, but not if there are 2,000 fields to check. So why did we chose the tablets? Obviously, they're digital. So we've no longer waste resources printing it and re-digitizing it again. But it adds extra features. So we have all maps and data at hand at any time. For the whole of Flaunters, all files are on the tablets. So you can change your planning during the day if you decide to do other things. And we have more maps available than we did in the paper age. Additionally, the tablets have cameras. So you can take photos of the fields to corroborate your decisions. This is handy afterwards if there should be any doubt about any decisions made. And lastly, they've got GPS, which is very handy in the field just to know where you are. Even at plot level, it's interesting to see which side you're on. So these are a few advantages. Now why did we chose QJS to build? To start the tablet application from. QJS is way more than your everyday desktop GIS system, as you probably know. It is a perfect starting point for building custom JS applications. Why is that? It has a solid base. It's been around for a few years. It's been tested thoroughly. So the base functionality works and is also available through an API. So you can use it in your own custom components, which is hugely advantage. Secondly, it's open source. I wouldn't need to convince you from the fact that this is beneficiary. So you can access the source code if there are any things unclear. There's a great community behind it if you have any questions. And there are lots of plugins already available that you can use and integrate in your projects. Thirdly, it's a collection of tools, languages and tools. So if you have the QJS installed, with it you get all these other tools that you can use. Namely, you have GDAL, you have OGR, you have Python, you have QT. With them you can really build anything. And you get cross platform for free. Once you build your application, which runs on Windows, Linux, OSX and Android more or less, your application does so as well. Now how do we start building the application? First and foremost, it's about the data, really. Developers like to think more in terms of applications. Users think in terms of data. Applications are really a means of working with their data. So yeah, it's the data that is important. So what is data in terms of GIS? It's the map, basically. The map is of the utmost importance in GIS. You use it all the time. It takes 95% of the screen and you need it to navigate, to identify features, to do analysis. So the map is really important. As a base map, we use a topographic map of the NGI, combined with certain things of Open Street Map. These combine really well. Open Street Map has, for example, the street names which are not in the topographic map. But we have way more than this. We have imagery. Imagery is on the tablets. It's useful in the field to know where you are. We have the soil map, which basically shows the things you cannot see on the field, which is under the ground, which is interesting if you need to assess the erosion. We have the water runoff map, which is basically a grid, which shows how the water accumulates when it rains. It's based on the digital elevation model. We have, of course, the potential erosion map. Not only the one from this year, but only the historic versions to see the evolution of the classification. We have the base grids, where the previous map is calculated from. So these are covered a whole of flanners. And the previous one is calculated based on the plot polygons. And, of course, we have the digital elevation model itself, which is color coded from red to blue. And it actually changes when you pan or zoom the map. So it's always from red to blue. Otherwise, at plot level, you wouldn't see the difference between the left and the right, because the difference is not so high. Of course, we have the plots with their objections in another color, so you can easily spot where you need to go. All these are in different formats. Basically every format you can throw at QGIS will work, because it is QGIS. Now how do we make it into a tablet application you can use with your fingers? Every is quite simple. We want to let things on the screen, and the things that remain need to be bigger, so you can hit them with your finger. Now how do we go about it? In practice, we start removing stuff. On the right, you can see the thing change. Now we remove toolbars that we don't need. Everything gone. We can remove parts of toolbars via the customization option in QGIS. So you can keep only the buttons we need. Remove the panels, basically all the panels. Remove the status bar. And then we start making things bigger. Increase the font size, which makes things more readable, but also makes, for example, drop downs easier to hit, because they get higher, because the font size is bigger. Same goes for icon size. The icons get bigger, but as a consequence, the buttons get bigger too. So the toolbar actually works with your finger. And then we add custom components. I will talk about it later. And at last, we make it full screen to make it look like an app. For when you are using a tablet in the field, you really want the best user experience you can have. And this is true for all applications, but even so, when you're standing in a field in the mud and it's raining and it's cold. So we want the best user interaction. And I believe in this case, really the best is no user interaction. You want really to do more by touching less buttons. You want one button to complete one action. Maximum two buttons, the less buttons we need to touch, the less we can't miss. So we want to minimize annoyance. How do we go about it? We make everything available offline because wireless will fail when you're standing in the field at the worst moment. So everything is available offline. All data is offline. And we have offline editing because there's no point standing somewhere and not be able to write your advice. Secondly, the map view automatically changes on the zoom level. So when you zoom in, more details appear, when you zoom out, it gets clearer. This is standard QGIS functionality. We just used it. It's hugely advantageous for the user to not be necessary to pick out certain layers. Thirdly, we do auto-saving of edits. Because if you ever edit something in GIS, it's difficult. With six steps needed, you need to select the layer. You need to enable edit mode, find the feature, do the edit, save the edit, quit edit mode, save it again. This is way too difficult. If you want to change, well, if you change something, you want to be changed. So we do have auto-saving of edits. Basically, you can change something with two buttons. This is important. And lastly, we want to get information with one touch. Even though in your data model, it might be split over 10 tables, you do not want to do to query 10 features to get the information you want. We want to touch one single field and get all the information about that field grouped already for us. When designing, you have to think as a pro user. Try using it for a single day, because they have to use it every day. If you throw it out of the window by noon, by noon, it's not good. Now we know the principles. We can start adding the custom components that make it really fluent for the tablet users. Now we start designing within the context. So this is a tablet. When you take it out of the box, you hold it this way. It looks great. Until you want to type something, it pops the keyboard and half of the screen is gone, which is not what we want. There's basically no space left for useful content. So we skip this and we turn it 90 degrees, which is a lot better, because now the keyboard only takes a third of the screen and we have two thirds left for useful things. So we add a toolbar on top with global functionality, like zooming and searching and identifying features. And we add the side panel with information of a specific field you touched. It's got also the contextual buttons linked to this specific field on the side panel on the right. Like for instance, zooming it to it on the map. And now we add the cool stuff, which is camera integration. So if you hit the camera button on the right hand side of the screen, it pops the camera application. It can take pictures of the field, which are automatically linked to the field you're currently looking at, because otherwise later on you will never know which field is on the photo. When you're done, you just close it, a dialogue is already sitting ready, and you have to just press save or cancel if you want to cancel out. Of course, we have search. So if you hit the two buttons, the two boots with the question mark in the toolbar, you can search for a farmer by name. And so you just type his name, press search. This actually works by using SQLite full text search capabilities. So it actually works. It finds what you need, and it's fast. It searches 100,000 records in milliseconds. So it's really fast. Of course, we have edit. So if you press edit, you get another window, which is designed to be useful on the left side and less useful on the right side. So you can actually slide it over the panel to show more of the map while editing. You even add the minimize button on the left side to get it out of the way completely because the minimize button has fallen off the screen. So you press the minimize button on the left side, and it goes away completely. Now how do I get it back? Because it's stuck behind the keyboard. The edit button doubles as restore button. So now you can press the add button again, and there it is. So these are really the details that make it work. This year we have another feature where if you're visualizing the restore grid, you can draw a polygon on the screen, and it will actually align it to the cells and calculate the average value for you. So this is useful if you want to recalculate. Oh, five minutes left. I'm going to skip after this. Because I want to tell you this is cool. So you can actually recalculate the value it should have without some hill in the corner, maybe. So five minutes. We need to talk about data synchronization because some of you might have spotted the elephant in the room now. We have full offline editing support, and we have multiple users on the ground. As I said, we have four persons on the ground and one person in the office, and we have offline data and editing. So if this does not make you nervous, something is wrong. Because this is the perfect recipe for total chaos, which is not what we want. So we need to do something about it. This is a situation for tablets, desktop computer running by the way, exactly the same code as on the tablets. And we have our server sitting around. So we might have moved the elephant to the server and add the database. We connect them all through the internet with something called the QJS versioning plugin. It was already available. It's made by the folks at Auslandia. And it basically makes the changes appear on the server and back on the other tablets again. So we create the single point of truth using this synchronization plugin. It works with a master table in post-JS on the server, and we have spatial light working copies on the clients. This has a number of advantages for us. Because on the server, there's no extra software or configuration required. We could use the same post-JS database we already had with the same user authentication and permissions. The working copy is in spatial light, which is a QJS native format. So for thinking, we do not need to do an import and export first, because we have a data of a few hundred megabytes to take too much time. And lastly, only the diffs. So the differences are being transferred. So it is fairly efficient and fast. So as I said, the clients can be tablets or ordinary PCs. So your changes end up on the other tablets too. And that's the office ready for post-processing. As a free bonus, you have the full history available at plot level. So you can see for each plot, who changed it, what was changed, when was it changed. This is perfect when things are unclear. Right, do we have time for a little demo? I will try to make it fast. So this is how it looks like. We have the toolbar on top and on the side. We can search for a farmer. I know Robin filed a complaint. So we press search, we find him. We can list. It's running from my external drive, which needs to spin up. See all the complaints he filed. We can take one. The information about it is visualized in the side panel. We can close all these. We can zoom to his complaint. We can maybe change the map view. So we added these buttons to change the map view with just two touches of a button, which basically just enables or disables certain layers. It basically replaces the layers panel, but much faster. We can press edit maybe. So as you can see, we have the minimize button here. It minimizes the tiny little thing here, where the maximize button is really close to the close button, which is not very handy. So we added this button right here to just make it big again. So let's say I set this to not accepted. And the farmer was at the field. So we write some data here. We hit save. This input form has validation inside. So if you see, I did not accept it, and it automatically changed it to green, because that's the color it had this year. So it does some things for you, so you cannot miss. And it has validation too, so you won't end up with the wrong data. Normally, it should say faster than this. Well, okay, I think we're about through the time. Voila. Thank you very much. This was great. Thank you. Actually, I'm one of those persons who are in the field, so I can't fully follow what you have been doing. I know there must be a lot of questions here. Who wants to start? We only have four minutes. Thank you for that presentation. My question is, did you plan to release some parts of your work to the public, or what are your plans about that? Currently, it's only used internally, as I said, by five persons. But it's not published yet. The case, specifically this case, is really specific to this purpose. But I guess, indeed, some parts of it are reusable, and I'm planning to... It's definitely on the planning to release them as open source. Any other questions? Yeah. I think I don't need it. It's needed for the streaming. So did you ever consider going with the InterMaps ROM application? I'm not familiar with the InterMaps ROM application. It's similar, but it's like two years, three years already stable, and I was wondering why you didn't chose that. Yeah, I'm afraid I never heard about it, so that's why I didn't use it. Okay. That was probably the wrong answer, but I did some checking before, and I found other projects with QJS and Android being one of them. But then I realized we already had quite a good basis with the standard QJS. We wanted basically just set up the project and then take it in the field, and this is what we did, basically. Cool. Thank you. Thank you. Anyone else who wants to have a question up here? Yeah. Then thank you very much. It was a very great inspiration. Thank you.
 Okay, we are going to the second presentation in this QGIS sessions.  This time it's also about taking QGIS out into the field.  This time it's from Belgium, a Royal Hoi Bricks.  Who is going to tell us how you can transform the QGIS desktop into a tablet?  Yes, I will.  Alright, welcome everyone.  Let me start by thanking you.  Now you're still here.  Thanks to your organization for having me and thanks to you all for being here and listening.  So a very short introduction about me.  My name is Roulou Hoi Bricks.  This is the way it's pronounced.  I'm a GS consultant at Real Dolmen, which is a Belgian-based IT consultancy firm.  I primarily work for the Flemish government, which is the northern part of Belgium, at  the department DOV, which stands for Data Bank on the Grundvladen.  We manage and publish all the data about the soil and the subsoil of Flanders.  We do so primarily using open source GIS products, mostly post-GIS and geo-server, added to  its spatial IT QGIS, etc.  I do some scripting in between to glue these things together in a more or less efficient  way.  And yeah, the maps, I love the maps.  As do you, I suspect.  So what will we talk about today?  I'll start with a very short introduction about soil erosion, just enough so you can  follow the case.  And then we'll jump right into the cool stuff, using QGIS as a platform, making it into the  tablet user experience.  And I will talk a little bit about data synchronization to keep it all working.  And I hope there's some time at the end to do a little demo.  So soil erosion, what is it?  Basically it's when your field ends up on the road, which is not what we want.  So it causes a variety of problems, so measures are needed to limit it.  How do we go about it?  Each year the Flemish government makes a map, which classifies each agricultural plot based  on its potential soil erosion.  This is calculated from a model based on digital elevation model, et cetera.  So every plot gets a classification from negligible to very high, which is color coded, so it  goes from green to purple, basically.  So each plot gets a color.  And based on the classification, the farmer has appropriate measures that need to be taken.  For example, the direction of plowing, et cetera.  Now we wouldn't be in a democracy if the farmer could not file an objection.  So if he finds his purple parcel really should be orange instead.  He files an objection.  And these end up on the desk in Brussels.  And they all need to be checked on the field whether they're legit or not.  And this is where the application comes into play.  So the tablets.  Why did we end up with the tablets?  Because previously everything was printed out on paper, basically, in the morning, annotated  in the field, and then re-digitized afterwards, which works if there are 50 fields to check,  but not if there are 2,000 fields to check.  So why did we chose the tablets?  Obviously, they're digital.  So we've no longer waste resources printing it and re-digitizing it again.  But it adds extra features.  So we have all maps and data at hand at any time.  For the whole of Flaunters, all files are on the tablets.  So you can change your planning during the day if you decide to do other things.  And we have more maps available than we did in the paper age.  Additionally, the tablets have cameras.  So you can take photos of the fields to corroborate your decisions.  This is handy afterwards if there should be any doubt about any decisions made.  And lastly, they've got GPS, which is very handy in the field just to know where you  are.  Even at plot level, it's interesting to see which side you're on.  So these are a few advantages.  Now why did we chose QJS to build?  To start the tablet application from.  QJS is way more than your everyday desktop GIS system, as you probably know.  It is a perfect starting point for building custom JS applications.  Why is that?  It has a solid base.  It's been around for a few years.  It's been tested thoroughly.  So the base functionality works and is also available through an API.  So you can use it in your own custom components, which is hugely advantage.  Secondly, it's open source.  I wouldn't need to convince you from the fact that this is beneficiary.  So you can access the source code if there are any things unclear.  There's a great community behind it if you have any questions.  And there are lots of plugins already available that you can use and integrate in your projects.  Thirdly, it's a collection of tools, languages and tools.  So if you have the QJS installed, with it you get all these other tools that you can  use.  Namely, you have GDAL, you have OGR, you have Python, you have QT.  With them you can really build anything.  And you get cross platform for free.  Once you build your application, which runs on Windows, Linux, OSX and Android more or  less, your application does so as well.  Now how do we start building the application?  First and foremost, it's about the data, really.  Developers like to think more in terms of applications.  Users think in terms of data.  Applications are really a means of working with their data.  So yeah, it's the data that is important.  So what is data in terms of GIS?  It's the map, basically.  The map is of the utmost importance in GIS.  You use it all the time.  It takes 95% of the screen and you need it to navigate, to identify features, to do analysis.  So the map is really important.  As a base map, we use a topographic map of the NGI, combined with certain things of Open  Street Map.  These combine really well.  Open Street Map has, for example, the street names which are not in the topographic map.  But we have way more than this.  We have imagery.  Imagery is on the tablets.  It's useful in the field to know where you are.  We have the soil map, which basically shows the things you cannot see on the field, which  is under the ground, which is interesting if you need to assess the erosion.  We have the water runoff map, which is basically a grid, which shows how the water accumulates  when it rains.  It's based on the digital elevation model.  We have, of course, the potential erosion map.  Not only the one from this year, but only the historic versions to see the evolution  of the classification.  We have the base grids, where the previous map is calculated from.  So these are covered a whole of flanners.  And the previous one is calculated based on the plot polygons.  And, of course, we have the digital elevation model itself, which is color coded from red  to blue.  And it actually changes when you pan or zoom the map.  So it's always from red to blue.  Otherwise, at plot level, you wouldn't see the difference between the left and the right,  because the difference is not so high.  Of course, we have the plots with their objections in another color, so you can easily spot where  you need to go.  All these are in different formats.  Basically every format you can throw at QGIS will work, because it is QGIS.  Now how do we make it into a tablet application you can use with your fingers?  Every is quite simple.  We want to let things on the screen, and the things that remain need to be bigger, so you  can hit them with your finger.  Now how do we go about it?  In practice, we start removing stuff.  On the right, you can see the thing change.  Now we remove toolbars that we don't need.  Everything gone.  We can remove parts of toolbars via the customization option in QGIS.  So you can keep only the buttons we need.  Remove the panels, basically all the panels.  Remove the status bar.  And then we start making things bigger.  Increase the font size, which makes things more readable, but also makes, for example,  drop downs easier to hit, because they get higher, because the font size is bigger.  Same goes for icon size.  The icons get bigger, but as a consequence, the buttons get bigger too.  So the toolbar actually works with your finger.  And then we add custom components.  I will talk about it later.  And at last, we make it full screen to make it look like an app.  For when you are using a tablet in the field, you really want the best user experience you  can have.  And this is true for all applications, but even so, when you're standing in a field in  the mud and it's raining and it's cold.  So we want the best user interaction.  And I believe in this case, really the best is no user interaction.  You want really to do more by touching less buttons.  You want one button to complete one action.  Maximum two buttons, the less buttons we need to touch, the less we can't miss.  So we want to minimize annoyance.  How do we go about it?  We make everything available offline because wireless will fail when you're standing in  the field at the worst moment.  So everything is available offline.  All data is offline.  And we have offline editing because there's no point standing somewhere and not be able  to write your advice.  Secondly, the map view automatically changes on the zoom level.  So when you zoom in, more details appear, when you zoom out, it gets clearer.  This is standard QGIS functionality.  We just used it.  It's hugely advantageous for the user to not be necessary to pick out certain layers.  Thirdly, we do auto-saving of edits.  Because if you ever edit something in GIS, it's difficult.  With six steps needed, you need to select the layer.  You need to enable edit mode, find the feature, do the edit, save the edit, quit edit mode,  save it again.  This is way too difficult.  If you want to change, well, if you change something, you want to be changed.  So we do have auto-saving of edits.  Basically, you can change something with two buttons.  This is important.  And lastly, we want to get information with one touch.  Even though in your data model, it might be split over 10 tables, you do not want to do  to query 10 features to get the information you want.  We want to touch one single field and get all the information about that field grouped  already for us.  When designing, you have to think as a pro user.  Try using it for a single day, because they have to use it every day.  If you throw it out of the window by noon, by noon, it's not good.  Now we know the principles.  We can start adding the custom components that make it really fluent for the tablet users.  Now we start designing within the context.  So this is a tablet.  When you take it out of the box, you hold it this way.  It looks great.  Until you want to type something, it pops the keyboard and half of the screen is gone,  which is not what we want.  There's basically no space left for useful content.  So we skip this and we turn it 90 degrees, which is a lot better, because now the keyboard  only takes a third of the screen and we have two thirds left for useful things.  So we add a toolbar on top with global functionality, like zooming and searching and identifying  features.  And we add the side panel with information of a specific field you touched.  It's got also the contextual buttons linked to this specific field on the side panel on  the right.  Like for instance, zooming it to it on the map.  And now we add the cool stuff, which is camera integration.  So if you hit the camera button on the right hand side of the screen, it pops the camera  application.  It can take pictures of the field, which are automatically linked to the field you're currently  looking at, because otherwise later on you will never know which field is on the photo.  When you're done, you just close it, a dialogue is already sitting ready, and you have to  just press save or cancel if you want to cancel out.  Of course, we have search.  So if you hit the two buttons, the two boots with the question mark in the toolbar, you  can search for a farmer by name.  And so you just type his name, press search.  This actually works by using SQLite full text search capabilities.  So it actually works.  It finds what you need, and it's fast.  It searches 100,000 records in milliseconds.  So it's really fast.  Of course, we have edit.  So if you press edit, you get another window, which is designed to be useful on the left  side and less useful on the right side.  So you can actually slide it over the panel to show more of the map while editing.  You even add the minimize button on the left side to get it out of the way completely because  the minimize button has fallen off the screen.  So you press the minimize button on the left side, and it goes away completely.  Now how do I get it back?  Because it's stuck behind the keyboard.  The edit button doubles as restore button.  So now you can press the add button again, and there it is.  So these are really the details that make it work.  This year we have another feature where if you're visualizing the restore grid, you can  draw a polygon on the screen, and it will actually align it to the cells and calculate  the average value for you.  So this is useful if you want to recalculate.  Oh, five minutes left.  I'm going to skip after this.  Because I want to tell you this is cool.  So you can actually recalculate the value it should have without some hill in the corner,  maybe.  So five minutes.  We need to talk about data synchronization because some of you might have spotted the  elephant in the room now.  We have full offline editing support, and we have multiple users on the ground.  As I said, we have four persons on the ground and one person in the office, and we have  offline data and editing.  So if this does not make you nervous, something is wrong.  Because this is the perfect recipe for total chaos, which is not what we want.  So we need to do something about it.  This is a situation for tablets, desktop computer running by the way, exactly the same code  as on the tablets.  And we have our server sitting around.  So we might have moved the elephant to the server and add the database.  We connect them all through the internet with something called the QJS versioning plugin.  It was already available.  It's made by the folks at Auslandia.  And it basically makes the changes appear on the server and back on the other tablets  again.  So we create the single point of truth using this synchronization plugin.  It works with a master table in post-JS on the server, and we have spatial light working  copies on the clients.  This has a number of advantages for us.  Because on the server, there's no extra software or configuration required.  We could use the same post-JS database we already had with the same user authentication  and permissions.  The working copy is in spatial light, which is a QJS native format.  So for thinking, we do not need to do an import and export first, because we have a data of  a few hundred megabytes to take too much time.  And lastly, only the diffs.  So the differences are being transferred.  So it is fairly efficient and fast.  So as I said, the clients can be tablets or ordinary PCs.  So your changes end up on the other tablets too.  And that's the office ready for post-processing.  As a free bonus, you have the full history available at plot level.  So you can see for each plot, who changed it, what was changed, when was it changed.  This is perfect when things are unclear.  Right, do we have time for a little demo?  I will try to make it fast.  So this is how it looks like.  We have the toolbar on top and on the side.  We can search for a farmer.  I know Robin filed a complaint.  So we press search, we find him.  We can list.  It's running from my external drive, which needs to spin up.  See all the complaints he filed.  We can take one.  The information about it is visualized in the side panel.  We can close all these.  We can zoom to his complaint.  We can maybe change the map view.  So we added these buttons to change the map view with just two touches of a button, which  basically just enables or disables certain layers.  It basically replaces the layers panel, but much faster.  We can press edit maybe.  So as you can see, we have the minimize button here.  It minimizes the tiny little thing here, where the maximize button is really close to the  close button, which is not very handy.  So we added this button right here to just make it big again.  So let's say I set this to not accepted.  And the farmer was at the field.  So we write some data here.  We hit save.  This input form has validation inside.  So if you see, I did not accept it, and it automatically changed it to green, because  that's the color it had this year.  So it does some things for you, so you cannot miss.  And it has validation too, so you won't end up with the wrong data.  Normally, it should say faster than this.  Well, okay, I think we're about through the time.  Voila.  Thank you very much.  This was great.  Thank you.  Actually, I'm one of those persons who are in the field, so I can't fully follow what  you have been doing.  I know there must be a lot of questions here.  Who wants to start?  We only have four minutes.  Thank you for that presentation.  My question is, did you plan to release some parts of your work to the public, or what  are your plans about that?  Currently, it's only used internally, as I said, by five persons.  But it's not published yet.  The case, specifically this case, is really specific to this purpose.  But I guess, indeed, some parts of it are reusable, and I'm planning to...  It's definitely on the planning to release them as open source.  Any other questions?  Yeah.  I think I don't need it.  It's needed for the streaming.  So did you ever consider going with the InterMaps ROM application?  I'm not familiar with the InterMaps ROM application.  It's similar, but it's like two years, three years already stable, and I was wondering why  you didn't chose that.  Yeah, I'm afraid I never heard about it, so that's why I didn't use it.  Okay.  That was probably the wrong answer, but I did some checking before, and I found other  projects with QJS and Android being one of them.  But then I realized we already had quite a good basis with the standard QJS.  We wanted basically just set up the project and then take it in the field, and this is  what we did, basically.  Cool.  Thank you.  Thank you.  Anyone else who wants to have a question up here?  Yeah.  Then thank you very much.  It was a very great inspiration.  Thank you.
foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_0_551.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_552_1259.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_1260_1307.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_1308_1691.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_1692_1739.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_1740_2987.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_2988_4967.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_4968_5507.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_5508_6203.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_6204_7403.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_7404_7631.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_7632_7859.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_7860_9383.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_9384_12203.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_12204_21299.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_21300_28727.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_28728_28919.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_28920_29351.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_29352_32531.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_32532_33191.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_33192_33287.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_33288_33647.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_33648_34103.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_34104_35339.png foss4g-2016-1338-qgis_as_a_platform_transforming_the_desktop_qgis_for_tablet_use_in_flanders_fields-_35340_35495.png