Incorrect parsing of string that starts with "0Dxxxxx"

[xldeltares]

Describe the bug
When reading a model that has storagenodes with id "0D05252", the string is parsed incorrectly as "0e05252"
A small test model is enclosed.
dflowfm.zip

To Reproduce
Steps to reproduce the behavior:

from hydrolib.core.dflowfm import FMModel
mdu = "FlowFM.mdu"
model = FMModel(mdu)
print(model.geometry.storagenodefile.storagenode[1].id)

The above steps returns: 0e05252

Expected behavior
The above steps should return" 0D05252

Screenshots
This can be verified in the nodeFile.ini:

Version info (please complete the following information):

• OS: Windows
• Version 0.5.2

Additional info
In my use case of Eindhoven, this is rather critical because there are more than 1000 nodes are parsed wrongly after reading. See below figure, the red nodes are parsed wrongly.
The wrongly parsed string will be written again but wont match the network node ID anymore, causing run to fail.

[priscavdsluis]

Another issue was reported via support: https://issuetracker.deltares.nl/browse/SOFTSUP-648

Source of bug:

for line in f:
    # Replace Fortran scientific notation for doubles
    # Match number d/D +/- number (e.g. 1d-05 or 1.23D+01 or 1.d-4)
    match = progline.match(line)
    if match:  # Only process value
        line = (
            match.group(1)
            + progfloat.sub(r"\1e\3", match.group(2))
            + str(match.group(3) or "")
        )
    else:  # Process full line
        line = progfloat.sub(r"\1e\3", line)
    parser.feed_line(line)

[tim-vd-aardweg]

A side-effect of our fix is that you can now also set attributes that are floats using the Fortran scientific notation, e.g.:

from hydrolib.core.dflowfm import FMModel
mdu = "FlowFM.mdu"
model = FMModel(mdu)
model.geometry.storagenodefile.storagenode[1].area = "1d3")

[tim-vd-aardweg]

@xldeltares Could you verify that this issue is fixed in branch: bug/559_Incorrect-parsing-of-string-starting-with-0D?

[xldeltares]

@tim-vd-aardwegAfter testing the reported bug in the example model enclosed, I confirm that the issues has been fixed in bug/559_Incorrect-parsing-of-string-starting-with-0D. Glad that this has been fixed and thanks!