Martin Desruisseaux wrote: > I have a few questions about some of recently added keys: > > CRS_AUTHORITY_EXTRA_FILE > ------------------------ > Doesn't seem to be used anywhere. Can we remove it? Its work seem to be > performed by CRS_AUTHORITY_EXTRA_DIRECTORY. > I kind of thought this pointed to a properties file; the existing implementation is kind half done CRS_AUTHORITY_EXTRA_DIRECTORY points to a path where an "epsg.properties" file may be found; if you want to specify a different property file we need this CRS_AUTHORITY_EXTRA_FILE key. > CRS_AUTHORITY_DATASOURCE > ------------------------ > Doesn't seem to be used anywhere, and its work seems to duplicate what > EPSG_DATA_SOURCE do (while maybe less generic since it allow only JNDI name as > String, but we can extend that). Should we remove CRS_AUTHORITY_DATASOURCE? > The > EPSG_DATA_SOURCE name may be more accurate since this data source is > explicitly > for the EPSG authority (not an arbitrary authority). > That would be fine; just so long as we can define that the string really is for a JNDI name. I don't mind if it is replaced with a full DataSource later in life ... > FEATURE_LOCK_FACTORY > -------------------- > Javadoc said "The org.opengis.data.FeatureLockFactory instance to use", but > the > implementation refers to "org.geotools.data.FeatureLockFactory". Should I > update > the javadoc? > Please. > FEATURE_COLLECTIONS > ------------------- > Same question than FEATURE_LOCK_FACTORY. > Switch to the GeoTools one.
Jody ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
