[Qgis-user] Problem loading a FME generated SpatiaLite file

[Jonathan Moules]

Hi Andreas,
  I've spoken to Safe and they said:

"We have made changes to the SpatiaLite writer to allow it to act in either
Generic Geometry or Specific Geometry mode now at generation time. When
choosing a specific geometry (and dimension) it should now be possible to
create layers that satisfy the needs of applications such as QGIS. This
should be available as of FME 2013 beta build 13194+."

So it should be working in the final 2013 release.
Jonathan

On 7 September 2012 14:20, Andreas Neumann <a.neumann at carto.net> wrote:

> Hi,
>
> May I suggest that you get in contact with the SpatiaLite developer
> (Alessandro Furieri) about this issue, maybe on the SpatiaLite mailinglist?
> Alexander is also the developer of SpatiaLite support in QGIS. There is a
> separate mailing list with SpatiaLite problems. Maybe Alessandro and the
> Safe/FME people can sort out the problems.
>
> I am also a FME user, so I also have an interest that FME properly
> supports SpatiaLite.
>
> Andreas
>
>
> On Fri, 7 Sep 2012 13:58:58 +0100, Jonathan Moules wrote:
>
>> Hi,
>> I've got a SpatiaLite file that was generated with FME 2013. Its beta,
>> and the writer is new, so maybe it has problems and that's where this
>> problem is caused.
>>
>> Anyway, when i try and "add" one of the tables, QGIS gives an error:
>> DBNAME='// TEMPORARY GIS DATA |+|AMP|+| MAP STORAGE/JM - ALTERNATE
>> MASTERMAPS/CONWY_SPATIALITE_**UNCOMPRESSED.SL3'
>> TABLE="OS_MM_BOUNDARYLINE" (GEOMETRY) SQL= IS AN INVALID LAYER - NOT
>> LOADED
>>
>>
>> However, it opens fine in SQLiteStudio (though being spatial data, I
>> can't actually .
>>
>> If I double click on one of the tables in the "add spatiaLite
>> table(s)" page, nothing happens but an error appears in the log:
>> SQLite error: unknown cause
>> SQL: SELECT type, srid, spatial_index_enabled, coord_dimension FROM
>> geometry_columns WHERE f_table_name='os_mm_**boundaryline' and
>> f_geometry_column='GEOMETRY'
>>
>> But that SQL query runs fine in SQLiteStudio and returns:
>> GEOMETRY, 27700, 1, XY
>>
>> The file looks fine and the query works in SQLiteStudio, so I'm more
>> inclined to suspect its a QGIS issue than a FME one, but that's just a
>> barely-educated guess.
>> This exact same data worked fine as a SQLite export from FME.
>>
>> Any thoughts what's going on?
>>
>> Jonathan
>>
>>  This transmission is intended for the named addressee(s) only and may
>> contain sensitive or protectively marked material up to RESTRICTED and
>> should be handled accordingly. Unless you are the named addressee (or
>> authorised to receive it for the addressee) you may not copy or use
>> it, or disclose it to anyone else. If you have received this
>> transmission in error please notify the sender immediately. All email
>> traffic sent to or from us, including without limitation all GCSX
>> traffic, may be subject to recording and/or monitoring in accordance
>> with relevant legislation.
>>
>
> --
> --
> Andreas Neumann
> Böschacherstrasse 10A
> 8624 Grüt (Gossau ZH)
> Switzerland
>
> ______________________________**_________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/qgis-user<http://lists.osgeo.org/mailman/listinfo/qgis-user>
>


This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us,  including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20120926/f3f59843/attachment.html>