Thanks for digging into this, a couple ideas added inline: -- Jody Garnett *1) "strongly-typed"* > Types are mapped as close as possible to the Java and GeoPackage schema. > It means the mapping is modified as follows: > Saving: > Float.class -> FLOAT > Double.class -> DOUBLE > Reading: > FLOAT -> Float.class > DOUBLE -> Double.class > REAL -> Double.class > This approach seems quite restrictive compared to SQLite itself and > clearly not backward-compatible if someone relies on the fact that the > reader will always return a Double.class. >
If it helps you can add a "data type" with value FLOAT, DOUBLE or REAL to the attribute type user map when reading, and make use of the same when writing to give client code better control of what is created. The user map is intended for data formats to take note of additional context beyond what is formally defined in the feature type api.
_______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
