Skip to content

[FEAT] Use proper tool name in error message, reference Osmium or osmconvert #232

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

Merged
merged 1 commit into from
Nov 19, 2023

Conversation

alfh
Copy link
Contributor

@alfh alfh commented Nov 19, 2023

This PR…

  • Trivial fix for error message being emitted when the extract phase fails.

Considerations and implementations

I assume this is a left over, copy/paste error, or that the osmosis was used for this phase earlier.
Tidy up the message, so it is clear where osmium is used and where osmosis is used.

Also wonder a bit why osmconvert is used on Windows, and not Osmium, I would assume we prefer
to use the same tools on Windows and Linux, to keep things simple and similar. But that is not relevant for this PR.

How to test

  1. ...
  2. ...

Pull Request Checklist

@treee111
Copy link
Owner

treee111 commented Nov 19, 2023

thanks for the unification PR! Also noticed that while researching for your question #229 (comment).
cleaned up the PR title + text. pylint checks have been failing before already

@treee111 treee111 changed the title Use proper tool name in error message, reference Osmium or osmconvert [FEAT] Use proper tool name in error message, reference Osmium or osmconvert Nov 19, 2023
@treee111 treee111 merged commit 41fdbf7 into treee111:develop Nov 19, 2023
treee111 pushed a commit that referenced this pull request Mar 22, 2024
…convert (#232)

Use proper tool name in error message, reference Osmium or osmconvert
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants