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

SAGA -> Terrain Analysis - Profiles -> Cross profiles gets a float where an integer is required #27034

Closed
qgib opened this issue Jun 15, 2018 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Easy fix Processing Relating to QGIS Processing framework or individual Processing algorithms Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented Jun 15, 2018

Author Name: Loren Amelang (@LorenAmelang)
Original Redmine Issue: 19205
Affected QGIS version: 3.0.3
Redmine category:processing/saga


This is like #26702. But a different SAGA module.

In QGIS 3.0.3:
Processing -> Toolbox -> SAGA -> Terrain Analysis - Profiles -> Cross profiles

'50.0' is not a correct numeric value for option 'NUM_PROFILE'.

Tried the default:
'10.0' is not a correct numeric value for option 'NUM_PROFILE'.

Looks like NUM_PROFILE is different from the other parameters:
Usage: saga_cmd ta_profiles 3 [-DEM ] [-LINES ] [-PROFILES ] [-DIST_LINE ] [-DIST_PROFILE ] [-NUM_PROFILE ]

-NUM_PROFILE: Profile Samples
Integer
Minimum: 3
Default: 10

I tried to delete the decimal point and zeros from the SAGA dialog, but it puts them right back as soon as I leave the field!


Related issue(s): #26702 (relates)
Redmine related issue(s): 18870


@qgib
Copy link
Contributor Author

qgib commented Jun 16, 2018

Author Name: Nyall Dawson (@nyalldawson)


Fixed in master


  • resolution was changed from to fixed/implemented
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Jun 16, 2018
@qgib
Copy link
Contributor Author

qgib commented Jun 18, 2018

@qgib
Copy link
Contributor Author

qgib commented Jun 18, 2018

Author Name: Jürgen Fischer (@jef-n)


  • description was changed from This is like:
    [[https://issues.qgis.org/issues/18870]]
    But a different SAGA module.

In QGIS 3.0.3:
Processing -> Toolbox -> SAGA -> Terrain Analysis - Profiles -> Cross profiles

'50.0' is not a correct numeric value for option 'NUM_PROFILE'.

Tried the default:
'10.0' is not a correct numeric value for option 'NUM_PROFILE'.

Looks like NUM_PROFILE is different from the other parameters:
Usage: saga_cmd ta_profiles 3 [-DEM ] [-LINES ] [-PROFILES ] [-DIST_LINE ] [-DIST_PROFILE ] [-NUM_PROFILE ]

-NUM_PROFILE: Profile Samples
Integer
Minimum: 3
Default: 10

I tried to delete the decimal point and zeros from the SAGA dialog, but it puts them right back as soon as I leave the field!
to This is like #26702. But a different SAGA module.

In QGIS 3.0.3:
Processing -> Toolbox -> SAGA -> Terrain Analysis - Profiles -> Cross profiles

'50.0' is not a correct numeric value for option 'NUM_PROFILE'.

Tried the default:
'10.0' is not a correct numeric value for option 'NUM_PROFILE'.

Looks like NUM_PROFILE is different from the other parameters:
Usage: saga_cmd ta_profiles 3 [-DEM ] [-LINES ] [-PROFILES ] [-DIST_LINE ] [-DIST_PROFILE ] [-NUM_PROFILE ]

-NUM_PROFILE: Profile Samples
Integer
Minimum: 3
Default: 10

I tried to delete the decimal point and zeros from the SAGA dialog, but it puts them right back as soon as I leave the field!

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms Regression Something which used to work, but doesn't anymore Easy fix labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Easy fix Processing Relating to QGIS Processing framework or individual Processing algorithms Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

1 participant