[Qgis-user] Fwd: RE: QGIS DB Manager geometry columns issue with PostGIS 2.0

[Neumann, Andreas]

Forgot to include the mailing-list - sorry. 

-------- Original Message -------- 

 		SUBJECT:
 		RE: [Qgis-user] QGIS DB Manager geometry columns issue with PostGIS
2.0

 		DATE:
 		2016-02-08 15:32

 		FROM:
 		"Neumann, Andreas" <a.neumann at carto.net>

 		TO:
 		Chris Buckmaster <chris.buckmaster at runnymede.gov.uk>

Hi Chris, 

Ah yes - sorry. Forgot about that. 

Here are the instructions: 

In FME, if you add a writer for a Postgis database have a look into the
"Parameters" dialogue. In there you find a checkbox labeled "Create
Generic Spatial Columns". --> make sure you uncheck this checkbox. 

Then if you add a new Feature type you will find a drop-down box in the
"General" tab labeled with "Geometry". There you can select the geometry
type, such as "postgis_point" or "postgis_linestring". 

Can you please let me know if this works for you? 

Andreas 

On 2016-02-08 15:24, Chris Buckmaster wrote: 

> Hi Andreas 
> 
> I have tried to find where I can do this in FME but still seem unable to - if it isn't too much work are you able to point me in the right direction please? 
> 
> Thank you, Chris 
> 
> FROM: Andreas Neumann [mailto:a.neumann at carto.net] 
> SENT: 05 February 2016 16:21
> TO: Chris Buckmaster; qgis-user at lists.osgeo.org
> SUBJECT: Re: [Qgis-user] QGIS DB Manager geometry columns issue with PostGIS 2.0 
> 
> Hi Chris,
> 
> This explains it.
> 
> You need to define as "geometry(WKBTYPE,srid)", e.g. "geometry(POLYGON,21781)" for QGIS. FME has an option to do that. I just don't have at hand. I could send you instructions on Monday, if you want.
> 
> Andreas 
> 
> On 05.02.2016 17:11, Chris Buckmaster wrote: 
> 
> Hi Andreas 
> 
> Yes it does exist in the geometry column view but the type is listed as GEOMETRY. 
> 
> This table is being created from a non-spatial SQL Server table, and we use a vertex creator transformer in FME to create the spatial table - we cannot seem to explicitly specify the geometry that the spatial table should be as it is not a spatial layer when imported? 
> 
> Chris 
> 
> FROM: Qgis-user [mailto:qgis-user-bounces at lists.osgeo.org] ON BEHALF OF Andreas Neumann
> SENT: 05 February 2016 12:43
> TO: qgis-user at lists.osgeo.org
> SUBJECT: Re: [Qgis-user] QGIS DB Manager geometry columns issue with PostGIS 2.0 
> 
> Hi Chris,
> 
> That's true - starting from Postgis 2.0, geometry_columns is a view in the public schema.
> 
> Did you check if that view exists and if the view contains an entry for your spatial table?
> 
> Also make sure, when importing from FME, that you restrict your geometry type to either POINT, POLYGON, LINESTRING, COMPOUNDCURVE or the MULTI versions. QGIS likes a single geometry type per table, while Postgis would permit to store mixed geometry types in the same geometry column.
> 
> Maybe you did not specify this geometry type restriction when importing your data with FME.
> 
> Andreas 
> 
> On 05.02.2016 13:33, Chris Buckmaster wrote: 
> 
> Hi 
> 
> I have been using FME to load some data into PostGIS and view it in QGIS 2.12.3. 
> 
> I am finding that when accessing the data in DB Manager, I get a warning that says 'There is no entry in geometry_columns!'. 
> 
> On asking another user they mentioned that the geometry columns table was removed in PostGIS 2.0, so my question is, is this a known issue / bug within QGIS, or is it the way in which I am storing my data? Just wondering if this will be looked at in future QGIS versions. 
> 
> Thanks, Chris 
> 
> _______________________________________________
> 
> Qgis-user mailing list
> 
> Qgis-user at lists.osgeo.org
> 
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-user
> 
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20160208/b8d17eb5/attachment.html>