google-trends-api VS kuwala

So I am trying to get google trends data for a stock market project. While getting data, I am confused about the category to pass to the cat attribute. There are two possibilities. I tried 5 (Compute and Electronics or CE) and 13 (Internet and Telecom or IT) for Apple. Similarly, I want to scrape for Google, Amazon, Facebook, Microsoft and Tesla. So according to this page, what categories should I use. https://github.com/pat310/google-trends-api/wiki/Google-Trends-Categories. Thanks in Advance

Hi HN!

Google Trends is underrated. This huge search engine is somewhat a projection of what the public has on their minds at a given time.

However, Trends have no API and it's not easy enough to go check trends regularly. You have to remind yourself to go to Trends website, choose your country etc.

Twitter is the perfect platform to have this. I've made a network of Twitter bots for sharing the Trends of each country 3 times a day. It works for 13+ countries (check Following) right now. The bot first posts a generated image of 20 trending topics and headlines. Then lists the trending topics, and if the account has enough followers it posts one related news link for each topic.

I had to dispose several accounts as they got marked as spam, and once that happens there is no going back... That's why I first start with an image and the list of trends as tweets first, then enable links once there's a decent follower base (around +100). It was difficult but interesting in hindsight trying to escape Twitter's spam filter. I needed an SMS number for each account. Thankfully there are services giving you burner SMS numbers starting $0.05 . Just need to get lucky they won't ask the number twice.

Technically it's a simple node.js script running on Google Cloud Functions. The function is triggered every hour and it checks the current time of countries. If it matches it retrieves the trends using https://github.com/pat310/google-trends-api package, generates the trends image and posts tweets one by one.

The setup is fragile. The google-trends-api package seems to use an academic API for Trends and can be shut down any time. Also Twitter is strict about bots (forbidden according to terms) and might shut the accounts down anytime. Anyways, it was fun to build it and now it's quite easy to kickstart a Twitter bot

Looking forward for your comments and feedbacks! Also let me know if you have any idea how I can spread it more.

--> Google Trends Data for Regions (Coming Soon)

The tool goes beyond our previously published CLI tool (https://github.com/kuwala-io/kuwala/tree/master/kuwala) by providing a hostable solution with a user-friendly interface. We have not open-sourced it yet but a demo is available here: https://geosage.kuwala.io/.

Urban planners can utilize movement data to analyze foot traffic in different city zones. Marketers can leverage demographic data to tailor campaigns more effectively. Developers can build their apps on top of it.

To round it up .... GeoSage brings...

Unified Data Management: Access data from OSM, Facebook, and soon Google, all in one place.

--> https://github.com/kuwala-io/kuwala/blob/master/kuwala/pipelines/osm-poi/README.md

Googe Popular Times: Movement data can be also found on Google. When you search a location it is often shown how frequently a place was visited on an hourly-daily basis (on an index of 0-100). With this libary you can access all the Popular Times data for location and entire cities

What are the 5 hottest dbt Repositories one should star on Github 2022?

dbt is a software framework that sits in the middle of the ELT process. It represents the transformative layer after loading data from an original source. Dbt combines SQL with software engineering principles.

Here are my top5!

- Lightdash (https://github.com/lightdash/lightdash): Lightdash converts dbt models and makes it possible to define and easily visualize additional metrics via a visual interface.

- ⏎ re_data (https://github.com/re-data/re-data): Re-Data is an abstraction layer that helps users monitor dbt projects and their underlying data. For example, you get alerts when a test failed or a data anomaly occurs in a dbt project.

- evidence (https://github.com/evidence-dev/evidence): Evidence is another tool for lightweight BI reporting. With Evidence, you can build simple reports in "medium style" using SQL queries and Markdown.

- Kuwala (https://github.com/kuwala-io/kuwala): With Kuwala, a BI analyst can intuitively build advanced data workflows using a drag-drop interface on top of the modern data stack without coding. Behind the Scenes, the dbt models are generated so that a more experienced engineer can customize the pipelines at any time.

- fal ai (https://github.com/fal-ai/fal): Fal helps to run Python scripts directly from the dbt project. For example, you can load dbt models directly into the Python context which helps to apply Data Science libraries like SKlearn and Prophet in the dbt models.

Kuwala ( https://github.com/kuwala-io/kuwala ) Kuwala is a data workspace that consolidates the Modern Data Stack and makes it usable for BI analysts and Engineers. Even though dbt is originally targeted at BI Analysts, dbt is mainly used by Engineers. This shifts a large amount of pipeline engineering effort to the IT department. With Kuwala, a BI analyst can intuitively build advanced data workflows using a drag-drop interface on top of the modern data stack without coding. Consequently, the BI Analyst can work more iteratively and maintain the complete workflow from source to metrics in a dashboard. Under the hood and Behind the Scenes, the dbt models are generated so that a more experienced engineer can customize the pipelines at any time. In addition, engineers can easily convert dbt models into reusable “drag and drop” components.

- 🧱 Kuwala: With Kuwala, a BI analyst can intuitively build advanced data workflows using a drag-drop interface on top of the modern data stack without coding. Behind the Scenes, the dbt models are generated so that a more experienced engineer can customize the pipelines at any time.

I have then built with a friend this here: https://github.com/kuwala-io/kuwala/tree/master/kuwala/pipelines/admin-boundaries . So the script is extracting the boundaries from OSM and cleans it (forms the hierachy and connect shapes). However, it did not lift up and I had not the feeling this was in the end an interesting feature for the community. It would be wonderful to hear your feedback and maybe find someone to pick it up :-)

Hi, we have a nice slack channel, here: https://kuwala-community.slack.com/ssb/redirect and my repo on Github is here available: https://github.com/kuwala-io/kuwala

**Global Admin Boundaries:** A huge problem that often people feel when working with location data is aggregating the data into different geo-based slices (country level, admin level, or even smaller into sub-districts). Here is a repo that cleaned the data out of Open Street Map for geo boundaries worldwide from very broad to a very small granularity --> https://github.com/kuwala-io/kuwala/blob/master/kuwala/pipelines/admin-boundaries/README.md

If it is about location data you should know OpenStreetMap. It's the biggest Database with meta info on location. It's not perfect but big companies like Mapbox, Apple, and Microsoft rely on it. Since the API is kind of messy, you can load with this repository whole cities information smoothly into a PostGres --> https://github.com/kuwala-io/kuwala/blob/master/kuwala/pipelines/osm-poi/README.md