正在加载视频...

视频加载失败

How I map millions of features without breaking the bank: - Data prep: R - Data tiling: tippecanoe, PMTiles - Deployment: Cloudflare R2 / Workers - Mapping: MapLibre / R / mapgl Lightning-fast with edge caching, minimal hosting costs See it in action:

31,134 次观看 • 7 个月前 •via X (Twitter)

14 条评论

ᑕᕼᗩᗪᗷᖇ 的头像
ᑕᕼᗩᗪᗷᖇ7 个月前

Curious if you have tried for the viz?

Kyle Walker 的头像
Kyle Walker7 个月前

yeah is great

Alex Allchin 的头像
Alex Allchin7 个月前

Your R usage seems to be a bit of an outlier in the GIS community. What drives your preference to it?

Kyle Walker 的头像
Kyle Walker7 个月前

It does absolutely everything I want! R has a very strong GIS community going back 20+ years. I was just on a podcast where I went into more detail on this topic, if you're interested:

Alex Allchin 的头像
Alex Allchin7 个月前

Yeah, maybe I'm just in the wrong bubble. I haven't used R in many years but might have to give it another look in.

First Miles 的头像
First Miles7 个月前

Amazing as always Kyle

Kyle Walker 的头像
Kyle Walker7 个月前

thanks!

Greg Field 的头像
Greg Field7 个月前

PMTiles with Cloudfrare / R2 with workers works great!

josek 的头像
josek7 个月前

wow : Deployment: Cloudflare R2 / Workers

HiddeKehrer 的头像
HiddeKehrer7 个月前

this is brilliant – cloudflare workers + r2 for geo-distributed features is exactly what teams need to avoid the aws trap. have you considered for the full stack?

. 的头像
.7 个月前

Can you divide it by ethnic groups, maybe categorize it from what country they are mostly? that would be interesting to see

martin 的头像
martin7 个月前

will be trying out your formula. it's so slick and fast in the browser! thank you for sharing Kyle.

Josh Santiago 的头像
Josh Santiago7 个月前

This looks great. Have you considered using H3 hexagonal grids for density aggregation? The point-level granularity is compelling, but at city scale I start to lose the broader spatial pattern, which the hex view might surface macro trends.

Kristian Freeman 的头像
Kristian Freeman7 个月前

This is super cool - is it open-source somewhere? We're working on something on my team at CF to share OSS projects, would love to feature this

相关视频

I built a self-hosted Sentry clone that runs entirely on Cloudflare Workers, and I think it showcases one of the most underrated features in the Cloudflare ecosystem: Service Bindings. Let me explain why this matters. When you have multiple Cloudflare Workers (an API, a webhook handler, a cron job), they all need common things: error tracking, authentication, rate limiting, metrics. The typical solution? External HTTP calls to third-party services. That means: - 50-200ms latency per call - Egress fees - Your data leaving your infrastructure - Another vendor to manage Service bindings let Workers call each other directly inside Cloudflare's network. No HTTP. No internet. Just internal RPC with <5ms latency. With Workers Sentinel, any Worker in my account can just point Sentry-SDK into the Service binding, and have all errors flow into one centralized dashboard, stored in Durable Objects with SQLite. No external calls. No added latency. Service bindings aren't just for error tracking. You can centralize: 🔐 Authentication — One Worker that validates tokens for all your services 📊 Metrics — Centralized collection without external observability costs 🚦 Rate Limiting — Shared counters that actually work across Workers 🚩 Feature Flags — Instant propagation, no deployment needed Think of it as building your own internal microservices mesh, but at the edge, with zero network overhead. Workers Sentinel uses two Durable Objects: - AuthState (singleton) — users, sessions, projects - ProjectState (per-project) — issues, events, stats Events are fingerprinted and grouped intelligently. The dashboard is a Vue.js app served from the same Worker. I could say i built this to learn Durable Objects or that I needed error tracking for side projects, but honestly I just need a way to show my wife why I'm sending $200/month to some guy named Claudio who apparently helps me write code. The whole thing is open source. Deploy it to your Cloudflare account, point your Sentry SDKs at it, and you're done. But more importantly: take a closer look at service bindings. They're the glue that turns a collection of Workers into an actual platform. Most Cloudflare customers I talk to aren't using them, and they're missing out. To the Sentry team: I love your work. Genuinely. Sentry is battle-tested, has incredible features, and is what you should use for anything that matters. This project is a toy. A learning exercise. A weekend hack that got slightly out of hand. Please do not trust your production errors to this dummy clone. If your startup goes down at 3 AM because Workers Sentinel missed an edge case, that's on you. I warned you. Use the real thing. But if you want to learn about Durable Objects, service bindings, and how error tracking works under the hood? Clone away. Your Workers shouldn't be islands. Connect them.

