Changes between Initial Version and Version 1 of Ticket #1468


Ignore:
Timestamp:
10/19/10 09:18:03 (14 years ago)
Author:
brucedechant
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1468 – Description

    initial v1  
    1 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.
     1Currently, 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.
    22
    33When 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.