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.

Sign up for GitHub

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

Jump to bottom

Error with UTF-8 characters in outputted .osm file for stops #56

Closed
wolfy1339 opened this issue Mar 22, 2024 · 2 comments · Fixed by #57
Closed

Error with UTF-8 characters in outputted .osm file for stops #56

wolfy1339 opened this issue Mar 22, 2024 · 2 comments · Fixed by #57

Comments

@wolfy1339
Copy link
Contributor

wolfy1339 commented Mar 22, 2024 •
edited
Loading

In the outputted *.osm file for stops, there is an issue with encoding UTF-8 characters

Specifically, it's encoding a é as é
@wolfy1339 wolfy1339 changed the title Error with UTF-8 characters in outputted .osm file Error with UTF-8 characters in outputted .osm file for stops Mar 22, 2024
@Gabboxl
Copy link
Owner

Gabboxl commented Mar 23, 2024

thanks, will fix it

@wolfy1339
Copy link
Contributor Author

To add a bit more context, in the gtfs-import.properties file I entered the operator's name which contains the é character.

There is the stop name from the GTFS feed, and from the gtfs-import.properties file

wolfy1339 added a commit to wolfy1339/gtfs-osm-import that referenced this issue May 1, 2024
@wolfy1339
Load properties file with UTF-8 encoding
c2fb9b1 
Fixes Gabboxl#56
@wolfy1339 wolfy1339 mentioned this issue May 1, 2024
Merged
@Gabboxl Gabboxl closed this as completed in 6a5874c Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix problems with UTF-8 encoding wolfy1339/gtfs-osm-import
2 participants
@wolfy1339 @Gabboxl