Hi John,
Thanks for the reply. That's a good question.
I had some applications, data structures and metadata based on those old
names.
So the upgrade will also require a rename/slight refactor of all the
dependent parts which I was aiming to avoid or at least scheduled for a
different moment.
Regards,
Daniele
On Sat, Feb 24, 2024 at 6:26 PM John Caron <jcaron1129@xxxxxxxxx> wrote:
> Hi Daniele:
>
> Do you want to keep using the previous version names because you know that
> they are correct, or because they look right and you would prefer not to
> know if they are incorrect?
>
> Sorry to be a snark, but GRIB is so badly messed up with its table
> versioning that someone has to ask that.
>
> Regards,
> John
>
> On Fri, Feb 23, 2024 at 1:04 PM Daniele Romagnoli <
> daniele.romagnoli@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
>> Hi All,
>> I'm investigating upgrading the NetCDF library used in one application,
>> moving from 4.6.15 to 5.5.3.
>>
>> During the upgrade attempt I have noticed some inconsistencies and
>> missing functionalities on the GRIB data that I was using in the
>> application. I think it can be related to some GRIB2 tables that have been
>> modified (so that some variables changed name) with this change:
>> https://github.com/Unidata/netcdf-java/pull/601/
>>
>> I would like to keep using the previous variable names in that
>> application.
>> Is there any way to provide a hint, a config param, a pluggable factory
>> or any kind of resource to let that variable's naming keep using the
>> previous nomenclature?
>> Is there any type of support for a similar use case?
>>
>> Please let me know if you have any hints or suggestions on that topic.
>>
>> Best Regards,
>>
>> Daniele
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> netcdf-java mailing list
>> netcdf-java@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> https://www.unidata.ucar.edu/mailing_lists/
>>
>
