I was thinking make an app using gt-epsg-hsql jar, and go through hall the code made available by the factory - and write out their WKT :)
-- Jody Garnett On 1 October 2015 at 11:42, Mart Sõmermaa <mrts.py...@gmail.com> wrote: > Thanks! > > I looked around the EPSG HSQLDB file > https://github.com/geotools/geotools/blob/master/modules/plugin/epsg-hsql/src/main/resources/org/geotools/referencing/factory/epsg/EPSG.zip?raw=true, > but did not figure out an obvious way to dump the data to properties file > as you proposed. The property file should be in 'CRS code'='CRS definition > in WKT format' as far as I can see. > > Here are the tables: > > EPSG_ALIAS > EPSG_AREA > EPSG_CHANGE > EPSG_COORDINATEAXIS > EPSG_COORDINATEAXISNAME > EPSG_COORDINATEREFERENCESYSTEM > EPSG_COORDINATESYSTEM > EPSG_COORDOPERATION > EPSG_COORDOPERATIONMETHOD > EPSG_COORDOPERATIONPARAM > EPSG_COORDOPERATIONPARAMUSAGE > EPSG_COORDOPERATIONPARAMVALUE > EPSG_COORDOPERATIONPATH > EPSG_DATUM > EPSG_DEPRECATION > EPSG_ELLIPSOID > EPSG_NAMINGSYSTEM > EPSG_PRIMEMERIDIAN > EPSG_SUPERSESSION > EPSG_UNITOFMEASURE > EPSG_VERSIONHISTORY > > What should I SELECT from there - or should I look into something else? > > (By the way, the code snippet for the transformation is here: > https://gitlab.com/mrts/broken-gt-epsg-wkt-crs-transform/blob/master/src/main/java/com/mrts/crs/CRSTransform.java > ) > > Thanks in advance, > MS > > > > On Wed, Sep 30, 2015 at 3:53 AM, Jody Garnett <jody.garn...@gmail.com> > wrote: > >> Yes, this was intended. The gt-epsg-wkt implementation was intended for >> use with Java Applets (which could not create an hsql database locally). >> >> If you must respect axis order you will need to write a script to dump >> out the contents of hsql database to a properties file (and replace >> epsg.properties). >> >> -- >> Jody Garnett >> >> On 28 September 2015 at 03:44, Mart Sõmermaa <mrts.py...@gmail.com> >> wrote: >> >>> Hi, >>> >>> it seems that the gt-epsg-wkt plugin does not support the longitudeFirst >>> parameter to org.geotools.referencing.CRS.decode() and generally behaves >>> differently than gt-epsg-hsql. >>> >>> Is this intended? If yes, what's the recommended way to deal with >>> longitude-first CRSes in gt-epsg-wkt? >>> >>> Here's a sample project that demonstrates that converting coordinates >>> from WGS84 to KKJ succeeds when using the gt-epsg-hsql plugin, but fails >>> when usinggt-epsg-wkt: >>> >>> https://gitlab.com/mrts/broken-gt-epsg-wkt-crs-transform >>> >>> Thanks in advance for any info, >>> Mart Sõmermaa >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> GeoTools-GT2-Users mailing list >>> GeoTools-GT2-Users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users >>> >>> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > GeoTools-GT2-Users mailing list > GeoTools-GT2-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users > >
------------------------------------------------------------------------------
_______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
