Catalog Endpoint for Location doesn't respect the unit-system argument

During the documentation meeting the Catalog end-point was demoed

When requesting Locations in EN the results can include Locations with "m" Elevation.

For example, this query:

curl -X 'GET'
'https://cwms-data.usace.army.mil/cwms-data/catalog/LOCATIONS?unit-system=EN&office=SPK'
-H 'accept: application/json;version=2'

Includes in the response this location:
{
"office": "SPK",
"name": "Farmington Dam",
"nearest-city": "Oakdale",
"public-name": "Farmington Dam & Reservoir",
"long-name": "Farmington Pool Farmington Pool",
"description": "FRM - Farmington Dam Pool Elevation Station",
"kind": "PROJECT",
"time-zone": "US/Pacific",
"latitude": 37.915,
"longitude": -120.935,
"elevation": 54.860952000000005,
"unit": "m",
"vertical-datum": "NGVD29",
"nation": "United States",
"state": "CA",
"county": "San Joaquin",
"bounding-office": "SPK",
"active": true,
"aliases": [
{
"name": "Agency Aliases-NIDID",
"value": "CA10104"
}
]
}

Start with the Catalog Locations endpoint using the documented curl request and inspect how the unit-system=EN argument is handled. Verify the Farmington Dam response and related locations, then confirm that elevation values and their unit are consistently converted for EN requests.