Closed johngallo closed 1 year ago
I have this issue (Images ) in relation with build network and Map Linkages, ERROR: It looks like decimals are indicated by commas instead of decimal points.
Try changing your Windows Regional and Language settings to English (United States) or another convention that uses decimal points. I've tried to change the Lenguage setting and when try again the tool a new error appear , perhaps posibble generate by the Python configuration. Someone with the same issue or idea ?
Hello Ruborlado,
Please send the log file with the most recent error message if you would like people to comment on it.
I believe it is at: [project folder]\output[output name]\run_history\log[date]_Linkage Mapper.txt
Thank you,
John
John Gallo, Ph.D. Senior Scientist Conservation Biology Institute https://consbio.org/people/staff/john-gallo 136 SW Washington Avenue, Suite 202 Corvallis, OR 97333 Remote Office: Inglenook, CA Phone: 707.357.3982 Twitter: @johnagallo https://twitter.com/johnagallo Updates: Action Research Newsletter https://consbio.us9.list-manage.com/subscribe?u=3dea159e4cbe0a0ff3b43eadd&id=e3bd82fd81
On Tue, Nov 29, 2022 at 12:54 AM ruborlado @.***> wrote:
I have this issue (Images ) in relation with build network and Map Linkages, ERROR: It looks like decimals are indicated by commas instead of decimal points.
Try changing your Windows Regional and Language settings to English (United States) or another convention that uses decimal points. I've tried to change the Lenguage setting and when try again the tool a new error appear , perhaps posibble generate by the Python configuration. Someone with the same issue or idea ?
— Reply to this email directly, view it on GitHub https://github.com/linkagescape/linkage-mapper/issues/166#issuecomment-1330292236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD7CJ2ZNQ4ZM4TCLTW56I6TWKXAD5ANCNFSM6AAAAAAQG6KCSQ . You are receiving this because you authored the thread.Message ID: @.***>
Solved thanks to community ID of problem and the coded fix by @dkav
LM works in all the other previous versions of ArcPro though. Wait for v 3.1 to come out to see if issue fixes itself, otherwise needs fixing.
See community dialog from a month or so ago for exact issue.