[mapguide-trac] #1576: Values set via MgCoordinateSystem::SetLonLatBounds() are not written back to CsMap's dictionary for user defined systems

[MapGuide Open Source]

#1576: Values set via MgCoordinateSystem::SetLonLatBounds() are not written back
to CsMap's dictionary for user defined systems
---------------------------+------------------------------------------------
   Reporter:  baertelchen  |       Owner:  baertelchen                                             
       Type:  defect       |      Status:  new                                                     
   Priority:  low          |   Milestone:  2.3                                                     
  Component:  General      |     Version:  2.1.0                                                   
   Severity:  minor        |    Keywords:  Coordinate System API SetLonLatBounds MgCoordinateSystem
External_id:               |  
---------------------------+------------------------------------------------
 The MgCoordinateSystem class has an API "SetLonLatBounds". This allows for
 dynamically setting a range in which coordinates are valid for the
 respective system. If switched on (i.e. by calling this method with a set
 of valid parameters), CsMap will fail or at least set a warning, when a
 coordinate transformation is done with input values that do not fall
 within the range specified.

 Currently, values set via this method will not be saved to CsMap's
 dictionaries when saving a user-created system. For built-in systems,
 however, CsMap stores such values in the coordsys.asc dictionary in the
 MIN_LNG, MIN_LAT, MAX_LNG, MAX_LAT fields.

 If the values are not set, CsMap calculates mathematically valid values on
 the fly, if a coordinate system definition is read from the dictionaries.
 This might result in values like 197.9998272522.

 This ticket is to fix the API as follows:[[BR]]
 - changes only apply to user-defined systems[[BR]]
 - Fix the implementation in coordsys.cpp so that MinMaxLatLon[[BR]]
 values are written back to the dictionaries when set before via the
 API[[BR]]
 - document the methods[[BR]]

 Specifically, this ticket is *NOT* about doing any changes to the other
 existing API [SetXYBounds()].

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/1576>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals