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

Advanced QGIS forms into the web with Lizmap

00:00

Formal Metadata

Title
Advanced QGIS forms into the web with Lizmap
Title of Series
Number of Parts
351
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2022

Content Metadata

Subject Area
Genre
Abstract
You would like many people from your team or crowdsourcing to fill data in your geodatabase. One way to do that is to make appealing, easy to use and well-constructed forms avoiding wrong inputs. Also, you do not want people to give up filling because the form is too long while in the same time you could automatically fill some entries based on others. With QGIS Desktop, it is possible to make great maps but also advanced forms by using expressions to control field visibility, default values, proposed values, constraints and more. It is very powerful but now how to share those forms to anybody whatever their device or operating system? Could it be possible to share a link for people to open and fill those forms in their web browser? Let’s see how you can get most of these features for your forms in web browsers thanks to QGIS Server and Lizmap.
Keywords
CAN busWeb 2.0Multiplication signConfiguration spaceLevel (video gaming)
Web pageDrop (liquid)Drag (physics)Online helpField (computer science)InformationGUI widgetGroup actionFinitary relationElectronic visual displayRepresentation (politics)AliasingDigital photographyLoginData typeForm (programming)MathematicsOrder (biology)CuboidGroup actionField (computer science)Self-organizationLevel (video gaming)Drop (liquid)Drag (physics)AliasingProcess (computing)Computer animation
Online helpDrag (physics)Drop (liquid)Finitary relationGUI widgetDigital photographyRegulärer Ausdruck <Textverarbeitung>Control theoryLoginInformationLocal GroupControl theorySoftware testingExpressionCuboidResultantComputer animation
Annulus (mathematics)DigitizingWell-formed formulaInformationDigital filterAliasingDigital photographyData storage deviceElectronic visual displayGUI widgetAbsolute valueAsynchronous Transfer ModeDefault (computer science)Extension (kinesiology)EstimationDrop (liquid)Drag (physics)Field (computer science)Finitary relationGroup actionLoginLine (geometry)Computer-generated imageryElectronic visual displaySelectivity (electronic)Extension (kinesiology)GUI widgetLevel (video gaming)Type theoryDigital photographyMedical imagingField (computer science)SoftwareComputer fileXMLProgram flowchartComputer animation
InformationConstraint (mathematics)Default (computer science)GUI widgetData typeRegulärer Ausdruck <Textverarbeitung>Uniqueness quantificationLoginVariable (mathematics)Electronic visual displayAliasingFinitary relationOrder (biology)NumberDrop (liquid)Drag (physics)Group actionDigital photographyLoginDrag (physics)Electronic mailing listGroup actionMereologyVariable (mathematics)Field (computer science)Form (programming)ExpressionDrop (liquid)Theory of relativityLevel (video gaming)Source codeXMLComputer animation
InformationElectronic mailing listRow (database)Sheaf (mathematics)Order (biology)CASE <Informatik>View (database)Query languageSelectivity (electronic)XMLProgram flowchart
Personal digital assistantOrder (biology)LoginMiniDiscDemo (music)NumberDigital filterOnline helpGUI widgetElectronic visual displayDrag (physics)Drop (liquid)InformationFinitary relationDigital photographyAliasingData typeAttribute grammarForm (programming)Row (database)TableauExpressionDemo (music)Electronic mailing listSpeciesAttribute grammarVariable (mathematics)Computer animation
Transcript: English(auto-generated)
Hi, I'm Nicolas from Trace Company and I'm going to show you some tips to make advanced forms in QGIS which will be easy for users to be filled. I also will show you those forms in the web thanks to Lizmap. We have no more configuration most of the time. This way you get more participation and less mistake in your data.
First we have the QGIS drag and drop designer. We can decide which fields needs to be filled, change the fields order, create tabs and group boxes. Let's say we create a form for a processing campaign but also for logged in users in Lizmap
like people in our organization. This form may have many fields but many of them are not monetary so we don't want to show them all because when form seems too long to fill some users might give up and close it.
To avoid that here we create a boolean field called as details with add details as an alias to have a more understandable title and define it as a check box. We also create a details tab configured with a control visibility by expression to only
display it when the as details check box is checked. Here is the result. As you can see... It's better, thank you.
As you can see details tab is only visible when add details is checked. Now we want people to upload photos so we create fields defined with an attachment widget type and we have a filter to only display GPMG and PNG files.
You can see in Lizmap only files with defined extensions are displayed when selecting them. After file selection you can also rotate or crop images. It is way more convenient than to have to install a software for that.
I missed that, sorry. Now when contributors are logged in Lizmap we can use a user login or user groups in forms expression thanks to expression variables.
Here we create an invisible login field. It is invisible. We don't put it with the drag and drop designer on the middle part. And it will be filled automatically with the user login when the form will be saved.
The value relation is very convenient to display a list of value from another layer. But sometimes the list can be very long. In this example we display scientific names for amphibians and reptiles in France. So to this section we could, for example, suggest the last previous record on top of
the list for logged in users. For that we create a layer from view with this SQL query. It is a union order with the last previous record for logged in users. It could be also the two or three or more records but in this case it is just the
last and the whole list of animals. In red the attribute table shows us the last record for Alice, Bob and demo users. The rest is the whole list of animals.
Okay, so to only get the previous record for the logged in users in Lizmap we use this filter expression which uses again the Lizmap user expression variable. And as you can see now when a logged in user saves a form is then added on top of
the scientific name list the last species suggested. We come now, save. When the form is open again, a new form, you have here the last previous record.
Finished.