Hi,
On Dec 3, 2007 10:45 AM, Andreas Hocevar <[EMAIL PROTECTED]> wrote:
> On Dec 3, 2007 2:27 AM, Mike Adair <[EMAIL PROTECTED]> wrote:
> I am concerned about this change in GMLRendererOL, and it breaks my
> current applications. The reason is that my geometries are not in
> EPSG:4326. A better wa
Hi,
On Dec 3, 2007 10:56 AM, Andreas Hocevar <[EMAIL PROTECTED]> wrote:
> Mike,
>
> another problem:
>
> If I use a custom projection that is in proj4js/lib/defs, the url by
> which the def file should be fetched is wrong: in the case of
> EPSG31286.js, proj4js will try to fetch it from
> /proj4js
Mike,
another problem:
If I use a custom projection that is in proj4js/lib/defs, the url by
which the def file should be fetched is wrong: in the case of
EPSG31286.js, proj4js will try to fetch it from
/proj4js/lib/defs/EPSG31286.js. This will obviously not work because I
have no proj4js webapp a
Hi Mike,
great work! After a first glance, I have the following comments on its
integration into Mapbuilder:
On Dec 3, 2007 2:27 AM, Mike Adair <[EMAIL PROTECTED]> wrote:
> There is also a new example checked in to demo this (as presented at
> FOSS4G/07) in examples/projDemo. This includes a chan
All,
I've checked in the change for MAP-443 so that we are using the latest
proj4js. The main advantage of this version is that if the projection
definition is not known beforehand, it will be looked up automatically
through the spatialreference.org web service.
I think everything is working