Gabriel Massadas

28,840 次观看 • 8 个月前

A new roadmap. A New Era of The Graph 🗺️ The Graph’s new roadmap introduces a bold and transformative vision for the future of The Graph! The new R&D roadmap details an expansion of The Graph’s ability to serve web3’s growing demands for data access, while better serving builders and protocol contributors, and improving the overall simplicity and efficiency of the network. After three years of serving builders, The Graph Network is mature, reliable, and performant. The Graph ecosystem has followed through on its commitment to democratize access to blockchain data while also establishing subgraphs as a web3 standard. But The Graph’s innovation journey doesn’t end there. The New Era of The Graph is organized into five core objectives: 1️⃣ World of Data Services: Expanding to provide new data services beyond subgraphs to deliver a rich market of data on the network, serving novel use cases for data scientists and more. This will include more data sources, new query languages, and support for LLMs. 2️⃣ Developer Empowerment: Supporting developers through enhanced DevEx and tooling by introducing streamlined billing, clear pricing models, a new free query plan, and reduced gas fees. A more SaaS-like experience for devs, without compromising on decentralization! 3️⃣ Protocol Evolution & Resiliency: Delivering improvements resulting in a more resilient, flexible, and simple protocol, including updates to delegation. 4️⃣ Optimized Indexer Performance: Boosting network performance with improved Indexer tooling and operational capabilities to deliver increased scalability, reduce costs, and enhanced network reliability. 5️⃣ Interconnected Graph of Data: Creating tools for composable data and a global, organized knowledge graph – interlinking open data and making it easier to build upon. The new roadmap sets in motion an exciting evolution in web3 data infrastructure. In a phased rollout, The Graph will introduce many new features and benefits, including the integration of new data services, new query languages, enhanced developer tooling, improved UX + UI, alongside greater protocol efficiency and resilience. As this new era unfolds, The Graph crystallizes as the connective tissue across the many layers of the web3 stack, evolving into a comprehensive, interwoven graph of data equipped to serve every project dreamt up by web3’s innovators. Read the full announcement linked in the comment below!

The Graph

426,146 次观看 • 2 年前

In the second episode of Scenius Studio's mini-series "The Use-Case", I sit down with Andrej Co-Founder of touch grass. Grass gives users the ability to earn ownership in the Grass network by supplying the protocol with their unused internet bandwidth for data scraping purposes (something that is already happening to most of us and we don’t get paid!). The grass protocol packages this scraped web data and sells it to AI companies who have insufficient data to further develop their models. With over 3 millions users and millions of annualized revenue, Grass is a real commercial business with a roadmap that makes it one of the most exciting projects at the intersection of crypto x AI and data. In this episode we discuss: ➔ Andrej’s background in physics, finance, and sports betting ➔ Big companies using your IP address without your knowledge or permission ➔ How the Grass protocol puts a toll booth on your internet bandwidth highway ➔ Packaging web scraped data and selling it to AI companies building Multi-Modal models ➔ Dynamics between the Grass Protocol and the labs entity developing Grass’ IP ➔ Protocol design decisions to ensure that all tokenholders (VCs, team, and community) are aligned ➔ Why Grass needed to be built on crypto rails to maximize its potential ➔ The future of LLMs and how they will search for context and information Hope you enjoy this episode of Scenius Studio's "The Use-Case". Links to listen in bio or below👇

Ben Jacobs

22,468 次观看 • 1 年前