Re: [Qgis-user] Fwd: Census Geocoder - Batch Geocoding API Now Available

2014-03-24 Thread Paolo Cavallini
Il 23/03/2014 23:03, Randal Hale ha scritto:
 Of course if I had the skills to do one - this appears to be ripe for a
 plugin to QGIS against the US Census Bureau's service.

I think an unified, pluggable infrastructure is appropriate:
http://hub.qgis.org/wiki/17/Google_Summer_of_Code_2014#Unified-address-search
Please do not add (yet another) address search plugin.
Contributions welcome.
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS  PostGIS courses: http://www.faunalia.eu/training.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] Qgis-Processing (former Sextante) has two bug trackers

2014-03-24 Thread Filipe Dias
Hi

QGIS-Processing (former Sextante) has open tickets on two bugtrackers:

- the plugin bug tracker, built when it was a plugin, but with a lot of
active tickets - http://hub.qgis.org/projects/sextante/activity

- the main bug tracker with a few open tickets -
http://hub.qgis.org/projects/quantum-gis/issues

I understand those two can't be merged in one go, because the
plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing
GRASS GIS etc) that don't fit in the main bug tracker. But this should be
solved ASAP, because the current situation is quite confusing

Regards
F.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] QGIS Plugin to open and parse xml metadata

2014-03-24 Thread Suryo Miles
I make plugin in QGIS to open and read XML file, then parse it and show
scale map from it, its a big xml file and line with scale information have
format like this

gmd:denominatorgco:IntegerScaleValue/gco:Integer/gmd:denominator

and i try code like this to open xml file and then parse it:

from PyQt4 import QtCore, QtGuifrom ui_latih import Ui_latih# create
the dialog for zoom to point

class latihDialog(QtGui.QDialog):
def __init__(self):
QtGui.QDialog.__init__(self)
# Set up the user interface from Designer.
self.ui = Ui_latih()
self.ui.setupUi(self)

cariButton = self.ui.btnCari
QtCore.QObject.connect(cariButton, QtCore.SIGNAL('clicked()'),self.cari)

def cari(self, event=None):

#open dialog
filename = QtGui.QFileDialog.getOpenFileName(self, 'Open File', '*.xml')

self.ui.lineFile.setText(filename)

#call text
self.isiDataFile(filename)

def isiDataFile(self, nmfile):
#open with read mode
teksFile = open(nmfile, 'r').read()

self.ui.textFile.setText(teksFile)

import xml.etree.ElementTree as ET

tree = ET.parse(filename)
doc = tree.getroot()

for elem in doc.findall('Default_Config/gmd:denominator'):
x = elem.tag, elem.text
self.ui.lineSkala.setText(x)

for elem in doc.findall('Default_Config/gmd:MD_Format'):
y = elem.tag, elem.text
self.ui.lineFitur.setText(y)

I try using Element Tree to parse and show ScaleValue in LineEdit because
its integrated in python, but i have error message like this :

NameError: name 'filename' is not defined

i am really newbie in python and xml parser, can i pass the xml location
from open xml code to

tree = ET.parse( )

because i plan to open more than one xml file and scale in one and another
xml file have different value as well

Can Someone help me?
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] QGIS Plugin to open and parse xml metadata

2014-03-24 Thread Horst Düster
substitute filename with self.filename than it should work


All the best
Horst Düster


