Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor how River - Reach is returned in JSON #30

Open
4 tasks
ar-siddiqui opened this issue Jun 14, 2022 · 0 comments
Open
4 tasks

Refactor how River - Reach is returned in JSON #30

ar-siddiqui opened this issue Jun 14, 2022 · 0 comments
Labels
bug Something isn't working golang psql

Comments

@ar-siddiqui
Copy link

ar-siddiqui commented Jun 14, 2022

HEC-RAS has the following hierarchical structure for Rivers and Reaches:

{
    "River A": {
       "Reach 1": [
            "Node 1",
            "Node 2",
            "...."
       ],
       "Reach 2": [
            "Node 1",
            "Node 2",
            "...."
        ]       
    },
    "River B": {
        "Reach 1": [
             "Node 1",
             "Node 2",
             "...."
        ],
        "Reach 2": [
            "Node 1",
            "Node 2",
            "...."
        ]
    }
}

Currently, the API doesn't conform to this structured format and returns data like this in index, geospatialdata, forcingdata (forcingdata was done deliberately like this to match the pattern):

{
    "River A - Reach 1": [
        "Node 1",
        "Node 2",
        "...."
    ],
    "River A - Reach 2": [
        "Node 1",
        "Node 2",
        "...."
    ]
}

Fix the API response to match HEC-RAS Structure in

  • Index
  • GeospatialData
  • ForcingData
  • Database

This will be a breaking change.

@ar-siddiqui ar-siddiqui added bug Something isn't working golang psql labels Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working golang psql
Projects
None yet
Development

No branches or pull requests

1 participant