Question

Chart Generator

T

I am trying to make a chart with XY coordinates generated from the Profile Generator. I have two inputs and trying to plot both on the same chart with different color. I can run with one dataset, but when I try to run with data series it gives me this error: ChartGenerator: Non-numeric input provided. Please validate that the values of the "X Attribute","Y Attribute" and "Error Attribute" (if supplied) are numeric.

14 replies

danilo_fme
Rank
Userlevel 4
Badge +30

Hi @tbs_gis_team

 

Could you share us the Workspace or print?

And the full Log file?

 

Thanks,

Danilo

nielsgerrits
Rank
Userlevel 6
Badge +32

This is probably caused by a space in the attribute name of the data you use to generate the chart. See

https://knowledge.safe.com/questions/59906/chartgenerator-fatal-error-non-numeric-input-provi.html

T

No space in the name, I have two datasets and I can run each separately. It gives the error when I try to run in the chart generator with multiple data series enabled.

T

chart_generator.zip

T

I attached a simplified version of what I am trying to build. It is basically two csv files with XY values generated with the profile generator. I made sure they have the same amount of X values so they plot the Y on the same X for the chart. The end result is I want each line on one chart with different color.

Chad

xiaomengatsafe
Rank
Badge +2

Hi @tbs_gis_team, I had a look at your data, and workspace. I was momentarily confused by the error as well, then realized why this was happening:

By routing both data stream after the AttributeCreator into the ChartGenerator, we've created a dataset where only some records have attributes x2 and y2 (because they are only created on the second stream). Now when a record without the x2 and y2 attributes goes into ChartGenerator, the x2 y2 values are missing, therefore not numeric.

One idea I can think of to make this work, is to use a FeatureJoiner before the ChartGenerator, to combine the two data streams, so that all records will have both x y, and x2 y2 attributes. Can you give that a try?

Tip: You may need to use generate a count attribute, with the Counter transformer (make sure to set the scope to local), on both streams to act as the attribute to join on.

Here is the screenshot of the suggested workflow.

T

Hi @tbs_gis_team, I had a look at your data, and workspace. I was momentarily confused by the error as well, then realized why this was happening:

By routing both data stream after the AttributeCreator into the ChartGenerator, we've created a dataset where only some records have attributes x2 and y2 (because they are only created on the second stream). Now when a record without the x2 and y2 attributes goes into ChartGenerator, the x2 y2 values are missing, therefore not numeric.

One idea I can think of to make this work, is to use a FeatureJoiner before the ChartGenerator, to combine the two data streams, so that all records will have both x y, and x2 y2 attributes. Can you give that a try?

Tip: You may need to use generate a count attribute, with the Counter transformer (make sure to set the scope to local), on both streams to act as the attribute to join on.

Here is the screenshot of the suggested workflow.

Did it print both lines in your process? I will give it a try...Thanks Chad

T

Hi @tbs_gis_team, I had a look at your data, and workspace. I was momentarily confused by the error as well, then realized why this was happening:

By routing both data stream after the AttributeCreator into the ChartGenerator, we've created a dataset where only some records have attributes x2 and y2 (because they are only created on the second stream). Now when a record without the x2 and y2 attributes goes into ChartGenerator, the x2 y2 values are missing, therefore not numeric.

One idea I can think of to make this work, is to use a FeatureJoiner before the ChartGenerator, to combine the two data streams, so that all records will have both x y, and x2 y2 attributes. Can you give that a try?

Tip: You may need to use generate a count attribute, with the Counter transformer (make sure to set the scope to local), on both streams to act as the attribute to join on.

Here is the screenshot of the suggested workflow.

Thanks Xiaomeng, that did the trick...

T

I am having another issue now. I was using the two csv files created from two dem files to use as test data for the chart generator process. My end goal was to have a process that you could import two or more DEM files and create profiles for both and then create a chart in the generator for export. I am having an issue with the process only processing one DEM file and writing out its profile to the chart generator. I have tried feature holders, importing DEM files as two readers and also importing together and splitting by fme basename. If I can't bring both into one process I was thinking a workspace runner to run one DEM then the other and merge the profile values to run in the chart generator.

 

Thanks,

Chad

nielsgerrits
Rank
Userlevel 6
Badge +32

I am having another issue now. I was using the two csv files created from two dem files to use as test data for the chart generator process. My end goal was to have a process that you could import two or more DEM files and create profiles for both and then create a chart in the generator for export. I am having an issue with the process only processing one DEM file and writing out its profile to the chart generator. I have tried feature holders, importing DEM files as two readers and also importing together and splitting by fme basename. If I can't bring both into one process I was thinking a workspace runner to run one DEM then the other and merge the profile values to run in the chart generator.

 

Thanks,

Chad

I think you still got the same problem: you need one feature with two values to plot two lines in one chart:

Distance (x)ValueDem1 (y serie 1)ValueDem2 (y serie 2)

 

00.00.511.01.521.01.0

Where you might have:

Distance (x)

 

ValueDem1 (y serie 1)

 

ValueDem2 (y serie 2)

 

00.0

 

 

0

 

0.5

 

11.0

 

 

1

 

1.5

 

21.0

 

 

2

 

1.0

 

 

 

chartgenerator.fmw

T

I think you still got the same problem: you need one feature with two values to plot two lines in one chart:

Distance (x)ValueDem1 (y serie 1)ValueDem2 (y serie 2)

 

00.00.511.01.521.01.0

Where you might have:

Distance (x)

 

ValueDem1 (y serie 1)

 

ValueDem2 (y serie 2)

 

00.0

 

 

0

 

0.5

 

11.0

 

 

1

 

1.5

 

21.0

 

 

2

 

1.0

 

 

 

chartgenerator.fmw

It will not get to the chart generator. Once one DEM goes through the profile generator the second one stops at the profile generator it is linked to and the process finishes..

xiaomengatsafe
Rank
Badge +2

It will not get to the chart generator. Once one DEM goes through the profile generator the second one stops at the profile generator it is linked to and the process finishes..

Hi @tbs_gis_team, It might help the community better understand your problem, if you could attach your workspace (.fmw) the log file generated from the translation (.log), as well as the sample data (if they are different from the previous attachment)

nielsgerrits
Rank
Userlevel 6
Badge +32

Hi @tbs_gis_team, It might help the community better understand your problem, if you could attach your workspace (.fmw) the log file generated from the translation (.log), as well as the sample data (if they are different from the previous attachment)

It is hard to reproduce your issue without data and workspace. I could not read the transformer names from your last screenshot either.

So created a poc from might be what you described. I used pointclouds instead of rasters but the principle is the same.

Edit: uploaded workpace template file with data. profilesfrompointcloud.fmwt

 

T

I got it working, Thanks for all the comments...Chad

Reply


Community Stats

28,670
Posts
109,366
Replies
36,531
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.