Skip to content

Uncatched error when csv colums cannot be found #2

@GrHalbgott

Description

@GrHalbgott

When using new solar exposure files (csvs), the columns can be named differently. This can be changed in developer_config.yaml.
However, the error that the columns cannot be read is uncatched and will be printed for the whole loop.

Catch following errors and handle them accordingly:

raise ValueError(str(e))
      ValueError: 500 ({'error': {'code': 2099, 'message': 'Illegal column name: 17010'}, 'info': {'engine': {'build_date': '2024-03-21T13:55:54Z', 'version': '8.0.0'}, 'timestamp': 1755081936016}})
raise exceptions.ApiError(
      openrouteservice.exceptions.ApiError: 500 ({'error': {'code': 2099, 'message': 'Illegal column name: 17010'}, 'info': {'engine': {'build_date': '2024-03-21T13:55:54Z', 'version': '8.0.0'}, 'timestamp': 1755081936016}})

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions