[mapguide-trac] #1468: Unset the EPSG code when cloning a Coordinate System entity

[MapGuide Open Source]

#1468: Unset the EPSG code when cloning a Coordinate System entity
---------------------------+------------------------------------------------
   Reporter:  baertelchen  |       Owner:       
       Type:  enhancement  |      Status:  new  
   Priority:  low          |   Milestone:       
  Component:  General      |     Version:  2.1.0
   Severity:  minor        |    Keywords:       
External_id:               |  
---------------------------+------------------------------------------------
 Currently, when calling one of the various CreateClone() methods in the Mg
 Coordinate System (CS) API, all of the entity's data is copied - incl. the
 EPSG code. This opens the door for inconsistencies, because the cloned
 entity becomes editable and can be saved to the dictionaries. Keeping the
 EPSG code creates a mess, because the underlying CsMap NameMapper
 component doesn't even consider the EPSG field in the dictionaries but
 does the mapping on its own.

 When assuming that a caller clones a CS entity to modify it, it's safe to
 unset the EPSG code because the underlying definition is about to change
 anyway and will thus no longer match the definition as defined by the
 EPSG.

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