I would try with a WMS or Mapserver CGI definition using a simple OL
example with your specific EPSG code. You could also ask on the OL
mailing list where to define special projections.
Or for test purposes use the 900913 projection or any other standard
projection like UTM. For a web mapping application I doubt people will
notice any difference... If you want to try the tiling (one of the
advantages of OL) then you need anyway to use spherical mercator.
armin
On 26/03/2012 21:36, Thomas RAFFIN wrote:
> Hi,
>
> For me everything is OK concerning mapserver projection (all epsg codes
> are well defined on the server, and mapserver re-projection function
> works well).
>
> But I can't use my user-defined epsg code in config/xxx/js_config.php
> like this :
> PM.mapOptions = {
> projection: new OpenLayers.Projection("EPSG:2154"),
> displayProjection: new OpenLayers.Projection("EPSG:2154"),
> ...
> };
>
> I've tried to add Proj4js and my "defs" for customs codes, but no dice...
>
> Le 26/03/2012 20:21, Armin Burger a écrit :
>> Hi Thomas
>>
>> I forgot probably to add in the readme that all projections (at least
>> the one for the map) have to be defined as EPSG code and like
>> "init=epsg:4326"
>>
>> The EPSG codes are defined in the file "epsg" (lower case, which is
>> important at least under Unix). The default place on Unix/Linux is
>> /usr/local/share/proj/
>> (if compiled proj4 from sources)
>> or
>> /usr/share/proj
>> (if installed via package manager)
>>
>> On Windows there are no default places, could be
>> c:\proj or c:\proj\nad
>>
>> In any case it can be defined in the map file under the MAP tag as
>> CONFIG "PROJ_LIB" "/usr/local/share/proj/"
>> or
>> CONFIG "PROJ_LIB" "c:\proj\"
>>
>> I don't have a clue why it's sometimes needed even on Linux and why
>> sometimes not. On Windows it's typically needed.
>>
>> Armin
>>
>>
>>
>> On 26/03/2012 18:49, Thomas RAFFIN wrote:
>>> Hi,
>>>
>>> Does someone know how to add epsg codes definitions plz?
>>>
>>> Le 25/03/2012 19:59, Armin Burger a écrit :
>>>> Hi all
>>>>
>>>> since there was some interest expressed, I put a first sort of beta
>>>> version of p.mapper 5 for download at
>>>> http://www.pmapper.net/dl/pmapper5-beta1.zip
>>>>
>>>> Some very basic config info is at
>>>> http://www.pmapper.net/dl/pmapper5_configuration.txt
>>>>
>>>> The main new functionality is the integration of the OpenLayers
>>>> framework. So you can have tiling, use OSM or Google layers, or the
>>>> various functionality of OL (drawing, editing, etc).
>>>>
>>>> Note that some core parts like print are not adapted yet and therefore
>>>> not working at all. Other parts like the query have a few small things
>>>> still not fully working (like automated zoom, etc). Generic OL layer
>>>> types other than OSM or Google have not been tested yet, they might
>>>> work
>>>> or not.
>>>>
>>>> There will not be much of support for the time being, so this first
>>>> version is intended for the early adopters and strongly interested
>>>> only.
>>>>
>>>> Cheers
>>>> Armin
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> This SF email is sponsosred by:
>>>> Try Windows Azure free for 90 days Click Here
>>>> http://p.sf.net/sfu/sfd2d-msazure
>>>> _______________________________________________
>>>> pmapper-users mailing list
>>>> pmapper-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>>>
>>>>
>>>
>>
>>
>>
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users
