[mapguide-trac] #1831: IsValid() API of MgCoordinateSystemGeodeticTransformDef and MgCoordinateSystemGeodeticPath is inconsistent with other Mg coordinate system API types

[MapGuide Open Source]

#1831: IsValid() API of MgCoordinateSystemGeodeticTransformDef and
MgCoordinateSystemGeodeticPath is inconsistent with other Mg coordinate
system API types
---------------------------+------------------------------------------------
   Reporter:  baertelchen  |       Owner:  baertelchen                                            
       Type:  defect       |      Status:  new                                                    
   Priority:  low          |   Milestone:                                                         
  Component:  General      |     Version:  2.2.0                                                  
   Severity:  minor        |    Keywords:  Coordinate System API IsValid SerializeFrom SerializeTo
External_id:               |  
---------------------------+------------------------------------------------
 When (de-)serializing an MgCoordinateSystemGeodeticPath or an
 MgCoordinateSystemGeodeticTransformDef, the implementation will always
 call IsValid(), which for the both types checks whether the targeted
 datums actually exist in the dictionaries.

 With that inconsistent behavior/defect its impossible to create a new
 datum and an accompanying transformation or path on the fly, because the
 code would always insist on the datum to be available. For exactly that
 reason, all other MgCoordinateSystem definition types like cs, datums and
 ellipsoids never required any "child object" to exist when
 (de-)serializing.

 The fix is to simply not pass the cs_GXCHK_DATUM flag to CSMAP's CS_gxchk
 method.

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