<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi Bernd,</p>
<p>The best intro to QGIS reports (that I know) can be found at Nyall Dawsons website: <a href="https://north-road.com/2018/01/23/exploring-reports-in-qgis-3-0-the-ultimate-guide/">https://north-road.com/2018/01/23/exploring-reports-in-qgis-3-0-the-ultimate-guide/</a></p>
<p>Nyall is also the developer who worked on the reports.</p>
<p>The reports in QGIS did not get a lot of attention yet - Tim Sutton presented reports and his reults at FOSS4G in Bucharest - and like you, he ran into a lot of limitations and hidden things you need to do with expressions and such. There is definitely room for improvements.</p>
<p>Collecting feature requests at Github is great, but it would be very good to collect (reference) all of these in a QGIS QEP and then we could find a dev (most likely Nyall) and come up with funding. I am pretty sure that Tim Sutton would join your effort - and myself as well ;-) If this effort is backed by a convincing collection of useful improvements, I am confident that we can find organizations funding it.</p>
<p>We could also schedule a meeting with Tim, Nyall and yourself - and other interested users to discuss further improvements. But collecting missing things upfront to such a meeting would make the discussion much more productive.</p>
<p>Hope this helps,</p>
<p>Andreas</p>
<p id="reply-intro">On 2020-09-15 11:17, Bernd Vogelgesang wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="white-space: nowrap;">Hi Andreas,</span><br /><br /><span style="white-space: nowrap;">hope I did not sound too negative. For sure I would like to help in some</span><br /><span style="white-space: nowrap;">way. I give money in nearly every crowdfunding project, though I even</span><br /><span style="white-space: nowrap;">don't need most functionalities there.</span><br /><span style="white-space: nowrap;">Around the report function, there is quite a sounding silence in the</span><br /><span style="white-space: nowrap;">lists and the web, so I assume that few people use it, or feel too</span><br /><span style="white-space: nowrap;">stupid to ask cause they don't get it to work properly.</span><br /><br /><span style="white-space: nowrap;">What I already tried, was to collect issues on github for the Report </span><br /><span style="white-space: nowrap;">But already there the problems begin: There is not a label for it (only</span><br /><span style="white-space: nowrap;">a general "Print Layout") and report is a very common word)</span><br /><span style="white-space: nowrap;">This may be intended as the reporting seems to be the younger brother of</span><br /><span style="white-space: nowrap;">the Atlas, but makes it not easier ;)</span><br /><br /><span style="white-space: nowrap;">Before I would be able to create a QEP, I would need someone to explain</span><br /><span style="white-space: nowrap;">me the parts in Report that I maybe simply do not understand.</span><br /><br /><span style="white-space: nowrap;">So, count me in (at least a bit ;) )</span><br /><br />Bernd<br /><br /><br /><span style="white-space: nowrap;">On 15.09.20 08:30, Andreas Neumann wrote:</span>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><span style="white-space: nowrap;">Hi Bernd,</span><br /><span style="white-space: nowrap;">The report functionality definitely needs some love. There is a great</span><br /><span style="white-space: nowrap;">base now, but it needs to improve.</span><br /><span style="white-space: nowrap;">Would you volunteer to collect missing things regarding reports in a QEP</span><br /><span style="white-space: nowrap;">and then help organize a crowd-funding? Even if you can't fund this</span><br /><span style="white-space: nowrap;">yourself, it would help a lot to come up with a sound proposal /</span><br /><span style="white-space: nowrap;">specification, that some interested developer can submit a quote and we</span><br /><span style="white-space: nowrap;">can look around for funders.</span><br /><span style="white-space: nowrap;">There are quite a few successful examples in the past where someone who</span><br /><span style="white-space: nowrap;">missed a functionality in QGIS but couln't finance it came up with a</span><br /><span style="white-space: nowrap;">sound proposal and then we could find a developer and funders based on</span><br /><span style="white-space: nowrap;">that initiative.</span><br /><span style="white-space: nowrap;">Or you could organize this as a joint effort - e.g. through the german</span><br /><span style="white-space: nowrap;">QGIS user group.</span><br /><span style="white-space: nowrap;">Greetings,</span><br />Andreas<br /><span style="white-space: nowrap;">On 2020-09-14 23:09, Bernd Vogelgesang wrote:</span><br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><span style="white-space: nowrap;">On 14.09.20 22:30, Håvard Tveite wrote:</span>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><span style="white-space: nowrap;">Including photos / images in reports is covered by the documentation.</span><br /><br /><span style="white-space: nowrap;">See:</span><br /><span style="white-space: nowrap;"><a href="https://docs.qgis.org/testing/en/docs/user_manual/print_composer/create_reports.html#including-pictures-in-a-report" target="_blank" rel="noopener noreferrer">https://docs.qgis.org/testing/en/docs/user_manual/print_composer/create_reports.html#including-pictures-in-a-report</a></span><br /><br /><br /><span style="white-space: nowrap;">It worked for me.</span><br /><span style="white-space: nowrap;">It should now also be possible to use images stored in a BLOB field.</span><br /><br /><span style="white-space: nowrap;">Håvard</span></blockquote>
<br /><span style="white-space: nowrap;">Thanx for answering. Indeed there is something about adding photos, but</span><br /><span style="white-space: nowrap;">actually this version of the doc is somehow not showing up in google</span><br /><span style="white-space: nowrap;">searches:</span><br /><br /><span style="white-space: nowrap;">Furthermore, I did not have the problem of having to construct a path to</span><br /><span style="white-space: nowrap;">the image. The full path is already in the data (from the nice toolbox</span><br /><span style="white-space: nowrap;">function for geotagged images). The report just did't eat the path.</span><br /><span style="white-space: nowrap;">After dozend and dozends of attemps, QGIS somehow seemed to give up on</span><br /><span style="white-space: nowrap;">refusing them, and now miraculously is accepting the path.</span><br /><br /><span style="white-space: nowrap;">The problem, that all images where repeatedly showing in all section got</span><br /><span style="white-space: nowrap;">solved too. In the level up for the subplots, I had to use the field</span><br /><span style="white-space: nowrap;">unique for each subplot and not that for the plot, as I wrongly assumed.</span><br /><span style="white-space: nowrap;">Having it set wrongly didn't influence the correct print of the plots</span><br /><span style="white-space: nowrap;">and then their subplots, but had influence on the follwing photos. Pfuh,</span><br /><span style="white-space: nowrap;">the logic behind, how the report "knows "what to print in lower levels</span><br /><span style="white-space: nowrap;">is actually not really obvious, It seems to figure this out on its own.</span><br /><br /><span style="white-space: nowrap;">So, seems I get it working.</span><br /><br /><span style="white-space: nowrap;">Major flaws:</span><br /><span style="white-space: nowrap;">There is only the possibility to select an existing field for a layer in</span><br /><span style="white-space: nowrap;">report groups. So the data has to be prepared for each and every</span><br /><span style="white-space: nowrap;">possible usage beforehand. Having the possibilty to use expressions here</span><br /><span style="white-space: nowrap;">would be phantastic. So now, when you find out that you had not the</span><br /><span style="white-space: nowrap;">right variables for your job in the data, you have to stop working on</span><br /><span style="white-space: nowrap;">the report and fumble the stuff into the attributes. I worked around</span><br /><span style="white-space: nowrap;">this problem by setting up a nice model to prepare my data, but not</span><br /><span style="white-space: nowrap;">everyone has the knowledge to do so.</span><br /><br /><span style="white-space: nowrap;">Found no way to add sections within the "tree" or to move anything. Once</span><br /><span style="white-space: nowrap;">you laid out a design and forgot a title page or mid-sections, you seem</span><br /><span style="white-space: nowrap;">to have to restart from scratch. No way to manipulate it later.</span><br /><br /><span style="white-space: nowrap;">Found no way so far to add page numbers.</span><br /><br /><span style="white-space: nowrap;">All in all. Spent 2 days now on this 30 page report and I hope I will</span><br /><span style="white-space: nowrap;">remember next time how to glue things together.</span><br /><span style="white-space: nowrap;">This could be a really powerful tool for lazy people having to do boring</span><br /><span style="white-space: nowrap;">reports frequently. So far, no time was gained, and I had to use extra</span><br /><span style="white-space: nowrap;">doses of alcohol not to give up.;)</span><br /><span style="white-space: nowrap;">Hopefully developers will give it a little more love some day to make it</span><br /><span style="white-space: nowrap;">a bit smoother, then it will really rock!</span><br /><br /><span style="white-space: nowrap;">On 14.09.2020 18:20, Bernd Vogelgesang wrote: Hi there,</span><br /><br /><span style="white-space: nowrap;">I'm really eager to finally figure out how to create a photo</span><br /><span style="white-space: nowrap;">documentation with QGIS.</span><br /><br /><span style="white-space: nowrap;">Everything needed is prepared and in place. I have overview coverages of</span><br /><span style="white-space: nowrap;">plots with sub-plot over an aerial image. The maps are nicely produced</span><br /><span style="white-space: nowrap;">to a report as groups. On each overview, the belonging sub-plots follow</span><br /><span style="white-space: nowrap;">as individual maps.</span><br /><br /><span style="white-space: nowrap;">Now I would like to show pictures taken on the sub-plots.</span><br /><br /><span style="white-space: nowrap;">First issue: I add a new group photo-points and as field I select the</span><br /><span style="white-space: nowrap;">referencing field for the sub-plot. Edit body, add picture frame. When</span><br /><span style="white-space: nowrap;">setting the full file path for the images (stored as field "photo" in</span><br /><span style="white-space: nowrap;">the point file, generated with "Import geotagged photos") there is only</span><br /><span style="white-space: nowrap;">a red cross shown, and the selection in the dialog jumps from raster to</span><br /><span style="white-space: nowrap;">svg. On export as pdf, there is a warning "Picture source is missing or</span><br /><span style="white-space: nowrap;">corrupt".</span><br /><br /><span style="white-space: nowrap;">I redid this several times, to no avail, but once in a sudden, a preview</span><br /><span style="white-space: nowrap;">image was shown, though I did not change the slightest thing in the</span><br /><span style="white-space: nowrap;">settings. I swear!</span><br /><br /><span style="white-space: nowrap;">Second issue: Now that it finally accepted the path, exporting the</span><br /><span style="white-space: nowrap;">report now produced a page for each picture under each sub-plot, instead</span><br /><span style="white-space: nowrap;">of filtering those which actually fit there (and how it does with the</span><br /><span style="white-space: nowrap;">sub-plots within the plots!)</span><br /><br /><span style="white-space: nowrap;">Has anyone an idea what might be wrong here. Documentation on this</span><br /><span style="white-space: nowrap;">matter or examples are unfortunatly nonexistent.</span><br /><br /><span style="white-space: nowrap;">Linux Mint, 3.14.1</span><br /><br /><span style="white-space: nowrap;">Cheers,</span><br /><br />Bernd<br /><br />_______________________________________________<br /><span style="white-space: nowrap;">Qgis-user mailing list</span><br /><span style="white-space: nowrap;"><a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a></span><br /><span style="white-space: nowrap;">List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></span><br /><span style="white-space: nowrap;">Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></span></blockquote>
_______________________________________________<br /><span style="white-space: nowrap;">Qgis-user mailing list</span><br /><span style="white-space: nowrap;"><a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a></span><br /><span style="white-space: nowrap;">List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></span><br /><span style="white-space: nowrap;">Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></span></blockquote>
</div>
</blockquote>
<p><br /></p>
</body></html>