-
Notifications
You must be signed in to change notification settings - Fork 2
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: 646 write adaptation to file #650
feat: 646 write adaptation to file #650
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Validation on the test should be improve. I have a feeling it will not work when using the AnalysisResultWrapperExporter
, so it's better so have a proper test for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I still think you should be comparing the results of the generated results (you have the reference data "by hand") the issue can be merged.
Please keep in mind there are two remarks (one affects two similar pieces of code) to be addressed before merging.
Added an assert on the file content, although I'm not convinced it should be part of this test. We have other tests to check if the export itself goes well. |
Issue addressed
Solves #646
Code of conduct
What has been done?
Add "geometry" to the output gdf so it can be exported.
Checklist
black
andisort
definitions.master
.Additional Notes (optional)
N.A.