Jody Garnett a écrit :
> I was not aware of that convention "authority.properties", regardless
> the code is set up to only look for "epsg.properties" (no convention
> about it - hard coded).
This is because the FactoryUsingWKT class is defined in the
org.geotools.referencing.factory.epsg package, so it is designed specifically
for working in EPSG namespace. We can see that from the getAuthority() method
implementation, which is also hard-coded:
public Citation getAuthority() {
return Citations.EPSG;
}
The current approach is to define a "FactoryUsingWKT" class for every authority.
Since "FactoryUsingWKT" is just a wrapper around an other implementation class,
I don't think that it would had too much overhead. But I admit that it is not
generic.
> I would think it better to adjust our property file format to include a
> initial header containing the authority definition. But these are
> details ... are they interesting details to you at this time?
Maybe in the future if there is a need for that. For now there is other tasks to
finish first. So what do we do with CRS_AUTHORITY_EXTRA_FILE? Can we ommit this
hint for now, improve the javadoc for CRS_AUTHORITY_EXTRA_DIRECTORY (so we talk
about the authority.properties convention), and maybe revisit
CRS_AUTHORITY_EXTRA_FILE later if there is a need and less rush?
Martin
-------------------------------------------------------------------------
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
