69 | | Any of the well known and highly used systems in CS-Map is unit tested with a list of test points that should be transformed to an expected target point within a certain tolerance. This test points in this list typically come from official sources. We can expect slightly different results between the two libraries depending on the reasons listed above but if there is a large difference between the two products, and we have valid test points for a given transformation to test what is expected, the resulting defect we would be facing in that case in the algorithm or in the system definition will have to be fixed. |
70 | | |
| 69 | Any of the well known and highly used systems in CS-Map is unit tested with a list of test points that should be transformed to an expected target point within a certain tolerance. This test points in this list typically come from official sources. We can expect slightly different results between the two libraries depending on the reasons listed above but if there is a large difference between the two products, and we have valid test points for a given transformation to test what is expected, the resulting defect we would be facing in that case in the algorithm or in the system definition will have to be fixed.[[BR]] |
| 70 | [[BR]] |
| 71 | Some coordinate systems may not work with the new CSMAP. Though the number should be very low. Resources would need to be updated to use the CS-MAP equivalent CS if there is failing CS.[[BR]] |
| 72 | If a definition is missing, the creation of a custom system is possible via the fully implemented MgCoodinateSystem API that will be provided.[[BR]] |
| 73 | If a projection or datum technique is missing, a source code update would be needed inside CS-Map. This would be of course possible after approval of the corresponding RFC that would need to be written against that OSGEO project. |