mmcloughlin/globe

Globe wireframe visualizations in Golang

globe's Issues

Non-issue

Just wanna say, this is pretty lit 🔥📣🔥

culling the "wires" in the background

First.. this is cool and amazingly easy. I could really see me using this in some of the visualizations I do for scientific drilling data from NSF.

Second.. I am not a graphics person.. so forgive the poorly worded question..

The visuals are ncie, but might get a bit confusing given the wireframe aspect of these where one can see through to the continent coastlines on the other side of the globe.

Is there there any chance in the code base to enable a situation where the globe surface is opaque?

regardless.. thanks.. would love to see more of these types of packages in Go for geospatial data

Text on globe

Are you planning to add text to the map ? I think you've started a great and fun mapping project !

Overlapping points causes a turquoise noise/artefact

Firstly thanks for the great library! Top work.

I noticed that using GeoJSON files with overlapping points sometimes produces these strange turquoise noise effects. Any way to combat/fix that behaviour?

CenterOn has confusing behavior when called more than once

As noticed in #3 the CenterOn method does the wrong thing when called multiple times. This is because the rotation is applied assuming the default initial state of the globe.

It should be an easy fix to remember the current position the globe has been rotated to and apply a rotation relative to that.

Globe animations/GIFs?

It would be cool to be able save a rotating globe as a GIF (or similar format). This could possibly be done through sewing generated images together (using something like ffmpeg).

TestGraticuleCenterOn fails on arm64

On Apple M1:

> GOARCH=arm64 go test -v
=== RUN   TestGraticule
--- PASS: TestGraticule (0.10s)
=== RUN   TestGraticuleCenterOn
    globe_test.go:50:
        	Error Trace:	globe_test.go:50
        	            				globe_test.go:63
        	Error:      	Not equal:
        	            	expected: "04c8271e8d48ea580a6d340d9be7a261"
        	            	actual  : "80e7f15997d3597d8cc451876e0bc7ae"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-04c8271e8d48ea580a6d340d9be7a261
        	            	+80e7f15997d3597d8cc451876e0bc7ae
        	Test:       	TestGraticuleCenterOn
--- FAIL: TestGraticuleCenterOn (0.09s)
=== RUN   TestDrawDots
--- PASS: TestDrawDots (0.03s)
=== RUN   TestDrawLand
--- PASS: TestDrawLand (0.06s)
=== RUN   TestDrawCountries
--- PASS: TestDrawCountries (0.08s)
=== RUN   TestLine
--- PASS: TestLine (0.02s)
=== RUN   TestRect
--- PASS: TestRect (0.02s)
=== RUN   TestCartestian
--- PASS: TestCartestian (0.00s)
=== RUN   TestHaversine
--- PASS: TestHaversine (0.00s)
=== RUN   TestIntermediate
--- PASS: TestIntermediate (0.00s)
=== RUN   TestDestination
--- PASS: TestDestination (0.00s)
FAIL
exit status 1
FAIL	github.com/mmcloughlin/globe	0.597s

The test still passes under amd64. Unclear to me right now why the output should be different. On visual inspection, the images look right on both architectures, but there are tiny pixel value differences.