Hi Chris, (hi all)
there is still a serious issue with 1.5.0: it's very very
hard to add new projections to the server.
I'm inclined to try Alex workaround on 1.5.x, which has no
UI but allows for relatively simple explanations, and
adopt Martin's solution (available only on gt2 trunk)
for Geoserver trunk.
What do you think?
On the bright side, people trying 1.5.x are having nice surprises, like improved reprojection accuracy compared to 1.4.0, see for example this:
http://www.nabble.com/Projection-problem-Mapserver-Geoserver-Geotools-tf3218849.html
Cheers
Andrea
I can look into this before the IRC meet today.
Sorry for not making some sort of UI--there was some talk to switching
to something else, and have been putting it off.
I will try my workaround with 1.5 beta2 and look at Martin's code as
well. If I recall correctly, the drawback of writing custom proj
definitions to the HSQL database is that any time there is a new
version of the HSQL jar, the local database gets overwritten during
upgrade. I experienced it a few times myself.
Alex
On 2/13/07, Andrea Aime <aaime@anonymised.com> wrote:
Hi Chris, (hi all)
there is still a serious issue with 1.5.0: it's very very
hard to add new projections to the server.
I'm inclined to try Alex workaround on 1.5.x, which has no
UI but allows for relatively simple explanations, and
adopt Martin's solution (available only on gt2 trunk)
for Geoserver trunk.
What do you think?
On the bright side, people trying 1.5.x are having nice surprises, like
improved reprojection accuracy compared to 1.4.0, see for example this:
http://www.nabble.com/Projection-problem-Mapserver-Geoserver-Geotools-tf3218849.html
Cheers
Andrea
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Alexander Petkov ha scritto:
I can look into this before the IRC meet today.
Sorry for not making some sort of UI--there was some talk to switching
to something else, and have been putting it off.
I will try my workaround with 1.5 beta2 and look at Martin's code as
well. If I recall correctly, the drawback of writing custom proj
definitions to the HSQL database is that any time there is a new
version of the HSQL jar, the local database gets overwritten during
upgrade. I experienced it a few times myself.
Yes, that's by design. We want people to have the latest version
since they constantly add new CRS and fix older ones.
That's also why I prefer Martin's solution in the long run, it allows
to keep the user extensions outside of the database.
Cheers
Andrea
That's also why I prefer Martin's solution in the long run, it allows
to keep the user extensions outside of the database.
that is what I do as well for now--definitions are kept somewhere in a
user's file.
Alex
Alexander Petkov ha scritto:
That's also why I prefer Martin's solution in the long run, it allows
to keep the user extensions outside of the database.
that is what I do as well for now--definitions are kept somewhere in a
user's file.
I thought you added the definitions to the hsql db on startup?
Cheers
Andrea
On 2/13/07, Andrea Aime <aaime@anonymised.com> wrote:
Alexander Petkov ha scritto:
>> That's also why I prefer Martin's solution in the long run, it allows
>> to keep the user extensions outside of the database.
>
> that is what I do as well for now--definitions are kept somewhere in a
> user's file.
I thought you added the definitions to the hsql db on startup?
No--user definitions (WKT) are stored in a plain text file. The
drawback of this approach is that keeps the epsg-wkt jar alive. That
makes Simone a sad panda 
BTW, I am looking around to find Martin's code for user CRS
definitions. Where in gt-trunk should I look? Any quick hints?
Otherwise I'll keep digging.
Alex
Alexander Petkov ha scritto:
On 2/13/07, Andrea Aime <aaime@anonymised.com> wrote:
Alexander Petkov ha scritto:
>> That's also why I prefer Martin's solution in the long run, it allows
>> to keep the user extensions outside of the database.
>
> that is what I do as well for now--definitions are kept somewhere in a
> user's file.
I thought you added the definitions to the hsql db on startup?
No--user definitions (WKT) are stored in a plain text file. The
drawback of this approach is that keeps the epsg-wkt jar alive. That
makes Simone a sad panda
Well, nothing prevents people from adding at least the TOWGS84 parameters to the WKT.
BTW, I am looking around to find Martin's code for user CRS
definitions. Where in gt-trunk should I look? Any quick hints?
Otherwise I'll keep digging.
http://svn.geotools.org/geotools/trunk/gt/modules/unsupported/epsg-extension/
Cheers
Andrea