Am 24.03.2014 17:45, schrieb Suryo Miles:
 I make plugin in QGIS to open and read XML file, then parse it and show
 scale map from it, its a big xml file and line with scale information have
 format like this

 gmd:denominatorgco:IntegerScaleValue/gco:Integer/gmd:denominator

 and i try code like this to open xml file and then parse it:

 from PyQt4 import QtCore, QtGuifrom ui_latih import Ui_latih# create
 the dialog for zoom to point

 class latihDialog(QtGui.QDialog):
 def __init__(self):
 QtGui.QDialog.__init__(self)
 # Set up the user interface from Designer.
 self.ui = Ui_latih()
 self.ui.setupUi(self)

 cariButton = self.ui.btnCari
 QtCore.QObject.connect(cariButton, 
 QtCore.SIGNAL('clicked()'),self.cari)

 def cari(self, event=None):

 #open dialog
 filename = QtGui.QFileDialog.getOpenFileName(self, 'Open File', 
 '*.xml')

 self.ui.lineFile.setText(filename)

 #call text
 self.isiDataFile(filename)

 def isiDataFile(self, nmfile):
 #open with read mode
 teksFile = open(nmfile, 'r').read()

 self.ui.textFile.setText(teksFile)

 import xml.etree.ElementTree as ET

 tree = ET.parse(filename)
 doc = tree.getroot()

 for elem in doc.findall('Default_Config/gmd:denominator'):
 x = elem.tag, elem.text
 self.ui.lineSkala.setText(x)

 for elem in doc.findall('Default_Config/gmd:MD_Format'):
 y = elem.tag, elem.text
 self.ui.lineFitur.setText(y)

 I try using Element Tree to parse and show ScaleValue in LineEdit because
 its integrated in python, but i have error message like this :

 NameError: name 'filename' is not defined

 i am really newbie in python and xml parser, can i pass the xml location
 from open xml code to

 tree = ET.parse( )

 because i plan to open more than one xml file and scale in one and another
 xml file have different value as well

 Can Someone help me?



 ___
 Qgis-user mailing list
 Qgis-user@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-user

-- 

--
Dr. Horst Düster
Managing Director
Sourcepole AG - Linux  Open Source Solutions 
Weberstrasse 5, 8004 Zürich, Switzerland
Tel: +41 (0)44 440 77 11
Direkt: +41 (0)44 515 67 70
horst.dues...@sourcepole.ch  http://www.sourcepole.ch

www.sourcepole.ch/kurse - Das Kursangebot Frühjahr 2014

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Qgis-user Digest, Vol 97, Issue 62

2014-03-24 Thread Nicola Stella
Hello to everyone, i'm new to this mailinglist!

I've ha question about QGIS 2.2.0 API.
I've developed a qgis plugin in python for version 1.8 and now i'm
rewriting it for 2.2.0 version; i've encountered a problem:

i've defined a raster layer with QgsRasterLayer, eg.

rasterLayer = QgsRasterLayer(fileName, fileBaseName)

and i've defined a drawing style (with new rules of 2.2.0 APIs)

rasterLayer.setDrawingStyle('SingleBandPseudoColor')

So i need to define a color shading algorithm, in the same way that i used
with 1.8 version

rasterLayer.setColorShadingAlgorithm(QgsRasterLayer.PseudoColorShader)

but i see there's not

setColorShadingAlgorithm()

in new API

Someone can help me to find a way to define it?

Thanks in advance

Nicola

Web Site:

*http://www.nicolastella.it
http://www.nicolastella.iti...@nicolastella.it i...@nicolastella.it*
*nicolastel...@gmail.com* nicolastel...@gmail.com

..Innovation has nothing to do with how many RD dollars you have.It's not
about money. It's about the people you have, how you're led, and how much
you get it...
Steve Jobs
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] QGIS 2.2.0 API Question

2014-03-24 Thread Alex Mandel
1. Please start a new thread for new questions.
2. API questions are better suited to the QGIS-developer mailing list
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Thanks,
Alex

