[fusion-users] RE: Scale and Unit problems with state plane coord sys

[Mike Adair]

Mark,

I'm currently working on resolving the issues around projections in 
Fusion, but you should be able to get a little farther if you add a 
<ProjectionDef> element (and probably a <ProjectionCode> element too)  
to your  <Map><Extension> block in AppDef:

<ProjectionDef>+proj=lcc +lat_1=48.73333333333333 +lat_2=47.5 +lat_0=47 +lon_0=-120.8333333333333 +x_0=500000.0001016001 +y_0=0 +ellps=GRS80 +to_meter=0.3048006096012192 +no_defs</ProjectionDef>
<ProjectionCode>EPSG:2926</ProjectionCode>

The current MapGuide standard template in Fusion trunk shows an example of this.  If that doesn't solve your issue can you enter a ticket in the Trac system please?

OpenLayers and Proj4js work with EPSG codes whereas MapGuide uses WKT to define projection parameters and we need a way to bridge the two systems.

Mike

 

Mark Pendergraft wrote:
> I looked in the active tickets and it appears that there is already one for
> supporting proj4js, which i believe is the root of the problem here.  The
> default projection for openlayers is EPSG:4326 and my map is in EPSG:2926. 
> So the viewer opens and treats the map as if it were in 4326 regardless of
> the projection of the map.
>
> For those interested, i was able to implement a workaround by editing the
> openlayers.js file around line 14636:
> projection: "EPSG:4326",
>
> to be:
> projection: "EPSG:2926",
>
> this is not a very effective workaround though, as it assumes all of your
> maps are in the same projection.
>
> -Mark P.
>   

-- 
   Michael Adair
   Senior Software Architect
   DM Solutions Group Inc.

   Office: (613) 565-5056 x26
   madair at dmsolutions.ca
   http://www.dmsolutions.ca
   http://research.dmsolutions.ca