Hello Larry

Larry Reeder a écrit :
> To resolve my immediate problem, I've created a workaround ESRI PRJ
> formatter class.    I'd like to help add ESRI prj formatting to
> geotools, but may need some guidance on the best approach to a fix.

It should be done in Geotidy (to be linked to GeoTools 3 when the referencing 
part will be finished - progress reported here: 
http://hg.geomatys.fr/geotidy/). 
However if you would like, you could greatly help with the task described below.

Geotidy has a vastly improved framework for managing Projection parameter names 
compared to GeoTools 2.x. Basically GeoTools 2 put parameter names in the same 
bag without consideration about whatever a name is really applicable to a given 
projection according a given authority. Geotidy now make the distinctions and 
can use this knownledge when parsing and formatting WKT.

If you have time, you could browse over every files in the following directory:

http://hg.geomatys.fr/geotidy/file/tip/modules/referencing/gt-referencing/src/main/java/org/geotools/referencing/operation/provider/

You can also checkout http://hg.geomatys.fr/geotidy/ using Mercurial if it is 
more pratical for you (if you use the NetBeans IDE, you already have Mercurial 
integrated in your IDE).

For every files in the above directory, look at the static fields. Many of them 
contains a parameter name flagged with the // ESRI comment. For example if you 
click on the Mercator1SP.java file, you should see:

     public static final ParameterDescriptor<Double> CENTRAL_MERIDIAN =
         Identifiers.CENTRAL_MERIDIAN.select(
             "central_meridian",            // OGC
             "Longitude of natural origin", // EPSG
             "Longitude_Of_Origin",         // ESRI
             "NatOriginLong");              // GeoTIFF

If you could check if the name on the left side of "ESRI" is really the name 
used by ESRI for that particular projection, that would be much appreciated. 
Note that different projection may have different parameter names (this is the 
detail where everything were mixed in GeoTools 2).

To be honest I must said that if you accept to help with that, this work would 
not appear immediatly in GeoTools 2 since I need to finish the remaining of the 
referencing module first. However I commit myself to offer this work to 
GeoTools 
once it will be ready, and to help with the port. Whatever it will be accepted 
depends on the community decision.

        Martin

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to