Ok, I overlooked a few features, thanks Nathan for pointing out the refresh rate!
I rely on web based tile or WMS backgrounds (OpenStreetMap, NRCan Geogratis, etc.). CityPhi fills in the background as the tiles show up. QGIS seems to need to draw the entire background in it's head, then displays it all at once, before it can use the cool multithreaded features on the vectors. Or is there another checkbox for "draw my background as it arrives from the tile service, but don't wait around for it to respond"? -- John Abraham > On Jul 10, 2017, at 6:00 PM, Nathan Woodrow <[email protected]> wrote: > > Hey John, > > QGIS has had multithreaded rendering since 2.0 which allows the map to be > rendered as you pan around so you don't have to wait. You can also set the > refresh rate in order to draw more features so you get feedback quicker. > > Regards, > Nathan > > On Tue, Jul 11, 2017 at 2:32 AM, John Abraham <[email protected] > <mailto:[email protected]>> wrote: > Is incremental drawing possible, especially for web features in the > background? > > I've been playing with some GPU based visualizers lately (in particular > CityPhi from INRO https://www.inrosoftware.com/en/products/cityphi/ > <https://www.inrosoftware.com/en/products/cityphi/> ) and switching back to > QGIS and waiting for the maps to redraw on every single pan or zoom is > extremely painful. > > GPU-drawn 3D visualizations at 30 frames per second is probably not a > realistic short-term goal for QGIS. But, what about allowing the graphics > system to draw the current status of the internal render, before it's > complete? For example, if WMS tiles are being downloaded, can the background > map be updated as data comes in, while the foreground features stay on top? > Can layers be shown as they are drawn, instead of popping up the entire image > after the final layer has been drawn? > > >> On Jul 10, 2017, at 9:44 AM, [email protected] >> <mailto:[email protected]> wrote: >> >> Send QGIS-Developer mailing list submissions to >> [email protected] <mailto:[email protected]> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.osgeo.org/mailman/listinfo/qgis-developer >> <https://lists.osgeo.org/mailman/listinfo/qgis-developer> >> or, via email, send a message with subject or body 'help' to >> [email protected] >> <mailto:[email protected]> >> >> You can reach the person managing the list at >> [email protected] >> <mailto:[email protected]> >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of QGIS-Developer digest..." >> >> >> Today's Topics: >> >> 1. Re: QGIS/OGR: FeatureIds reassigned on write to data >> provider? (Even Rouault) >> 2. Re: Value entry using comma as decimal separator? >> (Bernhard Ströbl) >> 3. Plugin [1246] go2mapillary approval notification. >> ([email protected] <mailto:[email protected]>) >> 4. Re: QGIS/OGR: FeatureIds reassigned on write to data >> provider? (Régis Haubourg) >> 5. Re: QGIS/OGR: FeatureIds reassigned on write to data >> provider? (Even Rouault) >> 6. qgis-bin.exe - Entry Point Not Found (Patrice) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 10 Jul 2017 13:58:57 +0200 >> From: Even Rouault <[email protected] >> <mailto:[email protected]>> >> To: [email protected] <mailto:[email protected]> >> Subject: Re: [QGIS-Developer] QGIS/OGR: FeatureIds reassigned on write >> to data provider? >> Message-ID: <2643131.9G3uCidT8S@even-i700> >> Content-Type: text/plain; charset="utf-8" >> >>> I did some playing around and came up with some FeatureId mapping code >>> which is pretty space efficient (basically requiring just >>> 3*nDeletedFeatures entries), see below. >>> >>> The code however assumes that the gaps in the fid-sequence are filled by >>> decreasing the fids after the gap, which may be pretty specific to the >>> OGR/Shapefile behaviour. >> >> This should clearly be restricted to Shapefiles. Other drivers don't have >> this compaction logic >> and will let happily holes in the feature ids. >> >>> Hence in my view such code should really belong >>> into the OGR provider (or perhaps even ogr itself) and not in the >>> plugin. Thoughts? >> >> Regarding putting that in OGR itself, there's no such API for that right >> now, and I'm not >> completely clear of the value to add one (specific use case, for a single >> driver) >> >> Perhaps the QGIS OGR provider would be a better place for now. >> >> Even >> >> -- >> Spatialys - Geospatial professional services >> http://www.spatialys.com <http://www.spatialys.com/> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/138fa822/attachment-0001.html >> >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/138fa822/attachment-0001.html>> >> >> ------------------------------ >> >> Message: 2 >> Date: Mon, 10 Jul 2017 14:15:46 +0200 >> From: Bernhard Ströbl <[email protected] >> <mailto:[email protected]>> >> To: qgis-developer <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [QGIS-Developer] Value entry using comma as decimal >> separator? >> Message-ID: <[email protected] >> <mailto:[email protected]>> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Hi, >> just my two cents: My users are working in a German administration and >> they depend on QGIS having a German UI. They will be puzzled if they are >> supposed to use a point instead of the regular komma as decimal >> separator. On the other hand they won't expect "5.5" to be a regular >> entry into a decimal field either. >> >> Bernhard >> >> Am 08.07.2017 um 09:58 schrieb Richard Duivenvoorde: >>> On 08-07-17 01:11, Nyall Dawson wrote: >>> >>>> It's a trivial change to make to get the spin boxes to accept the >>>> local decimal separator, but this would prevent users entering "5.5" >>>> in those locales. >>>> >>>> Can someone from one of these affected regions let me know what the >>>> correct behavior should be? I don't want to make the change if it >>>> breaks entry of 5.5 and that's the standard used in those locales. >>> >>> My personal view: >>> >>> In The Netherlands we also use comma as a decimal separator (don't most >>> european countries do?), and though I never use the Dutch locale myself, >>> I know ALL governmental organisations I've been run the Dutch >>> QGIS/localse just because Windows there is in Dutch (and set the Dutch >>> locale). >>> >>> I also know in the Spreadsheet world this gives A LOT of trouble because >>> most average users are not even aware what 'locale' they are using... So >>> people sending a us-locale spreadsheet to a dutch-locale user is often >>> in trouble.... >>> >>> This makes for example so that in modern Banking web applications they >>> check and you can use both , and . as decimal separator (probably there >>> is some heuristic in which they check: >>> - if there is only one type of separator >>> - if there is one, and it is just 2 position from the end >>> - it is used as decimal separator >>> etc etc >>> But... that is easier when you are only doing currency numbers... >>> >>> I would not try to fight this locale war, or try to be smarter then >>> Qt/Windows: >>> IF people use a 'comma'-locale, they should use comma. >>> IF they do not like that: use us-locale >>> >>> It is the same problem with the character encoding in shapefiles. People >>> are not aware of what they do, but 'we' as part of the Qt or Windows >>> should not try to be smarter then that world we are part of. >>> >>> Untill the rest of the world come to their senses and start using the >>> comma as separator, use 24hr clocks (well preferably 100...), meters, >>> kilograms etc etc... >>> >>> Regards, >>> >>> Richard Duivenvoorde >>> _______________________________________________ >>> QGIS-Developer mailing list >>> [email protected] <mailto:[email protected]> >>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >>> <https://lists.osgeo.org/mailman/listinfo/qgis-developer> >>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >>> <https://lists.osgeo.org/mailman/listinfo/qgis-developer> >>> >> >> >> >> __________ Information from ESET Mail Security, version of virus signature >> database 15722 (20170710) __________ >> >> The message was checked by ESET Mail Security. >> http://www.eset.com <http://www.eset.com/> >> >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Mon, 10 Jul 2017 12:41:22 -0000 >> From: [email protected] <mailto:[email protected]> >> To: [email protected] <mailto:[email protected]>, >> [email protected] <mailto:[email protected]> >> Subject: [QGIS-Developer] Plugin [1246] go2mapillary approval >> notification. >> Message-ID: <20170710124122.20479.19151@320558c5528b> >> Content-Type: text/plain; charset="utf-8" >> >> >> Plugin go2mapillary approval by pcav. >> The plugin version "[1246] go2mapillary 1.2" is now approved >> Link: http://plugins.qgis.org/plugins/go2mapillary/ >> <http://plugins.qgis.org/plugins/go2mapillary/> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Mon, 10 Jul 2017 15:01:56 +0200 >> From: Régis Haubourg <[email protected] >> <mailto:[email protected]>> >> To: Even Rouault <[email protected] >> <mailto:[email protected]>> >> Cc: QGIS Developers List <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [QGIS-Developer] QGIS/OGR: FeatureIds reassigned on write >> to data provider? >> Message-ID: >> <cabgoyceocdzqk7lg+u+azsfxmpuggxvgmsq0nnjsp9lkqxu...@mail.gmail.com >> <mailto:cabgoyceocdzqk7lg%2bu%[email protected]>> >> Content-Type: text/plain; charset="utf-8" >> >> Hi, >> >> This should clearly be restricted to Shapefiles. Other drivers don't have >>> this compaction logic and will let happily holes in the feature ids. >> >> >> What about Mapinfo TAB, which relies on DBF like shapefiles, and dbf files? >> Just asking, I didn't dig into that in depth. >> Régis >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/4376189d/attachment-0001.html >> >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/4376189d/attachment-0001.html>> >> >> ------------------------------ >> >> Message: 5 >> Date: Mon, 10 Jul 2017 15:12:47 +0200 >> From: Even Rouault <[email protected] >> <mailto:[email protected]>> >> To: Régis Haubourg <[email protected] >> <mailto:[email protected]>> >> Cc: QGIS Developers List <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [QGIS-Developer] QGIS/OGR: FeatureIds reassigned on write >> to data provider? >> Message-ID: <1738591.dH2YPQ2QbH@even-i700> >> Content-Type: text/plain; charset="iso-8859-1" >> >> On lundi 10 juillet 2017 15:01:56 CEST Régis Haubourg wrote: >>> Hi, >>> >>> This should clearly be restricted to Shapefiles. Other drivers don't have >>> >>>> this compaction logic and will let happily holes in the feature ids. >>> >>> What about Mapinfo TAB, which relies on DBF like shapefiles, and dbf files ? >> >> Deleted records are flagged as such in the .dat/.dbf files (with '*' >> character , which is also >> what the Shapefile driver use for non-compacted deleted DBF records) and in >> the .map file. >> There's no compaction logic. >> >> I don't remember of having heard about compatibility issues with MapInfo >> regarding this >> (but my memories can be wrong :-)), so I assume MapInfo does the same >> >> Even >> >> -- >> Spatialys - Geospatial professional services >> http://www.spatialys.com <http://www.spatialys.com/> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/20fe6f78/attachment-0001.html >> >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/20fe6f78/attachment-0001.html>> >> >> ------------------------------ >> >> Message: 6 >> Date: Mon, 10 Jul 2017 11:44:16 -0400 >> From: Patrice <[email protected] >> <mailto:[email protected]>> >> To: [email protected] <mailto:[email protected]> >> Subject: [QGIS-Developer] qgis-bin.exe - Entry Point Not Found >> Message-ID: <[email protected] >> <mailto:[email protected]>> >> Content-Type: text/plain; charset="utf-8"; Format="flowed" >> >> I just installed QGIS 2.18.9 on Windows 10 64 bits with the network >> install (64 bits) and I got this error (attached picture). >> >> >> >> >> >> >> >> This was the version I had before formatting my computer and I am still >> using the same OS version as before. >> >> I browsed to the folder and the DLL is indeed there. I have never seen >> that error before. >> >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/2880d8ab/attachment.html >> >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/2880d8ab/attachment.html>> >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: mdjkeejagnadklmj.png >> Type: image/png >> Size: 8003 bytes >> Desc: not available >> URL: >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/2880d8ab/attachment.png >> >> <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20170710/2880d8ab/attachment.png>> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> QGIS-Developer mailing list >> [email protected] <mailto:[email protected]> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> <https://lists.osgeo.org/mailman/listinfo/qgis-developer> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> <https://lists.osgeo.org/mailman/listinfo/qgis-developer> >> >> ------------------------------ >> >> End of QGIS-Developer Digest, Vol 141, Issue 27 >> *********************************************** > > > _______________________________________________ > QGIS-Developer mailing list > [email protected] <mailto:[email protected]> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> >
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
