-
Notifications
You must be signed in to change notification settings - Fork 35
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
Investigation: storage for QuadEdge #8
Comments
I'm not sure I quite understand what you're working on here... So I'd like to be sure I understand what you are proposing. From time to time, I've thought about the idea of reading and writing the content of a TIN to a data file. This would be useful in the case where you wanted to re-use the same TIN structure at different times. Is that what you're trying to do? I think that you definitely are taking the right approach by starting with the semi-virtual implementation. |
Yes I want to reuse same TIN structure multiple times. SemiVirtual is indeed good start point.
Martin JANDA
26. 1. 2017 v 20:29, gwlucastrig <[email protected]>:
… I'm not sure I quite understand what you're working on here... So I'd like to be sure I understand what you are proposing.
From time to time, I've thought about the idea of reading and writing the content of a TIN to a data file. This would be useful in the case where you wanted to re-use the same TIN structure at different times. Is that what you're trying to do?
I think that you definitely are taking the right approach by starting with the semi-virtual implementation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Martin, |
I want to investigate possibility of custom storage format for QuadEdge. Creating TIN takes some time and loading can take less time.
No action is required. I will try to make some tests based on semi-virtual implementation.
The text was updated successfully, but these errors were encountered: