[mapserver-dev] RFC 126: Port to PROJ 6 API

Daniel Morissette dmorissette at mapgears.com
Tue Oct 1 20:08:10 PDT 2019

Hi Even,

Thanks a lot for taking on that work.

The significant performance hit caught my attention for the CGI case 
which is a more common use case than the RFC seems to suggest. Is there 
really not much that can be done about that?  Is it really just the 
projection setup that is slower or are the coordinate conversions also 
slower? Could we serialize the projection context pool for any given 
mapfile to some kind of cache file in /tmp/ for instance and start from 
the cached version at loadMap() time?  Could we get some gains this way 
by not having to recompute all the projection transformations all the time?


On 2019-10-01 15:10, Even Rouault wrote:
> Hi
> See https://mapserver.org/development/rfc/ms-rfc-126.html
> (I promise there won't be another new RFC tomorrow)
> Even

Daniel Morissette
Mapgears Inc
T: +1 418-696-5056 #201

More information about the mapserver-dev mailing list