a thoughtful web.
Good ideas and conversation. No ads, no tracking.   Login or Take a Tour!
comment
user-inactivated  ·  1554 days ago  ·  link  ·    ·  parent  ·  post: Hubski Craft Fair v1.50 - January 16, 2020

Truth be told, I merely know a little about a lot, so I'm not mega-fluent in lingo. I'm assuming ML means machine learning. This is the first time I've seen Keras, and a google search into it looks hella neat. Looking beyond my scope, currently.

What I'm using is solely Python libraries. For API access ('requests' package to retrieve, and 'pandas' for data manipulation) to both that dataset and Google API ('bokeh' for visualization, but 100% planning on something else) to make a nicer map. Those parts are complete thus far. Also, some dynamic querying (meaning you can look at all fireballs within a specific year or month or recurring month/year/decade) rather than just 'from this date backward/forward'.

The following checklist is sorta me cleaning out my brain space, but also goal setting to look back on here.

What I'd like to present in the thread later is a cleaner version:

- not using Bokeh

- show generalized shockwave impact areas per fireball, see: Chelyabinsk:

- be able to share my code without sharing my Google Maps API key (hehe)

- clean up symbology with proper visual scaling per impact energy

Stretch Goals:

- Better hover tool-tips

- Create GUI to dynamic query, rather than going into the code to query

- Efficiently import CSV data into a PostgreSQL database, and pull from there rather than API since the CSVs give velocity components.

I really just wanted to make the map on the site more interactive, and less static.... Also gives me something to present to employers in an application to NASA. O:^)