I am looking for more information on SQLite support. Is this functional? The SQLite guide isn’t complete on your site (see Create Table) and the documentation for SQLiteFeatureLayer and SQLiteFeatureSource doesn’t exist.
I am trying to test the performance and feasibility of using a SQLite database as my storage in place of numerous shapefiles. I need to know how the tables are supposed to be structured and read in a SQLite database for these layers to work.
I have loaded all my features into tables in a SQLite database, created a column to hold a BLOB value for my WKB, and tried to get the layers to read. I have also tried to create blank tables with basic columns, and copy features from shapefiles into these features. I used a loop and tried to insert them into the database using the Inserting New Records in the documentation.
So, I am looking for suggestions on loading data into a SQLite table. If you can give me an idea of how to convert a ShapefileFeatureLayer’s features into a SQLiteFeatureLayer, that’d be great, too. I am assuming that the same basic spatial queries and such still work with this type of layer? I am also assuming the layer itself builds and maintains the R-Tree index.
Lastly, how does the feature shape get stored in the tables? Is it compatible with ESRI’s support for SQLite? I am looking to try to institute and all-around (yet compact) storage system for our data. SQLite seems like a great option.
SqLiteFeatureLayer/SqLiteFeatureSource How-To
Hi Brandon,
I am sorry our guide is not enough complete.
The SQLite support is new feature, so it looks we don’t have some samples or documentation, but our WorldMapKit SDK use SQLite as its database, maybe you can get more from it, and you can view the code samples in Product Center of WorldMapKit SDK.
Wish that’s helpful.
Regards,
Don
Ok… I will dig into it. For some feedback as a customer, it would be best if you don’t publish changes to your code without adding documentation to support that change. It is frustrating when we are trying to change our software to take advantage of a ‘supported’ feature when the only help to use the feature comes from a few minor statements, and what little intellisense can pick up. It is bad for our business too since I had spent days trying to figure out a proper way to use a SQLite db with the classes, and now I must spend even more time digging through more of your code to figure out how your product is supposed to work.
Hi Brandon,
Thanks very much for your feedback!
I am so sorry our guide is simple, so our customers have to takes more time on research on our new features. I will let our development team knows that and ask them public more detail documentation when they public new features.
Any suggestion please let us know, we will do our best to make our products better.
Regards,
Don