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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Use geospatial functions on geodata type without making a SQL Table in Data module
We want to use spatial functions with spatial data type in informix in a datamodule. We have a lot of tables containing a spatial data type. We want it to have it like in framework manager.
I got a response from dev team and there is some light differences between data module and FM. FM transform the data in unknow type and can proceed it.
Here is the explanation.
By design, when data modules encounters an unknown or unsupported data type, in the SQL we simply do not request it from the DB and instead place a string of <Unsupported: Datatype> as the column
Or something similar to this.
If you look at the query information of the table, you will see this in both the Cognos and Native SQL. So when you try to perform st_x function on this item in a stand alone calculation, you will get an error because you are passing a string to the function which instead expects a map co-ordinate data type.
To accomplish what is desired in data modules, you can create a SQL table and incorporate the function there.
The example below works, but you will likely want to change the C0, C1, C2, etc column aliases to column names you desire. The bolded line is where the function is applied.
Do not place IBM confidential, company confidential, or personal information into any field.