[fusion-trac] #395: Tiles and maps are not displayed in MapGuide
Arbitrary XY-M maps
Fusion
trac_fusion at osgeo.org
Thu May 20 00:24:11 EDT 2010
#395: Tiles and maps are not displayed in MapGuide Arbitrary XY-M maps
---------------------------+------------------------------------------------
Reporter: trevorwekel | Owner: madair
Type: defect | Status: new
Priority: P2 | Milestone: 2.0
Component: MapGuide | Version: 2.0.0-RC1
Severity: Major | Keywords: arbitrary xy tile
External_id: | State: New
Browser: All | Os: All
---------------------------+------------------------------------------------
The attached !MapGuide mgp package contains a tiled map based on an
Arbitrary XY meters coordinate system
!Library://TestData/ArbitraryXY/Maps/PlanTiled.MapDefinition. The tiles
are not displayed.
A non-tiled map of the same data is
!Library://TestData/ArbitraryXY/Maps/Plan.MapDefinition is only marginally
useful due to scale range issues. The map starts out smaller than a pixel
and cannot be zoomed in sufficiently to adequately display the map detail.
Two patches for !MapGuide.js are attached to the defect which seem to
correct the issue. The first patch ArbitraryXYMUnits.patch is a
workaround to keep the units at meters instead of switching to degrees.
By default EPSG:4326 is used when no EPSG code is given. This switches
the units to degrees which is incorrect for a map with meters as a unit.
Alternatively, custom EPSG codes for the various LOCAL_CS variants could
be defined in PROJ4js and then used by Fusion when no EPSG code is
specified. This would be a better workaround. As far as I know, there
are no official EPSG codes designated for LOCAL_CS.
The second patch !EnableTiles.patch turns off "single tile" behaviour when
a base map layer is found during parsing. The "bSingleTile" tile variable
does not seem to be set based on map content anywhere else in the code.
Shopping mall tenant plans and office floor plans will typically use
LOCAL_CS coordinate systems. This defect represents a fairly serious use
case limitation for !MapGuide/Fusion. The defect seems to occur in the
2.0 branch and trunk.
This ticket may be related to #310 and #394
--
Ticket URL: <http://trac.osgeo.org/fusion/ticket/395>
Fusion <http://trac.osgeo.org/fusion>
Fusion is a web-mapping application development framework for MapServer and MapGuide OS.
More information about the fusion-trac
mailing list