We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#150 improved show, but now
using LibGEOS ls = LineString([[cosd(a), sind(a)] for a in range(0, stop=360, length=1000)])
more than fills the screen. Compactified output of display would be preferable (similar to how rand(100,100) fills only one screen on REPL).
display
rand(100,100)
Also, note that ?show says
?show
The representation used by show generally includes Julia-specific formatting and type information, and should be parseable Julia code when possible.
Therefore, I think readgeom("POLYGON ((0 0, 1 0, 0 1, 0 0))") style has merits for show. Output of display could be POLYGON ((0 0, 1 0, 0 1, 0 0)).
readgeom("POLYGON ((0 0, 1 0, 0 1, 0 0))")
show
POLYGON ((0 0, 1 0, 0 1, 0 0))
The text was updated successfully, but these errors were encountered:
No branches or pull requests
#150 improved show, but now
more than fills the screen. Compactified output of
display
would be preferable (similar to howrand(100,100)
fills only one screen on REPL).Also, note that
?show
saysTherefore, I think
readgeom("POLYGON ((0 0, 1 0, 0 1, 0 0))")
style has merits forshow
. Output ofdisplay
could bePOLYGON ((0 0, 1 0, 0 1, 0 0))
.The text was updated successfully, but these errors were encountered: