Skip to Main Content
IBM Sustainability Software - Ideas Portal
Hide about this portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add EC-Earth3 ssp585 to catalog

See this idea on ideas.ibm.com

We would like to be able to use the SSP585 dataset. We currently only have SSP126 in the EIS catalog

We have these available to us currently:

   "-  56500: EC-Earth3 ssp126 precipitation\n",
   "-  56501: EC-Earth3 ssp126 surface wind\n",
   "-  56502: EC-Earth3 ssp126 near surface specific humidity\n",
   "-  56503: EC-Earth3 ssp126 near surface relative humidity\n",
   "-  56504: EC-Earth3 ssp126 daily near surface air temperature\n",
   "-  56505: EC-Earth3 ssp126 surface downwelling longwave radiation\n",
   "-  56506: EC-Earth3 ssp126 daily minimum near surface air temperature\n",
   "-  56507: EC-Earth3 ssp126 daily maximum near surface air temperature\n",
   "-  56508: EC-Earth3 ssp126 surface downwelling shortwave radiation\n",

We'd like all of the same types of forecasting, but for the ssp585 outcome as well.

Idea priority High
Needed By Month
  • Admin
    Kate Draper
    Reply
    |
    Feb 27, 2025

    Excellent news. Please reach out to me personally if you run into any further issues. Thank you!

  • Guest
    Reply
    |
    Feb 27, 2025

    Hi Kate,

    Thank you for the workaround, it appears to be working correctly now that I've added alias to the query.

    And yes, SSP585 is querying successfully, we were able to gather all the data we need from 2015-2100 with the new dataset.

    Thank you,
    Jagger

  • Admin
    Kate Draper
    Reply
    |
    Feb 27, 2025

    Our tech team has evaluated and was finally able to reproduce the error. We are testing a fix. In the meantime, we have a workaround that should help you (see below). Additionally, can you please confirm 2014+ for net new model is something you can query successfully?


    Below is a workaround for the customer to try directly. You will need to add an alias to the layer spec in the query. Here is an example:

    {
    "name": "Simon_Layer_56510_Year_1950_Polygon",
    "layers": [
    {
    "alias" : "ExampleMeanAggregation",
    "type": "raster",
    "id": 56510,
    "aggregation": "Mean"
    }
    ],
    "spatial": {
    "type": "poly",
    "polygon": {
    "wkt": "MULTIPOLYGON (((-180.0 74.01954331150226, -180.0 11.178401873711794, -56.25 11.178401873711794, -56.25 74.01954331150226, -180.0 74.01954331150226)))"
    }
    },
    "temporal": {
    "intervals": [
    {
    "start": "1950-01-01T00:00:00Z",
    "end": "1950-12-31T23:59:59Z"
    }
    ]
    }
    }

    The added line is "alias" : "ExampleMeanAggregation",

    It shouldn't matter what is inside the quotes as long as it is a single piece of text with no punctuation or special characters.

  • Guest
    Reply
    |
    Feb 24, 2025

    I have retried it and I'm still getting the same error for years before 1970: 1740398400_19853134

    {

    "id": "1740398400_19853134",

    "status": "Failed",

    "start": 1740418253134,

    "folder": "1740418253134",

    "swLat": 11.178401947021484,

    "swLon": -180.0,

    "neLat": 74.01954650878906,

    "neLon": -56.25,

    "nickname": "Layer_56510_Year_1950_Polygon",

    "message": "java.lang.NullPointerException",

    "usage": 660879220,

    "usageUnit": "bytes",

    "statusCode": 40

    }


    1740398400_20068341
    {

    "id": "1740398400_20068341",

    "status": "Failed",

    "start": 1740418468341,

    "folder": "1740418468341",

    "swLat": 11.178402,

    "swLon": -180.0,

    "neLat": 74.01955,

    "neLon": -56.25,

    "nickname": "Layer_56510_Year_1951_Polygon",

    "message": "java.lang.NullPointerException",

    "usage": 660879220,

    "usageUnit": "bytes",

    "statusCode": 40

    }

  • Admin
    Kate Draper
    Reply
    |
    Feb 24, 2025

    In the meantime, can you please retry? Wondering if you hit an error as we were actively uploading net new data on Friday.

  • Admin
    Kate Draper
    Reply
    |
    Feb 24, 2025

    I have passed the error along to our tech team.


    Additionally, all historical data 1950+ and ssp585 through 2100 should also now be available.

  • Guest
    Reply
    |
    Feb 21, 2025

    Currently I can only query 1970+ on the historical dataset. Any year before 1970 gives a java.lang.NullPointerException error

    Here's an example of the query output I get from 1950-1969 using layer 56510 (historical temperature): 1740139200_06233488

    {

    "id": "1740139200_06233488",

    "status": "Failed",

    "start": 1740145433488,

    "folder": "1740145433488",

    "swLat": 11.178402,

    "swLon": -180.0,

    "neLat": 74.01955,

    "neLon": -56.25,

    "nickname": "Layer_56510_Year_1969_Polygon",

    "message": "java.lang.NullPointerException",

    "usage": 660879220,

    "usageUnit": "bytes",

    "statusCode": 40

    }

  • Guest
    Reply
    |
    Feb 19, 2025

    All historical data 1950+ should now be available to query. Please let us know if you run into any issues. SSP585 is currently in development, we will update by end of week on target availability.

  • Admin
    Kate Draper
    Reply
    |
    Feb 18, 2025

    CMIP6 history common to SSP126 and SSP585 should now be available from 1980-2014.

    1970-79 is currently uploading and we will provide an update once available, target by end of week.

  • Admin
    Kate Draper
    Reply
    |
    Feb 11, 2025

    The team is currently working on this along with the other enhancements (additional temporal coverage back to 1950) as covered in our last conversation. We will provide an update at the end of the sprint on when the new model and backfilled data might be available.

  • Guest
    Reply
    |
    Jan 15, 2025

    we never loaded any data in EI Geospatial for  SSP565.  hence why we removed any access to it

     

    1 reply