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

feat(import-export): EPSG not mandatory and fix encoding issue #428

Merged
merged 1 commit into from
Sep 25, 2019

Conversation

cbourget
Copy link
Collaborator

Please check if the PR fulfills these requirements

What is the current behavior? (You can also link to an open issue here)

  • "EPSG" is mandatory in the EPSG code
  • Encoding issue may happen when exporting files with ogre
  • GPX files are exported with ogre and it's not so good at it

What is the new behavior?

  • "EPSG" is not mandatory in the EPSG code
  • No more encoding issue when exporting files with ogre
  • GPX files are exported using OL. Some files that ogre wouldn't process now work perfectly fine

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications:

Other information:

@mbarbeau mbarbeau merged commit ee37eb3 into master Sep 25, 2019
@mbarbeau mbarbeau deleted the import-export-enchancement branch September 25, 2019 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants