STASH Code to CF name translations: look consistent but aren't accepted

[ehogan]

Here is a copy of my upload file:
STASH(msi)|CFName|units|force_update(y/n)|
|m01s03i236|air_temperature|K|n|
|m01s03i237|specific_humidity|1|n|
|m01s03i245|relative_humidity|%|n|

Here is the responce:
The file failed to parse; in order to process this file you should consider:
line1: forcing replacement of m01s03i236 -> air_temperature(K) with m01s03i236 -> air_temperature(K)
line2: forcing replacement of m01s03i237 -> specific_humidity(1) with m01s03i237 -> specific_humidity(1)
line3: forcing replacement of m01s03i245 -> relative_humidity(%) with m01s03i245 -> relative_humidity(%)

These look identical to me, so I'm not sure why they aren't being accepted :(

[marqh]

All three of these mappings are correct but also include an implied height, so they are regressive steps, which the repo won't accept
http://www.metarelate.net/metOcean/mapping/8c7bf2c7c1d0e61fce8a46ad2ee20108efcd506b/
http://www.metarelate.net/metOcean/mapping/e4c23d7ed8f58fe29d5e48ed0154c4f6f995b551/
http://www.metarelate.net/metOcean/mapping/fb6ede32544b9a2413d4ad8d34d4f4f025504c71/

I suggest these are well handled and that this ticket is no longer required

@ehogan, are you happy to close the issue on this basis?

[ehogan]

@marqh, in the case where the uploaded translation is regressive, is there a way for metarelate to say something to this effect and at least accept the name, units etc.?

[marqh]

in the case where the uploaded translation is regressive, is there a way for metarelate to say something to this effect and at least accept the name, units etc.?

That is somewhat tricky to implement, I'm afraid

at the point where such situations come up, I recommend using the search facility to explore the mappings in question