Reputation
1,606
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
1 8 17
Newest
 Taxonomist
Impact
~44k people reached

16h
comment I cannot find osr after installing OSGeo4W package
Sorry if confusing. At the command prompt (after all the gdal_calc, gdal_edit stuff) you can enter the command python to use an interactive python session, or enter something like python myscript.py to run a script you have already written. (This assumes the script is in the current directory.)
17h
comment I cannot find osr after installing OSGeo4W package
No. Simply run the file to get a command line where you can run your Python scripts or the interpreter. Understanding the script will help you if you ever want to automate the startup of a Python program.
17h
answered I cannot find osr after installing OSGeo4W package
Jul
21
comment Updating SRID (Update_GeometrySRID) does not alter polygons (when it should)
In QGIS, right-click the layer with the updated SRID, select the General tab, and make sure that EPSG:4618 is indeed the selected coordinate reference system. Also ensure that 'on the fly' is enabled from top menu: Project -> Project Properties, CRS tab.
Jul
21
comment Updating SRID (Update_GeometrySRID) does not alter polygons (when it should)
Does ST_MinX(geom) give the same results for a particular row from "setor_censitario" and "setor_censitario_2"? If not, then a transform has occurred somehow. If so, then we may suspect that QGIS is mishandling the SRID.
Jul
20
comment Updating SRID (Update_GeometrySRID) does not alter polygons (when it should)
What are the results of select srid from geometry_columns where f_table_name = 'setor_censitario' and select st_srid(geom) from setor_censitario? (Using the table that should be correct, obviously.)
May
19
comment In PostGIS, why does ST_Covers return f on this query?
@ChrisMorrow It would have been difficult to be comprehensive, and you probably just educated yourself better than anyone else could have. Thinking and doodles are good.
May
19
revised In PostGIS, why does ST_Covers return f on this query?
added 130 characters in body
May
19
answered In PostGIS, why does ST_Covers return f on this query?
May
18
comment Connect to PostGIS database from Q GIS
To clarify, the top line of the QGIS connection dialog is just a friendly name. You need to put "mb_sed_class" in the field labeled "Database".
May
18
comment Connect to PostGIS database from Q GIS
In the screenshot provided, you did not specify a database.
May
15
comment .dxf export in QGIS 2.0.1 gives hatches instead of polylines
Covered in this question: gis.stackexchange.com/questions/80293/…
Apr
1
awarded  Taxonomist
Mar
18
comment PostgreSQL default values in QGIS 2.8.1
@Sergio - The bug has been fixed and should be available at next update or nightly build. Please accept this as the correct answer if it solves the issue for you.
Mar
18
revised PostgreSQL default values in QGIS 2.8.1
New info on bug fix
Mar
17
revised PostgreSQL default values in QGIS 2.8.1
Added qgis bug ticket number
Mar
17
revised PostgreSQL default values in QGIS 2.8.1
Update based on new insight
Mar
17
comment PostgreSQL default values in QGIS 2.8.1
Okay, it just occurs to me that we are looking not at your actual CREATE statements, but a reverse engineered output such as pgAdmin. Will update answer.
Mar
17
comment PostgreSQL default values in QGIS 2.8.1
I have no idea why the QGIS versions work differently, but it's almost certainly a bigger issue that you are casting your default values (and check constraints) to a different data type than the column definitions.
Mar
17
answered PostgreSQL default values in QGIS 2.8.1