added more flexibility in encoding georeference inside map.osm

[MishkaMN]

PR Details

Description

Added more flexibility in encoding geoReference string inside vector_map.osm.
Autoware_osm_parsert now supports following geoReference tags in the map, e.g.:

• <geoReference>+proj=tmerc +lat_0=39.46636844371259 +lon_0=-76.16919523566943 +k=1 +x_0=0 +y_0=0 +datum=WGS84</geoReference>

• <geoReference v="+proj=tmerc +lat_0=39.46636844371259 +lon_0=-76.16919523566943 +k=1 +x_0=0 +y_0=0 +datum=WGS84"/>

• <geoReference value="+proj=tmerc +lat_0=39.46636844371259 +lon_0=-76.16919523566943 +k=1 +x_0=0 +y_0=0 +datum=WGS84"/>

Related Issue

Initial issue is here

Motivation and Context

Initial way of encoding, which is to use inside-brackets approach, was not as common, and created confusion for developers when they used more common practices without being successfully loading the map. Particularly, this creates discrepancy when scripts like osm converter is used.

How Has This Been Tested?

Unit Tested using sample maps

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
  CARMA Contributing Guide
• I have added tests to cover my changes.
• All new and existing tests passed.