[Qgis-developer] Case study about aerial photo archive management with QGIS at IRPI in Turin, Italy
Dear Community, we have a new QGIS case study written by Danilo and Franco Godone. Franco Research works at the Institute for Geo-hydrological Protection of Turin (IRPI-CNR) as a specialized technician. Danilo is Postdoc grant holder, at Turin University, studying geomatic contribution in landslide, glacier and, more generally, natural disasters monitoring. The case study is about an aerial photo archive management, where they use QGIS to cope (manage and analyse) with the large amount of aerial imagery and other data. You find the whole story here: http://qgis.org/en/site/about/case_studies/italy_turin.html Thank you very much Danilo and Franco for your contribution! Kind Regards Otto ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Labeling in vector layer (development on Qt)
Hi, not sure if this helps, bu you can explore EasyCustomLabeling plugin where I use a lot those options.. check current version 1.1. Cheers, Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Labeling-in-vector-layer-development-on-Qt-tp5103733p5104157.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Labeling in vector layer (development on Qt)
Where can i get it? Thanks -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Labeling-in-vector-layer-development-on-Qt-tp5103733p5104166.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Labeling in vector layer (development on Qt)
Here you used label_style.qml, there is the string labeling/displayAll = false. It is that i needed, but it not worked for me... :( bool loadedStyle; m_layer-loadNamedStyle( path_to_style + /label_style.qml, loadedStyle); m_layer-setCustomProperty(labeling/fieldName, ); m_layer-setCustomProperty(labeling,pal ); m_layer-setCustomProperty(labeling/fontSize,8 ); m_layer-setCustomProperty(labeling/enabled,true); m_layer-setCustomProperty(labeling/displayAll, false); What is wrong? I am at a loss... -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Labeling-in-vector-layer-development-on-Qt-tp5103733p5104176.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] QGIS and LiDAR
Hello everybody, I just want to ask if any development towards lidar analysis is in act or has been planned for the future. I write here because, looking at the mailing lists, this seemed the most appropriate. If I missed the correct place, I apologise. Many thanks in advance for the good work you're doing, Niccolò ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Labeling in vector layer (development on Qt)
Mmm. .. m_layer-setCustomProperty(labeling/displayAll, false); that should work. Did you also put data defined properties like this? m_layer-setCustomProperty(labeling/dataDefined/AlwaysShow, 1~~0LblAShow) Thoses properties overide general placement properties on feature's level... I only have experience on PyQT side, maybe you miss something to refresh that? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Labeling-in-vector-layer-development-on-Qt-tp5103733p5104195.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-community-team] QGIS Browser -Prototype Icon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 17/02/2014 11:51, Paolo Cavallini ha scritto: Il 16/02/2014 18:25, jonnyforest ha scritto: Hi guys what was the decision for the icon of the qgis browser of this release (2.2)? https://drive.google.com/folderview?id=0B98hU-Ebn7VvX2lGTFRvWkdiX28usp=sharing +1 for me to change it, as the current situation is a continuous source of confusion for users. Thanks for reminding: can someone apply this please? is there an open ticket for this? - -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMB6fAACgkQ/NedwLUzIr6bRQCgp5tPB9obon84BmIjAJoKT2e6 4AwAoLqYRRFaIcT5yvkvIEG0azXx/vjC =hsOf -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Labeling in vector layer (development on Qt)
I did refreshing... nothing Also i tried m_layer-setCustomProperty(labeling/dataDefined/AlwaysShow, 1~~0LblAShow) - nothing too... It`s strange, why this not work. I looked at QGis sources and tried to do the same - again nothing... I thing there is something little nuance, but i don`t know what exactly... -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Labeling-in-vector-layer-development-on-Qt-tp5103733p5104207.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Spatialize attribute columns XY oor WKT, design choice
Hi, Users here ask us a good reliable way to spatialize data from XY or WKT columns and I'm wondering what could be the reference architecture to have it in core. I am aware of Xytools plugins, delimited text import and RTQspider plugin, and also of VRT GDAL format. Questions here are for 2.3 branch or later. Here are the functionnal requirements: - The action MUST allow to spatialize XY columns (cartesian or DMS units) from ANY OPENED data source attribute fields. - the action MUST be referenced in vector menu, AND in vector layer's contextual menu. - Geometry and attributes MUST be in sync with origin data source. - Spatialized data source SHOULD be correctly imported or linked in another project (embed project, import project plugin). - Geometry MUST not be editable to avoid conflicts with attribute or geometric editions. User should then save as a real spatial data source to edit geometries. - the user MUST be able to declare attribute field's SRS so that reprojection handles correctly. - the user should be able to spatialize only a selection or a feature subset (not sure about it) - refresh of data should work even if no additionnal plugin is loaded (dangerous for user experience). - attributes index and spatial index should be generated in memory. quite simple, but no plugin does satisfy all use cases. We have either replication of data, or direct access only for some specific data sources (csv, xls, ods.. ) Mapinfo does it but geometry is static and must be refeshed by calling the action another time. Mapinfo can use sub selections. Arcmap only refreshes content on project reload. Grouped with linear referening event actions in UI. Not editable Any opinions on the best implementation architecture? As i'm only developping with python, I have be exploring Memory layers, plugin layers, but it is still unclear to me if this is possible without declaring a new virtual provider using attributes from on data source. VRT is IMHO no adaptated since it is not dynamic with csv data, GDAL lacks many options to open correctly csv (text delimiters, decimal delimiters...) . This is why delimited text exists. It also has no spatial index. It still remains extremly powerfull for UNION, spatial queries thanks to SQL dialect... I would be glad to here from you, so that I can write some specs and hire a dev. Cheers, Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Spatialize-attribute-columns-XY-oor-WKT-design-choice-tp5104209.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and LiDAR
Hi Niccolò. the state of and the plans for QGIS and LiDAR are summarized in this thread: http://osgeo-org.1560.x6.nabble.com/Lidar-data-into-QGIS-td5100547.html my assumption is that plans will get be made during the code sprint in Vienna: http://wiki.osgeo.org/wiki/Vienna_Code_Sprint_2014 Martin On Mon, Feb 17, 2014 at 11:40 AM, Niccolò Marchi sciurusurba...@hotmail.itwrote: Hello everybody, I just want to ask if any development towards lidar analysis is in act or has been planned for the future. I write here because, looking at the mailing lists, this seemed the most appropriate. If I missed the correct place, I apologise. Many thanks in advance for the good work you're doing, Niccolò ___ 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
[Qgis-developer] QGIS mapserver: Occurrence of gml:featureMember elements in WMS GetFeatureInfo response in GML format
Hi guys, Current implementation of QGIS mapserver generates only one gml:featureMember element for all features of particular layer. For example, response from GeoServer ( http://demo.opengeo.org/geoserver/wms?LAYERS=topp%3Atasmania_water_bodiesQUERY_LAYERS=topp%3Atasmania_water_bodiesSTYLES=SERVICE=WMSVERSION=1.1.1REQUEST=GetFeatureInfoBBOX=141.5115%2C-43.933%2C150.8015%2C-39.288FEATURE_COUNT=10HEIGHT=256WIDTH=512FORMAT=application/xmlINFO_FORMAT=application/vnd.ogc.gmlSRS=EPSG%3A4326X=292Y=145) produces gml:featureMember element for every feature. Also parsing response from QGIS mapserver with OpenLayers (OpenLayers.Format.GML.read method) results in max. 1 feature per layer, even if XML document clearly contains more features. For me, it seems like bug, but I'm no expert on WMS standard, so maybe there was some good reason to do it this way. Thanks Marcel Dancak ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS mapserver: Occurrence of gml:featureMember elements in WMS GetFeatureInfo response in GML format
Hi Marcel, It's a bug, you can open an issue on hub.qgis.org with the category mapserver (QGIS-Server). Regards, René-Luc D'Hont 3Liz Le 17/02/2014 15:15, Marcel Dancak a écrit : Hi guys, Current implementation of QGIS mapserver generates only one gml:featureMember element for all features of particular layer. For example, response from GeoServer ( http://demo.opengeo.org/geoserver/wms?LAYERS=topp%3Atasmania_water_bodiesQUERY_LAYERS=topp%3Atasmania_water_bodiesSTYLES=SERVICE=WMSVERSION=1.1.1REQUEST=GetFeatureInfoBBOX=141.5115%2C-43.933%2C150.8015%2C-39.288FEATURE_COUNT=10HEIGHT=256WIDTH=512FORMAT=application/xmlINFO_FORMAT=application/vnd.ogc.gmlSRS=EPSG%3A4326X=292Y=145 ) produces gml:featureMember element for every feature. Also parsing response from QGIS mapserver with OpenLayers (OpenLayers.Format.GML.read method) results in max. 1 feature per layer, even if XML document clearly contains more features. For me, it seems like bug, but I'm no expert on WMS standard, so maybe there was some good reason to do it this way. Thanks Marcel Dancak ___ 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] QGIS mapserver: Occurrence of gml:featureMember elements in WMS GetFeatureInfo response in GML format
Hi Marcel, It's a bug, you can open an issue on hub.qgis.prg with the category mapserver (QGIS-Server). Regards, René-Luc D'Hont 3Liz Le 17/02/2014 15:15, Marcel Dancak a écrit : Hi guys, Current implementation of QGIS mapserver generates only one gml:featureMember element for all features of particular layer. For example, response from GeoServer ( http://demo.opengeo.org/geoserver/wms?LAYERS=topp%3Atasmania_water_bodiesQUERY_LAYERS=topp%3Atasmania_water_bodiesSTYLES=SERVICE=WMSVERSION=1.1.1REQUEST=GetFeatureInfoBBOX=141.5115%2C-43.933%2C150.8015%2C-39.288FEATURE_COUNT=10HEIGHT=256WIDTH=512FORMAT=application/xmlINFO_FORMAT=application/vnd.ogc.gmlSRS=EPSG%3A4326X=292Y=145 ) produces gml:featureMember element for every feature. Also parsing response from QGIS mapserver with OpenLayers (OpenLayers.Format.GML.read method) results in max. 1 feature per layer, even if XML document clearly contains more features. For me, it seems like bug, but I'm no expert on WMS standard, so maybe there was some good reason to do it this way. Thanks Marcel Dancak ___ 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
[Qgis-developer] iterating over fields an values API 2.0
Hi,
I'm working on porting a standalone app from 1.8 to 2.0 API
When iterating over vector features like this:
fields = layer.pendingFields()
field_names = [field.name() for field in fields]
for elem in layer.getFeatures():
atr = dict(zip(field_names, elem.attributes()))
returns this:
{PyQt4.QtCore.QString(u'off_set'): PyQt4.QtCore.QVariant object at
0x05115C70, PyQt4.QtCore.QString(u'code'): PyQt4.QtCore.QVariant object at
0x05115BC8, PyQt4.QtCore.QString(u'pk'): PyQt4.QtCore.QVariant object at
0x05115C00, PyQt4.QtCore.QString(u'id'): PyQt4.QtCore.QVariant object at
0x05115B90, PyQt4.QtCore.QString(u'annee'): PyQt4.QtCore.QVariant object at
0x05115CA8, PyQt4.QtCore.QString(u'id_anom'): PyQt4.QtCore.QVariant object at
0x05115B58, PyQt4.QtCore.QString(u'fk_position'): PyQt4.QtCore.QVariant
object at 0x05115C38, PyQt4.QtCore.QString(u'resolu'): PyQt4.QtCore.QVariant
object at 0x05115CE0}
Instead of tupple like u'off_set': 1 ...
Info here:
http://gis.stackexchange.com/questions/76364/how-to-get-field-names-in-pyqgis-2-0/86751#86751
What is missing to get good values?
Thanks
Sylvain
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] iterating over fields an values API 2.0
On Mon, Feb 17, 2014 at 10:36 PM, PIERRE Sylvain sylvain.pie...@cg67.fr wrote:
When iterating over vector features like this:
fields = layer.pendingFields()
field_names = [field.name() for field in fields]
for elem in layer.getFeatures():
atr = dict(zip(field_names, elem.attributes()))
returns this:
{PyQt4.QtCore.QString(u'off_set'): PyQt4.QtCore.QVariant object at
0x05115C70, PyQt4.QtCore.QString(u'code'): PyQt4.QtCore.QVariant object at
0x05115BC8, PyQt4.QtCore.QString(u'pk'): PyQt4.QtCore.QVariant object at
0x05115C00, PyQt4.QtCore.QString(u'id'): PyQt4.QtCore.QVariant object at
0x05115B90, PyQt4.QtCore.QString(u'annee'): PyQt4.QtCore.QVariant object
at 0x05115CA8, PyQt4.QtCore.QString(u'id_anom'): PyQt4.QtCore.QVariant
object at 0x05115B58, PyQt4.QtCore.QString(u'fk_position'):
PyQt4.QtCore.QVariant object at 0x05115C38,
PyQt4.QtCore.QString(u'resolu'): PyQt4.QtCore.QVariant object at
0x05115CE0}
Instead of tupple like u'off_set': 1 ...
You have not set SIP api to version 2 to QString, QVariant and other
Qt classes. QGIS python package tries to do that automatically for
you, but if you imported PyQt4 python modules before QGIS python
modules, that will not work. You have two options:
1. move import of QGIS module before PyQt4
2. keep the order of imports as is, but put these lines before import of PyQt4:
import sip
sip.setapi(QString, 2)
sip.setapi(QVariant, 2)
This is only necessary in standalone applications - inside QGIS
application this initialization is done before any plugins are loaded,
so this issue does not come up. Probably in qgis __init__.py there
should be some code checking if there are not Qt classes imported with
API v1 - in such case we could throw an exception.
Regards
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
