Docs improvements and dtype fixes #93
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…than field size Previously, field decimal precision wasn't actually used, nr was just stored in original precision. Now we format the nr before saving, which also fixes problem of correctly saving very small or big floats such as 4e-13. Fixes #89.
|
Travis fails are simply due to not having synced the most recent test files. Quick fix afterwards. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Much needed docs on field types (#73). Hopefully these look good to you @GeospatialPython, also since I used these as a partial replacement for the previous attributes writing docs.
Also fixed decimal precision field saving (#89), autocapping too large nrs, and misc small docs updates.
Fixed minor point() shapetype bug.
Added docs table of cotents.