[SIS-210] Enforce precedence of EPSG codes over names at parsing time

• Type: Sub-task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 0.6, 0.7, 0.8, 1.0, 1.1, 1.2, 1.3, 1.4
• Fix Version/s: 1.5
• Component/s: Referencing
• Assignee: Unassigned
• Reporter: Martin Desruisseaux
• Created: 02/Jul/15 17:35
• Updated: 23/Sep/23 10:28

Description

The specification §9.3.2 said:

If an identifier is provided as an attribute within the <map projection conversion> object, because it is expected to describe a complete collection of zone name, method, parameters and parameter values, it shall override any identifiers given within the map projection method and map projection parameter objects.

However this would require the GeodeticObjectParser to hold a CoordinateOperationAuthorityFactory, which we do not yet implement. Likewise, EPSG code in Parameter elements are also supposed to have precedence over the parameter name. This is not yet implemented in SIS, but may be less critical since SIS implementation is quite lenient (without introducing ambiguities) regarding parameter names.

For now, the only place where EPSG codes take precedence over names is when fetching the OperationMethod objects, which is the most critical place where we observed ambiguities in our experience.

Issue Links

• is depended upon by: SIS-433 Replace unit parsed from WKT by unit declared in EPSG database