Skip to main content
Solved

Use existing SpatiaLite non-geometry feature in FeatureWriter problem


jorge_rosales
Contributor
Forum|alt.badge.img+8

Trying this workspace,

 

imageI get an error saying 'owner' feature type does not exist. The FeatureWriter output format is SpatiaLite and a template.sqlite database is used. For both feature types "Use existing" table handling is selected. Parcel geometry type is wkb_polygon and owner is wkb_none. The 'owner' table exists in the template. Could it be a FeatureWriter error managing SpatiaLite?

 

 

Best answer by mark2atsafe

The good news is that this will work in FME 2022. The SpatiaLite reader/writer got a complete overhaul to include reading non-spatial tables. You just need to use 2022 (should be released in under 1 month now and the beta is fairly stable too) and use the format "SpatiaLite". The older format is renamed to "SQLite Spatial (GDAL) (deprecated)" and that's the one to avoid.

View original
Did this help you find an answer to your question?

6 replies

mark2atsafe
Safer
Forum|alt.badge.img+46
  • Safer
  • Best Answer
  • February 11, 2022

The good news is that this will work in FME 2022. The SpatiaLite reader/writer got a complete overhaul to include reading non-spatial tables. You just need to use 2022 (should be released in under 1 month now and the beta is fairly stable too) and use the format "SpatiaLite". The older format is renamed to "SQLite Spatial (GDAL) (deprecated)" and that's the one to avoid.


mark2atsafe
Safer
Forum|alt.badge.img+46
  • Safer
  • February 11, 2022
mark2atsafe wrote:

The good news is that this will work in FME 2022. The SpatiaLite reader/writer got a complete overhaul to include reading non-spatial tables. You just need to use 2022 (should be released in under 1 month now and the beta is fairly stable too) and use the format "SpatiaLite". The older format is renamed to "SQLite Spatial (GDAL) (deprecated)" and that's the one to avoid.

Oh, I should mention that if you want to do this in 2021 or earlier, use the SpatiaLite format to read the Parcels table and a separate reader in SQLite format to read the Owner table. Annoying, but like I said, resolved in 2022.


jorge_rosales
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • February 11, 2022

That is great! I hope to try the new version soon. Do you know if my "wish list" ("Improve SpatiaLite support

" in Ideas section) is included in FME 2022?

 


mark2atsafe
Safer
Forum|alt.badge.img+46
  • Safer
  • February 11, 2022
jorge_rosales wrote:

That is great! I hope to try the new version soon. Do you know if my "wish list" ("Improve SpatiaLite support

" in Ideas section) is included in FME 2022?

 

I don't think so. I can still create a datatype of varchar in 2022. But although that's odd, I don't think it's necessarily a problem. As I understand it, SQLite is very flexible in its data types and will accept any data type name and any type of data into it. So it's probably not a priority to change anything, but I'll check with our developers anyway why it is still available.


kimo
Contributor
Forum|alt.badge.img+10
  • Contributor
  • April 5, 2022
mark2atsafe wrote:

I don't think so. I can still create a datatype of varchar in 2022. But although that's odd, I don't think it's necessarily a problem. As I understand it, SQLite is very flexible in its data types and will accept any data type name and any type of data into it. So it's probably not a priority to change anything, but I'll check with our developers anyway why it is still available.

But the Readers ignore VARCHAR(0) and make it TEXT <infinite> which is a problem for converting to other databases. The DDL schema stored in Spatialite should be honoured, even if internally it is translated to limited data types.


andreaatsafe
Safer
Forum|alt.badge.img+12
mark2atsafe wrote:

I don't think so. I can still create a datatype of varchar in 2022. But although that's odd, I don't think it's necessarily a problem. As I understand it, SQLite is very flexible in its data types and will accept any data type name and any type of data into it. So it's probably not a priority to change anything, but I'll check with our developers anyway why it is still available.

Hi @kimo​ ,

Following up here as well from your other post - there is a bug with the SpatiaLite format in FME 2022 beta currently if the original table column was created with "VARCHAR" instead of "varchar" (internal ref: FMEENGINE-72938).

We'll update here when it's been resolved.

-Andrea


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings