Re: [Qgis-developer] Is QGIS supports dynamic display?
On 2014/08/11 04:11, ?? ? wrote: Dear all, I'm a new developer of QGIS using C++. I am doing a project which needs dynamically displaying maps/layers(just like GPS,layers automatically refreshing with the changing of object's position).I kown ARCGIS has the technique called dynamic diasplay(or something like that),which supports the capacity to do such things. Is QGIS has this ability? Any advices would be appreciated! Regards Bob Hi Bob, QGIS can definitely do this already. I used this feature in November last year - but make sure you use the latest versions of QGIS of all the plugins for field editing because at that stage some of the (digitising, I think) plugins caused serious loops when refreshing the screen or adding a feature, so not great if you are dynamically panning. I used a Garmin 60CSX, but any gps that can output an NMEA stream should work. You also need the free versions of Franson GPSGate from http://gpsgate.com/ On a practical note, I found dynamic panning not very useful for my purpose. When we drove passed a POI, we couldn't easily pause the panning in order to drop a points and add the attributes needed. We found the dynamic tracking (digitising) of the incoming GPS track very useful, and we manually panned the display as needed, whilst in motion. HTH, Zoltan -- === Zoltan Szecsei PrGISc [PGP0031] Geograph (Pty) Ltd. GIS and Photogrammetric Services P.O. Box 7, Muizenberg 7950, South Africa. Mobile: +27-83-6004028 Fax:+27-86-6115323 www.geograph.co.za === ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] After upgrade all fields are editable in QGIS project file
Hi Matthias, Hi Markus, Are you able to switch them back to non-editable? Somebody reported issues that he is not able to turn editing off [1]. Turning the editing off is possible on fields. So this issue I can not confirm. If you open your old files with the current development version, does the same happen? IIRC jef made some changes that could have fixed this. In that case, QGIS is upgrading the project to the Chugiak version and the problem I specified in the previous mail occurs. kind regards Markus ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Is QGIS supports dynamic display?
Hi Zoltan, Thanks a lot for your reply!The version i'm using is QGIS 2.4.0. I want to develop a desktop application using QGIS API, by C++ as i said. It is not GPS, but the way it is displayed like GPS-dynamic displaying by the changing data. So i built QGIS using source code according to INSTALL. At the time of Cmake, I unchecked the Python related plugins(such as WITH_BINDINGS,WITH_STAGED_PLUGINS), hope this does not affact the function you mentioned. Do you know which function or class is the one i'm looking for? I developed a simple demo that has these features: add layer, zoom in/out, pan. When i added a vector layer(.shp), i zoom in or zoom out, the refresh is not smooth or continuous. Are there any places i did not do right? Looking forward to your reply. RegardsBob Date: Mon, 11 Aug 2014 08:15:07 +0200 From: zolt...@geograph.co.za To: qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Is QGIS supports dynamic display? On 2014/08/11 04:11, 腾飞 牛 wrote: Dear all, I'm a new developer of QGIS using C++. I am doing a project which needs dynamically displaying maps/layers(just like GPS,layers automatically refreshing with the changing of object's position).I kown ARCGIS has the technique called dynamic diasplay(or something like that),which supports the capacity to do such things. Is QGIS has this ability? Any advices would be appreciated! Regards Bob Hi Bob, QGIS can definitely do this already. I used this feature in November last year - but make sure you use the latest versions of QGIS of all the plugins for field editing because at that stage some of the (digitising, I think) plugins caused serious loops when refreshing the screen or adding a feature, so not great if you are dynamically panning. I used a Garmin 60CSX, but any gps that can output an NMEA stream should work. You also need the free versions of Franson GPSGate from http://gpsgate.com/ On a practical note, I found dynamic panning not very useful for my purpose. When we drove passed a POI, we couldn't easily pause the panning in order to drop a points and add the attributes needed. We found the dynamic tracking (digitising) of the incoming GPS track very useful, and we manually panned the display as needed, whilst in motion. HTH, Zoltan -- === Zoltan Szecsei PrGISc [PGP0031] Geograph (Pty) Ltd. GIS and Photogrammetric Services P.O. Box 7, Muizenberg 7950, South Africa. Mobile: +27-83-6004028 Fax:+27-86-6115323 www.geograph.co.za === ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Processing i18n support
Hi Alexandre, 2014-08-10 13:46 GMT+03:00 Alexandre Neto senhor.n...@gmail.com: Correct me if I'm wrong, but that sounds like a repetitive simple task. Maybe I could help you with that. Well, relatively simple. In some files all you need is to wrap all visible strings in self.tr() call. But for other classes additional coding is required. Of course help and patches are welcome. Is it done in python or C++? Processing written in Python. -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] pyresample - Geospatial image resampling in Python - Google Project Hosting
Here is ticket for future reference https://hub.qgis.org/issues/11035 2014-08-03 10:34 GMT+03:00 Paolo Cavallini cavall...@faunalia.it: https://code.google.com/p/pyresample/ Possibly an useful addition to processing toolbox. All the best. -- http://faunalia.eu/ Sent from mobile, sorry for being short ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Bug #10974 QGIS WFS Server provides too much precision
2014-08-09 17:50 GMT+02:00 René-Luc Dhont rldh...@gmail.com: Hi, I have added a commit to my pull request https://github.com/qgis/QGIS/pull/1520 for the issue 9797 Next step is to update the OWS Tab in the project property to define precision. Regards, René-Luc Hello René-Luc, Thank you for the patches, I've successfully built and tested the patched binary. It works perfectly so far. -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Broken models with processing (i.e we shouldn't be doing that)
Hey Nathan I agree with you, and I have been wanting to do this...but it requires some work, since not only the format has changed, but also the inner structure of the models. Unfortunately, I am not having too much time to work on Processing lately, but I guess it will be ready for the next release. I would be a pity to ship QGIS with the older version, since this new one has plenty of improvements and good new things Thanks for the advice! 2014-08-11 5:03 GMT+02:00 Nathan Woodrow madman...@gmail.com: Hi all, I have noticed that old models don't work in the new processing modeler. This is really, really bad. Breaking a format is just as bad, or even worse, as breaking a API. Users don't care (much) for APIs but they care about formats and when they stop working people get annoyed. Processing is a core plugin and therefore people consider it part of QGIS, changes in it effect us as a whole product. If I break one of my plugins that hurts me, if I change a core format (e.g qgs, qlr) that hurts the whole QGIS project. I can understand the need to move forward to something better, and the new JSON format is much better then a custom format I will never argue for the later. However not providing a way to import old models, or even doing it by auto magic, is really bad. Some people invest a lot of time into creating models for processing and having it break under them with no option but to recreate will leave a bad taste with people, trust me on that. As processing has been core since 2.0 you can expect a lot of models in the wild and a lot of annoyed people if there is no option to upgrade. What I am NOT proposing is to revert that work, we do need to move forward but I do think there needs to be a conversion function/s. However if it comes close to release and there is no conversion ability then I would say we should revert the plugin in core and wait for the next release to upgrade the models. Breaking the models on people with no convert option will have much more effect then not having some of the new features. Regards, Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Broken models with processing (i.e we shouldn't be doing that)
On 11.08.2014 05:03, Nathan Woodrow wrote: However if it comes close to release and there is no conversion ability then I would say we should revert the plugin in core and wait for the next release to upgrade the models. Breaking the models on people with no convert option will have much more effect then not having some of the new features. +1 I haven't been following the whole thing but while maintaining the API can be a pain, I think it's a strcit requirement. Cheers, Denis ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Broken models with processing (i.e we shouldn't be doing that)
On 11 August 2014 22:43, Denis Rouzaud denis.rouz...@gmail.com wrote: On 11.08.2014 05:03, Nathan Woodrow wrote: However if it comes close to release and there is no conversion ability then I would say we should revert the plugin in core and wait for the next release to upgrade the models. Breaking the models on people with no convert option will have much more effect then not having some of the new features. +1 I haven't been following the whole thing but while maintaining the API can be a pain, I think it's a strcit requirement. I totally agree with this too. Given that processing is treated as part of core, the api should be frozen for the 2.0 series (as painful as that is becoming now!). I've seen stacks of answers to gis.stackexchange questions where processing api is used - it would be a real shame to break all of these. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] QgsMapLayerAction and QgsAttributeAction
Hi, I am currently working on a better integration of actions into the attribute dialog and the feature list on the attribute table in the form view. While working on this, I stumbled upon the class QgsMapLayerAction which I am having a hard time to understand the purpose of. Some comments in qgsdualview.cpp suggest that it is related to user defined actions vs standard actions [1]. I wondered also if it is related to vector layer vs raster layer (as QgsMapLayer is a common base class of the two and QgsMapLayerAction therefore might be interpreted as also valid for raster layers). What I am currently building is a gui component QgsAttributeActionMenu that will generate a QMenu based on a layer and feature (and an optional attribute index) that can be shown as context menu (map canvas, attribute table, feature list) or in a menu bar of the attribute dialog. It would be nice that this class can encapsulate any logic to fetch possible actions from different sources (some flags could be used to enable/disable certain actions based on the context such as open feature form which doesn't make sense if it's shown in a feature form (attribute dialog) window's menubar). I am happy about any hint I get on this, Best regards, Matthias [1] https://github.com/qgis/QGIS/blob/master/src/gui/attributetable/qgsdualview.cpp#L324 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Export atlas composition in python console to a single PDF file
On 11 August 2014 08:47, Junior Delaz del...@gmail.com wrote: Hi All, A couple of hours I'm trying without success to do something so I ask for your help. I would like to export as PDF (in a single file) an atlas composition within Python Console. I don't find how to do. All I obtain is either multiple PDF files corresponding to each iterated feature of the coverage layer or a single feature corresponding to the last iterated feature. Where should I look at, please? And more generally, where can I find the code used by a tool such as Export Atlas to PDF file in the composer GUI (atlas menu)? Unfortunately this code isn't currently exposed to the python bindings, so can't be accessed via the console. The c++ code you are looking for is in QgsComposer::exportCompositionAsPDF - at the moment you'd need to reimplement this yourself in python. It's far from ideal, and is on my list of things to fix, but I haven't found the time to tackle this yet. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QgsMapLayerAction and QgsAttributeAction
On 12 August 2014 01:25, Matthias Kuhn matthias.k...@gmx.ch wrote: While working on this, I stumbled upon the class QgsMapLayerAction which I am having a hard time to understand the purpose of. Some comments in qgsdualview.cpp suggest that it is related to user defined actions vs standard actions [1]. I wondered also if it is related to vector layer vs raster layer (as QgsMapLayer is a common base class of the two and QgsMapLayerAction therefore might be interpreted as also valid for raster layers). I can help you out here - QgsMapLayerActions are built-in c++ actions, or actions which are defined by a python plugin. Unlike the standard vector layer actions, these are not editable by users, and are not listed in the vector layer properties dialog. As far as I'm aware, there's only a single implementation currently in QGIS: https://github.com/qgis/QGIS/blob/master/src/app/composer/qgscomposer.cpp#L3566 This action allows users to jump directly to a specific atlas feature, and is only shown for vector layers which are set as the coverage layer for a composition. There's also some useful sample python code on how these actions can be used here: http://gis.stackexchange.com/a/94665/28443 Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
