rakeda

Thanks for your feedback Bob, the website is currently optimized for viewports smaller than 1920x1080p but I do plan support for the future.

Thank you for the advice, will incorporate smoother zooming, theres a trick between feeling snappy and responsive and smooth but sluggish.

There might be, but that would be missing out on half of the fun. Plus the real development challenge wasn't the frontend, but the database strategy, caching strategy, and edge availability. As with all my projects they serve as a way for me to learn.

Yup, if there is a bit more support ill begin to add in the mid-tier paid services, but I feel like its in a good spot for now. Working on terrain right now!

From what I put on reddit:

"The globe itself is just a black ball that hides anything behind it. On top of that we draw the grid (lat/lng) by looping through coordinates and connecting dots on the surface (same math youd do for platpoints on a map, just wrapped around the sphere). The coastlines and borders come from free geo data files and just drawn on the sphere, anchored.

The atmosphere and a majority of the affects are just tiny shaders (maybe 10 lines of code each) which gives it a strong 3d affect.

Everything else, data points, flights, events, is just coordinates associated with database entries and drawn ui components.

So if you tried it before and went down the rabbit hole of 3D and triangulation, you were probably overthinking it the same way I did at first. The wireframe aesthetic actually works in your favour because you never have to fill anything in"

It was less about performance and more about the visual storytelling. The globe itself isnt actually a 3d model, all of this are rendered in three.js as two dimensional wraps, but the performance is hit with the amount of data.

That is high praise. Thank you.

Satellite GIS for all vessels is pretty pricey. Waiting to see this project grow before investing in that realtime data. For now we have coastline GIS for vessels.

Some layers have additional enrichment, data linking everything internal external is a major goal for the project!

Military installations currently need to be sanitized and cleaned out. Will be working on later today. The source is unreliable and much of the data can be stored internally instead of public dataset.

Mobile has been a common complaint that I have received. Planning on conquering this soon! (90% of all initial traffic is mobile).

On it right now, should see the change live in 10 minutes! Was supposed to only show when imagery was selected.

I'm routing and caching a majority of the data into my own database so that all usage and rates are through my service. There are some client based api calls that are made (mostly around existing enrichment) but 95% of traffic hits the db my workers populate.