Because data is outside - QField, the future of QGIS on mobile devices
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 37 | |
| Autor | ||
| Lizenz | CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Deutschland: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben. | |
| Identifikatoren | 10.5446/40768 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Schlagwörter |
QGIS ACoruña Konferenz 201931 / 37
3
5
8
13
17
19
26
00:00
SoftwareentwicklerSchlussregelGesetz <Physik>Formation <Mathematik>CASE <Informatik>Endliche ModelltheorieDivisionCoxeter-GruppeKontrollstrukturMobiles InternetProgramm/QuellcodeComputeranimation
00:47
UMLComputeranimation
01:11
Textur-MappingHumanoider RoboterQuellcodeExpertensystemMereologieVererbungshierarchieVertauschungsrelationUML
01:39
BenutzeroberflächeBitmap-GraphikNotebook-ComputerHumanoider RoboterBildgebendes VerfahrenRechenwerkMultiplikationsoperator
02:21
Lie-GruppeRechter WinkelSoftwaretestMultiplikationsoperatorBenutzerbeteiligungXML
02:50
BenutzeroberflächeSinusfunktionProjektive EbeneNP-hartes ProblemNeuroinformatikRechter WinkelEntscheidungstheorieElektronische PublikationGamecontrollerDatenfeldMapping <Computergraphik>Interface <Schaltung>SpeicherabzugTablet PCStützpunkt <Mathematik>KonfigurationsraumMultiplikationsoperatorBenutzeroberflächeApp <Programm>Keller <Informatik>MaschinenschreibenLeistung <Physik>ResultanteEinfacher RingAnwendungsspezifischer ProzessorFlächeninhaltSichtenkonzeptSpezielle unitäre GruppeVisualisierungFrequenzART-NetzEnergiedichteBenutzerhandbuchSynchronisierungProgrammfehlerXMLUML
05:52
StrömungswiderstandDefaultDatensichtgerätZoomInformationBildschirmmaskeProjektive EbeneAttributierte GrammatikDigitalisierungMAPHumanoider RoboterDatensichtgerätEinfach zusammenhängender RaumKonditionszahlDifferentialAuflösung <Mathematik>DefaultWidgetNetzbetriebssystemTablet PCResultanteTypentheorieEinsMinimumArithmetischer AusdruckKartesische KoordinatenDatenfeldCodeMaschinenschreibenTropfenZellularer AutomatPhysikalische TheorieRechter WinkelFigurierte ZahlLeistung <Physik>EinfügungsdämpfungWald <Graphentheorie>Metropolitan area networkSelbst organisierendes SystemNebenbedingungComputerspielComputeranimation
08:40
Projektive EbeneOffene MengeURLZweiEinfach zusammenhängender RaumProgrammierumgebungDatenbankArithmetisches MittelProdukt <Mathematik>Algorithmische ProgrammierspracheAttributierte GrammatikDatenfeldEchtzeitsystemMetropolitan area networkVersionsverwaltungBitMultiplikationsoperatorPlug inSpeicherabzugSynchronisierungKomplexes SystemZentralisatorCASE <Informatik>Gesetz <Physik>Office-PaketDemoszene <Programmierung>Wald <Graphentheorie>Message-PassingPhysikalische TheorieSichtenkonzeptFamilie <Mathematik>DatenverwaltungAutomatische HandlungsplanungPhysikalisches SystemFlächeninhaltFormation <Mathematik>Zellularer AutomatGrundraumRechenwerkMathematikVarietät <Mathematik>SystemaufrufMultiplikationDiagrammFlussdiagramm
12:22
Physikalische TheorieGebäude <Mathematik>MereologieProgrammbibliothekKartesische KoordinatenCodeComputeranimation
12:40
NebenbedingungBitInterface <Schaltung>MAPNebenbedingungRelativitätstheorieComputersicherheit
13:27
NebenbedingungNebenbedingungFehlermeldungFlächentheorieDienst <Informatik>Beobachtungsstudie
14:08
DigitalisierungDichte <Stochastik>MereologieElektronische PublikationHochdruckAttributierte GrammatikMAPProjektive EbeneDichte <Stochastik>DatenfeldTabelleMomentenproblemProgrammierungXMLUMLComputeranimation
15:29
ProgrammierparadigmaPunktMAPDigitalisierungGeradeFormale SpracheSpezifisches VolumenFamilie <Mathematik>ElementargeometrieMapping <Computergraphik>MittelwertRuhmasseVollständiger VerbandComputeranimation
16:40
ATMViewerHybridrechnerVersionsverwaltungBitRichtungEinfach zusammenhängender RaumKartesische KoordinatenDatenbankAbstandWinkelSchnittmengeATMFunktionalComputerunterstützte ÜbersetzungEinflussgrößeFormation <Mathematik>Lie-GruppeGebäude <Mathematik>Divergente ReiheComputeranimation
18:13
ProgrammfehlerDemo <Programm>Projektive EbeneMereologieSoftwareentwicklerBildverstehenWort <Informatik>Computeranimation
19:07
FlächeninhaltResultanteMereologieQuick-SortMobiles InternetMAPInformationQuellcodeMakrobefehlFeuchteleitungMapping <Computergraphik>Demo <Programm>Kartesische KoordinatenElektronische PublikationProjektive EbeneHumanoider RoboterMultiplikationsoperatorUMLComputeranimation
20:55
EDV-BeratungComputeranimationJSONXMLUML
Transkript: Englisch(automatisch erzeugt)
00:07
We are starting the new session about development, and the first presentation is from Marco Benazzocchi, because data is outside Q-Field, the future of QGIS on mobile devices.
00:21
Just remember, after the presentation, there will be a short break for coffee.
00:52
Talk to you about Q-Field. Who am I? I'm Marco Benazzocchi. I'm the co-founder of OpenJS.ch, co-chair of QGIS project, and the great-great-grandfather of Q-Field.
01:13
As I said, for a company called OpenJS.ch, it's a small company in Switzerland, we are fairly much super expert in QGIS, Q-Field, and all the things that go around it.
01:25
We do live and love open source, so if you need anything, just go and discuss. Now, to the more relevant part of the presentation. Why Q-Field? What is the whole idea behind Q-Field? Well, most of the time, unless you are digitizing raster imagery, your data is going to be outside.
01:48
Having the data outside, and being there with our laptop to try to digitize it, is not really what we consider a user-friendly way to do things. So that's why in 2012, I decided, well, it would be cool to have something running
02:05
on Android, and that's when I started taking QGIS and made it run on Android, and QGIS for Android was born, with the idea that eventually the whole user interface will be replaced, and that's what Q-Field is.
02:20
Basically, it's a nice way to see QGIS on your mobile device. Another reason is because QGIS has such an amazing ecosystem already, we have QGIS server, we have the desktop, we have web clients, but we do not have really something that
02:41
is actually made for data digitizing that integrates very well with QGIS. That's what Q-Field can do. What is it? It's a mobile-based data collection app that integrates well in your stack.
03:03
It has a super-minimalistic user interface made from ground up for touch devices. Whenever we are thinking about putting a new button in there, we are debating hard. Does that button have the right to be there? We are really harsh on those kinds of decisions.
03:24
We want to have as little buttons as possible, because when you're out in the field, it's not what you want. You don't want to be fiddling around with small controls or little buttons. Maybe you as GIS semi-people know how to deal with that, but Q-Field is actually meant
03:41
for people that are working out and they are just digitizing so that it should make their life easier. We want them to be as efficient as possible so that actually we don't get resistance from people using it on the field and just want it to stick on paper maps. What we want is that people want to use Q-Field on the field just because it makes
04:02
them much more efficient. As I mentioned before, behind Q-Field there is a full QGIS core running. So that means that all the cartographic power of QGIS is available in Q-Field.
04:21
How do we deal with it? Well, I can comfortably prepare all my work on the desktop. Q-Field bases on the QGIS project. So there is no configuration tool for Q-Field. All the configuration is done within QGIS. In fact, many times when we need something new in Q-Field and we are evaluating if
04:46
it might be useful for QGIS as well, we end up putting it directly in QGIS itself, if it makes sense. You do all the work on the desktop. So you prepare your project there and then you deploy it on the tablet by however means you want.
05:08
It could be just by copy and pasting the project from the tablet, from the computer to tablet. You could have some kind of synchronized folders with projects in there which gets automatically
05:20
synchronized over in something like Dropbox, same thing where Google Drive is not going to do interest, for instance, because you need something that makes your files physically available on the device. Then once the project is on the device, you can efficiently start working on your data.
05:41
I'm going to show you later on the interface. Very, very nice way to work out. What is it that we hide in Q-Field? What is in there? We have the full QGIS experience. So maps, renderings, all those kind of things, symbology, labeling, all that.
06:03
So the map canvas that you know from QGIS is going to be there. It's made for touch and it has a lot of powerful features. The QGIS forms, for example, if you've been customizing them already in QGIS, so you have
06:20
already dropdowns, you have already tabs with the driving drop form composer. So all that is supported. We don't support yet. All the widget types are supported in QGIS, but most of them, the most useful ones are there. We have conditional visibility, attribute constraint, default values.
06:44
You can take pictures, obviously. So all those kind of things that are related to the forms are there. And as I said before, they are configured in QGIS. It means that the work that you did once for the QGIS project basically can directly be reused for your Q-Field.
07:03
Digitizing and editing. We can digitize points, lines, polygons, z-coordinates. It supports snapping also as you set it up on QGIS. And we can use the internal or an external GPS sensor, which means you can take your cell phone and go out
07:22
and that's it that's going to work. Or you can take a tablet and some Bluetooth connected high resolution differential GPS and that's going to work. Because Q-Field just takes whichever GPS information Android is delivering and wherever those coordinates and information come from.
07:45
As long as the operating system is giving those to us. There is an attribute search tool in QVAN. So as you know it from QGIS 3.0 as well, down in the bottom left side.
08:04
There is the search bar, we have it up on the top right side. You can search for attributes. It will search any layers that have been marked as searchable layers and it will search in the display expression. So you can actually have your fields in your data set up the way you want
08:23
and then if you have say road, road number, city and postal code you can set up a display expression that combines all of this and the search will search in your combined expression. It will zoom to the result.
08:44
So what kind of workflows can I have? We have kind of four different workflows. The first one, very simple one, is kind of an explorer workflow where you just take your data on the tablet, go out and have a look at the data.
09:01
So you're out and you're checking your data without doing anything else than just looking at attributes. Here what happens is on the desktop you do all the work and then when you're out you move the data and the project over to the mobile and when you're out you're just browsing and looking at the data.
09:21
Then the next step to this is you go out in the field and you edit your data and once you're done you come back and you move your data back to your desktop. This kind of is a workflow for a one man show. So you manage your data, you put them on the device, go out on the device,
09:43
have your work, do whatever you need to do, come back, play back your data, just copy back the data and those data is always kind of the newest version of it. So imagine just moving a geo-package around.
10:00
Then a bit more of a complex system where you have a centralized maybe Postgres database the projects get put on the device but the device has connections to the database. So this obviously implies connectivity of the device.
10:21
So you can do this on your cell phone if you have 3G, 4G, 5G, whatever you have. And this will make that multiple people can have access at the same time to the database and have a centralized kind of experience. Yesterday in the workshop that I did, we did play around with this kind of things
10:44
and we had people digitize, we had about 20 people digitizing at the same time and I had Qfield open with a live refreshing layer on second and you basically just see on real time what people are doing. So it's a pretty powerful environment. You can be obviously behind the server, in there you can have one database
11:06
that is maybe the working database and then behind it you can have triggers that after 40 days of non-activity on a feature they can copy on a production database or after some quality assurance procedures they can move to a production database
11:20
and that's actually the database where your final data are. So whatever you build up behind this thing is up to you. So this is just a minimal way to do it. The fourth way of working is when you do have a centralized database
11:43
but you do know that you will be working in a location without connection. So non-connectivity means you cannot just have a connection to your Postgres database centralized. So what we have is a plugin called Qfield Sync and Qfield Sync will create you dumps of the data
12:06
and prepare for you a geo-package which you can then copy over to device and the device will then work there and then I can play back and I can sync back the data to the database.
12:23
Obviously we can build custom applications as well on top of it because many parts of the Qfield code have been taken back into QGIS as a library and out of that library we can obviously build custom applications as well.
12:41
Let's stop me talking and let's show you a bit of things. Map themes. So we support map themes. This is the interface you see. It's a lot of map and very little interface. Things appear when they are needed but they tend to be not around when they are not needed.
13:05
We see on the left side we have a legend that layers and we can change map themes. Constraints. Here we are trying to, we are digitizing things.
13:33
So here we are digitizing surfaces that have certain constraints set and you will see that as soon as I have the constraint going
13:43
and not fulfilling it, I'm not allowed to save. So up here I have an error message telling me something in orange so maybe you're not allowed to do that. There's going to be now one more appearing so I'm not allowed to put 2017 there.
14:02
It has to be at least 2018. These constraints, as I mentioned, they are created in QGIS and are available throughout the project. Digitizing with picture, something that is done very often on the field is that you're digitizing a feature
14:23
and once you're done with the geometrical part of it you get the attribute and you can set all the attributes and then you can just snap a picture and it gets added as an attribute.
14:41
The path of the picture gets added as an attribute to our attribute table and the file is put in a folder at the same level as the project. At the moment, currently we can only support one picture per field so there is no one to end yet. That's something we're still working on.
15:01
We support printing of PDFs from print composers so when you say print, you can choose whichever print composer you have in your project and once you're done, click OK and you get PDF. From then on, what you do with the PDF is completely up to you.
15:30
Editing of geometries, that was one of the trickiest things to get properly. We don't digitize by clicking on the device
15:43
so you don't push with your finger to say where you want your point to be. We move the map and then say here we want the point. That's so that we can be precise in digitizing. Just digitizing by saying on a point click, here we want the point. It's not going to work if you want it to be precise and that's why we have this paradigm everywhere
16:03
where we say, well, the cross here in the middle of the map it's always where things get digitized and you move the map to wherever you want things to happen. Here, when digitizing a line or editing the geometry, we can actually just move around the nodes, add new nodes and everything.
16:30
For the polygons, it's the very same thing. When we're digitizing new polygons, we can remove nodes if we are unhappy with them and add new nodes if we want.
16:42
Roadmap, well, we've come a long way. As you can see, after the search, we have defined a kind of set of functionality that we want to have before we release version 1.0. You might have seen in the last month and a half
17:03
we've been releasing release candidate 1, 2 and 3 and as of today, maybe tomorrow, depending on how much work we manage to get in, we're going to release RC4, which hopefully is the last RC and which hopefully makes us be able to release version 1 very first.
17:25
After that, we would like to work on a hybrid mode which is basically saying, well, I want live connection but if there is no connectivity anymore, I want to cache the thing locally and as soon as I get connectivity again,
17:40
I want to be able to push that up to the database and for that, that's something that we will need to look into in detail and get some sponsoring for that. Also, getting data out of external sensor, distance measurements, angle and so on, all those kind of things could be very interesting.
18:02
A bit more of digitizing in the CAD direction and then building up custom applications. Please do help us to support the development of QFields.
18:21
There are so many ways you can help. Bug fixing, bug reporting, nice bug reports, detailed with demo projects that are small and handy and that they can be used to reproduce your problems. Obviously, you can support economically by helping us sponsor some new features or one of the probably most important and easiest ways to help us as well
18:45
is to help us write the documentation. We do a lot of work on the development part. We know that our documentation is not the best yet but there is a very easy place to help because as a user, you actually write documentation
19:01
in a way that is more useful for users than when developers write documentation. So please do help us on qfield.org. You'll find all the information and questions. We are here now. Thank you.
19:33
When I try to demo into some people, say hey, check it out, there's a big kind of barrier. They need to have a desktop project, they need to publish the device
19:42
and then they can see how to do those. I think it will be really useful for the users to have some demo project and then they can immediately start the demo. If you want to get a similar thing, there's a similar thing. So otherwise, it's really good. Thank you. We've been thinking about doing that because you cannot just show it off right at the beginning.
20:03
Thank you. Other questions? Have you thought of using other map sources that might already exist on a mobile device? For example, macro maps downloaded by other applications which might be able to be used on qfield and Stackdriver also?
20:21
Not really, no. We haven't gone that way yet because dealing with files on Android is always a good time. And we do really want to keep all the work on the desktop. That's kind of the base thing that we say is work is on the desktop
20:41
just because you're feeling around a lot. If not, have a good coffee.