Added Markdown and HTML rendering of Spark DataFrames #294
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
metasim
commented
Aug 20, 2019
metasim
commented
Aug 20, 2019
metasim
commented
Aug 20, 2019
Signed-off-by: Jason T. Brown <jason@astraea.earth>
Signed-off-by: Jason T. Brown <jason@astraea.earth>
vpipkt
suggested changes
Aug 20, 2019
Member
vpipkt
left a comment
vpipkt
left a comment
There was a problem hiding this comment.
A few lingering things from PR #284 that i think i did not get in until after merge.
In some of the rendered HTML docs the resulting tables were really wide, not responsive, and no scroll bar. I am not sure if this is an issue any more.
here was a specific trouble spot: #284 (comment)
One problem for me now is I am getting errors building the docs: org.pegdown.ParsingTimeoutException there is some really long un-truncated line that is being output someplace. Looks like time series markdown is 5MB...
core/src/main/scala/org/locationtech/rasterframes/util/package.scala
Outdated
Show resolved
Hide resolved
core/src/main/scala/org/locationtech/rasterframes/util/package.scala
Outdated
Show resolved
Hide resolved
* develop: (21 commits) Add ignored test from stale branch Expressions returning primitives can't return `null`, so changing how constant tiles are created to keep catalyst optimizer from pruning them. mm m Added tests for rf_convert_cell_type and rf_with_no_data. Fixed a bug with counting data/no_data cells on constant tiles. a Time series doc reorg vector filtering time series park geojson filepath variabl Additional fixes for issue locationtech#242 that cropped back up. ci tweak to get error markdown Attempt to save markdown artifacts on failed docs build. Attempt to save markdown artifacts on failed docs build. Tweak partitions Add folium to setup / requirements DataFrame API only, folium display of temp file Reenabled test (mostly) covered by 242. Fix for columnar functions which accept `Tile` or `ProjectedRasterTile`, but claimed all return values were `Tile`. This was problematic whenever the `Tile` as reified, and the serialization of `ProjectedRasterTile` confused the `Tile` deserializer. Bump python development version to match JVM version Updated copyright in template. Update LICENSE ...
…ipython-display-tweaks * commit '1ea29f2ccdc74eb3e900fbb075eae6e9421ea11a': Bug was with changes to `rf_with_no_data` acceptance of either `Double` or `Int`, and then incorrectly changing floating point tiles into a float cell type. Fixes locationtech#304. Updated ShowableTile to render NoData values differently. Moved array function tests to RasterFunctionsSpec. # Conflicts: # pyrasterframes/src/main/python/pyrasterframes/rf_ipython.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.