On 03/24/2014 10:27 AM, Nicola Stella wrote:
 Hello to everyone, i'm new to this mailinglist!
 
 I've ha question about QGIS 2.2.0 API.
 I've developed a qgis plugin in python for version 1.8 and now i'm
 rewriting it for 2.2.0 version; i've encountered a problem:
 
 i've defined a raster layer with QgsRasterLayer, eg.
 
 rasterLayer = QgsRasterLayer(fileName, fileBaseName)
 
 and i've defined a drawing style (with new rules of 2.2.0 APIs)
 
 rasterLayer.setDrawingStyle('SingleBandPseudoColor')
 
 So i need to define a color shading algorithm, in the same way that i used
 with 1.8 version
 
 rasterLayer.setColorShadingAlgorithm(QgsRasterLayer.PseudoColorShader)
 
 but i see there's not
 
 setColorShadingAlgorithm()
 
 in new API
 
 Someone can help me to find a way to define it?
 
 Thanks in advance
 
 Nicola
 
 Web Site:
 
 *http://www.nicolastella.it
 http://www.nicolastella.iti...@nicolastella.it i...@nicolastella.it*
 *nicolastel...@gmail.com* nicolastel...@gmail.com
 
 ..Innovation has nothing to do with how many RD dollars you have.It's not
 about money. It's about the people you have, how you're led, and how much
 you get it...
 Steve Jobs
 
 
 
 ___
 Qgis-user mailing list
 Qgis-user@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-user
 

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] [Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers

2014-03-24 Thread Filipe Dias
Hi
I think Processing tickets should be in the main bug tracker, since GDAL
tools, fTools and Grass plugin tickets are also there.

Also, Qgis-Processing is a really big (and great) feature, that interests a
lot of users, so it makes sense to keep its tickets in the main tracker.

Regards
F.


On Mon, Mar 24, 2014 at 6:02 PM, Alex Mandel tech_...@wildintellect.comwrote:

 On 03/24/2014 05:10 AM, Filipe Dias wrote:
  Hi
 
  QGIS-Processing (former Sextante) has open tickets on two bugtrackers:
 
  - the plugin bug tracker, built when it was a plugin, but with a lot of
  active tickets - http://hub.qgis.org/projects/sextante/activity
 
  - the main bug tracker with a few open tickets -
  http://hub.qgis.org/projects/quantum-gis/issues
 
  I understand those two can't be merged in one go, because the
  plugin-bugtracker has categories (QGIS-Processing SAGA GIS,
 QGIS-Processing
  GRASS GIS etc) that don't fit in the main bug tracker. But this should be
  solved ASAP, because the current situation is quite confusing
 
  Regards
  F.
 
 

 I'm of the opinion that the tracker should continue to be the Plugin
 tracker, not the main QGIS tracker. So I'd propse moving any
 Sextante/Processing tickets from the main or linking them into the
 Plugin tracker.

 To me it's still a plugin, just a core plugin but big enough that it's
 really a subproject. If we wanted to move the Plugin tracker as a
 sub-project of QGIS that would also make sense.

 Also Processing bugs aside from Processing not loading aren't
 showstoppers for release.

 Thanks,
 Alex

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Multipoint vs point postgis error

2014-03-24 Thread Daniel Kranich

Hello all,

I just recently have converted a bunch of shape files I had been using 
into postGIS database tables. A couple of them are giving me major 
grief. The problem is that if I create a new point on one of these 
layers, it gives me the following error: PostGIS error while adding 
features: ERROR: Geometry type (Point) does not match column type 
(MultiPoint). I have done much Googling and found nothing on how to fix 
this problem. I am fairly new at Postgresql so I kinda get lost when 
trying to RTFM.


I could probably create a new table/layer and import the points from my 
problem layer, but i'm not sure if that will cause the error to persist.


Thanks for the Help

Daniel
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Multipoint vs point postgis error

2014-03-24 Thread Alex Mandel
On 03/24/2014 05:32 PM, Daniel Kranich wrote:
 Hello all,
 
 I just recently have converted a bunch of shape files I had been using
 into postGIS database tables. A couple of them are giving me major
 grief. The problem is that if I create a new point on one of these
 layers, it gives me the following error: PostGIS error while adding
 features: ERROR: Geometry type (Point) does not match column type
 (MultiPoint). I have done much Googling and found nothing on how to fix
 this problem. I am fairly new at Postgresql so I kinda get lost when
 trying to RTFM.
 
 I could probably create a new table/layer and import the points from my
 problem layer, but i'm not sure if that will cause the error to persist.
 
 Thanks for the Help
 
 Daniel


So the key to start is the Postgis definition of Point vs MultiPoint.
Point is 1 point per row
Multi-point is 1 or more points per row

I'm not sure why QGIS would care either way, but it is possible that
editing only work with Point and not MultiPoint. So unless your data is
truly multi-point it might be easiest to just convert the Postgis data
type to Point.

It should work though:
http://gis.stackexchange.com/questions/64856/how-can-i-create-a-multipoint-geometry-in-qgis
http://lists.osgeo.org/pipermail/qgis-developer/2011-April/014022.html

Tips on converting
http://gis.stackexchange.com/questions/55067/how-to-convert-multipoint-layer-to-point

Question,
What version of QGIS, what version of Postgis, what version of Postgres,
and what Operating system? And are you using and plugins to aide the
digitizing/editing?

Thanks,
Alex

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user