Podcasts about OpenStreetMap

This show has been flagged as Explicit by the host. ----------------- NYE 2025 6 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ [pdp8online:]( https://www.pdp8online.com/asr33/asr33.shtml) The ASR33 is a printing terminal and a program storage device (paper tape) used... [wikipedia:]( https://en.wikipedia.org/wiki/Radar_in_World_War_II) Radar in World War II greatly influenced many important aspects of the conflict... [ll:]( https://www.ll.mit.edu/impact/commemorating-scr-584-radar-historical-pioneer) SCR-584 radar developed at the MIT Radiation Laboratory in the 1940s... [wikipedia:]( https://en.wikipedia.org/wiki/PDP-1) The PDP-1 (Programmed Data Processor-1) is the first computer in... [w140:]( https://w140.com/tekwiki/wiki/Intel_8086) Intel 8086 is a 16-bit microprocessor monolithic integrated circuit introduced in 1978... [wikipedia:]( https://en.wikipedia.org/wiki/Chaosnet) Chaosnet is a local area network technology. It was first developed... [wikipedia:]( https://en.wikipedia.org/wiki/Hercules_Graphics_Card) The Hercules Graphics Card (HGC) is a computer graphics controller [wikipedia:]( https://en.wikipedia.org/wiki/ARPANET) The Advanced Research Projects Agency Network (ARPANET) was the first wide-area packet-switched network with... [goodreads:]( https://www.goodreads.com/book/show/281818.Where_Wizards_Stay_Up_Late) Where Wizards Stay Up Late: The Origins of the Internet [wikipedia:]( https://en.wikipedia.org/wiki/DTMF) Dual-tone multi-frequency signaling (DTMF) is a telecommunication signaling system. [wikipedia:]( https://en.wikipedia.org/wiki/Asperger_syndrome) Asperger syndrome (AS), also known as Asperger's syndrome or Asperger's, is a diagnostic label... [wikipedia:]( https://en.wikipedia.org/wiki/Autism) Autism spectrum disorder[a] (ASD), or simply autism, is a neurodevelopmental disorder... [wikipedia:]( https://en.wikipedia.org/wiki/Diagnostic_and_Statistical_Manual_of_Mental_Disorders) Diagnostic and Statistical Manual of Mental Disorders [wikipedia:]( https://en.wikipedia.org/wiki/DSM-5) The Diagnostic and Statistical Manual of Mental Disorders, Fifth Edition (DSM-5) [wikipedia:]( https://en.wikipedia.org/wiki/Agoraphobia) Agoraphobia[1] is a mental and behavioral disorder,[5] specifically an anxiety disorder characterized by [wikipedia:]( https://en.wikipedia.org/wiki/Nice_guy) "Nice guy" is an informal term, commonly used with either a literal or a sarcastic meaning... [ncbi:]( https://pubmed.ncbi.nlm.nih.gov/31468149/) Predictive utility of autistic traits in youth with ADHD [wikipedia:]( https://en.wikipedia.org/wiki/Causes_of_autism) Many causes of autism, including environmental and genetic factors... [massgeneral:]( https://www.massgeneral.org/psychiatry/treatments-and-services/clinical-and-research-program-for-autism-spectrum-disorder) Bressler Program for Autism Spectrum Disorder [wikipedia:]( https://en.wikipedia.org/wiki/International_Organization_for_Standardization) International Organization for Standardization [iso:]( https://www.iso.org/home.html) The International Organization for Standardization [wikipedia:]( https://en.wikipedia.org/wiki/Media_Transfer_Protocol) The Media Transfer Protocol (MTP) [wikipedia:]( https://en.wikipedia.org/wiki/Network_Time_Protocol) The Network Time Protocol (NTP) is a networking protocol for clock synchronization between... [wikipedia:]( https://en.wikipedia.org/wiki/OpenSSL) OpenSSL is a software library for applications that provide secure communications over computer networks... [wikipedia:]( https://en.wikipedia.org/wiki/Ntpd) The Network Time Protocol daemon (ntpd) is an operating system program that maintains the system time... [wikipedia:]( https://en.wikipedia.org/wiki/Eminent_domain) Eminent domain [a], also known as land acquisition, [b] compulsory purchase, [c] resumption... [amtrak:]( https://www.amtrak.com/train-routes) Amtrak Routes & Destinations [wikipedia:]( https://en.wikipedia.org/wiki/Dragline_excavator) A dragline excavator is a heavy-duty excavator used in civil engineering and surface mining. [raleighcounty:]( https://raleighcounty.gov/about-county-government-in-west-virginia/) ...attempt to introduce the township system was made in West Virginia's first constitution... [wikipedia:]( https://en.wikipedia.org/wiki/IRC) IRC (Internet Relay Chat) is a text-based chat system for instant messaging. [openstreetmap:]( https://www.openstreetmap.org/) OpenStreetMap is a free, open map database updated and maintained by a community of... [wineauthorities:]( https://durham.wineauthorities.com/product/peirano-estate-red-blend-the-other-2021/) Red Blend “The Other” [untappd:]( https://untappd.com/b/outer-range-brewing-rockies-alps-in-the-steep-ddh-mosaic/5675887) In the Steep DDH (Mosaic) [untappd:]( https://untappd.com/b/outer-range-brewing-rockies-alps-in-the-steep/2002572) In the Steep [amsterdambeer:]( https://amsterdambeer.com/products/boneshaker-ipa-473ml-can?variant=39251514654791) Boneshaker is brewed with copious amounts of hops balanced with... [bigskybrew:]( https://bigskybrew.com/beers/moose-drool/) Moose Drool [beeradvocate:]( https://www.beeradvocate.com/beer/profile/1251/112788/) Double Pig's Ear [beeradvocate:]( https://www.beeradvocate.com/beer/profile/48912/41665/) Pig's Eye Ice [theshedbrewery:]( https://theshedbrewery.com/) The Shed Brewery [wikipedia:]( https://en.wikipedia.org/wiki/Private_Stock_(malt_liquor)) Private Stock (malt liquor) [wikipedia:]( https://en.wikipedia.org/wiki/Colt_45_(malt_liquor)) Colt 45 (malt liquor) [ebay:]( https://www.ebay.it/itm/275280350569) Patch liquore di malto SINGOLA COLT 45 COOL [wikipedia:]( https://en.wikipedia.org/wiki/Haffenreffer_Brewery) Haffenreffer Brewery [beeradvocate:]( https://www.beeradvocate.com/beer/profile/24964/669/) Haffenreffer Private Stock [justia:]( https://trademarks.justia.com/737/23/great-wall-vodka-imported-from-the-people-s-republic-of-china-73723624.html) GREAT WALL VODKA IMPORTED FROM THE PEOPLE'S REPUBLIC OF CHINA [wikipedia:]( https://en.wikipedia.org/wiki/Everclear) Everclear is an American brand name of a line of rectified spirit (also known as grain alcohol and neutral spirit) [wikipedia:]( https://en.wikipedia.org/wiki/Bacardi_151) Bacardi 151 is a discontinued brand of highly alcoholic rum... [caskers:]( https://www.caskers.com/vermont-ice-maple-bourbon-whiskey/) Vermont Ice Maple Bourbon Whiskey [greatamericanbeerfestival:]( https://www.greatamericanbeerfestival.com/) The Great American Beer Festival (GABF) [wikipedia:]( https://en.wikipedia.org/wiki/Great_American_Beer_Festival) The Great American Beer Festival (GABF) [vermontsalumi:]( https://www.vermontsalumi.com/) At Vermont Salumi, we embrace the art of salumi-making... Provide feedback on this episode.

In diesem Deep Dive geht es um eine Art von Produkt, das so gut wie alle regelmäßig nutzen. Egal ob im Auto, zu Fuß, auf dem Fahrrad oder Motorrad – Navigationssysteme sind aus unserem modernen Alltag kaum mehr wegzudenken.Dennis und Jan haben in dieser Folge Besuch von Robin Boldt im Podcast-Studio. Robin ist der Gründer von Kurviger, einer Navigations-App speziell für Motorradfahrer:innen. Das macht ihn zum idealen Partner für ein Gespräch über die Entwicklung maßgeschneiderter Routenführung.Robin berichtet, wie Kurviger Open-Source-Software wie GraphHopper und -Datenquellen wie OpenStreetMap nutzt und diese mit eigenen Daten und Berechnungen anreichert, um so eine Navigation basierend auf individuellen Wünschen zu ermöglichen.Außerdem sprechen wir mit Robin über die Herausforderungen im UX-Design der App und wie man Ablenkungen während der Fahrt verhindert. Welche technischen Hürden Navigations-Apps vom Offline-Support bis zur Sprachausgabe sonst noch überwinden müssen, erfahrt ihr in dieser Folge.Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback: podcast@programmier.barFolgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. BlueskyInstagramLinkedInMeetupYouTubeMusik: Hanimo

Brandon Liu is an open source developer and creator of the Protomaps basemap project. We talk about how static maps help developers build sites that last, the PMTiles file format, the role of OpenStreetMap, and his experience funding and running an open source project full time. Protomaps Protomaps PMTiles (File format used by Protomaps) Self-hosted slippy maps, for novices (like me) Why Deploy Protomaps on a CDN User examples Flickr Pinball Map Toilet Map Related projects OpenStreetMap (Dataset protomaps is based on) Mapzen (Former company that released details on what to display based on zoom levels) Mapbox GL JS (Mapbox developed source available map rendering library) MapLibre GL JS (Open source fork of Mapbox GL JS) Other links HTTP range requests (MDN) Hilbert curve Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: I'm talking to Brandon Liu. He's the creator of Protomaps, which is a way to easily create and host your own maps. Let's get into it. [00:00:09] Brandon: Hey, so thanks for having me on the podcast. So I'm Brandon. I work on an open source project called Protomaps. What it really is, is if you're a front end developer and you ever wanted to put maps on a website or on a mobile app, then Protomaps is sort of an open source solution for doing that that I hope is something that's way easier to use than, um, a lot of other open source projects. Why not just use Google Maps? [00:00:36] Jeremy: A lot of people are gonna be familiar with Google Maps. Why should they worry about whether something's open source? Why shouldn't they just go and use the Google maps API? [00:00:47] Brandon: So Google Maps is like an awesome thing it's an awesome product. Probably one of the best tech products ever right? And just to have a map that tells you what restaurants are open and something that I use like all the time especially like when you're traveling it has all that data. And the most amazing part is that it's free for consumers but it's not necessarily free for developers. Like if you wanted to embed that map onto your website or app, that usually has an API cost which still has a free tier and is affordable. But one motivation, one basic reason to use open source is if you have some project that doesn't really fit into that pricing model. You know like where you have to pay the cost of Google Maps, you have a side project, a nonprofit, that's one reason. But there's lots of other reasons related to flexibility or customization where you might want to use open source instead. Protomaps examples [00:01:49] Jeremy: Can you give some examples where people have used Protomaps and where that made sense for them? [00:01:56] Brandon: I follow a lot of the use cases and I also don't know about a lot of them because I don't have an API where I can track a hundred percent of the users. Some of them use the hosted version, but I would say most of them probably use it on their own infrastructure. One of the cool projects I've been seeing is called Toilet Map. And what toilet map is if you're in the UK and you want find a public restroom then it maps out, sort of crowdsourced all of the public restrooms. And that's important for like a lot of people if they have health issues, they need to find that information. And just a lot of different projects in the same vein. There's another one called Pinball Map which is sort of a hobby project to find all the pinball machines in the world. And they wanted to have a customized map that fit in with their theme of pinball. So these sorts of really cool indie projects are the ones I'm most excited about. Basemaps vs Overlays [00:02:57] Jeremy: And if we talk about, like the pinball map as an example, there's this concept of a basemap and then there's the things that you lay on top of it. What is a basemap and then is the pinball locations is that part of it or is that something separate? [00:03:12] Brandon: It's usually something separate. The example I usually use is if you go to a real estate site, like Zillow, you'll open up the map of Seattle and it has a bunch of pins showing all the houses, and then it has some information beneath it. That information beneath it is like labels telling, this neighborhood is Capitol Hill, or there is a park here. But all that information is common to a lot of use cases and it's not specific to real estate. So I think usually that's the distinction people use in the industry between like a base map versus your overlay. The overlay is like the data for your product or your company while the base map is something you could get from Google or from Protomaps or from Apple or from Mapbox that kind of thing. PMTiles for hosting the basemap and overlays [00:03:58] Jeremy: And so Protomaps in particular is responsible for the base map, and that information includes things like the streets and the locations of landmarks and things like that. Where is all that information coming from? [00:04:12] Brandon: So the base map information comes from a project called OpenStreetMap. And I would also, point out that for Protomaps as sort of an ecosystem. You can also put your overlay data into a format called PMTiles, which is sort of the core of what Protomaps is. So it can really do both. It can transform your data into the PMTiles format which you can host and you can also host the base map. So you kind of have both of those sides of the product in one solution. [00:04:43] Jeremy: And so when you say you have both are you saying that the PMTiles file can have, the base map in one file and then you would have the data you're laying on top in another file? Or what are you describing there? [00:04:57] Brandon: That's usually how I recommend to do it. Oftentimes there'll be sort of like, a really big basemap 'cause it has all of that data about like where the rivers are. Or while, if you want to put your map of toilets or park benches or pickleball courts on top, that's another file. But those are all just like assets you can move around like JSON or CSV files. Statically Hosted [00:05:19] Jeremy: And I think one of the things you mentioned was that your goal was to make Protomaps or the, the use of these PMTiles files easy to use. What does that look like for, for a developer? I wanna host a map. What do I actually need to, to put on my servers? [00:05:38] Brandon: So my usual pitch is that basically if you know how to use S3 or cloud storage, that you know how to deploy a map. And that, I think is the main sort of differentiation from most open source projects. Like a lot of them, they call themselves like, like some sort of self-hosted solution. But I've actually avoided using the term self-hosted because I think in most cases that implies a lot of complexity. Like you have to log into a Linux server or you have to use Kubernetes or some sort of Docker thing. What I really want to emphasize is the idea that, for Protomaps, it's self-hosted in the same way like CSS is self-hosted. So you don't really need a service from Amazon to host the JSON files or CSV files. It's really just a static file. [00:06:32] Jeremy: When you say static file that means you could use any static web host to host your HTML file, your JavaScript that actually renders the map. And then you have your PMTiles files, and you're not running a process or anything, you're just putting your files on a static file host. [00:06:50] Brandon: Right. So I think if you're a developer, you can also argue like a static file server is a server. It's you know, it's the cloud, it's just someone else's computer. It's really just nginx under the hood. But I think static storage is sort of special. If you look at things like static site generators, like Jekyll or Hugo, they're really popular because they're a commodity or like the storage is a commodity. And you can take your blog, make it a Jekyll blog, hosted on S3. One day, Amazon's like, we're charging three times as much so you can move it to a different cloud provider. And that's all vendor neutral. So I think that's really the special thing about static storage as a primitive on the web. Why running servers is a problem for resilience [00:07:36] Jeremy: Was there a prior experience you had? Like you've worked with maps for a very long time. Were there particular difficulties you had where you said I just gotta have something that can be statically hosted? [00:07:50] Brandon: That's sort of exactly why I got into this. I've been working sort of in and around the map space for over a decade, and Protomaps is really like me trying to solve the same problem I've had over and over again in the past, just like once and forever right? Because like once this problem is solved, like I don't need to deal with it again in the future. So I've worked at a couple of different companies before, mostly as a contractor, for like a humanitarian nonprofit for a design company doing things like, web applications to visualize climate change. Or for even like museums, like digital signage for museums. And oftentimes they had some sort of data visualization component, but always sort of the challenge of how to like, store and also distribute like that data was something that there wasn't really great open source solutions. So just for map data, that's really what motivated that design for Protomaps. [00:08:55] Jeremy: And in those, those projects in the past, were those things where you had to run your own server, run your own database, things like that? [00:09:04] Brandon: Yeah. And oftentimes we did, we would spin up an EC2 instance, for maybe one client and then we would have to host this server serving map data forever. Maybe the client goes away, or I guess it's good for business if you can sign some sort of like long-term support for that client saying, Hey, you know, like we're done with a project, but you can pay us to maintain the EC2 server for the next 10 years. And that's attractive. but it's also sort of a pain, because usually what happens is if people are given the choice, like a developer between like either I can manage the server on EC2 or on Rackspace or Hetzner or whatever, or I can go pay a SaaS to do it. In most cases, businesses will choose to pay the SaaS. So that's really like what creates a sort of lock-in is this preference for like, so I have this choice between like running the server or paying the SaaS. Like businesses will almost always go and pay the SaaS. [00:10:05] Jeremy: Yeah. And in this case, you either find some kind of free hosting or low-cost hosting just to host your files and you upload the files and then you're good from there. You don't need to maintain anything. [00:10:18] Brandon: Exactly, and that's really the ideal use case. so I have some users these, climate science consulting agencies, and then they might have like a one-off project where they have to generate the data once, but instead of having to maintain this server for the lifetime of that project, they just have a file on S3 and like, who cares? If that costs a couple dollars a month to run, that's fine, but it's not like S3 is gonna be deprecated, like it's gonna be on an insecure version of Ubuntu or something. So that's really the ideal, set of constraints for using Protomaps. [00:10:58] Jeremy: Yeah. Something this also makes me think about is, is like the resilience of sites like remaining online, because I, interviewed, Kyle Drake, he runs Neocities, which is like a modern version of GeoCities. And if I remember correctly, he was mentioning how a lot of old websites from that time, if they were running a server backend, like they were running PHP or something like that, if you were to try to go to those sites, now they're like pretty much all dead because there needed to be someone dedicated to running a Linux server, making sure things were patched and so on and so forth. But for static sites, like the ones that used to be hosted on GeoCities, you can go to the internet archive or other websites and they were just files, right? You can bring 'em right back up, and if anybody just puts 'em on a web server, then you're good. They're still alive. Case study of news room preferring static hosting [00:11:53] Brandon: Yeah, exactly. One place that's kind of surprising but makes sense where this comes up, is for newspapers actually. Some of the users using Protomaps are the Washington Post. And the reason they use it, is not necessarily because they don't want to pay for a SaaS like Google, but because if they make an interactive story, they have to guarantee that it still works in a couple of years. And that's like a policy decision from like the editorial board, which is like, so you can't write an article if people can't view it in five years. But if your like interactive data story is reliant on a third party, API and that third party API becomes deprecated, or it changes the pricing or it, you know, it gets acquired, then your journalism story is not gonna work anymore. So I have seen really good uptake among local news rooms and even big ones to use things like Protomaps just because it makes sense for the requirements. Working on Protomaps as an open source project for five years [00:12:49] Jeremy: How long have you been working on Protomaps and the parts that it's made up of such as PMTiles? [00:12:58] Brandon: I've been working on it for about five years, maybe a little more than that. It's sort of my pandemic era project. But the PMTiles part, which is really the heart of it only came in about halfway. Why not make a SaaS? [00:13:13] Brandon: So honestly, like when I first started it, I thought it was gonna be another SaaS and then I looked at it and looked at what the environment was around it. And I'm like, uh, so I don't really think I wanna do that. [00:13:24] Jeremy: When, when you say you looked at the environment around it what do you mean? Why did you decide not to make it a SaaS? [00:13:31] Brandon: Because there already is a lot of SaaS out there. And I think the opportunity of making something that is unique in terms of those use cases, like I mentioned like newsrooms, was clear. Like it was clear that there was some other solution, that could be built that would fit these needs better while if it was a SaaS, there are plenty of those out there. And I don't necessarily think that they're well differentiated. A lot of them all use OpenStreetMap data. And it seems like they mainly compete on price. It's like who can build the best three column pricing model. And then once you do that, you need to build like billing and metrics and authentication and like those problems don't really interest me. So I think, although I acknowledge sort of the indie hacker ethos now is to build a SaaS product with a monthly subscription, that's something I very much chose not to do, even though it is for sure like the best way to build a business. [00:14:29] Jeremy: Yeah, I mean, I think a lot of people can appreciate that perspective because it's, it's almost like we have SaaS overload, right? Where you have so many little bills for your project where you're like, another $5 a month, another $10 a month, or if you're a business, right? Those, you add a bunch of zeros and at some point it's just how many of these are we gonna stack on here? [00:14:53] Brandon: Yeah. And honestly. So I really think like as programmers, we're not really like great at choosing how to spend money like a $10 SaaS. That's like nothing. You know? So I can go to Starbucks and I can buy a pumpkin spice latte, and that's like $10 basically now, right? And it's like I'm able to make that consumer choice in like an instant just to spend money on that. But then if you're like, oh, like spend $10 on a SaaS that somebody put a lot of work into, then you're like, oh, that's too expensive. I could just do it myself. So I'm someone that also subscribes to a lot of SaaS products. and I think for a lot of things it's a great fit. Many open source SaaS projects are not easy to self host [00:15:37] Brandon: But there's always this tension between an open source project that you might be able to run yourself and a SaaS. And I think a lot of projects are at different parts of the spectrum. But for Protomaps, it's very much like I'm trying to move maps to being it is something that is so easy to run yourself that anyone can do it. [00:16:00] Jeremy: Yeah, and I think you can really see it with, there's a few SaaS projects that are successful and they're open source, but then you go to look at the self-hosting instructions and it's either really difficult to find and you find it, and then the instructions maybe don't work, or it's really complicated. So I think doing the opposite with Protomaps. As a user, I'm sure we're all appreciative, but I wonder in terms of trying to make money, if that's difficult. [00:16:30] Brandon: No, for sure. It is not like a good way to make money because I think like the ideal situation for an open source project that is open that wants to make money is the product itself is fundamentally complicated to where people are scared to run it themselves. Like a good example I can think of is like Supabase. Supabase is sort of like a platform as a service based on Postgres. And if you wanted to run it yourself, well you need to run Postgres and you need to handle backups and authentication and logging, and that stuff all needs to work and be production ready. So I think a lot of people, like they don't trust themselves to run database backups correctly. 'cause if you get it wrong once, then you're kind of screwed. So I think that fundamental aspect of the product, like a database is something that is very, very ripe for being a SaaS while still being open source because it's fundamentally hard to run. Another one I can think of is like tailscale, which is, like a VPN that works end to end. That's something where, you know, it has this networking complexity where a lot of developers don't wanna deal with that. So they'd happily pay, for tailscale as a service. There is a lot of products or open source projects that eventually end up just changing to becoming like a hosted service. Businesses going from open source to closed or restricted licenses [00:17:58] Brandon: But then in that situation why would they keep it open source, right? Like, if it's easy to run yourself well, doesn't that sort of cannibalize their business model? And I think that's really the tension overall in these open source companies. So you saw it happen to things like Elasticsearch to things like Terraform where they eventually change the license to one that makes it difficult for other companies to compete with them. [00:18:23] Jeremy: Yeah, I mean there's been a number of cases like that. I mean, specifically within the mapping community, one I can think of was Mapbox's. They have Mapbox gl. Which was a JavaScript client to visualize maps and they moved from, I forget which license they picked, but they moved to a much more restrictive license. I wonder what your thoughts are on something that releases as open source, but then becomes something maybe a little more muddy. [00:18:55] Brandon: Yeah, I think it totally makes sense because if you look at their business and their funding, it seems like for Mapbox, I haven't used it in a while, but my understanding is like a lot of their business now is car companies and doing in dash navigation. And that is probably way better of a business than trying to serve like people making maps of toilets. And I think sort of the beauty of it is that, so Mapbox, the story is they had a JavaScript renderer called Mapbox GL JS. And they changed that to a source available license a couple years ago. And there's a fork of it that I'm sort of involved in called MapLibre GL. But I think the cool part is Mapbox paid employees for years, probably millions of dollars in total to work on this thing and just gave it away for free. Right? So everyone can benefit from that work they did. It's not like that code went away, like once they changed the license. Well, the old version has been forked. It's going its own way now. It's quite different than the new version of Mapbox, but I think it's extremely generous that they're able to pay people for years, you know, like a competitive salary and just give that away. [00:20:10] Jeremy: Yeah, so we should maybe look at it as, it was a gift while it was open source, and they've given it to the community and they're on continuing on their own path, but at least the community running Map Libre, they can run with it, right? It's not like it just disappeared. [00:20:29] Brandon: Yeah, exactly. And that is something that I use for Protomaps quite extensively. Like it's the primary way of showing maps on the web and I've been trying to like work on some enhancements to it to have like better internationalization for if you are in like South Asia like not show languages correctly. So I think it is being taken in a new direction. And I think like sort of the combination of Protomaps and MapLibre, it addresses a lot of use cases, like I mentioned earlier with like these like hobby projects, indie projects that are almost certainly not interesting to someone like Mapbox or Google as a business. But I'm happy to support as a small business myself. Financially supporting open source work (GitHub sponsors, closed source, contracts) [00:21:12] Jeremy: In my previous interview with Tom, one of the main things he mentioned was that creating a mapping business is incredibly difficult, and he said he probably wouldn't do it again. So in your case, you're building Protomaps, which you've admitted is easy to self-host. So there's not a whole lot of incentive for people to pay you. How is that working out for you? How are you supporting yourself? [00:21:40] Brandon: There's a couple of strategies that I've tried and oftentimes failed at. Just to go down the list, so I do have GitHub sponsors so I do have a hosted version of Protomaps you can use if you don't want to bother copying a big file around. But the way I do the billing for that is through GitHub sponsors. If you wanted to use this thing I provide, then just be a sponsor. And that definitely pays for itself, like the cost of running it. And that's great. GitHub sponsors is so easy to set up. It just removes you having to deal with Stripe or something. 'cause a lot of people, their credit card information is already in GitHub. GitHub sponsors I think is awesome if you want to like cover costs for a project. But I think very few people are able to make that work. A thing that's like a salary job level. It's sort of like Twitch streaming, you know, there's a handful of people that are full-time streamers and then you look down the list on Twitch and it's like a lot of people that have like 10 viewers. But some of the other things I've tried, I actually started out, publishing the base map as a closed source thing, where I would sell sort of like a data package instead of being a SaaS, I'd be like, here's a one-time download, of the premium data and you can buy it. And quite a few people bought it I just priced it at like $500 for this thing. And I thought that was an interesting experiment. The main reason it's interesting is because the people that it attracts to you in terms of like, they're curious about your products, are all people willing to pay money. While if you start out everything being open source, then the people that are gonna be try to do it are only the people that want to get something for free. So what I discovered is actually like once you transition that thing from closed source to open source, a lot of the people that used to pay you money will still keep paying you money because like, it wasn't necessarily that that closed source thing was why they wanted to pay. They just valued that thought you've put into it your expertise, for example. So I think that is one thing, that I tried at the beginning was just start out, closed source proprietary, then make it open source. That's interesting to people. Like if you release something as open source, if you go the other way, like people are really mad if you start out with something open source and then later on you're like, oh, it's some other license. Then people are like that's so rotten. But I think doing it the other way, I think is quite valuable in terms of being able to find an audience. [00:24:29] Jeremy: And when you said it was closed source and paid to open source, do you still sell those map exports? [00:24:39] Brandon: I don't right now. It's something that I might do in the future, you know, like have small customizations of the data that are available, uh, for a fee. still like the core OpenStreetMap based map that's like a hundred gigs you can just download. And that'll always just be like a free download just because that's already out there. All the source code to build it is open source. So even if I said, oh, you have to pay for it, then someone else can just do it right? So there's no real reason like to make that like some sort of like paywall thing. But I think like overall if the project is gonna survive in the long term it's important that I'd ideally like to be able to like grow like a team like have a small group of people that can dedicate the time to growing the project in the long term. But I'm still like trying to figure that out right now. [00:25:34] Jeremy: And when you mentioned that when you went from closed to open and people were still paying you, you don't sell a product anymore. What were they paying for? [00:25:45] Brandon: So I have some contracts with companies basically, like if they need a feature or they need a customization in this way then I am very open to those. And I sort of set it up to make it clear from the beginning that this is not just a free thing on GitHub, this is something that you could pay for if you need help with it, if you need support, if you wanted it. I'm also a little cagey about the word support because I think like it sounds a little bit too wishy-washy. Pretty much like if you need access to the developers of an open source project, I think that's something that businesses are willing to pay for. And I think like making that clear to potential users is a challenge. But I think that is one way that you might be able to make like a living out of open source. [00:26:35] Jeremy: And I think you said you'd been working on it for about five years. Has that mostly been full time? [00:26:42] Brandon: It's been on and off. it's sort of my pandemic era project. But I've spent a lot of time, most of my time working on the open source project at this point. So I have done some things that were more just like I'm doing a customization or like a private deployment for some client. But that's been a minority of the time. Yeah. [00:27:03] Jeremy: It's still impressive to have an open source project that is easy to self-host and yet is still able to support you working on it full time. I think a lot of people might make the assumption that there's nothing to sell if something is, is easy to use. But this sort of sounds like a counterpoint to that. [00:27:25] Brandon: I think I'd like it to be. So when you come back to the point of like, it being easy to self-host. Well, so again, like I think about it as like a primitive of the web. Like for example, if you wanted to start a business today as like hosted CSS files, you know, like where you upload your CSS and then you get developers to pay you a monthly subscription for how many times they fetched a CSS file. Well, I think most developers would be like, that's stupid because it's just an open specification, you just upload a static file. And really my goal is to make Protomaps the same way where it's obvious that there's not really some sort of lock-in or some sort of secret sauce in the server that does this thing. How PMTiles works and building a primitive of the web [00:28:16] Brandon: If you look at video for example, like a lot of the tech for how Protomaps and PMTiles works is based on parts of the HTTP spec that were made for video. And 20 years ago, if you wanted to host a video on the web, you had to have like a real player license or flash. So you had to go license some server software from real media or from macromedia so you could stream video to a browser plugin. But now in HTML you can just embed a video file. And no one's like, oh well I need to go pay for my video serving license. I mean, there is such a thing, like YouTube doesn't really use that for DRM reasons, but people just have the assumption that video is like a primitive on the web. So if we're able to make maps sort of that same way like a primitive on the web then there isn't really some obvious business or licensing model behind how that works. Just because it's a thing and it helps a lot of people do their jobs and people are happy using it. So why bother? [00:29:26] Jeremy: You mentioned that it a tech that was used for streaming video. What tech specifically is it? [00:29:34] Brandon: So it is byte range serving. So when you open a video file on the web, So let's say it's like a 100 megabyte video. You don't have to download the entire video before it starts playing. It streams parts out of the file based on like what frames... I mean, it's based on the frames in the video. So it can start streaming immediately because it's organized in a way to where the first few frames are at the beginning. And what PMTiles really is, is it's just like a video but in space instead of time. So it's organized in a way where these zoomed out views are at the beginning and the most zoomed in views are at the end. So when you're like panning or zooming in the map all you're really doing is fetching byte ranges out of that file the same way as a video. But it's organized in, this tiled way on a space filling curve. IIt's a little bit complicated how it works internally and I think it's kind of cool but that's sort of an like an implementation detail. [00:30:35] Jeremy: And to the person deploying it, it just looks like a single file. [00:30:40] Brandon: Exactly in the same way like an mp3 audio file is or like a JSON file is. [00:30:47] Jeremy: So with a video, I can sort of see how as someone seeks through the video, they start at the beginning and then they go to the middle if they wanna see the middle. For a map, as somebody scrolls around the map, are you seeking all over the file or is the way it's structured have a little less chaos? [00:31:09] Brandon: It's structured. And that's kind of the main technical challenge behind building PMTiles is you have to be sort of clever so you're not spraying the reads everywhere. So it uses something called a hilbert curve, which is a mathematical concept of a space filling curve. Where it's one continuous curve that essentially lets you break 2D space into 1D space. So if you've seen some maps of IP space, it uses this crazy looking curve that hits all the points in one continuous line. And that's the same concept behind PMTiles is if you're looking at one part of the world, you're sort of guaranteed that all of those parts you're looking at are quite close to each other and the data you have to transfer is quite minimal, compared to if you just had it at random. [00:32:02] Jeremy: How big do the files get? If I have a PMTiles of the entire world, what kind of size am I looking at? [00:32:10] Brandon: Right now, the default one I distribute is 128 gigabytes, so it's quite sizable, although you can slice parts out of it remotely. So if you just wanted. if you just wanted California or just wanted LA or just wanted only a couple of zoom levels, like from zero to 10 instead of zero to 15, there is a command line tool that's also called PMTiles that lets you do that. Issues with CDNs and range queries [00:32:35] Jeremy: And when you're working with files of this size, I mean, let's say I am working with a CDN in front of my application. I'm not typically accustomed to hosting something that's that large and something that's where you're seeking all over the file. is that, ever an issue or is that something that's just taken care of by the browser and, and taken care of by, by the hosts? [00:32:58] Brandon: That is an issue actually, so a lot of CDNs don't deal with it correctly. And my recommendation is there is a kind of proxy server or like a serverless proxy thing that I wrote. That runs on like cloudflare workers or on Docker that lets you proxy those range requests into a normal URL and then that is like a hundred percent CDN compatible. So I would say like a lot of the big commercial installations of this thing, they use that because it makes more practical sense. It's also faster. But the idea is that this solution sort of scales up and scales down. If you wanted to host just your city in like a 10 megabyte file, well you can just put that into GitHub pages and you don't have to worry about it. If you want to have a global map for your website that serves a ton of traffic then you probably want a little bit more sophisticated of a solution. It still does not require you to run a Linux server, but it might require (you) to use like Lambda or Lambda in conjunction with like a CDN. [00:34:09] Jeremy: Yeah. And that sort of ties into what you were saying at the beginning where if you can host on something like CloudFlare Workers or Lambda, there's less time you have to spend keeping these things running. [00:34:26] Brandon: Yeah, exactly. and I think also the Lambda or CloudFlare workers solution is not perfect. It's not as perfect as S3 or as just static files, but in my experience, it still is better at building something that lasts on the time span of years than being like I have a server that is on this Ubuntu version and in four years there's all these like security patches that are not being applied. So it's still sort of serverless, although not totally vendor neutral like S3. Customizing the map [00:35:03] Jeremy: We've mostly been talking about how you host the map itself, but for someone who's not familiar with these kind of tools, how would they be customizing the map? [00:35:15] Brandon: For customizing the map there is front end style customization and there's also data customization. So for the front end if you wanted to change the water from the shade of blue to another shade of blue there is a TypeScript API where you can customize it almost like a text editor color scheme. So if you're able to name a bunch of colors, well you can customize the map in that way you can change the fonts. And that's all done using MapLibre GL using a TypeScript API on top of that for customizing the data. So all the pipeline to generate this data from OpenStreetMap is open source. There is a Java program using a library called PlanetTiler which is awesome, which is this super fast multi-core way of building map tiles. And right now there isn't really great hooks to customize what data goes into that. But that's something that I do wanna work on. And finally, because the data comes from OpenStreetMap if you notice data that's missing or you wanted to correct data in OSM then you can go into osm.org. You can get involved in contributing the data to OSM and the Protomaps build is daily. So if you make a change, then within 24 hours you should see the new base map. Have that change. And of course for OSM your improvements would go into every OSM based project that is ingesting that data. So it's not a protomap specific thing. It's like this big shared data source, almost like Wikipedia. OpenStreetMap is a dataset and not a map [00:37:01] Jeremy: I think you were involved with OpenStreetMap to some extent. Can you speak a little bit to that for people who aren't familiar, what OpenStreetMap is? [00:37:11] Brandon: Right. So I've been using OSM as sort of like a tools developer for over a decade now. And one of the number one questions I get from developers about what is Protomaps is why wouldn't I just use OpenStreetMap? What's the distinction between Protomaps and OpenStreetMap? And it's sort of like this funny thing because even though OSM has map in the name it's not really a map in that you can't... In that it's mostly a data set and not a map. It does have a map that you can see that you can pan around to when you go to the website but the way that thing they show you on the website is built is not really that easily reproducible. It involves a lot of c++ software you have to run. But OpenStreetMap itself, the heart of it is almost like a big XML file that has all the data in the map and global. And it has tagged features for example. So you can go in and edit that. It has a web front end to change the data. It does not directly translate into making a map actually. Protomaps decides what shows at each zoom level [00:38:24] Brandon: So a lot of the pipeline, that Java program I mentioned for building this basemap for protomaps is doing things like you have to choose what data you show when you zoom out. You can't show all the data. For example when you're zoomed out and you're looking at all of a state like Colorado you don't see all the Chipotle when you're zoomed all the way out. That'd be weird, right? So you have to make some sort of decision in logic that says this data only shows up at this zoom level. And that's really what is the challenge in optimizing the size of that for the Protomaps map project. [00:39:03] Jeremy: Oh, so those decisions of what to show at different Zoom levels those are decisions made by you when you're creating the PMTiles file with Protomaps. [00:39:14] Brandon: Exactly. It's part of the base maps build pipeline. and those are honestly very subjective decisions. Who really decides when you're zoomed out should this hospital show up or should this museum show up nowadays in Google, I think it shows you ads. Like if someone pays for their car repair shop to show up when you're zoomed out like that that gets surfaced. But because there is no advertising auction in Protomaps that doesn't happen obviously. So we have to sort of make some reasonable choice. A lot of that right now in Protomaps actually comes from another open source project called Mapzen. So Mapzen was a company that went outta business a couple years ago. They did a lot of this work in designing which data shows up at which Zoom level and open sourced it. And then when they shut down, they transferred that code into the Linux Foundation. So it's this totally open source project, that like, again, sort of like Mapbox gl has this awesome legacy in that this company funded it for years for smart people to work on it and now it's just like a free thing you can use. So the logic in Protomaps is really based on mapzen. [00:40:33] Jeremy: And so the visualization of all this... I think I understand what you mean when people say oh, why not use OpenStreetMaps because it's not really clear it's hard to tell is this the tool that's visualizing the data? Is it the data itself? So in the case of using Protomaps, it sounds like Protomaps itself has all of the data from OpenStreetMap and then it has made all the decisions for you in terms of what to show at different Zoom levels and what things to have on the map at all. And then finally, you have to have a separate, UI layer and in this case, it sounds like the one that you recommend is the Map Libre library. [00:41:18] Brandon: Yeah, that's exactly right. For Protomaps, it has a portion or a subset of OSM data. It doesn't have all of it just because there's too much, like there's data in there. people have mapped out different bushes and I don't include that in Protomaps if you wanted to go in and edit like the Java code to add that you can. But really what Protomaps is positioned at is sort of a solution for developers that want to use OSM data to make a map on their app or their website. because OpenStreetMap itself is mostly a data set, it does not really go all the way to having an end-to-end solution. Financials and the idea of a project being complete [00:41:59] Jeremy: So I think it's great that somebody who wants to make a map, they have these tools available, whether it's from what was originally built by Mapbox, what's built by Open StreetMap now, the work you're doing with Protomaps. But I wonder one of the things that I talked about with Tom was he was saying he was trying to build this mapping business and based on the financials of what was coming in he was stressed, right? He was struggling a bit. And I wonder for you, you've been working on this open source project for five years. Do you have similar stressors or do you feel like I could keep going how things are now and I feel comfortable? [00:42:46] Brandon: So I wouldn't say I'm a hundred percent in one bucket or the other. I'm still seeing it play out. One thing, that I really respect in a lot of open source projects, which I'm not saying I'm gonna do for Protomaps is the idea that a project is like finished. I think that is amazing. If a software project can just be done it's sort of like a painting or a novel once you write, finish the last page, have it seen by the editor. I send it off to the press is you're done with a book. And I think one of the pains of software is so few of us can actually do that. And I don't know obviously people will say oh the map is never finished. That's more true of OSM, but I think like for Protomaps. One thing I'm thinking about is how to limit the scope to something that's quite narrow to where we could be feature complete on the core things in the near term timeframe. That means that it does not address a lot of things that people want. Like search, like if you go to Google Maps and you search for a restaurant, you will get some hits. that's like a geocoding issue. And I've already decided that's totally outta scope for Protomaps. So, in terms of trying to think about the future of this, I'm mostly looking for ways to cut scope if possible. There are some things like better tooling around being able to work with PMTiles that are on the roadmap. but for me, I am still enjoying working on the project. It's definitely growing. So I can see on NPM downloads I can see the growth curve of people using it and that's really cool. So I like hearing about when people are using it for cool projects. So it seems to still be going okay for now. [00:44:44] Jeremy: Yeah, that's an interesting perspective about how you were talking about projects being done. Because I think when people look at GitHub projects and they go like, oh, the last commit was X months ago. They go oh well this is dead right? But maybe that's the wrong framing. Maybe you can get a project to a point where it's like, oh, it's because it doesn't need to be updated. [00:45:07] Brandon: Exactly, yeah. Like I used to do a lot of c++ programming and the best part is when you see some LAPACK matrix math library from like 1995 that still works perfectly in c++ and you're like, this is awesome. This is the one I have to use. But if you're like trying to use some like React component library and it hasn't been updated in like a year, you're like, oh, that's a problem. So again, I think there's some middle ground between those that I'm trying to find. I do like for Protomaps, it's quite dependency light in terms of the number of hard dependencies I have in software. but I do still feel like there is a lot of work to be done in terms of project scope that needs to have stuff added. You mostly only hear about problems instead of people's wins [00:45:54] Jeremy: Having run it for this long. Do you have any thoughts on running an open source project in general? On dealing with issues or managing what to work on things like that? [00:46:07] Brandon: Yeah. So I have a lot. I think one thing people point out a lot is that especially because I don't have a direct relationship with a lot of the people using it a lot of times I don't even know that they're using it. Someone sent me a message saying hey, have you seen flickr.com, like the photo site? And I'm like, no. And I went to flickr.com/map and it has Protomaps for it. And I'm like, I had no idea. But that's cool, if they're able to use Protomaps for this giant photo sharing site that's awesome. But that also means I don't really hear about when people use it successfully because you just don't know, I guess they, NPM installed it and it works perfectly and you never hear about it. You only hear about people's negative experiences. You only hear about people that come and open GitHub issues saying this is totally broken, and why doesn't this thing exist? And I'm like, well, it's because there's an infinite amount of things that I want to do, but I have a finite amount of time and I just haven't gone into that yet. And that's honestly a lot of the things and people are like when is this thing gonna be done? So that's, that's honestly part of why I don't have a public roadmap because I want to avoid that sort of bickering about it. I would say that's one of my biggest frustrations with running an open source project is how it's self-selected to only hear the negative experiences with it. Be careful what PRs you accept [00:47:32] Brandon: 'cause you don't hear about those times where it works. I'd say another thing is it's changed my perspective on contributing to open source because I think when I was younger or before I had become a maintainer I would open a pull request on a project unprompted that has a hundred lines and I'd be like, Hey, just merge this thing. But I didn't realize when I was younger well if I just merge it and I disappear, then the maintainer is stuck with what I did forever. You know if I add some feature then that person that maintains the project has to do that indefinitely. And I think that's very asymmetrical and it's changed my perspective a lot on accepting open source contributions. I wanna have it be open to anyone to contribute. But there is some amount of back and forth where it's almost like the default answer for should I accept a PR is no by default because you're the one maintaining it. And do you understand the shape of that solution completely to where you're going to support it for years because the person that's contributing it is not bound to those same obligations that you are. And I think that's also one of the things where I have a lot of trepidation around open source is I used to think of it as a lot more bazaar-like in terms of anyone can just throw their thing in. But then that creates a lot of problems for the people who are expected out of social obligation to continue this thing indefinitely. [00:49:23] Jeremy: Yeah, I can totally see why that causes burnout with a lot of open source maintainers, because you probably to some extent maybe even feel some guilt right? You're like, well, somebody took the time to make this. But then like you said you have to spend a lot of time trying to figure out is this something I wanna maintain long term? And one wrong move and it's like, well, it's in here now. [00:49:53] Brandon: Exactly. To me, I think that is a very common failure mode for open source projects is they're too liberal in the things they accept. And that's a lot of why I was talking about how that choice of what features show up on the map was inherited from the MapZen projects. If I didn't have that then somebody could come in and say hey, you know, I want to show power lines on the map. And they open a PR for power lines and now everybody who's using Protomaps when they're like zoomed out they see power lines are like I didn't want that. So I think that's part of why a lot of open source projects eventually evolve into a plugin system is because there is this demand as the project grows for more and more features. But there is a limit in the maintainers. It's like the demand for features is exponential while the maintainer amount of time and effort is linear. Plugin systems might reduce need for PRs [00:50:56] Brandon: So maybe the solution to smash that exponential down to quadratic maybe is to add a plugin system. But I think that is one of the biggest tensions that only became obvious to me after working on this for a couple of years. [00:51:14] Jeremy: Is that something you're considering doing now? [00:51:18] Brandon: Is the plugin system? Yeah. I think for the data customization, I eventually wanted to have some sort of programmatic API to where you could declare a config file that says I want ski routes. It totally makes sense. The power lines example is maybe a little bit obscure but for example like a skiing app and you want to be able to show ski slopes when you're zoomed out well you're not gonna be able to get that from Mapbox or from Google because they have a one size fits all map that's not specialized to skiing or to golfing or to outdoors. But if you like, in theory, you could do this with Protomaps if you changed the Java code to show data at different zoom levels. And that is to me what makes the most sense for a plugin system and also makes the most product sense because it enables a lot of things you cannot do with the one size fits all map. [00:52:20] Jeremy: It might also increase the complexity of the implementation though, right? [00:52:25] Brandon: Yeah, exactly. So that's like. That's really where a lot of the terrifying thoughts come in, which is like once you create this like config file surface area, well what does that look like? Is that JSON? Is that TOML, is that some weird like everything eventually evolves into some scripting language right? Where you have logic inside of your templates and I honestly do not really know what that looks like right now. That feels like something in the medium term roadmap. [00:52:58] Jeremy: Yeah and then in terms of bug reports or issues, now it's not just your code it's this exponential combination of whatever people put into these config files. [00:53:09] Brandon: Exactly. Yeah. so again, like I really respect the projects that have done this well or that have done plugins well. I'm trying to think of some, I think obsidian has plugins, for example. And that seems to be one of the few solutions to try and satisfy the infinite desire for features with the limited amount of maintainer time. Time split between code vs triage vs talking to users [00:53:36] Jeremy: How would you say your time is split between working on the code versus issue and PR triage? [00:53:43] Brandon: Oh, it varies really. I think working on the code is like a minority of it. I think something that I actually enjoy is talking to people, talking to users, getting feedback on it. I go to quite a few conferences to talk to developers or people that are interested and figure out how to refine the message, how to make it clearer to people, like what this is for. And I would say maybe a plurality of my time is spent dealing with non-technical things that are neither code or GitHub issues. One thing I've been trying to do recently is talk to people that are not really in the mapping space. For example, people that work for newspapers like a lot of them are front end developers and if you ask them to run a Linux server they're like I have no idea. But that really is like one of the best target audiences for Protomaps. So I'd say a lot of the reality of running an open source project is a lot like a business is it has all the same challenges as a business in terms of you have to figure out what is the thing you're offering. You have to deal with people using it. You have to deal with feedback, you have to deal with managing emails and stuff. I don't think the payoff is anywhere near running a business or a startup that's backed by VC money is but it's definitely not the case that if you just want to code, you should start an open source project because I think a lot of the work for an opensource project has nothing to do with just writing the code. It is in my opinion as someone having done a VC backed business before, it is a lot more similar to running, a tech company than just putting some code on GitHub. Running a startup vs open source project [00:55:43] Jeremy: Well, since you've done both at a high level what did you like about running the company versus maintaining the open source project? [00:55:52] Brandon: So I have done some venture capital accelerator programs before and I think there is an element of hype and energy that you get from that that is self perpetuating. Your co-founder is gungho on like, yeah, we're gonna do this thing. And your investors are like, you guys are geniuses. You guys are gonna make a killing doing this thing. And the way it's framed is sort of obvious to everyone that it's like there's a much more traditional set of motivations behind that, that people understand while it's definitely not the case for running an open source project. Sometimes you just wake up and you're like what the hell is this thing for, it is this thing you spend a lot of time on. You don't even know who's using it. The people that use it and make a bunch of money off of it they know nothing about it. And you know, it's just like cool. And then you only hear from people that are complaining about it. And I think like that's honestly discouraging compared to the more clear energy and clearer motivation and vision behind how most people think about a company. But what I like about the open source project is just the lack of those constraints you know? Where you have a mandate that you need to have this many customers that are paying by this amount of time. There's that sort of pressure on delivering a business result instead of just making something that you're proud of that's simple to use and has like an elegant design. I think that's really a difference in motivation as well. Having control [00:57:50] Jeremy: Do you feel like you have more control? Like you mentioned how you've decided I'm not gonna make a public roadmap. I'm the sole developer. I get to decide what goes in. What doesn't. Do you feel like you have more control in your current position than you did running the startup? [00:58:10] Brandon: Definitely for sure. Like that agency is what I value the most. It is possible to go too far. Like, so I'm very wary of the BDFL title, which I think is how a lot of open source projects succeed. But I think there is some element of for a project to succeed there has to be somebody that makes those decisions. Sometimes those decisions will be wrong and then hopefully they can be rectified. But I think going back to what I was talking about with scope, I think the overall vision and the scope of the project is something that I am very opinionated about in that it should do these things. It shouldn't do these things. It should be easy to use for this audience. Is it gonna be appealing to this other audience? I don't know. And I think that is really one of the most important parts of that leadership role, is having the power to decide we're doing this, we're not doing this. I would hope other developers would be able to get on board if they're able to make good use of the project, if they use it for their company, if they use it for their business, if they just think the project is cool. So there are other contributors at this point and I want to get more involved. But I think being able to make those decisions to what I believe is going to be the best project is something that is very special about open source, that isn't necessarily true about running like a SaaS business. [00:59:50] Jeremy: I think that's a good spot to end it on, so if people want to learn more about Protomaps or they wanna see what you're up to, where should they head? [01:00:00] Brandon: So you can go to Protomaps.com, GitHub, or you can find me or Protomaps on bluesky or Mastodon. [01:00:09] Jeremy: All right, Brandon, thank you so much for chatting today. [01:00:12] Brandon: Great. Thank you very much.

Entrevista al Director del Secretariado de la oficina de software libre y profesor titular deUniversidad de Granada en el departamento de Ingeniería Computadores, Automática y Robótica, Pablo García Sánchez, sobre el proyecto de mapa libre Open Street Maps---------------------------Radiolab, la radio universitaria de la Universidad de Granada, es un espacio de participación de la comunidad universitaria abierto a la ciudadanía. Nuestra universidad, como institución de aprendizaje está abierta al conocimiento y al debate. Desde su autonomía proporciona espacio para un debate libre y crítico, abierto a la pluralidad de voces y a la demandas de la sociedad dentro del marco de los derechos humanos y de los valores de nuestra institución. De este modo, constatamos que las opiniones vertidas en nuestros programas son exclusiva responsabilidad de quienes las emiten, sin representar un posicionamiento de la institución como tal. Defendemos la libertad de expresión y la comunicación en el espacio público como una forma de hacer ciudadanía y avanzar en el conocimiento. 

On this episode, I'm joined by Dr. Jeff Boeing, an assistant professor at the University of Southern California whose research spans urban planning, spatial analysis, and data science. We explore why OpenStreetMap is such a powerful source of global map data—and how Jeff's Python library, OSMnx, makes that data easier to download, model, and visualize. Along the way, we talk about what shapes city streets around the world, how urban design influences everything from daily commutes to disaster resilience, and why turning open data into accessible tools can open up completely new ways of understanding our cities. If you've ever wondered how to build or analyze your own digital maps in Python, or what it takes to manage a project that transforms raw geographic data into meaningful research, you won't want to miss this conversation. Episode sponsors Posit Podcast Later Talk Python Courses Links from the show City Street Orientations World: geoffboeing.com OSMnx Documentation: readthedocs.io OSMnx GitHub: github.com OpenStreetMap: openstreetmap.org Open Database License: opendatacommons.org ID Editor (Web Editor): wiki.openstreetmap.org Planet OSM: planet.openstreetmap.org Overpass API: wiki.openstreetmap.org GeoPandas: geopandas.org NetworkX: networkx.org Shapely: shapely.readthedocs.io Watch this episode on YouTube: youtube.com Episode transcripts: talkpython.fm --- Stay in touch with us --- Subscribe to Talk Python on YouTube: youtube.com Talk Python on Bluesky: @talkpython.fm at bsky.app Talk Python on Mastodon: talkpython Michael on Bluesky: @mkennedy.codes at bsky.app Michael on Mastodon: mkennedy

Buscando alternativas para Apple Maps y Google Maps me encontré con Organic Maps, una aplicación simple, bonita, rápida y que funciona sin Internet, usando para sus mapas OpenStreetMaps. Te invito a debatir sobre este tema en el Foro de Como Pienso Digo https://foro.comopiensodigo.com Y otras formas de contacto las encuentran en: https://ernestoacosta.me/contacto.html Todos los medios donde publico contenido los encuentras en: https://ernestoacosta.me/ Si quieres comprar productos de RØDE, este es mi link de afiliados: https://brandstore.rode.com/?sca_ref=5066237.YwvTR4eCu1 Te invito a debatir sobre este tema en el Foro de Como Pienso Digo https://foro.comopiensodigo.com Y otras formas de contacto las encuentran en: https://ernestoacosta.me/contacto.html Todos los medios donde publico contenido los encuentras en: https://ernestoacosta.me/ Si quieres comprar productos de RØDE, este es mi link de afiliados: https://brandstore.rode.com/?sca_ref=5066237.YwvTR4eCu1

Tom MacWright is a prolific contributor in the geospatial open source community. He made geojson.io, Mapbox Studio, and was the lead developer on the OpenStreetMap editor. He's currently on the team at Val Town. In 2021 he bootstrapped a solo business and created the Placemark mapping application. He acquired customers and found steady growth but after spending two years on the project he decided it was financially unsustainable. He open sourced the code and shut down the business. In this interview Tom speaks candidly about why geospatial is difficult, chasing technical rabbit holes, the mental impact of bootstrapping, and his struggles to grow a customer base. If you're interested in geospatial or the good and bad of running a solo business I think you'll enjoy this conversation with Tom. Related Links Tom's blog Placemark Play Placemark GitHub Placemark archive geojson.io Valtown Datawrapper (Visualization tool) Geospatial Companies mentioned Mapbox ArcGIS QGIS Carto -- Transcript You can help correct transcripts on GitHub. [00:00:00] Introduction Jeremy: Today I'm talking to Tom MacWright. He worked at Mapbox as a, a very early employee. He's had a lot of experience in the geospatial community, the open source community. One of his most recent projects was a mapping project called Placemark he started and ran on his own. So I wanted to talk to Tom about his experience going solo and, eventually having to, shut that down. Tom, thanks for agreeing to chat today. Tom: Yeah, thanks for having me. [00:00:32] Tools and Open Source at Mapbox Jeremy: So maybe to give everyone some context on, what your background was before you started Placemark. Um, let's talk a little bit about your experience at, at Mapbox. What did you work on there and, and what would you say are like the big things you learned from that experience? Tom: Yeah, so if you include the time that I was at Development Seed, which essentially turned into Mapbox, I kind of signed the paper to get fired from Development Seed and hired at Mapbox within the same 20 seconds. Uh, I was there for eight and a half years. so it was a lifetime in tech years. and the company really evolved from, uh, working for Human Rights Watch and Amnesty International and the World Bank and doing these small, little like micro websites to the point at which I left it. It had. Raised a lot of money, had a lot of employees. I think it was 350 or so when I left. and yeah, just expanded into a lot of different, uh, try trying to own more and more of the mapping stack. but yeah, I was kind of really focused on the creative and tooling side of it. that's kind of where I see a lot of the, the fun and programming is making these tools where, uh, they can give people the same kind of fun like interaction loop that programming has where you, you know, you do a little bit of math and you see the result and you're able to just play with, uh, what you're working on, letting people have that in other domains. so it was really cool to figure out how to get A map design tool where somebody changes the background color and it just automatically changes that in your browser. and it covered like data editing. It covered, um, map styling and we did, uh, three different versions of that tool over the years. and then Mapbox is also a company that was, it came from, kind of people who are working on the Howard Dean campaign. And so it was pretty ideological and part of the ideology was being pretty hardcore about open source. we hired a lot of people who were working on open source projects before and basically just paid them to work on the open source projects, uh, for their whole time there. And during my time there, I just tried to make as much of my work, uh, open as possible, which was, you know, at the time it was, it was pretty great. I think in the long term it's been, o open source has changed a lot. but during the time that we were there, we both kind of, helped things like leaflet and mapnik and openstreetmap, uh, but also made like some larger contributions to the open source world. yeah, that, that's kind of like the, the internal company facing side. And also like what I try to create as like a more of a, uh, enduring work. I think the open source stuff will hopefully have more of a, a long term, uh, benefit. [00:03:40] How open source has changed (value capture by large companies) Jeremy: When I was working on a project that needed offline maps, um, we couldn't use Google Maps or any of the, the other publicly available, cloud APIs. So yeah, we actually used a, a tool, called Tile Mill that I, I hadn't known that you'd worked on, but recently found out you did. So that actually let us pull in OpenStreetMap data and then use this style, uh, language called carto to, to basically let us choose what the colors would be and how the different, uh, the roads and the buildings would look. What's kind of interesting to me is that it being open source really let us, um, build something we otherwise wouldn't have been able to do. But like, at the same time, we also didn't pay Mapbox any money. (laughs) So I'm, I'm kind of curious, like, if it's changed, like what the thinking was in terms of, you know, we pay for people to build all these things. We make it open source. but then people may just not ever pay us, you know, for all these things we did. Tom: Yeah. Yeah. I think that the main thing that's changed since the era of tilemill is, the dominance of cloud platforms. Like back then, I think, uh, Mapbox was still using, we were using like a little bit of AWS but people were still just on like VPSs and, uh, configuring things in cPanel and sometimes even running their own servers. And the, the danger of people using the product for free was such a small thing for us. especially when tile Mill was also funded by the Knight Foundation, so, you know, that at least paid half of my salary for, or, well, sorry, probably, yeah, maybe half of my salary for the first year that I was there and half of three other people's salaries. but that, yeah, so like when we built Tile Mill, a few companies have really like built on those same tools. Uh, there's a company called Carto coincidentally, they had the same name as Carto CSS, and they built on a lot of the same stack they built on mapnik. Um, and it was, was... I mean, I'm not gonna say that it was all like, you know, sunshine and roses, but it was never a thing that we talked about in terms of like this being a brutal competition between us and these other startups. Mapbox eventually closed source some stuff. they made it a source available license. and eventually Mapbox Studio was a closed source product. Um, and that was actually a decision that I advocated for. And that's mostly just because at one point, Esri, Microsoft, Amazon, all had whitelisted versions of Mapbox code, which, uh, hurts a little bit on a personal level and also makes it pretty hard to think about. working almost like it. You don't want to go to your scrappy open source company and do unpaid labor for Amazon. Uh, you know, Bezos can afford to pay for the labor himself. that's just kind of my personal, uh, that I'm obviously, I haven't worked there in a long time, so I'm not speaking for the company, but that's kind of how it felt like. and it yeah, kind of changed the arithmetic of open source in this way that. It made it less fun and, more risky, um, for people I think. [00:07:11] Don't worry about the small free users Jeremy: Yeah. So it sounds like the thinking was if someone on a small team or an individual, they took the open source software and they used it for their own projects, that was fine. Like you expected that and didn't worry about it. It's more that when these really large organizations like a, a Microsoft comes in and, just like you said, white labels the software, and doesn't really contribute significantly back. That's, that's when it, the, the thinking sort of shifted. Tom: Yeah, like a lot of the people who can't pay full price in USD to use your product are great users and they're doing cool stuff. Like when I was working on Placemark and when I was like selling. The theme for my blog, I would get emails from like some kid in India and it's like, you know, you're selling this for a hundred dollars, which is a ton of money. And like, you know, why, why should I care? Why shouldn't I like, just send them the zip file for free? it's like nothing to me and a lot to them. and mapping tools are really, really expensive. So the fact that Mapbox was able to create a free alternative when, you know, ArcGIS was $500 a month sometimes, um, depending on your license, obviously. That's, that's good. You're always gonna find a way for, like, your salespeople are gonna find a way to charge the big companies a lot of money. They're great at that. Um, and that's what matters really for your, for the revenue. [00:08:44] ESRI to Google Maps with little in-between Jeremy: That's a a good point too about like the, my impression of the, the mapping space, and maybe this has changed more recently, but you had the, probably the biggest player Esri, who's selling things at enterprise prices and then there were, or there are like a few open source options. but they feel like the, the barrier to entry feels a little high. And so, and then I guess you have stuff like Google Maps, right? That's, um, that's very accessible, but it's pretty limited, so. There's this big gap, it feels like right between the, the Esri and the, the Google Maps and open source. It's, it's sort of like, there's almost like there's no sweet spot. guess May, maybe it's just because people's uses are so different, but I'm, I'm not sure, um, what makes maps so unique in that way Tom: Yeah, I have come to understand what Esri and QGIS do as like an extension of what CAD is like. And if you've used CAD software recently, it's just as crazy and as expensive and as powerful. and it's really hard to capture like the people who are motivated enough to make a map but don't want to go down the whole rabbit hole. I think that was one of the hardest things about Placemark was trying to be in the middle of those things and half of the people were mystified by the complexity and half the people wanted more complexity. Uh, and I just couldn't figure out how to get it to the right in between spot. [00:10:25] Placemark and its origins in geojson.io Jeremy: Yeah. So let's, let's talk a little bit about Placemark then, in terms of from its start. What was your, your goal with Placemark and, and what was the product itself? Tom: So the seed of the idea for Placemark, uh, is this website called geojson.io, uh, which is still around. And, Chris Fong (correction -- Whong) at, at Mapbox is still, uh, developing it. And that had become pretty useful for a lot of people who I knew in the industry who were in this position of managing geospatial data but not wanting to boot up ArcGIS uh, geojson.io is based on, I just tweeted, I was like, why? Why is there not a thing where you can edit data on a map and have a GeoJSON representation and just go Back and forth between the two really easily. and it started with that, and then it kind of grew to be a little bit more powerful. And then it was just a tool that was useful for everyone. And my theory was just that I wanted that to be more useful. And I knew just like anything else that you build and you work on for a long time, you know exactly how it could be so much better. And, uh, all the things that you would do better if you did it again. And I was, uh, you know, hoping that there was something where like if you make that more powerful and you make it something that's like so essential that somebody's using every day, then maybe there's some some value in that. And so Placemark kind of started as being like, oh, this is the thing where if you're tasking a satellite and you need a bounding box on a specific city, this is the easiest way to do that. Um, and it grew a little bit into being like a tool for collaborating because people were collaborating on it. And I thought that that would be, you know, an interesting thing to support. but yeah, I think it, it like tried to be in that middle of like, not exactly Google my Maps and certainly a lot, uh, simpler than, uh, QGIS or ArcGIS Jeremy: something I noticed, so I've actually used geojson.io as well when I was first learning how to put stuff on a map and learning that GeoJSON was a format that a lot of things were using, it was actually really helpful to, to be able to draw, uh, polygons and see, okay, this is how the JSO looks and all that stuff. And it was. Like just very simple. I think there's something like very powerful about, websites or applications like that where it, it does this one thing and when you go there, you're like, oh, okay, I, I, I know what I'm doing and it's, it's, uh, you know, it's gonna help me do the, this very specific thing I'm trying to do. [00:13:16] Placemark use cases (Farming, Transportation, Interior mapping, Satellite viewsheds) Jeremy: I think with Placemark, so, one question I would have is, you gave an example of, uh, someone, I think you said for a satellite, they're, are they drawing the, the area? What, what was the area specifically for? Tom: the area of interest, the area where they want the, uh, to point the camera. Jeremy: so yeah, with, with Placemark, I mean, were there, what were some of the specific customers or use cases you had in mind? 'cause that's, that's something about. Um, placemark as a product I noticed was it's sort of like, here's this thing where you can draw polygons put markers and there's all these like things you can do, but I think unless you already have the specific use case, it's not super clear, who uses it for what. So maybe you could give some examples of what you had in mind. Tom: I didn't have much in mind, but I can tell you what people, what some people used it for. so some of the more interesting uses of it, a bunch of, uh, farming oriented use cases, uh, especially like indoor and small scale farming. Um, there were some people who, uh, essentially had a bunch of flower farms and had polygons on the map, and they wanted to, uh, mark the ones that had mites or needed to be watered, other things that could spread in a geometric way. And so it's pretty important to have that geospatial component to it. and then a few places were using it for basically transportation planning. Um, so drawing out routes of where buses would go, uh, in Luxembourg. And, then there was also a little bit of like, kind of interesting, planning of what to buy more or less. Uh, so something of like, do we want to buy this tract of land or do we wanna buy this tract of land or do we wanna buy access to this one high speed internet cable or this other high speed internet cable? and yeah, a lot of those things were kind of like emergent use cases. Um, there's a lot of people who were doing either architecture or internal or in interior mapping essentially. Jeremy: Interior, you mean, inside of a building Tom: yeah. yeah. Jeremy: Hmm. Okay. Tom: Which I don't think it was the best tool for. Uh, but you know, people used it for that. Jeremy: Interesting. Yeah. I guess, would people normally use some kind of a CAD tool for that, or Tom: Yeah. Uh, there's CAD tools and there are a few, uh, companies that do just, there's a company that just does interior maps especially of airports, and that's their whole business model. Um, but it's, it's kind of an interesting, uh, problem because most CAD architecture work is done with like a local coordinate system, and you have like very good resolution of everything, and then you eventually place it in geo geospatial space. Uh, but if you do it all in latitude and longitude, you know, you're, you're moving a door and it's moving the 10th or 12th decimal point, and eventually you have some precision problems. Jeremy: So it's almost like if you start with latitude and longitude, it's hard to go the other way. Right? you have to start more specific and then you can move it into the, the geospatial, uh, area. Tom: Yeah. Uh, that's kind of why we have local projections for towns is that you can do a lot of work just in that local projection. And the numbers are kind of small 'cause your town's small, relatively. Jeremy: yeah, those are kind of interesting. So it sounds like just anytime somebody wants to, like you gave the example of transportation planning or you want to visually see where things are, like your crops or things like that, and that, that kind of makes sense. I mean, I think if you just think about paper maps, if somebody wants to sketch something out and, and sort of track the layout of something, this could serve the same purpose but be editable. and like you said, I think it's also. Collaborative so you can have multiple people editing the same, um, map. that makes sense. I think something that I believe I saw on your website is you said though that it was, it's like an editing tool, but it's not necessarily a visualization tool. Uh, I'm kind of curious what you, what you meant by that. [00:17:39] An editing tool that allows you to export data not a visualization tool Tom: Yeah, I, when you say a map, I think there's, people can interpret that as everything from raw data to satellite imagery and raster data. and then a lot of it is like, can I use this to make a choropleth map of the voter turnout in our, in my country? and that placemark did a little bit, but I think that it was, it was never going to be the, the thing that it did super well. and so, yeah, and also like the, the two things kind of, don't mesh all that well. Like if you have a scale point map and you have that kind of visualization of it and then you're editing the points at the same time and you're dragging around these like gigantic points because this point means a lot of population, it just doesn't really make that much sense. There are probably ways to square that circle and have different views, but, uh, I felt like for visualizations, I mean partly I just think data wrapper is kind of great and uh, I had already worked for observable at that point, which is also, which I think also does like great visualization work. Jeremy: Would that be the case of somebody could make a map inside a placemark and then they would take the GeoJSON and then import that into another visualization tool? Is that what you were kind of imagining people would do? Tom: Yeah. Yeah, exactly. Jeremy: And I could see from the customer's perspective, a lot of them, they may have that end, uh, visualization in mind. So they might look for a tool that kind of just does both. Right. Tom: Yeah. Yeah. Certain people definitely, wanted that. And yeah, it was an interesting direction to go down. I think that market was going to be a lot different than the people who wanted to manage and edit data. And also, I, one thing that I had in mind a lot, uh, was if Placemark didn't work out, how much would people be burned? and I think if I, if I built it in a way that like everyone was heavily relying on the API and embeds, people would be suffer a lot more, if I eventually had to shut it down. every API that you release is really a, a long-term commitment. And instead for me, like guilt wise, having a product where you can easily export everything that you ever did in any format that you want was like the least lock in, kind of. Jeremy: Yeah. And I imagine the, the scope of the project too, you're making it much smaller if you, if you stick to that editing experience and not try to do everything. Tom: Yeah. Yeah. I, the scope was already pretty big. as you can tell from the open source project, it's, it's bigger than I wish it was. the whole time I was really hoping that I could figure out some niche that was much more compact. there's, I forget the name, but there's somebody who has a, an application that's very similar to Placemark in. Technical terms, but is just a hundred percent focused on planning septic systems. And I'm just like, if I just did this just for septic systems, like would that be a much, would that be 10,000 lines of code instead of 40,000 lines of code? And it would be able to perfectly serve those customers. but you know, that I didn't do enough experimentation to figure that out. Um, I, that's, I think one thing that I wish I had done a lot more was, pivot and do experiments. Jeremy: that septic example, do you know if it's a, a business in and of itself where it can actually support one person or a staff of people? Or is it, is that market just too small? Tom: I think it's still a solo bootstrapped project. yeah. And it's, it's so hard to tell whether a company's doing well or not. I could ask the person over DM. [00:21:58] Built the base technology before going public Jeremy: So when you were first starting. placemark. You were, you were doing it as a solo, developer. A solo entrepreneur, reallyyou worked on it for quite a while, I think before you announced, right? Like maybe a year or so? Tom: Yeah, yeah. Almost, almost a year, I think, maybe, maybe 10 months in the dark. Jeremy: I think that there's, there was a lot of overlap between the different directions that I would eventually go in and. So just building a collaborative editor that can edit map data fairly quickly and checks all the boxes of being able to import and export things, um, that is, was a lot of work. and I mean also I, I was, uh, freelancing during part of it, so it wasn't a hundred percent of my time. Tom: But that, that core, I think even now if I were to build something similar, I would probably still use that work. because that, whether you're doing the septic planning application or you're doing a general purpose kind of map editor or some kind of social application, a lot of that stuff will be in common. Um, and so I wanted to really get, like, to figure out that problem space and get a few solutions that I could live with. Jeremy: The base. libraries or technologies you were gonna pick to get the map and have the collaborative aspect. Those are all things you wanted to get settled first. And then you figured, okay, once I have this base, then I can go find the, you know, the, the, the customers or, or find the specifics of what I'm gonna build. Tom: Yeah, exactly. Jeremy: I I think you had said that going forward when you're gonna work on another project, you would probably still start the same way. [00:23:51] Geospatial is a tough industry, no public companies Tom: if I was working on a project in the geospatial space, I would probably heavily reference the work that I already did here. but I don't know if I'll go back to, to maps again. It's a tough industry. Jeremy: Is it because of the, the customer base? Is it because like people don't really understand the market in terms of who actually needs the maps? I'm kind of curious what you feel makes it tough. Tom: I think, well there are no, there are no public mapping companies. Esri is I think one of the 10 largest private companies in the us. but it's not like any of these geospatial companies have ever been like a pure play. And I think that makes it hard. I think maps are just, they're kind of like fonts in a way in which they are this. Very deep well of complexity, which is absolutely fascinating. If you're in it, it's enough fun and engineering to spend an entire career just working on that stuff. And then once you're out of it, you talk to somebody and you're just like, oh, I work on this thing. And they're like, oh, that you Google maps. Um, or, you know, I work at a font type like a, you know, a type factory and it's like, oh, do you make, uh, you know, courier in, uh, word. It's really infrastructure, uh, that we mostly take for granted, which is, that's, that means it's good in some ways. but at the same time, I, it's hard to really find a niche in which the mapping component is that, that is that useful. A lot of the companies that are kind of mapping companies. Like, I think you could say that like Strava and Palantir are kind of geospatial companies, both of them. but Strava is a fitness company and Palantir is a military company. so if you're, uh, a mapping expert, you kind of have to figure out what, how it ties into the real world, how it ties into the business world and revenue. And then maps might be 50% of the solution or 75% of the solution, but it's probably not going to be, this is the company that makes mapping software. Jeremy: Yeah, it's more like, I have this product that I'm gonna sell and it happens to have a map as a part of it. versus I'm going to sell you, tools that, uh, you know, help you make your own map. That seems like a, a harder, harder sell. Tom: yeah. And especially pro tools like the. The idea of people being both invested in terms of paying and invested in terms of wanting to learn the tool. That's, uh, that's a lot to ask out of people. [00:26:49] Knowing the market is tough but going for it anyways Jeremy: I think the things we had just talked about, about mapping being a tough industry and about there being like the low end is taken care of by Google, the high end is taken care of by Esri with ArcGIS. Uh, I think you mentioned in a blog post that when you started Placemark you, you, you knew all this from the start. So I'm kind of curious, like, knowing that, what made you decide like, I'm gonna, I'm gonna go for it and, you know, do it anyways. Tom: uh, I, well, I think that having seen, I, like I am a co-founder of val.town now, and every company that I've worked for, I've been pretty early enough to see how the sausage is made and the sausage is made with chaos. Like every company doesn't know what it's doing and is in an impossible fight against some Goliath figure. And the product that succeeds, if it ever does succeed, is something that you did not think of two or three years in advance. so I looked at this, I looked at the odds, and I was like, oh, these are the typical odds, you know, maybe someday I'll see something where it's, uh, it's an obvious open blue water market opportunity. But I think for the, for the most part, I was expecting to grind. Uh, you know, like even, even if, uh, the odds were worse, I probably would've still done it. I think I, I learned a lot. I should have done a lot more marketing and business and, but I have, I have no regrets about, you know, taking, taking a one try at solving a very hard to solve problem. Jeremy: Yeah, that's a good point in that the, the odds, like you said, are already stacked against you. but sometimes you just gotta try it and see how it goes, Tom: Yeah. And I had the, like I was at a time where I was very aware of how my life was set up. I was like, I could do a startup right now and kind of burn money for a little while and have enough time to work on it, and I would not be abandoning an infant child or, you know, like all of the things that, all the life responsibilities that I will have in the near future. Um. So, you know, uh, the, the time was then, I guess, [00:29:23] Being a solo developer Jeremy: And comparing it to your time at Mapbox and the other startups and, and I suppose now at val.town, when you were working on Placemark, you're the sole developer, you're in charge of everything. how did that feel? Did you enjoy that experience or was it more like, I, I really wish I had other people to, you know, to kind of go through this with, Tom: Uh, around the end I started to chat with people who, like might be co-founders and I even entertained some chats with, uh, venture capital people. I am fine with the, the day to day of working on stuff alone of making a lot of decisions. That's what I have done in a lot of companies anyway. when you're building the prototype or turning a prototype into something that can be in production, I think that having, uh, having other people there, It would've been better for my mentality in terms of not feeling like it was my thing. Um, you know, like feeling detached enough from the product to really see its flaws and really be open to, taking more radical shifts in approach. whereas when it's just you, you know, it's like you and the customers and your email inbox and, uh, your conscience and your existential dread. Uh, and you know, it's not like a co-founder or, uh, somebody to work with is gonna solve all of that stuff for you, but, uh, it probably would've been maybe a little bit better. I don't know. but then again, like I've also seen those kinds of relationships blow up a lot. and I wanted to kind of figure out what I was doing before, adding more people, more complexity, more money into the situation. But maybe you, maybe doing that at the beginning is kind of the same, you know, like you, other people are down for the same kind of risk that you are. Jeremy: I'm sure it's always different trade offs. I mean, I, I think there probably is a power to being able to unilaterally say like, Hey, this is, this is what I wanna do, so I'm gonna do it. Tom: Yeah. [00:31:52] Spending too much time on multiplayer without a business case Jeremy: You mentioned how there were certain flaws or things you may not have seen because you were so in it. Looking back, what, what were some of those things? Tom: I think that, uh, probably the, I I don't think that most technical decisions are all that important, um, that it never seems like the thing that means life or death for companies. And, you know, Facebook is still on PHP, they've fought, fixed, the problem with, with money. but I think I got rabbit holed into a few things where if I had like a business co-founder, then they would've grilled me about like, why are we spending? The, the main thing that comes to mind, uh, is real time multiplayer, real time. It was a fascinating problem and I was so ready to think about that all the time and try to solve it. And I think that took up a lot of my time and energy. And in the long term, most people are not editing a map. At the same time, seeing the cursors move around is a really fun party trick, and it's great for marketing, but I think that if I were to take a real look at that, that was, that was a mistake. Especially when the trade off was things that actually mattered. Like the amount of time, the amount, the amount of data that the, that could be handled at. At the same time, I could have figured out ways to upload a one gigabyte or two gigabyte or three gigabyte shape file and for it to just work in that same time, whereas real time made it harder to solve that problem, which was a lot closer to what, Paying customers cared about and where people's expectations were? Jeremy: When you were working on this realtime collaborative functionality, was this before the product was public? Was this something you, built from the start? Tom: Yeah. I built the whole thing without it and then added it in. Not as like a rewrite, but like as a, as a big change to a lot of stuff. Jeremy: Yeah, I, I could totally see how that could happen because you are trying to envision people using this product, and you think of something like Google Docs, right? It's very powerful to be typing in a document and see the other cursors and, um, see other people typing. So, I could see how you, you would make that leap and say like, oh, the map should, should do that too. Yeah. [00:34:29] Financial pressures of bootstrapping, high COL, and healthcare Tom: Yeah. Yeah. Um, and, you know, Figma is very cool. Like the, it's, it's amazing. It's an amazing thing. But the Figma was in the dark for way longer than I was, and uh, Evan is a lot smarter than I was. Jeremy: He probably had a big bag of money too. Right. Tom: Yeah. Jeremy: I, I don't actually know the history of Figma, but I'm assuming it's, um, it's VC funded, right? Tom: Uh, yeah, they're, they're kind of famous for just having, I don't think they raised that much in the beginning, but they just didn't hire very much and it was just like the two co-founders, or two or three people and they just kept building for long time. I feel like it's like well over three years. Jeremy: Oh wow. Okay. I think like in your case, I, I saw a comment from you where you were saying, this was your sole source of income and you gotta pay for your health insurance, and so you have no outside investments. So, the pressures are, are very different I think. Tom: Yeah. Yeah. And that's really something to on, to appreciate about venture capital. It gives you the. Slack in your, in your budget to make some mistakes and not freak out about it. and sadly, the rent is not going down anytime soon in, in Brooklyn, and the health insurance is not going down anytime soon. I think it's, it's kind of brutal to like leave a job and then realize that like, you know, to, to be admitted to a hospital, you have to pay $500 a month. Jeremy: I'm, I'm sure that was like, shocking, right? The first time you had to pay for it yourself. Tom: Yeah. And it's not even good. Uh, we need to fix this like that. If there's anything that we could do to fix entrepreneurship in this country, it's just like, make it possible to do this without already being wealthy. Um, it was, it was a constant stress. [00:36:29] Growth and customers Jeremy: As you worked on it, and maybe especially as you, after you had shipped, was there a period where. You know, things were going really well in terms of customers and you felt like, okay, this is really gonna work. Tom: I was, so, like, I basically started out by dropping, I think $5,000 in the business bank account. And I was like, if I break even soon, then I'll be happy. And I broke even in the first month. And that was amazing. I mean, the costs were low and everything, but I was really happy to just be at that point and that like, it never went down. I think that probably somebody with more, uh, determination would've kept going after, after I had stopped. but yeah, like, and also The people who used Placemark, who I actually chatted with, and, uh, all that stuff, they were awesome. I wish that there were more of them. but like a lot of the customers were doing cool stuff. They were supportive. They gave me really informative feedback. Um, and that felt really good. but there was never a point at which like the, uh, the growth scale looked like, oh, we're going to hit a point at which this will be a sustainable business within a year. I think it, according to the growth when I left it, it would've been like maybe three years until I would've been, able to pay my rent and health insurance and, live a comfortable life in, in New York. Jeremy: So when you mentioned you broke even that was like the expenses into the business, but not for actually like rent and health insurance and food and all that. Okay. Okay. can you say like roughly how much was coming in or how many customers you had? Tom: Uh, yeah, the revenue initially I think was, uh, 1500 MRR, and eventually it was like 4,000 or so. Jeremy: And the growth was pretty steady. [00:38:37] Bootstrapping vs fundraising Tom: Um, so yeah, I mean, the numbers where you're just like, maybe I could have kept going. but it's, the other weird thing about VCs is just that I think I have this rich understanding of like, if you're, if you're running a business that will be stressful, but be able to pay your bills and you're in control of it, versus running a startup where you might make life changing money and then not have to run a business again. It's like the latter is kind of better. Uh, if stress affects you a lot, and if you're not really wedded to being super independent. so yeah, I don't know between the two ways of like living your life, I, I have some appreciation for, for both. doing what Placemark entailed if I was living cheaply in a, in a cheap city and it didn't stress me out all the time, would've been a pretty good deal. Um, but doing it in Brooklyn with all the stress was not it, it wasn't affecting my life in positive ways and I, I wanted to, you know, go see shows at night with my friends and not worry about the servers going down. Jeremy: Even putting the money aside, I think that's being the only person responsible for the app, right? Probably feels like you can't really take a vacation. Right. Tom: Yeah, I did take a vacation during it. Like I went to visit my partner who was in, uh, Germany at the time, and we were like on a boat, uh, between Germany, across the lake to Switzerland, and like the servers went down and I opened up my laptop and fixed the servers. It's just like, that is, it's a sacrifice that people make, but it is hard. Jeremy: There's, there's on call, but usually it's not just you 24 7. Tom: Yeah. If you don't pick up somebody else [00:40:28] Financial stress and framing money spent as an investment Jeremy: Yeah, yeah, yeah, I guess at what point, because I'm trying to think. You started in 2021 and then maybe wrapped up, was it sometime in 2024? Tom: Uh, I took a job in, uh, I, I mean I joined val.town in the early 2023 and then wrapped up in November, 2023. Jeremy: At what point did you really start feeling the, the stress? Like I, I imagine maybe when you first started out, you said you were doing consulting and stuff, so, um, probably things were okay, but once you kind of shifted away from that, is that kind of when the, the, the worries about money started coming in? Tom: Yeah. Um, I think maybe it was like six or eight months, um, in. Just that I felt like I wasn't finding, uh, like a, a way to grow the product without adding lots of complexity to it. and being a solo founder, the idea of succeeding, but having built like this hulking mess of a product felt just as bad as not succeeding. like ideally it would be something that I could really be happy maintaining for the long term. Uh, but I was just seeing like, oh, maybe I could succeed by adding every feature in QGIS and that's just not, not a, not something that I wanted to commit to. but yeah, I don't, I don't know. I've been, uh, do you know, uh, Ramit Sethie he's like a, Jeremy: I don't. Tom: an internet money guy. He's less scummy than the rest of them, but still, I. an internet money guy. Um, but he does adjust a lot of stuff about like, money psychology. And that has made me realize that a lot of what I thought at the time and even think now is kind of a rational, you know, like, I think one of the main things that I would do differently is just set a budget for Placemark. Like if I had just set away, like, you know, enough money to live on for a year and put that in, like the, this is for Placemark bucket, then it would've felt better to me then having it all be ad hoc, month to month, feeling like you're burning money instead of investing money in a thing. but yeah, nobody told me, uh, how to, how to think about it then. Uh, yeah, you only get experience by experiencing it. Jeremy: You're just seeing your, your bank account shrinking and there's this, psychological toll, right? Where you're not, you're not used to that feeling and it, it probably feels like something's wrong, Tom: Yeah, yeah. I'm, I think it, I'm really impressed by people who can say, oh, I invested, uh, you know, 50 or a hundred thousand dollars into this business and was comfortable with that risk. And like, maybe it works out, maybe it doesn't. Maybe you just like threw a lot of money down into that. and the people, I think with the healthy, productive, uh, relationship with it. Do think of it as like, oh, I, I paid for kind of a bet on a risk. and that's, that's what I was doing anyway. You know, like I was paying my rent and my health insurance and spending all my time working on the product instead of paying, uh, freelance work. but if you don't frame it that way, it doesn't feel like an investment. It feels like you're making a risky gamble. Jeremy: Yeah. And I think that makes sense to, to actually, I think, like you were saying, have a separate account or a separate thing set aside where you are like, this is, this is this money for this purpose. And like you said, look at it as an investment, which with regular investments can go down. Tom: Yeah, exactly. Yeah. Jeremy: Yeah [00:44:26] In hindsight might have raised money or tried smaller bets Jeremy: Were there, there other things, whether technical or or business wise, that, that if you were to to do it again, you would do differently? Tom: I go back and forth on whether I should have raised venture capital. there are, there's kind of a, an assumption in venture capital that once you're on it, you have to go the whole way. You have to become a billion dollar company, uh, or at least really tell people that you're going to be a billion dollar company and I am not. yeah, I, I don't know. I've seen, I've seen other companies in my space, or like our friends of my current company who are not really targeting that, or ones who were, and then they had somewhere in between the billion dollar and the very small outcome. Uh, and that's a little bit of a point in the favor of accepting a big pile of money from the venture capitalists. I'm also a little bit biased right now because val.town has one investor and he's like the, the best venture capitalist that I have ever met. Big fan. don't quote me on that. If he sacks me in like a year, we'll see. Um, but uh, yeah, there, I, I think that I understand more why people take that approach. or I've understood more why people take like the venture capital but not taking $300 million from SoftBank approach. yeah, and I don't know, I think that, trying a lot of things also seems really appealing. Uh, people who do the same kind of. of Maybe 10 months, but they build four or five different products or three different products instead of just one. I think that, that feels, feels like a good idea to me. Jeremy: And in doing that, would that be more of a, like as a solo entrepreneur or you, you're thinking you would take investment and then say, I'm gonna try all these things with, with your money. Tom: Oh, I've seen both. I, that I, yeah, one friend's company has pivoted like four times between very different ideas and yeah, it, it's one way to do it, but I think in the long term, I would want to do that as a solo developer and try to figure out, you know, something. but yeah, I, I think, uh, so much of it is mindset, that even then if I was working on like three different projects, I think I. My qualifications for something being worth, really adopting and spending all my time doing, you just have to accept, uh, a lot of hits and a lot of misses and a lot of like keeping things alive and finding out how to turn them into something. I am really inspired by my friends who like started around the same time that I did and they're not that much further in terms of revenue and they're like still, still doing it because that is what they want to do in life. and if you develop the whole ecosystem and mindset around it, I think that's somewhere that people can stay and, and be happy. just trying to find, trying to find a company that they own and control and they like. Jeremy: While, while making the the expenses work. Tom: Yeah. Yeah. that's the, that's the hard part, like freelancing on the side also. I probably could have kept that up. I liked my freelance clients. I would probably still work with them as well. but I kind of just wanted the, I wanted the focus, I wanted the motivation of, of being without a net. Jeremy: Yeah, I mean, energy wise, do you think that that would've worked? I mean, I imagine that Placemark took a lot of your time when you were working full time, so you're trying to balance, you know, clients and all your customers and everything you're doing with the software. It just feels like it might be a lot. Tom: Yeah. Yeah. Maybe with different freelance clients. I, I loved my freelance clients because I, after. leaving config. I, I wanted to work on climate change stuff and so I was working for climate change foundations and that is not the way to max out your paycheck. It's the way to feel good about your conscience. And so I still feel great about those projects, but in the future, yeah, I would probably just work for, uh, you know, a hedge fund or something. [00:49:02] Marketing to developers but not potential customers Jeremy: I think something you mentioned in one of your posts is that you maybe could have spent more time or had a different approach with marketing. Maybe you could kind of say what you did do and then what maybe worked and what didn't. Tom: Yeah. So I like my sweet spot is writing documentation and blog posts and technical stuff. And so I did a lot of that and a lot of that like worked in a way that didn't matter. I am at this point, weirdly good at writing stuff that gets on Hacker News. I've written a lot of stuff that's gotten to the top of Hacker News and unfortunately, writing about your technical approach and your geospatial project for handling errors, uh, in your JavaScript code is not really a way to get customers. and I think doing a lot of documentation was also great, but it was also, I think that the, the thing that was missing is the thing that I think Mapbox does fairly well now, in which the homepage really pushes you toward use cases immediately. and I should have been saying to each customer who had anything compelling as a use case, like, let's write an article about you and what you're doing, and here's how you use this in your industry. and that probably would've also been like a good, a good way to figure out which of those verticals was the one that was most worth spending all the time on. yeah. So it, it was, it was a lot of good marketing to nerds. and it could have been better in terms of marketing to actual customers and to people who are making the buying decisions. Jeremy: Yeah. Looking at the, the Placemark blog, I can definitely see how as a developer, a lot of the posts are appealing to me, right? It's about how you worked on a technical challenge or decisions you made, but maybe less so to somebody who they wanna. Draw a map to manage their crops. They're like, I don't care about any of this. Right. Tom: Yeah, like the Mapbox blog used to be, just all that stuff as well. We would write about designing protocol buffer layouts, and it was amazing for hiring and amazing for getting nerds in the door. But now it's just, Toyota is launching with, Mapbox Maps or something like that. And that's, that's what you, you should do if you're trying to sell a product. Jeremy: Yeah. And I think the, the sort of technical aspect, it makes sense too. If you're venture funded and you are looking to hire, right? You wanna build your team and you just want to increase like, the amount of stuff you're building and not worrying so much about, am I gonna have a paycheck next Tom: Yeah. Yeah. I, I just kind of do it because it's fun, which is not the right reason to do it, but, Yeah, I mean, I still write my blog mostly just because it's, it's a fun thing to do, but it's not the best way to, um, to run a business. Jeremy: Yeah. Well, the fun part is important too though. Tom: Yeah. Yeah. That's, that's maybe the whole thing. May, that's maybe the most important thing, but you can't do it if you don't do the, the money part. [00:52:35] Most customers came from existing audience Jeremy: Right. So the people who did find you, was it mostly word of mouth from people who did identify with the technical posts, or were there places that surprised you, that people found you? Tom: Uh, a lot of it was people who were familiar with the Mapbox ecosystem or with, with me. and then eventually, yeah, a few of the users came in through, um, through Hacker News, but it was mostly, mostly word of mouth also. The geospatial community is like fairly tight and it's, and it's not too hard to be the person who writes the article about some geospatial challenge that everyone finds. Jeremy: Hmm. Okay. Yeah, that's a good point about like being in that community, especially since you've done so much work in geospatial and in open source that you have this little, this built-in audience, I guess. Tom: yeah. Which I appreciate. It makes me nervous, but yeah. [00:53:43] Val.town marketing to developers Jeremy: Comparing that to something like val.town, how is val.town marketing? How is it finding users? 'cause from what I can tell, it's, it's getting a lot of, uh, a lot of people coming in, right? Tom: Yeah. Uh, well, right now our, our kind of target user, or the user that we think of is a hobbyist, is somebody who's, sometimes a pro developer or somebody, sometimes just somebody who's really interested in the field. And so writing these things that are just about, you know, programming, does super well. Uh, but it, we have exactly the same problem and that that is kind of being revamped as we speak. uh, we hired somebody who actually knows marketing and has a good sense for it. And so a lot of that stuff is shifting to show you what you can do with val.town because it, it suffers from the same problem as well. It's an empty text field in which you can type, type script, code, and it runs. And knowing what you can do with that or what you should do with that is, is hard if you don't have a grasp of TypeScript and web applications. so pretty soon we'll have pages which are like, here's how to connect linear and GitHub with OW Town, or, you know, two nouns connect them, for all of those companies and to do automations and all these like concrete applications. I think that's, you have to do it. You have to figure it out. Jeremy: Just briefly for someone who hasn't heard of val.town, like what, what does it do? Tom: Uh, val.town is a social website, so it has comments and likes and all of that stuff. but it's for writing these little snippets of TypeScript and JavaScript code that run. So a lot of them are websites, some of them are automations, so they receive emails or send emails or connect one service to another. And yeah, it's, it's like combining some aspects of, GitHub or like a code platform, uh, but with the assumption that every time that you save, everything's instantly deployed. Jeremy: So it's maybe a little bit like, um, like a glitch, I guess? Tom: Uh, yeah. Yeah, it takes a lot of experience, a lot of, uh, inspiration from Glitch. Jeremy: And I, I think, like you had mentioned, you enjoy writing the, the technical blog posts and the documentation. And so at least with val.town, your audience is developers versus, the geospatial community who probably largely doesn't care about, TypeScript and the, the different technical decisions there. Tom: Yeah, it, it makes it easier, that's for sure. The customer is, is me. [00:56:30] Shifting from solo to in-person teams Jeremy: Nice. Yeah. Looking at, you know, you, you worked as a, a solo developer for Placemark, and then now you've got a team of, is it like maybe five Tom: Uh, it is seven at the moment. Jeremy: Seven people. Okay. Are you all in person or is it, remote Tom: We all sit around two tables in Brooklyn. It's very nice. Jeremy: So how did that feel? Like shifting from, I'm in, I don't know if you worked from home while you were working on Placemark or if you were in coworking spaces, but you're, you're shifting from I'm like in my own head space doing everything myself to, to, I'm in a room with all these people and we're like working on this thing together. I'm kind of curious like how that felt for you. Tom: Yeah, it's been a big difference. And I think that I was just talking with, um, one, one of our, well an engineer at, at val.town about how everyone kind of had, had been working remote for obvious pandemic world reasons. And this kind of privilege of just being around the same table, if that's what you like is, a huge difference in terms of, I just remember having to. Trick myself into going on a walk around the block because I would get into such a dark mental head space of working on the same project for eight hours straight and skipping lunch. and now there's a little bit more structure. yeah, it's, it's been, it's been a overall, an improvement. Some days I wish that I could go on a run at noon 'cause that's the warmest time of the day. but, uh, overall, like it makes things so much easier. just reading the emotions in people's faces when they're telling you stuff and being able to, uh, not get into discussions that you don't need to get into because you can talk and just like understand each other very quickly. It's, it's very nice. I don't wanna force everyone to do it, you know, but it it for the people who want it, they, they, uh, really enjoy it. Jeremy: Yeah. I think if you have the right set of people, it's definitely more enjoyable. And um, if you don't, maybe not so Tom: Yeah, we haven't hired any, like, extremely loud chewers yet or anything like that, but yeah, maybe my story will change. Jeremy: No, no one microwaving fish. Tom: No, there's, uh, yeah, thankfully the microwave is outside of the office. Jeremy: Do you live close to the office? Tom: Yeah. Yeah. Like most of the team is within a 20 or 30 minute walk of the office and it's very fortunate. I think there's been something of a mass migration to New York. A lot of us didn't live in New York before four years ago, and now all of us do. it's, it's, uh, it's very comfortable to be here. Jeremy: I think that makes, uh, such a big difference. 'cause I think the majority of people, at least within the US you know, you're, you're getting in your car, you're sitting in traffic. and I know people who, during the pandemic, they actually moved further, right? Because they went, oh, like, uh, I don't need to come into the office. but yeah, if you are close enough where you can walk, yeah, I think that makes a big difference. Tom: Oh yeah. If I had to drive to work, I think my blood pressure would be so much higher. Uh, especially in New York. Oh, I feel so bad for the people who have to drive, whereas I'm just walking with, you know, a bagel in hand, enjoying listening to the birds. Jeremy: Yeah. Yeah. well now they have, what is it, the congestion pricing in Tom: Yeah. Yeah. We're all in Brooklyn, so it doesn't affect us that much, but it's supposedly, it's, it's working great. Um, yeah. I hope we can keep it. Jeremy: I've never driven in New York and I, I wouldn't want to Tom: Yeah. It's only for the brave or the crazy. [01:00:37] The value of public writing and work Jeremy: I think that's probably a good place to, to wrap up, but is there any other thoughts you had or things you wanted to mention? Tom: No, I've just, uh, thank you so much. This has been, this has been a lot of fun. You're, you're very good at this as well. I feel like it's, uh, Jeremy: Thank you Tom: It's not easy to, to steer a conversation in a way that makes awkward people sound, uh, normal. Jeremy: I wouldn't say that, but um, what's been actually pretty helpful to me is, you have such a body of work, I guess I would say, in terms of your blogging and, just the amount that you write and the long history of projects that, that there's, you know, there's a lot to talk about and I'm sure it helps, helps your thought process as well. Tom: Yeah. I, I've been lucky to have a lot of jobs where people, where companies were like, cool with publishing everything, you know? so a lot of what I've done is, uh, is public. it's, it's, uh, I'm very, very thankful for like, early on that being a big part of company culture. Jeremy: And you can definitely tell, I think for people who look at the Placemark blog posts or, or now your, your val.town blog posts, like there's, there's a clear difference when somebody like is very intentional and, um, you know, it's good at writing versus you're doing it because, um, it's your corporate responsibility or whatever, like people can tell. Yeah. Tom: Yeah. You can't fake being interested. so you gotta work on things that are interesting. Jeremy: Tom, thanks again for, for agreeing to chat. This was fun. Tom: Yeah thank you so much.

Andy and Michael discuss the FOSDEM 2025 conference and the open-sourcing of the Moxie toy server. They also explore the use of Clams for water monitoring, Minecraft worlds generated from Open Street Map data, and VR glasses for mice.

Aktuelle Top-Navis von Garmin, Wahoo und Hammerhead im Vergleich. Garmins neue Fenix 8 mit Amoled-Display, Sprachausgabe. Wer läuft am längsten durch die Wüste, und wer kann mit seinen Bordkarten auch offline neue Routen berechnen? OpenStreetMap ist gerade 20 Jahre alt geworden - und schon jetzt auf den meisten Outdoor-Geräten zu finden. Komoot baut seinen Spitzenplatz weiter aus - was gab es dort neues, und wohin gehen die Trends im nächsten Jahr?

In this week's episode, I'm thrilled to welcome back Ariel Seidman, founder of HiveMapper. Ariel was my very first podcast guest back in 2019, and HiveMapper has come a long way since then! We explore how HiveMapper has evolved from a drone-based mapping system to a cutting-edge platform collecting street-level data at a global scale. Ariel shares the challenges of scaling large-scale mapping efforts, the pivot to building their own hardware, and the role of blockchain-based incentives in driving adoption. Here are just a few topics we cover: Why HiveMapper shifted focus from drones to street-level mapping. The power of combining hardware and software to solve mapping challenges. How HiveMapper has already mapped 28% of the global road network. The revolutionary edge computing and data filtering techniques driving efficiency. What it takes to compete with industry giants like Google Maps. Whether you're fascinated by the intersection of geospatial technology and innovation or looking for insights into scaling impactful startups, this episode is packed with value. Let me know your thoughts or hit reply if you'd like to discuss the episode!   https://beemaps.com/ Connect with Ariel here https://www.linkedin.com/in/aseidman/   PS I have just finished creating a web-based tool that lets you explore and download OpenStreetMap data, It is a bit different from other tools and I would appreciate some feedback.  https://mapscaping.com/openstreetmap-category-viewer/       

Für viele ist OpenStreetMap nicht mehr aus dem Alltag wegzudenken. Dieses Jahr feiert das Projekt das 20-jährige Bestehen - zusammen mit Jochen Topf besprechen wir neben der Geschichte auch zahlreiche Tools und Highlights.

This week we pontificate on Gnome OS and whether KDE and Gnome really need their own distros, the much-delayed progress in Wayland development that's finally happening, and whether here's really a trend from Ubuntu back to Debian. We discuss the Pi CM5 announcement, the new UEFI bootkit announcement, and the leaked steam controller designs. For tips we have dstat for system monitoring, and SSH agent forwarding to forward your SSH keys on remote systems. The show notes are at https://bit.ly/4idT1Qb and until next week! Host: Jonathan Bennett Co-Host: Rob Campbell Want access to the video version and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Privacy & Security FAQ: Week Ending November 19th, 20241. What happened with T-Mobile and Chinese hackers? Chinese hackers, suspected of ties to Chinese intelligence, infiltrated T-Mobile as part of a larger cyberespionage operation. This attack targeted telecom companies to gather intelligence on high-value targets. While T-Mobile claims no significant impact on their systems or customer data, the breach raises concerns about the security of telecommunications networks and the potential for surveillance. Google is rolling out an AI-powered scam call detection feature for Android phones, starting with Pixel 6 and newer models. This feature analyzes real-time conversation patterns to detect potential scams and alerts users through audio, haptic, and visual warnings. The system operates entirely on the device, ensuring privacy by not storing or transmitting call data externally. India's competition watchdog fined Meta $25.4 million and ordered WhatsApp to stop sharing user data with other Meta units for advertising for five years. This action stems from WhatsApp's 2021 privacy policy update, which mandated data sharing with Meta companies without an opt-out option. The watchdog deemed this practice as an abuse of Meta's dominant position and coercive towards users. Legal documents from a US lawsuit between NSO Group and WhatsApp revealed that NSO Group, not their government clients, directly install and extract information from phones targeted by their Pegasus spyware. This contradicts NSO's claims that clients solely operate the spyware. The revelation raises concerns about the control and accountability of NSO Group's powerful surveillance technology. ChatGPT's desktop app for macOS can now read code from developer-focused apps like VS Code, Xcode, and TextEdit. This integration allows developers to directly send code snippets to ChatGPT for analysis and assistance without manual copy-pasting. While it currently lacks the ability to write code directly into apps, this feature marks a step towards streamlined AI assistance in coding workflows. DeFlock is an open-source project utilizing Open Street Map to map the locations of automated license plate readers (ALPRs) worldwide. Concerned about the proliferation of these surveillance devices, the project encourages crowdsourced reporting of ALPR locations, including details like camera direction. You can contribute to this initiative by reporting ALPRs in your area on the DeFlock website: https://deflock.me/report. Internal emails revealed that the US Secret Service debated the need for warrants when using location data from smartphone apps. Some officials argued that users' acceptance of app terms of service implied consent for data sharing, even if those terms didn't explicitly mention sharing with law enforcement. This raised concerns about government agencies accessing private location data without proper legal authorization. How can you enhance your privacy and security? For secure communication: Consider using encrypted messaging apps like Signal or Session. Protect against phone fraud: Be wary of suspicious calls and consider enabling Google's AI-powered scam call detection. Control data sharing: Scrutinize app permissions and privacy policies before granting access to personal information. Support privacy initiatives: Contribute to projects like DeFlock and advocate for stronger data protection laws. Stay informed: Follow reputable sources for news on privacy and security issues to make informed decisions about your digital life.

OpenFreeMap puts OpenStreetMap data on your website for free, Fatih Arslan builds a Dieter Rams inspired iPhone dock, Joseph Gentle thinks the Rust programming language feels like a first-gen product & the web dev community is debating the viability of Web Components once again.

OpenFreeMap puts OpenStreetMap data on your website for free, Fatih Arslan builds a Dieter Rams inspired iPhone dock, Joseph Gentle thinks the Rust programming language feels like a first-gen product & the web dev community is debating the viability of Web Components once again.

OpenFreeMap puts OpenStreetMap data on your website for free, Fatih Arslan builds a Dieter Rams inspired iPhone dock, Joseph Gentle thinks the Rust programming language feels like a first-gen product & the web dev community is debating the viability of Web Components once again.

Neben eurem Feedback besprechen wir auch die Zusammenhänge von UEFI, Secure Boot und Windows-/Linux-Dualboot-Systemen. Das OpenSteetMap-Projekt feiert 20-jähriges Bestehen, während Serpent OS als neue Linux-Distribution erscheint. Vanilla OS wird nach langer Entwicklungszeit in Version 2 veröffentlicht. Debian schraubt am Solver der Paketverwaltung und uBlock Origin stellt die Chrome-Version des beliebten Addons ein. Die Community freut sich über die erste Alpha von Pop!_OS 24.04, die auch den COSMIC-Desktop enthält. Die Fedora-Community stellt mit Ramalama ein weiteres KI-Werkzeug vor während Manjaro an einem Immutable-Ableger arbeitet.

heise-online-Chefredakteur Dr. Volker Zota (@DocZet), Markus Will und Malte Kirchner (@maltekir) sprechen in dieser Ausgabe der #heiseshow unter anderem über folgende Themen: - Offene Alternative: 20 Jahre OpenStreetMap – OpenStreetMap feiert sein 20-jähriges Jubiläum als offene Kartographie-Plattform. Wie hat sich das Projekt im Laufe der Zeit entwickelt? Kann OpenStreetMap mit kommerziellen Anbietern wie Google Maps mithalten? Welche Bedeutung hat die Open-Source-Philosophie für die Zukunft der digitalen Kartographie? - Lange Leitung: Erst ein Viertel der Glasfaser-Gelder ausgezahlt – Die Auszahlung von Fördergeldern für den Glasfaserausbau in Deutschland verläuft schleppend. Warum wurden bisher nur 25 Prozent der Mittel ausgezahlt? Welche Hindernisse gibt es beim Breitbandausbau? Wie kann der Prozess beschleunigt werden, um die digitale Infrastruktur zu verbessern? - Verlockender Deal: Google, Meta und die Jugendlichen – Ein geheimer Deal zwischen Google und Meta soll darauf abzielen, junge Nutzer anzulocken. Was sind die Details dieser Vereinbarung? Welche ethischen Fragen wirft diese Strategie auf? Wie können Jugendliche besser vor manipulativen Praktiken in sozialen Medien geschützt werden? Außerdem wieder mit dabei: ein Nerd-Geburtstag, das WTF der Woche und knifflige Quizfragen.

heise-online-Chefredakteur Dr. Volker Zota (@DocZet), Markus Will und Malte Kirchner (@maltekir) sprechen in dieser Ausgabe der #heiseshow unter anderem über folgende Themen: - Offene Alternative: 20 Jahre OpenStreetMap – OpenStreetMap feiert sein 20-jähriges Jubiläum als offene Kartographie-Plattform. Wie hat sich das Projekt im Laufe der Zeit entwickelt? Kann OpenStreetMap mit kommerziellen Anbietern wie Google Maps mithalten? Welche Bedeutung hat die Open-Source-Philosophie für die Zukunft der digitalen Kartographie? - Lange Leitung: Erst ein Viertel der Glasfaser-Gelder ausgezahlt – Die Auszahlung von Fördergeldern für den Glasfaserausbau in Deutschland verläuft schleppend. Warum wurden bisher nur 25 Prozent der Mittel ausgezahlt? Welche Hindernisse gibt es beim Breitbandausbau? Wie kann der Prozess beschleunigt werden, um die digitale Infrastruktur zu verbessern? - Verlockender Deal: Google, Meta und die Jugendlichen – Ein geheimer Deal zwischen Google und Meta soll darauf abzielen, junge Nutzer anzulocken. Was sind die Details dieser Vereinbarung? Welche ethischen Fragen wirft diese Strategie auf? Wie können Jugendliche besser vor manipulativen Praktiken in sozialen Medien geschützt werden? Außerdem wieder mit dabei: ein Nerd-Geburtstag, das WTF der Woche und knifflige Quizfragen.

In this episode, we chat with Luis Villa, co-founder of Tidelift, about everything from supporting open source maintainers to coding with AI. Luis, a former programmer turned attorney, shares stories from his early days of discovering Linux, to his contributions to various projects and organizations including Mozilla and Wikipedia. We discussed the critical importance of open source software, the challenges faced by maintainers, including burnout, and how Tidelift works toward compensating maintainers. We also explore broader themes about the sustainability of open source projects, the impact of AI on code generation and legal concerns, and the need for a more structured and community-driven approach to long-term project maintenance.   00:00 Introduction 03:20 Challenges in Open Source Sustainability 07:43 Tidelift's Role in Supporting Maintainers 14:18 The Future of Open Source and AI 32:44 Optimism and Human Element in Open Source 35:38 Conclusion and Final Thoughts   Guest: Luis Villa is co-founder and general counsel at Tidelift. Previously he was a top open source lawyer advising clients, from Fortune 50 companies to leading startups, on product development, open source licensing, and other matters.  Luis is also an experienced open source community leader with organizations like the Wikimedia Foundation, where he served as deputy general counsel and then led the Foundation's community engagement team. Before the Wikimedia Foundation, he was with Greenberg Traurig, where he counseled clients such as Google on open source licenses and technology transactions, and Mozilla, where he led the revision of the Mozilla Public License.  He has served on the boards at the Open Source Initiative and the GNOME Foundation, and been an invited expert on the Patents and Standards Interest Group of the World Wide Web Consortium and the Legal Working Group of OpenStreetMap.  Recent speaking engagements include RedMonk's Monki Gras developer event, FOSDEM, and as a faculty member at the Practicing Law Institute's Open Source Software programs. Luis holds a JD from Columbia Law School and studied political science and computer science at Duke University.  

Thanks for listening to another episode of English Go podcast! If you enjoy listening to this podcast, please join the English Go community at https://englishgo.co.uk/link/community

In this episode, I welcome Jason Gilman, a Principal Software Engineer at Element 84, to explore the exciting world of natural language geocoding. Key Topics Discussed: Introduction to Natural Language Geocoding: Jason explains the concept of natural language geocoding and its significance in converting textual descriptions of locations into precise geographical data. This involves using large language models to interpret a user's natural language input, such as "the coast of Florida south of Miami," and transform it into an accurate polygon that represents that specific area on a map. This process automates and simplifies how users interact with geospatial data, making it more accessible and user-friendly. The Evolution of AI and ML in Geospatial Work: Over the last six months, Jason has shifted focus to AI and machine learning, leveraging large language models to enhance geospatial data processing. Challenges and Solutions: Jason discusses the challenges of interpreting natural language descriptions and the solutions they've implemented, such as using JSON schemas and OpenStreetMap data. Applications and Use Cases: From finding specific datasets to processing geographical queries, the applications of natural language geocoding are vast. Jason shares some real-world examples and potential future uses. Future of Geospatial AIML: Jason touches on the broader implications of geospatial AI and ML, including the potential for natural language geoprocessing and its impact on scientific research and everyday applications. Interesting Insights: The use of large language models can simplify complex geospatial queries, making advanced geospatial analysis accessible to non-experts. Integration of AI and machine learning with traditional geospatial tools opens new avenues for research and application, from environmental monitoring to urban planning. Quotes: "Natural language geocoding is about turning a user's textual description of a place on Earth into a precise polygon." "The combination of vision models and large language models allows us to automate complex tasks that previously required manual effort." Additional Resources: Element 84 Website State of the Map US Conference Talk on YouTube Blog Posts on Natural Language Geocoding Connect with Jason: Visit Element 84's website for more information and contact details. Google "Element 84 Natural Language Geocoding" for additional resources and talks.

This is a recap of the top 10 posts on Hacker News on July 30th,2024.This podcast was generated by wondercraft.ai(00:40): Dear AI Companies, instead of scraping OpenStreetMap, how about a $10k donation?Original post: https://news.ycombinator.com/item?id=41109926&utm_source=wondercraft_ai(01:44): Our audit of HomebrewOriginal post: https://news.ycombinator.com/item?id=41114839&utm_source=wondercraft_ai(02:57): If we want a shift to walking, we need to prioritize dignityOriginal post: https://news.ycombinator.com/item?id=41105944&utm_source=wondercraft_ai(03:58): A eulogy for Dark Sky, a data visualization masterpiece (2023)Original post: https://news.ycombinator.com/item?id=41109799&utm_source=wondercraft_ai(05:09): Meta to pay Texas $1.4B for using facial recognition without users' permissionOriginal post: https://news.ycombinator.com/item?id=41111145&utm_source=wondercraft_ai(06:27): Porffor: A from-scratch experimental ahead-of-time JS engineOriginal post: https://news.ycombinator.com/item?id=41112854&utm_source=wondercraft_ai(07:36): C Macro Reflection in ZigOriginal post: https://news.ycombinator.com/item?id=41106686&utm_source=wondercraft_ai(08:45): Calculating the cost of a Google DeepMind paperOriginal post: https://news.ycombinator.com/item?id=41107721&utm_source=wondercraft_ai(10:07): Why doesn't advice work?Original post: https://news.ycombinator.com/item?id=41109891&utm_source=wondercraft_ai(11:18): Fake job interviews are securities fraudOriginal post: https://news.ycombinator.com/item?id=41112855&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

Bruno Sanchez is the Executive Director of the Clay Foundation, which just released their v1 of a “Foundational Model of Earth”. We talk about what that means, building open source & non profits and can't help but draw parallels to the not-so-open anymore OpenAI. Previously Bruno was the Program Director of the Microsoft Planetary ComputerSponsor: OpenCageUse OpenCage for your geocoding needs with their APIGeomobShownotesNote: Links to books are Amazon Affiliate links. I earn a small commission if you buy any of these books.ClayGithub repoWebsiteMy previous interview with BrunoBook & Podcast recommendationA Thousand Brains by Jeff Hawkins (Affiliate Link)Bad Therapy by Abigael Shrier (Affiliate Link)Timestamps(00:00) - Intro(01:59) - Sponsor: OpenCage(03:39) - What is a Foundational Model?(08:45) - Foundational Task(11:00) - Embeddings, and why they matter(13:49) - Comparing to compression algorithms(16:57) - What do embeddings enable?(19:50) - Finding the Relationship between data(24:16) - Implementation of monitoring all the data - I believe this is where you're going with the question(25:44) - Implementation details(27:52) - Validating a foundational model(33:49) - Earth is a "limited problem"(42:47) - Funding as a non-profit(47:53) - Raising enough philanthropic funding(53:02) - A Litmus test for open projects(56:26) - Future predictions(58:01) - Transparency/privacy(01:00:53) - Commercial data(01:03:36) - Openstreetmap(01:05:49) - Updating foundational models(01:12:17) - Clay model v2?(01:13:43) - Dataset to embedding size comparison(01:14:41) - Model v2 - continued(01:16:45) - Difference working at a non-profit vs a corp(01:20:27) - Book & Podcast recommendation(01:24:01) - Support the podcast on Patreon!Support the podcast on PatreonMy TwitterPodcast TwitterRead Previous Issues of the NewsletterEdited by Peter XiongFind more of his work

Would you like to get more practice working with APIs in Python? How about exploring the globe using the data from OpenStreetMap? Christopher Trudeau is back on the show this week, bringing another batch of PyCoder's Weekly articles and projects.

Sponsor: OpenCageUse OpenCage for your geocoding needs with their APIGeomobShownotesNote: Links to books are Amazon Affiliate links. I earn a small commission if you buy any of these books.GeoLayersgeolayers.appJohnny HarrisMarkus's cameo in a recent videoSearch PartyFeltProcreate dreamsJason Boone's episodePodcast recommendation: Syntax.fmTimestamps(00:00) - Intro(02:26) - Sponsor: OpenCage(03:52) - Markus Describes himself(04:29) - GEOlayers in simple terms(05:50) - From Motion Designer, to Map Animation Developer(07:51) - The team behind GEOlayers(08:20) - How does a Motion Designer turn into software engineer?(10:45) - Tricky nature of Map Animation(13:10) - OpenStreetMap(14:57) - Markus before and after diving into GIS(17:01) - Map projections(20:01) - Business Model & Funding(24:08) - Self Funding(26:38) - Being your own user(27:37) - GEOLayers used on Youtube(30:23) - Working with creator, example of Johnny Harris(32:20) - Paid Support(33:33) - Focusing ones time on what you enjoy doing(35:11) - Making a web app(42:35) - Subscription models(46:34) - Expectations in modern software business models(49:22) - High tech barrier to entry(55:01) - Inspiration from 2 other projects(01:05:32) - The future of GEOLayers(01:07:21) - Local vs Web based software(01:16:13) - Marketing & Social Media(01:20:50) - Book/podcast recommendation(01:23:18) - Support the podcast on PatreonSupport the podcast on PatreonMy video on an introduction to satellite imagesWebsiteMy TwitterPodcast TwitterRead Previous Issues of the NewsletterEdited by Peter XiongFind more of his work

Foundations of Amateur Radio As a self-proclaimed radio nerd I'm aware of the various amateur bands. Depending on your license, your familiarity will likely vary. I've never been on 6m for example, but I have a good working relationship with the 10m band. Amateur bands aside, there's plenty of other activity across the radio spectrum. It occurred to me that I've never actually stopped to take note of what specifically I can hear from my own station. Think of it as a station frequency survey. Obvious sources are AM and FM radio broadcasters. Then there's the aviation frequencies, the local control tower, arrival and departure frequencies as well as Perth airport ground on occasion. There's the ATIS, the Automatic Terminal Information Service. There was a time when I could hear various aviation non-directional beacons, or NDBs, that are near me, but many of them were switched off in 2016. I haven't yet found a current list of which of the 213 remaining navigation aids that form part of the Backup Navigation Network across Australia are still on the air. As it happens, there's currently some horrendous noise on HF with several new potential sources that I have not yet identified, a pool pump, a bank of solar panels, plasma TV, you name it. Staying with aviation, I've briefly played with Automatic Dependent Surveillance-Broadcast, better known as ADS-B, or ADSB, on 1090 MHz. If you have a PlutoSDR, I updated the dump1090 program to use Open Street Map several years ago. You can find it on my VK6FLAB GitHub page. If you want to see some very interesting visualisations for ADSB, have a look at the adsb.exposed website. Further up the frequencies are things like 2.4 and 5 GHz Wi-Fi. In a previous life, before I was an amateur, I played with Ku-band satellite frequencies in the range between 12 to 18 GHz, specifically DVB-S, or Digital Video Broadcasting - Satellite. While that's an impressive list of things, it leaves an awful lot of unexplored territory. For example, the local trains and public transit authority, the fire and emergency services, the volunteer bush fire brigades, water bombers and the like. I've not even looked at local digital services like DVB-T, that's the terrestrial standard, or the local radio version, DAB+, or Digital Audio Broadcasting. Then there's pagers, and countless marine services and channels, the ubiquitous CB frequencies and a couple of pirate ones, and global services like GPS, weather satellite and other Earth monitoring services. Note that I'm specifically highlighting things that I can hear at my station, or more precisely, should be able to hear. I'm in the process of figuring out which particular tools I need to actually have a stab at hearing and decoding things like weather satellite. I wouldn't be me if I didn't try this with my hands tied behind my back. I'm limiting myself to things I can hear using the antennas that I already have. I don't, well not at this stage, want to start building and installing more antennas, probably because in the not too distant future I plan to finally erect a replacement HF antenna, but that's a story for another day. As for now, I'm plotting noise levels using a tool called rtl_power. I'm working on figuring out what extra noise has joined my environment. I'm also starting to make a concerted effort to document specifically what I've actually heard. Not so much a continuous log, more of a one-way log if you like, some might call it a shortwave listener log. What RF sources have you heard in your shack and how many of them did you document? I'm Onno VK6FLAB

17th March 2024 The Spokesmen Cycling Podcast EPISODE 349: Turn on Strava for everyday journeys, it could reshape streets for the better SPONSOR: Tern Bicycles HOST: Carlton Reid GUEST: Tom Knights, Strava Metro LINKS: https://www.the-spokesmen.com/ https://www.ternbicycles.com https://twitter.com/CarltonReid https://press.strava.com/articles/stravas-metro-reaches-significant-milestone-of-10-year-anniversary https://metro.strava.com Carlton Reid 0:13 Welcome to Episode 349 of the Spokesmen cycling podcast. This show was engineered on Sunday 17th of March 2024. David Bernstein 0:28 The Spokesmen cycling roundtable podcast is brought to you by Tern bicycles. The good people at Tern are committed to building bikes that are useful enough to ride every day and dependable enough to carry the people you love. In other words, they make the kind of bikes that they want to ride. Tern has e-bikes for every type of rider. Whether you're commuting, taking your kids to school or even carrying another adult, visit www.ternbicycles.com. That's t e r n bicycles.com to learn more. Carlton Reid 1:03 I'm Carlton Reid. On today's show, I'm talking with Tom Knights. He's the senior manager of partnerships and marketing for Strava Metro. This is a super-useful active travel city-making dataset-service from the athlete tracking app. And if you bristled at the word athlete, because you think there's no sport in transport, listen on ... Strava metro was very, very insistent in 2020. About how successful cycling and and walking in all active mode because of the pandemic and the blog posting was, you know, we're very pained to say this. However, you know, it's really, really, we're going crackers with the amount of cycling as you know, the bike boom, yeah, what did go amazing. Now, the bike industry right now is famously and woefully massively down in the dumps. So what have you seen with usage? So what has happened since 2022? actual usage of bicycles not just, you know, we know the sales are bad. Is the usage bad also? Tom Knights 2:21 Yeah, that's a really good question. And actually like to say the kind of the free, the free, free call to Strava Metro kind of suddenly going free was actually very well timed, unfortunately, under very difficult circumstances globally. One of the reasons like I say, we kind of made Strava Metro free wasn't actually because of the pandemic and the looming kind of crisis. And obviously, this switch to human powered transportation. It was like, almost like an unfortunate timing, but but obviously beneficial for cities and all the planners that start to use this data. So yes, we definitely saw this huge boom during the kind of 2020 21 era. And thankfully, because a lot of cities and a lot of regions and governments had the foresight to start investing in protecting cycle lanes in safe routes, which we know is one of the biggest barriers to people actually kind of picking up a bicycle. Lot of those initiatives have stayed, and we hope that they've stayed because actually, they've been able to see some of the Strava activity straight through Strava Metro, and then use that against other data sources to start to understand actually, is this being used in terms of trends, and overall, we've definitely seen more of a normalisation but again, what we are seeing is obviously, people looking for alternatives to either commute, and then well, kind of 2024 the word commute looks a bit different than maybe it did in 2019. But anything that's a utility trip, and essentially through safe and accessible infrastructure. That's what we know. And I'm sure you know, from all the kind of conversations you've had over the years, that's the biggest driver to people, making it feel safe. So, long story short, yes, we've definitely seen a normalisation now, in terms of growth Carlton Reid 4:06 Normalisation, that sounds like quite a bit of a euphemism for, for what? Tom Knights 4:12 So I guess the new the new normal as it were, so we've definitely seen that growth. And then now what we've seen, like I say, as people who are consistently cycling now, and then obviously, we hope that through infrastructure improvements into society into communities, that will then also encourage even more folks to pick up a bicycle on that front. Carlton Reid 4:33 I'm gonna carry on digging here, because I think it's quite important. So that graph that was on the Strava Metro, I remember it well, the human powered transportation one Yep. Yeah. So I mean, that was that was great. But, you know, so when you've been normalisation, is that graph, it went up like crazy. And do you mean by normalisation that it went down so well usage is down or has plateaued, Tom Knights 5:00 so not I mean, it's difficult to say but I wouldn't say plateau because we're always seeing kind of growth. And that's what's so exciting a and I can't necessarily kind of say a lot more about the Strava core Strava world because of course, that's a different kind of department as it were. But in terms of the Metro world, and what we're seeing in terms of cycling, in general, we've just seen that spike from 2019 to 2020, that continued growth into 2021. And now what is is probably more of that kind of continuous steady growth. As opposed to that, we I wouldn't say we've definitely seen any kind of drop off as it were on that front. Carlton Reid 5:34 So it's interesting, because we now have metrics that we just didn't have, you know, 10, 15 20 years ago, from an industry perspective, used to be able to track sales of number of bikes, and but you never knew whether, actually people even though a few bikes sold, actually, people might actually be riding more, potentially. So now we have metrics from from people like you, where you can not only track the number of bikes sold, but you can also track roughly whether people are using those bikes. So that's fascinating information from a market point of view. And the way I'm going from on that is you've got some high end holiday companies, you know, Glorious Gravel going to Sri Lanka, Namibia, all these amazing places with people who got clearly a lot of money and a fair bit of time. Yeah, still getting out there cycling. So when we haven't seen that end shift at all. But no, that's the rarefied end, isn't it? That's like, Yeah, from from a metro point of view. Tom Knights 6:42 Yeah, definitely. I mean, I in terms of, you know, think travel and tourism, that is obviously a kind of luxury. And, you know, for kind of people a having the kind of means to kind of jump on a plane or to kind of visit and take the time off. And that's great, though, for kind of seeing that, that boom, because we want people to kind of get an introduction to cycling in general. And if that means discovering it on a holiday tour, fantastic. Hopefully, that then translates into cycling into work maybe two or three days a week, or suddenly dropping a car trip once a week, because they've discovered the joy of cycling. But I think January what we're hoping, though, is we see this bike boom, fueled by better and safer streets. That's, that's our kind of main concern is that, if you build it, I know, you've heard this phrase a lot before, you know, if you build it, people will come. And we know that from Strava Metro data, when you look at the kind of streets where there's been investment, the Before and After Effects is amazing. See this kind of increase in trips. Now, of course, you might say, Well hold on Strava growth. But actually, what we're seeing is that Strava Metro data alongside Eco-counter or Telraam data, you can start to kind of normalise and build a model. And I think that's what we're we're hoping that people can start to, as you mentioned, all these amazing datasets start to pull these together, and then really build this picture to kind of tell a different story than perhaps maybe the negative stories are saying in terms of, you know, cycling booms over or no one's using this bike lane, etc. Carlton Reid 8:10 And this is an obvious question, okay. And this is a question that I'm sure you are incredibly well used to batting away, and you know, you're gonna get it. And you, you could almost do it yourself. So that is in your documentation. It's all about athletes. Of course, when you put that into Strava Metro, you're talking about non lycra. I know you discuss this on your blogs, but just just tell me now, why I would be wrong to suggest that Mamils, women on bikes and lycra why the data is robust, even though you talk about athletes? Tom Knights 8:53 Yeah, no, you're quite right. And it's a, it's a really good point. And I suppose, from the data point of view, we're not looking at, we look at those as activities and people and trips so that the athletes is more of a kind of Strava kind of communications in a playful way to call our community athletes, and you've probably seen various different messages over the years about, you know, if you're an athlete, you're on Strava. And, and essentially, there is a lot of truth in that, you know, we want anyone who moves through human powered transportation, or through moves and find their joy in discovering movement ways we would define as an athlete, you know, anyone who is doing that, now appreciating the world of transportation planning and bike lanes and commuting, you might not think, you know, cycling across the Waterloo Bridge in the morning at 830. You're an athlete, but essentially, from a metro point of view, what we're looking to do is see these community based trips as data points, like say that can be used for improving infrastructure on that front. And I think the way that actually I would position it personally is often thinking, well, everyone who uploads a ride on to Strava is a human powered counter, because through through Metro That's going towards some kind of better cause in terms of funding and reviewing active travel investment. But I do understand your point about you know, Mamil. And you know, a lot of drivers growth in the early days was fueled by that amazing core set of athletes. And you know, I grew up in this town called Dorking, which you're probably familiar with, from the classic ride, sorry, and I'm very familiar, you know, the weekends kind of seeing, you know, the the kind of, I say the kind of more sportive rides coming through the town. But actually, what that served is actually an inspiration for more people's go. Actually, that was quite fun. I should try that. And I think the data we're seeing through Year in Sport that we've done anecdotally, through Metro data, that actually we've got a lot more 18 to 34 year olds, who are now also discovering the joy of active transportation. And again, Metro data is telling us that it's not just, you know, the weekend, you know, the Saturday morning at 10am, in the Surrey Hills or on the the kind of Yorkshire Dales it's actually taking place on the streets of Manchester, or the streets of London, etc. And I think that's what we're hoping is that story through community or athletes, as you know, we're calling it that that helps planners to see that trend is is not just, you know, the kind of Lycra brigade Who are you know, cycling and I would all use what the same people that are cycling at the weekends, you know, on the kind of right sorry, classics or up in the Yorkshire Dales are also the same people that are using bike lanes. And equally as important when we're thinking about counting. Carlton Reid 11:30 Of course, you're not getting the invisible in American terms, it's called the invisible cyclists. So these are often Latino. Basically poor people on bikes, who are definitely not going to be using Strava. But going to using bikes, and then they call them invisible cyclists, because they're not on bicycles that perhaps an enthusiast would ride, but they are using bicycles and all power to their elbow, but power to their knees. Now, you're not capturing them. So if you're not capturing a significant number of people who are using the roads, does that not suggest that you're missing an important chunk of people who are not using? You just can't capture everybody? And how important is that? Tom Knights 12:27 Yeah, really, really good point. And I guess a couple of bits on that is that essentially no data set, you know, the world is accurate, you think about a, you know, a bicycle counsellor on the embankment or, you know, in the middle of Manchester, or even in the rural area, you know, if someone doesn't go through that specific kind of counting station, as it were, you're not being picked up in the count. And I think that's what Strava Metro is really kind of aiming to do is essentially colouring the map with all the blank spots that aren't being picked up. And being free, which is, again, one of these kind of opportunities to kind of get this data into the masses, allows transportation planners allows Safe Streets advocates, anyone who's focused on transportation equity and environmental racism to dive into that data and go, Okay, looks like actually, there's people going through this counting station here. But actually, Strava Metro is also showing us that people are going down this route. So what's interesting what's going on there. And again, you're quite right to call out that the heat map, for example, in, you know, maybe underrepresented areas, or places that don't necessarily have the same political will have, you know, more affluent areas who have perhaps built cycle lanes or made their streets more attractive from things like heat islands, you think about kind of cities outside of the UK that suffer a lot from high temperatures, you know, the streets are not necessarily designed for being walkable and bikable. That's what we're really hoping we can also use the Strava data to show what's not happening, as well as what's happening. And again, a lot of the work that Metro is involved in is ties back into this kind of social impact piece. It's not just, you know, we obviously want this data to be used by, you know, transportation planners, but we're also hoping we can start to, you know, work a lot more with, you know, say advocacy groups, anyone likes easy, bold environmental racism and transportation equity, to really kind of look at that data, and metrics looks, it's been designed that anyone including myself, I'm not a geospatial professional, but I can see, you know, through a map and looking at certain areas where people are cycling and when they're not cycling, but also we want to build a product and I can't really, you know, say I'm not necessarily holding the Strava product side, but we want to build an experience, which is all encompassing for everyone on there, but I definitely understand your point about the barriers to entry, you know, just in general, you cycling you need to have a bike to join Strava you need a mobile phone that supports you know, obviously your Strava although we do have connections with lots of fitness devices, but again, that comes at a cost, but hopefully, the more people that learn about Metro and the authenticity and the kind of the fact that it's free. The fact that Strava is free to join, it gives people a sense of empowerment that actually, I can change something that's happening on my street. And that's a big part of the messaging that, you know, I'm working on, and certainly have been working on for the last five years, because as you say, maybe the association with Strava is it's just for athletes, or people who are doing k runs, and Q RMS, etc. But actually, what we're seeing is that more and more people are turning to Strava, to kind of log their activities, and hopefully through when they learn about Metro, they'll realise that they're actually changing their communities, because that data is really kind of playing a part in helping to shape your better infrastructure or, essentially, build a political case for more investment. Carlton Reid 15:45 Good point. So somebody like me, who's been a Strava member since 2013 I discovered by looking into my profile this morning, Tom Knights 15:53 and then thank you for your long term membership. Carlton Reid 15:57 I would say, I'm not a frequent updater. But I should be, shouldn't I? So what you're saying is people like me who have it on our phones, don't use it, you know, because I don't consider myself an athlete. Yeah, that should be turning on, for even everyday journeys, because it helps. Tom Knights 16:18 So I've been, you know, I'd have that in writing. And, as it quite, you know, when we kind of go out to advocacy kind of events and talk to kind of people because I think, as you've just said, you know, the more people that discover about this, you know, cycle of like Strava, being free and then wanting to make streets better. And then Metro, obviously, enabling that, we think there's a really compelling story. And I genuinely there's, this is such a passionate thing to kind of work on. And I think we're very lucky, you know, part of the metro team to be able to have these conversations with partners all over the world. And I think we are we've met at Velo-city a couple of times before. And the one thing that comes up all the time at these conferences is, you know, how are we measuring it? Or how do we win the case for safer streets? And, you know, this is our answer to that and to say, well, let's come together and bring all these amazing datasets that are available out there. You know, let's build a case and get people to see that this is available. Carlton Reid 17:12 And those datasets, the expectation is, from your point of view, that a transportation planning department will be using multiple sources, they won't be just using Metro. They'll be using their own counting devices, hopefully, if they've got them. And they'll be plotting everything. And they'll have some sort of, will they have a desktop with everything on? Or have they got like a look at lots of different screens? Tom Knights 17:40 Yeah, so what we hear from from foreigners, they use a lot of geospatial kind of software, you know, there's obviously various different enterprise kind of grade level software and data analytics tools where you can always ingest multiple sorts of data. So we make extracting the data from from Metro, which is, I'm sure, hopefully, everyone realises completely anonymized, obviously, and then also aggregated, we make that very easy for partners to essentially download, and then upload back into, like, say, all of this data planning tools. And obviously, you know, there's multiple data sets out there. And largely, like I say, we use the same mapping tools as well. So OpenStreetMap is really important, you know, in terms of, actually, how do you paint a picture of your infrastructure in your area. And like, say, planners will then use that to build reports to kind of maybe produce research, and then essentially come up with this kind of our number, which says, you know, for every X number of trips on Strava, you can say that there's 100 trips of normal, non non Strava usage, for example, send your Strava. But, and we've seen a couple of examples that, you know, the Office of National Statistics have done that, in rural remote areas, Transport for London, have been using it to kind of model traffic lights through London and the timing that you get on green times, you know, and it's not just Strava D. So you don't want to build cities just around one particular user. But that's why being like I say, a free tool to do that allows us to kind of plug into all these other datasets. Unknown Speaker 19:12 Let's let's go backwards a little bit into Carlton Reid 19:16 that, that I'll use your term, the athlete, so you basically got a rider? Yeah, going along. I'll use like, even though I'm like to 50 miles away. I'll use London as an example. So going along the Embankment. Yeah, yeah, yes, you've anonymized all the data. So this is not you know, you know, you don't know this particular person on a bike at all. You can't track anything. But you can see at a granular level, whether they are on the road or whether they are on the Embankment cycleway, and you can see where they make that you know, sudden turn like there's a there's a few turns on the embankment where you've got to make quite a shift to get on to the cycleway. So you in Strava Metro, you can see that too. happening? Tom Knights 20:01 Exactly that so we can see, like I say the, I think there's something like 420 million edges in the whole world. So edge is referred to as streets on OpenStreetMap. And if you've got some enthusiastic mapping listeners on this podcast, hopefully they might be able to write in and correct me in some tell me how many exactly edges there are. But if you think about the world as all of these kind of different edges and routes that are built up, where there's been a Strava activity gone over the top of that, and, of course, where there's been a minimum of free, which allows us to kind of aggregate those activities, we can exactly that show you where people have turned left, how many trips went off, on a certain direction? Was this route busier because of a road closure one week? Or was this route more improved year on year because of a safer kind of passageway? You know, I appreciate we're talkinh about cycling here. But if you think about running and walking, you know, was this improved? Because there was better lighting? Or were more people using this pathway, because, you know, there was a kind of nice new path put down. So I think this is like it's this kind of colouring in the map with all the other kind of datasets that are available. And then Strava can kind of tell you that picture of where, you know, there has been activity. Carlton Reid 21:12 So when Nick Ferrari goes on the radio and says, I got stuck behind a cyclist on the Embankment, they should be on the cycleway. You could or anybody could go to Strava Metro, and say, well, actually, that must have been just a completely unusual person. Because look, 99.9% of of cyclists are going on to the cycleway. And here look, we can show you the heat map where that is happening. That's what you can do? Tom Knights 21:42 Exactly that. And like I say you want one colour, I would say is it's not anyone. So that was one of the caveats to the authenticity of the kind of Metro project. And I know that word authenticity thrown a lot you know about but that the only reason Metro works is because the Strava community buy into this idea that the data has been used for something good, not for commercial purposes. So not anyone can access Metro, but TfL can access it, for example, in your example of the bike lanes in London, London cycling campaign could access this because of course, you know, they're involved in advocacy work. Unfortunately, LBC wouldn't be able to access this, because obviously they're using it for other purposes. But actually anyone involved in safe infrastructure, and we hope that this is it, you know, when the the transportation teams, all these different medical authorities or local authorities can actually go, actually what we have seen on the street is that X percentage of people are using this bike lane on there. And that's, that's what I think it's going to take to kind of not win the argument, but really convinced people that bike lanes are being used, and they're a good investment. They're just incredibly efficient, because you never see anyone in traffic. And then yes, people are constantly moving. Carlton Reid 22:53 Yes. Now, I know you're not on this side of it. So it's a slightly unfair question to ask, but I'd like one I'd like you to tell me about anyway. So at the end, not not now. But at the end, I'd like you to go through and just tell people how much it costs to, you know, go the full fat version of Strava. But before you do that, and that's going to be the end anyway, just let's just, you know, just confirm this right now, you do not need to use Strava Metro for is free for transportation planners, anybody else. But you don't need any, you're not going to get hassled to become a pro member. To be one of these people like me who just want to do good for the community by turning metro or Strava on for our normal daily rides, you won't be charged for that you can get a free membership that will do everything apart from all the pro level stuff that you don't need anyway, if you're just one of these lapsed people? Tom Knights 23:56 Yeah, it's possible. And so, you know, Strava is like has always operated on that kind of freemium model, as it were, that you know, at its simplest, you can download the app, join the community upload rise. And then if you've made that road public, so I should have added that caveat as well, that will contribute to metric because of course, you know, people might want to hide the start or the end of their journeys, they won't count. Some people might want to also hide a certain route. But hopefully, like say when they hear about the project and go actually, this is a pretty good idea, I should start uploading my routes and maybe, you know, further down the line as they kind of start to explore Strava they want to kind of look at a route or they want to kind of go oh, that could be quite a good tool to have because I've got more into my cycling journey, then yes, of course. Strava is open for them. But at its source and Metro, they are both free. Carlton Reid 24:46 Mm hmm. Okay. At this point, I would like to cut away to my colleague, David who will give a short break. David Bernstein 24:56 This podcast is brought to you by Tern bicycles. The good people at Tern are committed to building bikes that are useful enough to ride every day and dependable enough to carry the people you love. In other words, they make the kind of bikes that they want to ride. Tern has e-bikes for every type of rider. Whether you're commuting, taking your kids to school or even carrying another adult, visit www.ternbicycles.com. That's t e r n bicycles.com to learn more. This podcast is brought to you by Tern bicycles. The good people at Tern understand that while a large cargo bike can carry oodles of stuff, many of us prefer something a little more manageable. That's why they've come up with the HSD e-cargobike for folks with big aspirations to go car free, delivered in a compact size, with its rear shock, 280 kilos, and a combined hauling capacity of 180 kilos. The robust new HSD is stable and easy to manoeuvre, even when under load. And with its Bosch eBIKE SYSTEM tested and certified to meet the highest UL standards for electric and fire safety you'll be able to share many worryfree adventures with a loved one whether it's your kiddo or Nan. Visit www.ternbicycles. That's te r n turn bicycles.com to learn more Carlton Reid 25:57 Thanks, David. And we're back with Tom Knights of Strava Metro, and I was looking at your LinkedIn profile. And as you do when you when you want to talk to somebody and you want to find out their background, and you've kind of similar background to me, in that you did classics you did you did like nothing to do with what you're doing in your day job. You did like it will tell me what you did it was Exeter University exactly what you did. So I kind of found found myself essentially looking at degree subjects where, you know, I was interested in more the kind of anthropological aspects of history and actually Classical Studies, and I'm always very much told by classic students that classics versus Classical Studies is a very different subjects. Obviously, one focuses heavily on Latin language in Greek texts, whereas Classical Studies is more about, you know, the discovery of what was going on during the Roman Empire in the Greek Empire period. So that was always a passion of mine about kind of understanding society, and maybe what was the kind of political kind of themes at the time and, you know, fascinated about some communities on there. And, of course, the story for the dad joke, but like, most people, when you study history, there's no future in it. I'll use that. Tom Knights 27:24 But yeah, obviously, you know, that allowed me, you know, I suppose to back in the kind of early 2000s, when I was at university, you know, it was a very privileged time, when they weren't necessarily crippling university fees and structure. So it allowed me to kind of study a subject, which was more of a passion project. But of course, you know, didn't necessarily elude me into kind of a specific career working in British museum or on an archaeological site in antiquity. And actually, in hindsight, I think geography would have been more of my passion, because that's ultimately what's kind of landed me in this area of transportation and maps and bicycles. Geography was always my kind of first passion. Carlton Reid 28:04 But you're a man after my own heart, because I did a degree, that was nothing connected to what I eventually did. And that was religious studies and comparative religion. And I did Hebrew, as well. So I did do a not a classic language, but I did a language that was known to antiquity. I'd say, yeah, we've come similar backgrounds. But then you've if you look at your career progression, it went very quickly from something that's completely useless to and affect your career. If I look at your career arc has been certainly tech. So from the very first it was you went from classics, blummin' heck,, to tech, that's that's a leap. And then you've carried on that, that that trajectory. Tom Knights 28:45 Yeah, definitely, I think that kind of, you know, almost juxtaposes the kind of interest in history, but I think a lot of my friends maybe went into, you know, in the early 2000s, like most people kind of found their way going into financial services, I'd always kind of been more interested in the world of tech and technology. And then working my way up through various kind of research firms and kind of people teams in that world of headhunting and kind of early days of, of search, when it comes to kind of jobs and careers. Allow me I suppose just to suppose learn a lot more about the world of tech, and then actually through interviewing people and and candidates and helping people on their search journey. That then opened my eyes into this whole world of kind of software, which again, early 2000s was really interesting, and then tied into that passion for sports and maps and mapping, landed, actually initially at a company when I lived in Hong Kong for five or six years, which was doing event registration for marathons and five K's and stuff like that, which is obviously very relevant to the Strava world nowadays. But it was when Strava Metro came along and said that they were looking for someone to essentially grow the community on Strava Metro in Europe. It was too good an opportunity not to kind of put my CV forward so You know, tied into all my passions around mapping and transportation. Carlton Reid 30:04 And, and getting out there and doing stuff. As in Yes. Being an athlete if you want to use that term. Tom Knights 30:11 Exactly. And you know, that's a it's an interesting point to kind of call up. But essentially the the advice, actually the CEO at the time, who was a gentleman called James, and actually Michael Hogarth, the founder of Strava, they said, The most important thing you can do in this role at Strava Metro is get out there and see bike lanes and infrastructure, or really understand what the kind of partners are doing. So over the last five years, that's kind of allowed me to get involved and actually see some of these projects. And you know, one of the best moments of the year or certainly at conferences, or events we go to whenever there's a bike parade, and I've never had a bike tour or a technical tour around the cities that you can visit, and you can really start to see the, you know, how those numbers come to life, actually, in the physical world, because, again, we've focused a lot on on this talk, we talked a lot about the Embankment. But actually, there's a whole multitude of examples around the European continent, and also across the world of bike lanes, which we visited and gone. Gosh, that's really interesting, what innovative design and oh, look at how that impacted this number of people. Carlton Reid 31:13 Tell me about your day them. So you've got somebody flagged out that yes, sometimes travelling around a bit. So what what do you do, Tom, scribe, what you actually do to people who don't know what you might be doing day to day? Tom Knights 31:28 I love it. So my biggest kind of responsibility is to grow the awareness of Strava Metro. And obviously, the more people that hear about Metro, hopefully, from listening to this, the more people might go, okay, that's really interesting. I didn't know that. So essentially, that's our, our main focus is to speak to the folks that active travel England through to the city of Paris, and obviously, the, the onset of zoom and online meetings has made that a lot more accessible now, which is great. So as much as I'd love to go visit all these places, a lot of them are done by kind of video conferencing, which is allowed us to scale and obviously tell the story in a kind of much more scalable way. But where possible, I'll always try and visit partners and learn about what they're doing on the ground. And then actually, one of the biggest kind of tasks this time around is to then how do we communicate these back to the Strava community, and then get all these 120 million athletes who are on Strava, to actually learn about these projects that their movement has contributed to, because that's going to be the power of when they understand that your cycles work, even though it's providing you with your exercise or your means of transportation. It's also having a big impact on how, for example, you transport Greater Manchester or Transport for London to building your roads and your cycling. So if it helps with that extra bit of motivation, to get out of bed on a kind of cold January morning to kind of, you know, get cycling or walking to work, then, you know, we've done our job. Carlton Reid 32:57 Isn't there an argument and I am playing devil's advocate here a little bit, council employee, a transportation but oh, maybe a councillor could actually use your data, which shows us lots and lots of people using a certain road? At a certain time? Yeah. And you would say, to a council? Officer? Well, look, we need to improve this route. Because look, how many cyclists are using it, we need to improve that. So it's more comfortable besides blah, blah, blah. But, you know, a councillor could use that exact same argument and say, Well, why do we need to improve anything? You're just telling me there's loads of cyclists using this road? Great, job done? Tom Knights 33:44 Well, I think the answer that is the kind of the theory that maybe, you know, a lot of highways and motorways around the world have used, which is what more lanes will fix it. And what did what happens when you get one more loan, we'll fix it, you get more cars driving? Well, I think the principle for that applies in terms of, if you keep fixing and increasing the number of cycle paths and bike lanes, then you'll see an increase in even more cyclists on there. So that would be my kind of caveat to say is, you know, the same way that we saw, you know, mass growth of roads and kind of infrastructure around the country, the same way that you could, if you keep investing, you'll, you'll see those increases come even more, as well. So it's just the start. I think this is the kind of the key point. And, you know, this has only really been what I've been in the industry for what five or six years intended, specifically around the world of transportation planning. And I've, I've read your in as another student of history, read your history of bike lanes, and what we're seeing is nothing new. You know, this obviously happened in the 1920s, as you've written about, it's happened, you know, the early 1950s. And we hope that obviously, this bike boom is going to continue, but we know that the secret to that is obviously infrastructure, but the extra secret sauce and I'm gonna say this with my Strava hat on so apologies is that you know, other people keep other people motivated. And that's where Strava comes into it as a motivation machine. Carlton Reid 35:06 So that game, gamification of it almost. Exactly, which is a good segue, thank you very much into my next question, which will be at the White House. So that's a that's a gamification, so, so just tell me exactly I know it's not UK, but this is a, this is a podcast that goes ... it's very popular in America. So Strava, not Strava Metro, but Strava is working with the White House on something. So just tell us what what you're doing. And then the gameifacation angle of that? Tom Knights 35:34 Yeah. So from obviously, my understanding internally of the team that's been working on that is very similar to other kind of projects or campaigns, or let's say gamification, or challenges that we would work on this time, though, there's obviously a social impact cause attached to it, I think what's happened and from what I understand is that the White House, obviously have a campaign or a kind of cause that they're looking to mobilise the community on, they had a commercial partner in work, which is, you know, obviously, kind of, I suppose, helping to kind of measure that through the through the wearable side. But the White House is partnering with Strava, to support physical activity, as part of its challenges to end hunger and build healthier communities. Now, as part of the social impact strategy, let's say the call to action is to raise awareness of that campaign through movement. And obviously, that movement there is on Strava. And it's very similar to lots of other campaigns that we might work with, from brands, but also also other charities, you know, that might want to also mobilise their community on Strava, through that kind of challenge format. Carlton Reid 36:38 So that's a US initiative. Obviously, it's the White House as in the White House. What other stuff might you be doing UK or maybe even worldwide, similar to that? Tom Knights 36:50 Well, I think ultimately, it's if if we've done our job, right, and you know, the more people that learn about these challenges for good for social impact, we hope that people will start to see Strava as a platform, where they can actually start to tell their message to what's a very engaged community. You know, like I say, not every cyclist is on Strava. But we do have, you know, in the UK, again, I'm going to correct myself on every one in seven adults has joined Strava, or something around 15% of the population. So that's not everyone, but it is a very engaged audience. It's bonkers, actually. So how many What's that in millions? Is that like 10 million downloads or something, I will come back with some specific figures. And James can help with that. On on, on our team, but Yeah, certainly, we obviously are in the millions of users in the UK. And of course, that's a really engaged community who are using Strava a for their movement, but also then can attach that through a challenge for a social impact campaign, or brand campaign. And again, these challenges are completely optional for people to dive into should they wish to. And I think that's one of the kind of key things to get at the Strava community, you know, having that say and what they do, and that's what's probably kept people coming back stronger over time, is that they get they have a choice in what they can join. And the challenges that the the team in Bristol, who in the UK run those operations for similar to the White House challenge, they do a fantastic job of making sure that there's some really exciting challenges to come onto the platform and keep people motivated. Carlton Reid 38:26 So can you now tell me the different pricing options, so people are like, they've got the free version? They maybe like me that don't. They will now start using the free version a bit more for the reasons we've discussed before. But if you wanted to up the game, what would you be paying? And what would you be getting? Tom Knights 38:46 So for UK based users, obviously Strava premium is an option and that it costs £8.99 per month, or £54.99 per year. Obviously, there's a freemium model, in terms of the kind of ability to join Strava and not have to, like, say, necessarily choose to subscribe. But again, the compelling products, and the opportunity that the product team in the US and all the amazing kind of engineers that work on Strava have built an experience that should you wish to subscribe. There's a really compelling reason to mostly through our amazing routing, mapping discovery tools, looking at new routes to explore. Obviously, like saying you've got access to technical data, should you wish to kind of see things like your heart rate and health and kind of segments and leaderboards, etc. So there's something on Strava for a lot of folks, and of course, you know, that community element and clubs and groups is really exciting. And another way for local authorities and governments to really drive engagement back to Metro, for example. Carlton Reid 39:54 And then you got things like integration with fat map so you can like do all sorts of stuff with that as well because it's Strava. Did you buy fat map? Is that was that? Tom Knights 40:02 Yeah, so there was a strategic acquisition of fat map and you know, the the, that's the exact date has been going on for the last year. So again, all these amazing tools and some mapping tools are such a good driver for people to discover the world around them. And I think that's what's really exciting is that, you know, yes, you might go on a bike ride and you know, kind of cycle from A to B on one of the cycle highways. But at the weekend, that same bike hopefully, is being used to then go, that that route is quite interesting, or I saw my friend do that route. You know, the other day that looks like I could probably do that I've got a spare couple of hours. And it's basically just keeping people active. Again, you've probably heard this one for every minute spent on Strava, you can attribute 30 minutes of activity back to your kind of daily life. So rather than that, and that's because you could you look at heat map, you see, you're in an unusual destination, you don't you're you're at your bike, and you fire up the heat map. It's like, everybody's gone that way. That way, then is that what you mean? Yeah, essentially, you know, like I say, you might, or it might just be on your activity feed that, you know, kind of been suggested a route or suggested a, an area to kind of move through. And I think that's what's really exciting is when you get somewhere new, you know that there's a community, because obviously, we're a global community that has cycled there before. And I say you can either look at the heat map, or you might be able to see someone's route. And they've recommended it as a kind of place to ride. That inspiration you get from not just like, say, scrolling through maybe another social network or Doom scrolling, should I say, hopefully, that movement and inspiration of people being active for something that's going to be a positive driver for people being, you know, engaged on Strava. Carlton Reid 41:44 There is another active travel analogy, which sometimes gets wheeled out. And that is, you can't tell why you need a bridge from the number of people swimming across the river. Because they aren't going to swim across the river with a bike, they probably aren't going to swim across the river full stop. But when you put a bridge in it suddenly get, you know, the heat map would go crazy. But once you put the bridge in, so is any of your cleverness your your text, can any of it can I spot? Well, if you only had something here, it would open up, you know, is this something that you can pinpoint that you can say that a bridge analogy can be used? Tom Knights 42:25 Absolutely. And thank you so much for asking that, because that's something we just updated last year in our metro product that obviously the planners and the transportation teams can see. And a lot of it ties back into some of the the kind of accessibility transportation equity, environmental racism that we talked about. What we've shown is that, when you put a pin on the map, we've also been able to kind of draw almost like a kind of circle around what's accessible within say, 10 minutes, 15 minutes, 30 minutes, etc. And people can see data within that kind of circle, which, again, will show you that where there's a massive motorway with no bridge crossing, that's that part of the community can't access the park on the other side of it, or where there's, for example, a big brownfield site where there's been industrial use, it's not safe to cycle through. So people have kind of diverted around it, we had a really good example, actually, recently in Germany, where, you know, there was a curb on the side of a bike lane. And you could see very clearly actually three desire lines on the on the actual grass and the verge that people were kind of going off this curb through the woods to kind of cut out maybe a mile. And again, using Strava, Metro, this German transportation team who are based in Frankfurt, actually, I'll share the example with you because it's fascinating see how even at a really small local level, these little changes can make a massive difference. And they're not expensive to do, I think it only cost them something a couple of 1000 euros to drop the curb, because they then saw that that was having an impact on where people were then cycling. So you know, the famous analogy of when it snows, you can really see the designs of cars. Actually, when you look at the design on the heat map, and then in turn, look at that on Strava, you can start to see Oh, that's interesting. And again, another great example that was Hartfordshire county council had a bicycle counsellor in one location. And they realised that the Strava count was actually higher than the bicycle counter. And they thought well hold on what's happening there. And actually, there was a kind of dangerous crossing just slightly further up from this bicycle counter. And they were able to then use the Strava data to kind of, I suppose understand that actually, people were going this way because it was a safer journey. And that's the these are the kind of insights that yes, we want to do the big high level projects and you know, make sure that we get new infrastructure and cycleways across major cities. But actually the really exciting ones when local advocacy groups or local councils who don't necessarily have big budgets for you to accessing data can make these small changes and really improve these kind of everyday life for their community. Carlton Reid 44:56 Can the Netherlands which obviously every week, look Up to is like, the absolute nirvana of cycling. Do you like do you have like, Dutch people go, Oh, we could use this. It's like, Jesus, they even removing even more, you haven't done so. So basically, can you improve the Dutch cycle network? Tom Knights 45:15 Yeah, definitely. And actually, we've had some interesting conversations with the folks over in Copenhagen, and obviously, in Amsterdam, and across the Netherlands as well. So not just Denmark and Holland. But, of course, the Netherlands is such a stays a bellwether of the cycling industry, but they're always looking at new ways to improve, you know, the technology that they're using and counting data. We are in Leuven, just at the end of November for the policy network events. And again, we are understanding that the kind of technical university they are leaving, we've been using metro to kind of understand, you know, and this is a really forward thinking Belgium city, which has got great cycle access, but they still need data to understand and counter. So rather than, you know, developing another app to count people, and getting the community to download it, they've seen that correlation between actually Strava and Strava, Metro. So again, they don't need to necessarily go and kind of reinvent the wheel, so to speak with, you know, building another kind of engagement tool with local community to get them to join, because Metro is hopefully fulfilling that service. Carlton Reid 46:20 Brilliant, Tom that's been absolutely fascinating. And we could go on for a good amount of time, probably on Classics literature, even while we discussed, what's your Roman Empire? Yes, exactly. But we can't, because we people just won't listen to 10 hours of us chatting away. Tom Knights 46:42 I'm sure they will. Carlton Reid 46:43 Now, could you tell us where people can find out? I'm sure people know where you can get onto Strava. But how they find out about Strava Metro, and and maybe how they can contact you? Tom Knights 46:56 Yeah, definitely. So the best way to get in touch with myself and travel metric is on metro.strava.com. And then on that website, you'll be able to learn more about case studies about how cities how researchers, communities have used the actual kind of practical steps of the data. There's also some frequently asked questions on there about you know, privacy and how the data is used, etc. And then most importantly, there's an apply button. So you can click apply for access. And then what we ask is that a you're a organisation that is involved in working to improve active transportation. If you're a consultancy, or an engineering firm, we also accept those applications as well. As long as you're under contract with say, for example, the local government or the city authority, we know that Metro kind of appearing as a line item as it were. And then, again, like saying, at its source, transportation planners around the world can can access, we ask that you use a work email, not a Gmail email. So normally an org or dot.gov, etc. And then just a short abstract, essentially, of how you're going to use the data. And so then we know that it's being used for a positive kind of cause, and then you will give you access to the area of interest that you've selected. Be it London, Birmingham, Somerset, wherever it is, as long as there's been Strava activity, you can start to really start to see trends and patterns, then hopefully feed that into other datasets to build the infrastructure. Carlton Reid 48:20 And Nick.Ferrari@LBC.co.uk or whatever his email address will just be rejected out of hand, that's nefarious use? Tom Knights 48:28 Yeah, I reserve the right not to comment on on LBC and Nick. Carlton Reid 48:34 Thanks for listening to Episode 349 of the Spokesen podcast brought to you in association with Tern bicycles. Show notes and more can be found at the-spokesmen.com The next episode – 350 – will be out next month. Meanwhile, get out there and ride ...

10th March 2024 The Spokesmen Cycling Podcast EPISODE 348: Jonathan Kambskarð-Bennett of Komoot SPONSOR: Tern Bicycles HOST: Carlton Reid GUEST: Jonathan Kambskarð-Bennett LINKS:  https://www.the-spokesmen.com/ https://www.ternbicycles.com https://twitter.com/CarltonReid https://www.komoot.com/user/655260825794 https://jkbsbikeride.com TRANSCRIPT Carlton Reid  0:13   Welcome to Episode 348 of the Spokesmen cycling podcast. This show was engineered on Sunday 10th of MARCH 2024. David Bernstein  0:28   The Spokesmen cycling roundtable podcast is brought to you by Tern bicycles. The good people at Tern are committed to building bikes that are useful enough to ride every day and dependable enough to carry the people you love. In other words, they make the kind of bikes that they want to ride. Tern has e-bikes for every type of rider. Whether you're commuting, taking your kids to school or even carrying another adult, visit www.ternbicycles.com. That's t e r n bicycles.com to learn more. Carlton Reid  1:03   I'm Carlton Reid. And this is the fourth in a five part series digging into bike navigation apps. There have been shows with folks from Ride With GPS, Bikemap, Cycle.travel, and today it's the turn of Komoot. although as you'll soon hear, in this nearly 90 minute chat with Jonathan Kambskarð-Bennett, we also talk a great deal about travelling the world by bike. And that's before, of course, there were smartphone apps to guide you. Jonathan, welcome to the show. And presumably you're you're in London, Jonathan Kambskarð-Bennett  1:51   thank you very much for having me. It's a real pleasure. And yeah, I'm in London, South London to be precise on a very beautiful sunny February morning.  Carlton Reid  2:01   It's kind of nice in Newcastle as well. So we're blessed. Now the reason I said that was because a your name. So we can get looking we can discuss that in a second and you can show me how you're you can tell me how to pronounce your, the Danish part of your name correctly. But also because cuz because we're talking here about Komoot and Komoot is a German company. But first of all, how do i pronounce your name correctly?  Jonathan Kambskarð-Bennett  2:29   My name is pronounced Jonathan Kambskarð-Bennett. And it's actually not a Danish surname. It's a Faroese surname from the Faroe Islands. So I am I a half British, my father's English my mother is Danish, but my mother is half Faroese, her grandma, my grandmother's from the Faroe Islands, and the Faroe Islands for anyone listening who isn't sure exactly where they are, is a bunch of islands about halfway between Scotland and Iceland. And on the southern most of those islands, called Suðuroyu. There's a kind of like a mountain ridge, behind the village where like my gran and her family are from called CamScanner. And that's where that name is from. So yeah, it's it's ferries surname via Denmark. Wow. Okay, good explanation. Carlton Reid  3:26   And because I didn't know any of that, I then didn't go back and check on your, your global world. Crossing cyclist. So I noticed that you went from Iceland? Did you go via the Faroe Islands at all? Yeah. Jonathan Kambskarð-Bennett  3:45   So many, many years ago. Now, I spent three years cycling around the world, which was a whole kind of story in episode in itself. And at the very end of that, I wanted to go and seek because my great grandmother was still alive at the time, and she was alive and kicking the pharaohs. So towards the end of this, this, this free journey, I really wanted to go to Iceland cycle there wasn't particularly advisable in the depths of winter, but had a wonderful time nonetheless. And from there, you can take a ferry to the pharaohs. So I did go. I did after sort of not really seeing any family for about three years. I did go and see my great grandmother, which was amazing. It's an incredibly beautiful place. By that point, I had seen an awful lot of devote the world and the pharaohs. You know, just like truly spectacular. And it was really wonderful that I got to go and see my great grandma because she passed away a few months later. So it was all kind of perfect. A really nice kind of like final stop before I returned to the UK. So Carlton Reid  4:52   I will admit I haven't read every single one of your blog posts from back then but I'll go backwards and I'll go back and read that one because I'm sure that Under brilliant because I hadn't spotted the Faroese part. Jonathan Kambskarð-Bennett  5:04   Yeah, it was a really lovely thing that I got to and then at the very beginning of my, the very beginning of this huge cycle, I left home said goodbye to my dad, my mum lives in Copenhagen. So I started that cycle around the world. I mean, at the time I had, I had no idea. It would be that big a cycle. I was just trying to see how far east I could get. But I wanted to go and visit my mum in Copenhagen. So that was kind of the beginning of the journey. So it was quite nice that I had like pitstop early on, you know, visiting family and it was quite nice that again, towards the very end, I also had a pit stop visiting fan for going home. Carlton Reid  5:42   That's your mum also came out and visited you like you as your beach bumming whether that was in somewhere in Indonesia or was in Thailand. Yeah, that's Jonathan Kambskarð-Bennett  5:50   right. She came and visited me in. I guess I was in in Thailand, often having seen her for probably a year and a half at that point. So we had a little, very nice, relaxing beach holiday, catching up, and most importantly, not doing any cycling at the time. Carlton Reid  6:07   And I'm sure she's treating you as well. It was, yeah, yeah. Know that for a fact, because we treated our son when he was doing stuff like that. Right. So let's get back to what we're meant to be talking about here, Jonathan, that is Komoot. So before we do that, I mean, give us the history of Komoot, because, you know, would you have used it on your? So yeah, this is 2015 to 2017. Yeah, yep. Jonathan Kambskarð-Bennett  6:37   So I think I was unfortunately, I was a little bit too early. Cuz it's been around the apps been around for about a decade now. Set up by six, six friends from Germany and Austria. They have, I guess they will kind of united by a love of both tech. And also nature, they will come from the fringes of like, beautiful parts of Europe. But a very clever bunch. Yeah, excited about like the future of tech and where it intersects with, like, you know, all aspects of reality in our day to day lives. So Komoot is a German company. But going back to your your opening comment is a German company, but we consider ourselves very much a global or at least a European company, people, the people who work for Komoot are spread out across all of Europe. So we have quite an international outlook on the world, I would say. Carlton Reid  7:39   Was that right from beginning? Or was it very localised to begin with, and then only gradually did become international? Jonathan Kambskarð-Bennett  7:45   Definitely, it was a gradual thing. I think Komoot I can't quite was before my time, the point because Komoot's fully remote. So one point switched and thought, Well, why not sort of recruit from across the entire continent instead of one country. And for a good number of years Komoot has been conscience consciously, international. So like had the app, the product translated to English a long time ago, we now have it available in half a dozen languages. So like, that obviously takes time and resources, but it's quite important for us to allow as many people as possible around the world to like, understand and interact with and interact with the app. So in terms of my own journey in cycling, I was kind of a bit too early on in the process is quite, it's quite funny actually, when I, when I first left, I really was not a cyclist. In 2015, when I left home, it all came together very quickly. And this was sort of the blogging, end of those blogging, glory years, I think around 2010 to the mid teens. So anyway, I found some resources online, and people were saying, Oh, you can buy a cycling computer and use that. I didn't really have much cash at the time. So I picked the cheapest cycling computer that looked like it might do the job. And it was this. This Garmin device, I can't quite recall what it was called. But you couldn't load base maps onto it, you could create a route somewhere and export a GPX file and then you could have this line to follow it. And I I was just following the North Sea coast coastline, on the way up to Scandinavia. And I spent a lot of time getting very lost. And after about three weeks on the road, I met someone who was was like, you know, you can just use your phone for this. And I didn't have mobile data across Europe. It was like before, it was quite so easy to connect to everywhere. But it hadn't even occurred to me that I could use my phone as a GPS device that it had this functionality, which feels a bit silly in hindsight, but why would I have I lived a sort of normal city life where I was always online at the time. And I hadn't realised that I could download load these map files from Open Street Map. And so I could kind of work out where I was at all times. So when I had that revelation, it was kind of blew my mind and things became a lot easier. And as we might discuss later, fast forward almost 10 years, it's now even easier than ever to have this these good quality maps offline and also to sync them with devices. But it's funny to look at where computers now, compared to my very rudimentary experiences, yeah, almost a decade ago. Carlton Reid  10:30   So the first time I came across, Komoot in certainly, you know, seared into my consciousness when my son was cycling back from China. Yeah. And I had all sorts of other ways of doing routes. But he was insistent that he was using Komoot. So all the way back from from China in some pretty hairy paid places, but parts of the world some of which I can see that you've cycled through as well. He was using Komoot and I need to ask him why he was he was using it but he did found it find it very valuable and certainly very valuable in those hairy parts of the world because it was drawing down some pretty ok maps. And it was giving him obviously really good information. So here's the pitch. Jonathan, why why use komoot? Why Why would world tourists use Komoot and why would that non well tourists want to use Komoot just you know, bumbling around the the Yorkshire lanes or the Norfolk coast towards why those two users might might wait. They want to use Komoot. Jonathan Kambskarð-Bennett  11:41   It's really that's really cool to hear that just used Komoot for that. I've watched his like video of that long journey. It's so amazing. And they're very nice to Komoot was able to help that little bit. And I know that you've travelled a lot by bike as well, I think is funny. You know, especially with bikes, and especially with bike touring, it's been around, you know, it's been a thing for a very long time. It wasn't really that long ago that people were relying on paper maps. But that's in the same way that people used to, you know, drive around with British people with A to Z you know, in the car. And that already feels like such a such an outdated thing. I think a lot of very young people will this is probably a fact that a lot of young people don't know how to read maps in the same way that older generations do. So I would say for bike touring, it's, it's kind of like I sometimes why would you not embrace the technology that we have now, when I was cycling around the world, I did not really do any complex route planning on my phone. But now, we have commute and some similar apps and products. It's incredibly easy. The commute app is really intuitive, the algorithms are very sophisticated, it's very easy to find multiple options, but to find very suitable options, from A to B, even in parts of the world, where some of the map data is, is less comprehensive. And you can do all of this from your phone really easily. You don't have to drag paper maps around, you can very easily forecast how long it will take to get from A to B, you can very easily find out where might be a nice detour to take. There's just a lot less guesswork involved. So for the bike tour, it's a really powerful tool. But I would also say for the recreational user popping around the local lanes in the British countryside, for example, or a beginner, we have, we have a lot of tools that make it really easy to find a suitable route based on your ability. So while we have the route planner, which is great for finding ATV rides, whether that's like 100 miles, or whether that's 2000 miles across a continent, for the casual users who are doing like, you know, regular recreational loops. On our discover interface, we have, within just a few clicks, you can find routes that are based on your preferred sport type, whether you're gravel riding or road cycling, if you like hilly, hilly routes or flatter routes, or whether you're a hiker as well, because we accommodate for, you know, hiking as well. So you have these options that are tailor made for your needs within just a couple of clicks. And you can go and someone who's cycling across a continent probably understands how maps work probably enjoys looking at them, probably enjoys the process of, of stitching a route together. But for a lot of other users. That's not a priority for them. They just want to spend the time outside, having a good time without anything to worry about. Carlton Reid  14:55   There are a number of navigation apps some some of which seem to you know, be very popular in North America. Akka and some that are more popular in, in Europe. So that ecosystem seems to be very, very healthy. There are a number of apps going for the same kind of thing you know, from, you know, including one man bands like Cycle.travel. So, all of these different apps that are out there, how are people choosing? Do you think people are going through a list? And they're gonna go, Oh, I've tried that one, try that we're all like this one? Or do you think they just find one? And then they just keep on using that one come? What may? How do you think this ecosystem works? Jonathan Kambskarð-Bennett  15:39   Gosh, that's a very good question. And a very big question. I think for a lot of people, it's probably a question of what they used first. And that's, that goes beyond just these, like app based kind of routing platforms, if someone is very used to using was successful, use paper maps for decades, or if someone in the UK is, you know, swears by Ordnance Survey. And they've always had, you know, good experience doing that, there'll be unlikely to change unless you give them a very compelling argument or a good example. So I think a lot of people, what they first start using, becomes the thing that they become familiar, familiarity is so important, same of a lot of like tech or products that we use day to day, we're quite hesitant to change our routines. I also think within that ecosystem, people's preferences probably change quite a lot based on if they have a bad experience as well. Same with all types of different, you know, products that we consume, you know, there's probably many things that you've used day to day for years, and suddenly when it breaks or something goes wrong, you decide I want to try something different. And then I would also say the local element probably plays a significant part in it. You mentioned in like other regions, or for example, North America, the market is in a different, like perhaps different status for us or you know, different other products that are available for people, I think a lot of it depends on the local side of it has to do with your peers. So like who you explore with you trusting your your recommendation of those you go out with, or the people who give you a great experience outdoors. But also whether or not the product is is localised and translated into your language that also makes a big difference people find rightly so it's reassuring when the product is as easy to understand gives a different level of trust. So I think those are a few of the factors, that that kind of changed the state of play. But overall, I would say that it's really, it's a good thing. There are a lot of incredible, incredibly bright minds and have great innovative companies in a kind of overlapping space, often with a slightly different objective. And, you know, that's, that's just great for the consumer, because it means that we're all kept on our toes, constantly looking for ways to improve those Carlton Reid  18:08   variety of companies out there, some are chosen by for instance, you know, cycle travel companies. So when you go on a on a cycle holiday, they will, they will choose to partner with a navigation app company, and then they will send you all the routes on that. So you're basically you're almost tied in on that particular holiday to that particular navigation app. Good thing, bad thing. So is that something that it's incredibly important to discover who are actually giving these links out and and calm them? Because you know, you go on a North American owned psychology company in say, Italy. And even though you're in Europe, you're using in effect and American app, because it's an American company that's leading those tours. So is that something that you are you as in Komoot? Or your your, your your colleagues and commute are actively trying to partner with these key companies? Yeah, Jonathan Kambskarð-Bennett  19:15   there are. I mean, there are a lot of ways that we might sort of acquire new users. And by that, I mean, like reaching people and giving them their first experience on commute, those kinds of partnerships. I guess they probably represent like a smaller percentage of the ways to reach people. But that doesn't mean that they're not important. Particularly because if that partner whether it's a tour operator, or you know, a hotel or someone who's running a hotel, or even an event organiser, if they trust in Khumbu, and you know, I would say in Europe is you're far more likely to find that stuff that information presented to you via commitment than anyone else. That's great. because it's just reassures the, you know, the user that people look for that kind of reassurance from those those kind of places of authority. So those partnerships are really important to us. And we do work with a lot of tourism organisations, maybe even like hotels, tour operators, we do have quite a lot of active partnerships. And it's great for us because we reach that audience. But it's really good for us, we put a lot of effort into the people that do choose to work with us on educational tools, so that they understand it coming inside out, and can then give their users good experience. And that remains like super important for any of those types of partnerships Carlton Reid  20:39   can notice. If you get a bradt guidebook, a cycling guidebook, and it's you know, to the lanes of East Anglia, or whatever have you Yeah. Well, you're flicking through this, this book. And there's a little QR code. You open that up, I know, there's your route in Komoot via the Bradt guidebook. So what else have you got? Who else are you apart from Bradt, what else you out there in like a published terms? Jonathan Kambskarð-Bennett  21:10   Well, it's just a good question off the top of my head. And when I struggle to think of them, but quite a lot of I mean, of course, is difficult because we are so you know, across the whole of the continent. There are some amazing publications and magazines that we've partnered with across Germany, France, Italy, Spain. And I think one thing that's really nice at the stage that commutes that is, particularly within certain segments, in Europe, we are, it would almost be strange for the user to have the route presented to them in a different way. Because they're so familiar with commute. That's what they use for their group rides. That's what they use for the events they sign up to. That's what they do for their day to day riding. And so a lot of those partners like they will present stuff on Komoot, regardless, like we'd always like to help them present the stuff in the best kind of best way possible. But they're still going to be reaching out and using Komoot, simply because it's a really nice, easy way to share and present routes with your kind of users or participants. Carlton Reid  22:16   And what do you do for Komoot? So what is the community part of your job title? What is what is? What does that involve? Yes, so Jonathan Kambskarð-Bennett  22:25   I'm the global community manager komoot. The global part is, well, global, but it's in particular, it's about the gaps between. So we have a team of community managers spread out. In some of the markets where we have more kind of community oriented stuff going on, we have more people. So there's, there's a couple of two or three people in Germany, we have a couple of community managers in the UK, I'm kind of filling in the gaps between a lot of the markets that are growing for us, but aren't quite at the same same kind of stage just yet. And then the community, part of it is kind of two things. One thing is our external partnerships. So that could be with events and event organisers that could be with the kind of inspiring individuals that we work with, because they have, you know, a great platform, or they have a very inspiring story to tell, or they're great at motivating people that that follow them. And then on the other side of that, I have a lot of focus, particularly these days on our core community. So Komoot is, while we're really lucky that we have such a huge audience, audience, we've got about 37 million users. So there's a lot of people. And not all of those people are, you know, active every day or using commute to connect with other people and share their stories within the community. But we have millions of people who are and I spend a lot of time, as do my colleagues on how do we give these people? Like how do we reward them for their contributions? How do we motivate them to share more? How do we make sure that people are getting fed the right inspirational content based on their preferences? So elevating our kind of, and looking after our core community is also a significant part of my role. Carlton Reid  24:22   So can you is it gonna kind of go slightly backwards into your background as well, if you if you are going to set out on a kind of track that you started in 2015? Are you going to do that now? For instance, could you open up Komoot and say, you know, do me a route from London all around the world back again? Or do you have to do it in stages? How would you use if you're going to be doing it again? How would you use commute? Jonathan Kambskarð-Bennett  24:55   I think I think doing a route around the world probably possible but That's an awful lot of information for for one file. So I will probably break it down into smaller segments, which is to be fair, exactly what I did when I cycled around the world, and what most people probably would. And so when I when I left home, and sometimes thinking about cycling around the world is quite kind of overwhelmingly big kind of concept to navigate. But I would break it down into really small parts. So I knew that I wanted to cycle from London to Copenhagen. I knew that I wanted to visit a friend in Amsterdam, for example. So to begin with, I would focus on how do I get from London to Amsterdam, that's a kind of more sensible, you know, if you break it down to blocks, the whole thing becomes a lot more manageable, both in terms of logistics, but also mentally. So I will do the same on Komoot. One thing that sets you apart from some similar, some similar platforms is that we have a variety of different sport types you can choose from. So if you go on the route planner, you'll see that even for cycling, there's a few variations. There's like road cycling, gravel riding, bike touring, mountain biking. And that's really important because well, even even within bike tours, people have different preferences. If someone wants to get to Amsterdam, in you know, two or three days, on a road bike, credit card, touring, staying in hotels, they might want to be thinking, you know, they want to have the mindset of a road cyclists, they want to choose quick, efficient routes, they're on 25 mil tires, they don't really want to be going down toe puffs, no matter how they're graded. So these different algorithms think slightly differently, which I think is is really important. I would personally I would, for the way I was touring leisurely, I would be on the bike touring mode. But no, that's it's just important to point out there's different types based on your kind of bike and you're writing preferences. We have a tool called the multi day tour planner, so I could pick from London to Amsterdam. And then I could divide it up into let's say, I want to do it in four days, or I know that I want to do about six hours of cycling a day, I can divide it up and it takes into account the elevation on the way. So it has like a kind of consistent breakdown, which is really helpful when you're trying to forecast when you might get to a certain location. The other tool that I would definitely would be using on the route planner. One of our features is the sport specific overlays. And then you can overlay the long distance or National Cycle routes, which is super helpful. I do this and I'm always toggling between these wherever I'm out hiking or cycling, it just means at a cursory glance, I can see the long distance routes. So for example, I was at the time following loosely one of the EuroVelo. The common which number is the one that goes up along that coast. Well, I can see that overlaid on the map. And so I can compare that against the route that I'm plotting, I can make sure that I'm like loosely following it that that makes a real big difference. Both when I'm long distance touring, or if I'm even just kind of out exploring in the south of England. So those are a few of the main tools that I would use. The final thing I would add, I wouldn't have such a rudimentary cycling computer, I would still have, I'd still have one. The Garmin that I have now is far more modern and has base maps. And we actually have an app designed for Garmin specifically. And with that, I can create the date the routes on my phone. And I can just press one button send to device and I can load up the IQ app on my Garmin device. And the route will just go bing. And here it is. And if I want to change my route, halfway through the day, I can now just update it on commute on the app on my phone and press updates. And I'll get a little notification and my route will be updated. So if I wanted to cut my day short, we'll go to a different hotel or campsite an evening. And that feature is so cool. And I think if I'd had that all those years ago, there would have been a lot less faffing involved, which would have been wonderful. Carlton Reid  29:14   Yeah, I use that the other day, in fact. So I had a Garmin unit and I had I was navigating with Komoot hadn't actually changed the route because I just got on my bike after 70 miles because the wind was about 50 miles an hour ahead of me. But still, I was using it and it was neat that so I agree. So the map, I've got the app open here now and in other apps, you have a choice of quite a few maps. But here I don't I see the the Komoot map. I see a satellite map but then there's no like Ordnance Survey for the UK. So because your is that because you were an international brand and that's just what on market, yeah, there's no point just offering an OS just for one market. I mean, Jonathan Kambskarð-Bennett  30:03   you could obviously you could argue for it. And in the UK, a lot of people aren't really familiar with and put a lot of trust into Ordnance Survey, commutes sort of core foundation revolves around OpenStreetMap, we are such committed believers of the Open Street Map Project. And it's really at the core of everything we do. And we are constantly looking for ways that, you know, we can help to enrich the data that's there or help to facilitate improvements to it. And you're right, I think, because we are active in so many different countries, we could protect, we could try and add all of these different national maps. But the the user experience would become quite convoluted. You know, if I travel a lot using commute, I quite like knowing that I can get my head around the commute render of OpenStreetMap, which is our like, primary map, and then we have satellite map. I like being familiar with it, I like knowing that the sort of routing algorithms will give me consistent results in different places. And that's quite important to ask that we still give people like a quite a not simple, but like, you know, familiar user experience that doesn't become overwhelming or confusing for them. But we really, we really, I should stress that we like, especially in the markets where we are most active in the quality of the OpenStreetMap data is is really amazing. And it's always improving. And it always is, yeah, enough for us to give people a really good experience. Carlton Reid  31:40   Maybe it's it's an age thing then because I mean, I grew up with OS maps, maybe people who are younger than me and not so hide bound, you know, as you could you have seen before, you know, people are no longer using paper maps, if I've grown up as a user of paper maps, and I no longer use paper maps, but I use the Ordnance Survey maps on my, my phone, it generally tends to be if I'm like trying to visualise an area, then me will as somebody who has grown up with that kind of Ordnance Survey mind map, I would I would default to Ordnance Survey as that's how I explain, you know, my, my where I am. So to me that's like, wow, I need I need, you know, I need iOS to know exactly where I am. It's great to have the Open Street Map. It's lovely. And the commute version of it. But still like, Yeah, but where am I? And I need that something's very familiar. But that might just be you know, people have an older generation. And that that is obvious to my son to Josh, that had zero relevance. And he probably wouldn't know his way around and OS map, but you don't know his way around, you know, the Komoot map really well. So do you think that's just telling me Jonathan, is this just me? Is it just me because I'm very, very old? Jonathan Kambskarð-Bennett  33:00   If I frame my answer, as well, to be careful, I think your Ordnance Survey specifically as a very particular place in the British sort of, well, the psyche of how we spend how we map the country, is equivalent in other countries. I'll give you an example because I sometimes almost feel like as a outdoorsy person who likes Grim Adventures and is British and spends a lot of time exploring the British outside. I, you know, I should be more familiar with Ordnance Survey I confess, I have grown up in London. I didn't kind of do much outdoorsy stuff at school. Honestly, I've never really used Ordnance Survey I am, when when I started to explore, there was sort of these phone based solutions available for me right away sort of 10 years ago, revolving around OpenStreetMap. I do spend a lot of time hiking and walking for leisure. And I've just never found that I that I needed it. I'm super familiar with OpenStreetMap. I'm now an expert in how Komoot works. And so it's just funny, I think it's like different types of people, for sure, especially in the UK, but I would say also globally, is just very different, like different generations who have grown up, especially have the sort of, you know, even for example of Google Maps is sort of omnipresent in our exploring of the world and navigating I'm talking about everything now from public transport to driving. And even like the sort of sat nav, the satnavifacation, I'm sure that's not a word, but how we drive a car around the world has now had a massive influence on on people hiking and cycling. A lot of people would prefer to hike with turn by turn instructions on their phone and find that far more easy to get their head around than navigating from a paper map and pen The people could argue that that's, that's not as good. But I think if you embrace, you know, the quality of the map data and you embrace it, this actually helps a lot more people explore because there are less boundaries or sorry, less. Yeah, sort of less friction points. So less obstacles for them to to get over to outside. I'm not sure that's necessarily such a bad thing. Carlton Reid  35:23   And let's go slightly backwards in that. The name Komoot is a pun on commute. So when it was originally developed, was it as an internal city thing? Or was it always, you know, this is meant to explore the world with or was that explore the world with just something that came afterwards and is the name a bit of a misnomer, Jonathan Kambskarð-Bennett  35:56   is actually a bit of a misnomer, partly because it's actually like a Komoot is derived from, I think it's called the Valsa dialect, which is the region that the founders are from and it's just like as far as I understand it, a casual greeting means something like simple and practical. And so it's a it's actually slightly misleading, because that's the origin of Komoot, obviously, was Carlton Reid  36:22   Nothing at all to do with commute. Well, Jonathan Kambskarð-Bennett  36:25   I don't, I mean, it's not sure if it's a good or a bad thing that they're so similar, but that's the origin of the name Komoot. It doesn't, and the sort of the product and the philosophy doesn't come from commuting at all, it's about spending time outside. Of course, you could probably interpret that in many ways. Perhaps this is an alternative way of you know, commuting in nature. As it happens, many people use commute as part of their commute within town because they want to find a more scenic way of getting from A to B. But that's not the that was never the objective of the company and and still that isn't the case. Carlton Reid  37:05   Right? Interesting. So I got that wrong that Well, Jonathan Kambskarð-Bennett  37:10   I also had one for a very long day if that makes you feel better. Carlton Reid  37:15   It does Thank you very much. Jonathan Kambskarð-Bennett  37:17   I'm afraid now that you'll really struggle to pronounce Komoot without saying Komoot because it's only a matter of time before for that becomes a riddle itself. Carlton Reid  37:26   Well, of course Google isn't I think it's a mathematical term isn't it? So would have been familiar to some people but most people it's not it's not familiar terms. It's just these unusual term. So anything that's slightly unusual is better for a website you know name so the fact that you kind of spelling this and you people think it means there's but doesn't but they remember anyway so that's that's the trick just remembering it. So if it's if it helps some people doing all that must be Komoot Oh, yes, he spelt with a K. And other people's know it as a, you know, a greeting in a certain language. That's also okay. So it's however you get your name remembered? Jonathan Kambskarð-Bennett  38:03   Yeah, very much so. Carlton Reid  38:06   So at this point, I'd like to actually cut away and let my colleague take over and we'll be back in a few minutes. So take it away, David. David Bernstein  38:16   This podcast is brought to you by Tern bicycles. The good people at Tern understand that while a large cargo bike can carry oodles of stuff, many of us prefer something a little more manageable. That's why they've come up with the HSD e-cargobike for folks with big aspirations to go car free, delivered in a compact size, with its rear shock, 280 kilos, and a combined hauling capacity of 180 kilos. The robust new HSD is stable and easy to manoeuvre, even when under load. And with its Bosch eBIKE SYSTEM tested and certified to meet the highest UL standards for electric and fire safety you'll be able to share many worryfree adventures with a loved one whether it's your kiddo or Nan. Visit www.ternbicycles. That's te r n turn bicycles.com to learn more. Carlton Reid  39:17   Thanks, David and we are back with with with Jonathan of Komoot we've discovered that it doesn't mean commute and that's it you want it to mean commute. It can mean whatever you want. But Jonathan is he's the community Global Community Manager for Komoot and he's if anybody's going around the world on their bicycle or wandering around the world on the bicycle and they wanted to use commute then then clearly Jonathan would be a good guy to to learn from Andy certainly in a pretty good job for for the kind of company commute is because Jonathan, you went round the world well, we have touched on this but now let's let's explore this in in greater detail. So we've got the Komoot out of the way. Let's let's, let's talk about what where you've come from and why are you working for for Komoot? So we laughed before. Could you mention the fact that when you started, you were much of a cyclist? And I was kind of thinking, Yeah, that's right, because of what the amount of kit you took to begin with is the kind of the classic. And I made this exact same mistake when I started my cycle touring adventures many, many, many years ago, you take too much kit. So you had an enormous amount of kit. And you had a kind of an old school bike, you were you on steel, you're on a bicycle that I would have been familiar with in the 1980s, you know, a Dawes Super Galaxy,  classic touring bike of a while ago. And then you you you've, you've clearly learned a lot. In that time that you're away, but you started reading your blog, you basically picked this bike, you didn't seem to know much about cycling, and then like, a week later, you're, you're off touring the world. So describe it. Have I got that? completely correct, you were pretty much a novice, and then you went cycled around the world. Jonathan Kambskarð-Bennett  41:18   That is, that is pretty much it. It's almost embarrassing to admit how little preparation or knowledge I had prior to leaving, but I think I was just blessed with youthful naivety time, and I didn't have high expectations at all, I just wanted an adventure. And there are very few simpler ways of finding one than grabbing a bike and kind of just heading off without a plan. Carlton Reid  41:44   Or when it's classic, absolutely classic, the way the way that kind of developed. But let's let's find out what were you doing at the time? How long were you expecting to do? You didn't have any plans at all. We literally tried to go around the world, we didn't know how long was going to take? Or were you just going to cycle and see where you got to and then just what you might give up at some point. What What were you doing? How old were you and what were you doing at the time. Jonathan Kambskarð-Bennett  42:08   So if I rewind a little bit further, we touched upon it at the beginning of the call. I grew up I grew up in London, but my my Yeah, my father's British, my mother's Danish. We never cycled or I never cycled for fitness. I never cycled for leisure or for exploring. However, I did grow up riding bikes, it was just very much like a functional tool to get around. London is not bike friendly city. But it's a very practical city to get around and manoeuvre by bicycle. So I grew up cycling. I studied music at university. And when I returned to London, I wasn't entirely sure what to do next, like I'm sure plenty of young people. Now, early 20s have the same sort of existential crisis. I was quite fortunate that I'd been working the whole time I was studying and, and while I had an awful lot of debt, I had somehow ended up with, you know, a few grand in the bank accounts saved up so I kind of had this incredible, I was in this incredibly privileged position where I could kind of yeah, go and explore a little bit without having to take the next the next most serious steps in life. I had always travelled a lot that had been a high priority for me, I had done a bit of long distance walking, I was kind of prepared for another long hike. And then kind of had this this moment, this epiphany I suppose, where I thought well, what about cycling that could be I was really interested in human power, not human powered, rather, I was interested in overland travel. So I became kind of fixated by this idea of, of cycling and then bike touring. And, and these were, I think, a wonderful period on internet where you could find all these incredible blogs that were so relatable and so inspiring and so informative as well. And so the sort of recommendations I found online, people said, those galaxies a good bike, found one on on eBay bought it was a good pannier to take Balsam or leave panniers from Argos and got all of this around Christmas. And I left two weeks later and the plan at the time, I'd been sort of telling my peers and family I was gonna cycle to Australia, but it was it was a it was a pipe dream. But it was kind of a joke as well. It was a good way of like picking something so outlandish that people wouldn't take it seriously at all, which was fair enough given that I had never cycled further than about 10 miles. And so I I set off as I said to go and visit my mother, and I said if if this goes well, I will continue heading east and I had a fantastic first month and I continued writing to Turkey. I became very good at living, I would say extremely cheap on the road. I realised that I could probably get quite a long way. And, and yeah, I ended up going all the way to Australia, by which point I was completely broke. But I got a job and worked for a few months there. And then at that point, I, it became very clear to me that I wanted to continue and make it around the world cycle. And so I did that. And Nick got home, just under three years after having left probably having clocked around 50,000 kilometres, which is kind of a mind boggling number when I say out loud, Carlton Reid  45:32   huh? There's some people kind of do that in three weeks. I'm exaggerating a little bit, but they do it fast. And, you know, some Komoot users, Markus Stitz, for instance, did on a single speed, etc, etc. But you took three years. Now, it's not that you weren't doing some big mileages, you know, there was there was, you know, I read on your blog, you know, some days you're doing 145 kilometres. And then other days, clearly, you're, you're just doing nothing, because you're just enjoying the location. So you never had any plan to do it in a certain amount of time, you would just basically ebb and flow. It was just whatever the live through it you you kind of did that. Jonathan Kambskarð-Bennett  46:17   Yep. And thank goodness, I personally like that. Because otherwise, I think it would be overwhelming to think about and those people who cycle around the world planning on it or trying to break records, I think it must just require so much. That's no fault and pressure, I really was just kind of going for a ride, there was never any pressure, no expectation. If I went home, whenever I was bored, that would have been fine. No one would have judged me. So I was really making up as I went along. And when I left, I had absolutely no plan to spend anywhere near that long on the road knows that I have any plans to cycle all the way around the world. I am a Tura. At heart cycling at that pace is and I've done a lot of more, sort of a dyno extreme bikepacking. I've done a lot of ultralight cycling, I've even tried a few ultra endurance races. But touring at that kind of pace, for me is just the most kind of beautiful ratio in life. Hmm. Carlton Reid  47:20   So notice, you've done the Transcontinental. So you have done these, these, these races, but your forte is basically just pootling along. Jonathan Kambskarð-Bennett  47:30   Definitely. And if I if I continued to my cycling trajectory in between cycling around the world, and ending up doing what I'm doing currently at Komoot, when I returned home, having spent all of this time on the road, I actually worked as a bicycle courier in London for a short period, which was there's no better way to re calibrate and reintegrate into city living having spent so much time on the road and to get paid to cycle around delivering stuff and exploring, you know, a city even if it's your home city by bike. And I then started working at a company called Apidura. And I know that you're familiar of a producer, because I believe you interviewed the founder of Apidura in this past few years. And I was there for a few years. And that was really, I mean, obviously made sense. I had a lot of touring experience. But that was in 2018, which was really when this hugely significant kind of shift in interest from bike touring to bikepacking. Which you can interpret in many ways. But, but this this shift was really kind of about to explode, and then get even more exaggerated through the pandemic. So I, I had learned so much about travelling by bike and then I learned so much about the benefit of ultralight cycling and these new packing systems that were so different to taking for panniers on a loaded bike. And so I spent four years at the Jura did the roller coaster that was COVID 19. And and that was sort of the segue that led me to Komoot because Komoothas been so involved with bike packing bikepacking as an established but also an emerging sport in the last few years. Because Carlton Reid  49:19   you looking at your your bike setup. Back then with the with the Dawes Galaxy, and the bags you had on that was very much old school. And then I can completely identify with that because I'm clearly old school. And that's where I started. So you know, for panniers at least loads of stuff and caring too much, etc, etc. And you look at that now and you think no, you would have the upward Eurostyle you know you'd have the bike packing bags, you probably wouldn't be carrying quite as much Kip, although some of the place you went to. You know I'm thinking of you like your Australia video. and stuff where you're obviously having to pack. I mean, when you go across the desert, you having to pack you know, an enormous amount of water, you've got to have all of the bug kit, you know, you've got to have all of the stuff that's protecting you from the nasties. So you had some times you have gotten better how many it's not an old school versus new school thing. It's just you have to have a lot of kit in some places and and there's no two ways about that. You know? Even if you're doing a transcontinental style, you know, fast route across somewhere, you would still need a fair bit of of kit. But when you were when you started out, okay, actually good point. Did you finish on the same bike? Jonathan Kambskarð-Bennett  50:43   I did, I finished on the same bike and I still ride that same Dawes Galaxy as my day to day pub, one around bike. Carlton Reid  50:51   Excellent. So it's but it's like Trigger's Broom, you've got you know, you've replaced tonnes of things, or it's still largely the same bike Jonathan Kambskarð-Bennett  50:58   is the same frame, the same fork. And that is nice. All That Remains of the original bike. Carlton Reid  51:05   So that's pretty good going well done Dawes Super Galaxy.  Jonathan Kambskarð-Bennett  51:09   Yeah, there's a lot to be said. Having modern bike so us so reliable in general. But yeah, I'm very much of the steel fan club. That bike has a lot of battle scars, from various sort of unfortunate collisions with other vehicles or just the road or ice. But it's still yet it's still going strong. And, and you're right, I've had the been very lucky to experience travelling by bike in very different forms from the kind of old school bike touring sense where you carry basically your entire house, to super ultra light, you know, bike travel, where you just have a bivy bag, and you sacrifice all levels of comfort. I've also done a lot of off road sort of mountain bike touring, I think the thing that I find so wonderful about bicycle travel in general, is that there's always a new way to do it. And there's absolutely no right or wrong way of doing it, I think it's very easy to get caught up in the the idea of I must be a lightweight bike packer, or I must do it in this particular way. But really, there's no right or wrong way of doing it. We're all very different, we all travel for very different reasons. And there's different ways of, of packing for it. And, and even if I refer back to commute and the way that we're set up, we give people the tools to, to pick, you know, they can pick the fast road route, if they want, or they can pick the meandering route, they can pick the most direct one, or they can pick the most leisurely one up over the mountains. I think this whole kind of space is really set up for the user to be able to customise you know, what they're doing, and how they're carrying it based on what their objectives is. And I think that's what's really kind of charming about the whole two wheeled travel thing. Carlton Reid  53:02   See, I'm a historian of many things, but including cycling, and Thomas Stevens, if you hadn't if you've come across that name in in the past, but he was basically a big wheel rider. So what would people would call Penny farthings. And this is 1880s. And the kit he had, the amount of kit he had and how it was packed is very much like bikepacking You know, it's the big pannier bags, that's pretty much the 70s and 80s thing, you know, really, really old and I was calling that old school, but genuinely old school. So 1880 stuff is you know, Apidura-style, incredibly lightweight, hard to carrying anything at all kind of touring. So that's that's kind of where cycle touring started. And we've kind of come full circle in many ways. And so people are going out there with incredibly minimal bits of of kit and somehow surviving. So when you did your your your your cirumnavigation, and you had all this enormous kit, where you jettison bits as you're going along. And just in case you didn't you don't really need this you pick it up basically you became an expert. Just cook you're having to carry this stuff. And because you haven't to carry it, you quickly learn I don't need that Chuck it Jonathan Kambskarð-Bennett  54:30   Yeah, and I did get rid of an awful lot of stuff. I had some some very questionable belongings with me. Like I had my my, I mean, I was on quite a budget when I left and and while I was going so it's sort of just what am I sacrificing a bit of weight for a cheaper option, but I had like my, my mother's old coat which was this like not anything resembling a down jacket, this monstrous thing that took up half a pannier. I had a pair of jeans with me to wear like when I was off the bike. So much unpractical. kind of clothing thing, I even had like a sort of smart casual shirt, I thought I would like to dress up like a non bike person when I was in town for a weekend, or things that I would never do now. And I did get rid of a lot of this stuff slowly. And as time went on out kind of improved things a bit as they broke. But then there was a lot of things that I wouldn't change, like I travelled with, I mean, I had like a cutting board with me so that I could chop vegetables up when I was camping, and had little film canisters, filmed of spices and a proper source bird. And so I could like, eat well, and, and I wouldn't, again, a lot of bikepackers could turn a nose up at that and think God's this person's just sort of like a moving kitchen. But I you know, for such a long period of the bike, I wouldn't, I wouldn't change that at all. And on and I know that the sort of, especially at the moment with the sort of influences bikepacking has had on on taking existing cyclists and making them realise what they can achieve on the bike. I still am a big believer in taking a bit more stuff if your legs can handle it. And if you're not in a hurry, you know, riding up a mountain with the extra weight on your bag, it's not going to do your fitness any any disservice. If you can get up it. I think a bit of both comfort is quite okay. And while in general, I'm a minimalist these days, I think there's plenty of space for carrying a few extra luxury items whenever you're travelling. Carlton Reid  56:30   But did you come back? Not you but did the bike and the kit come back a lot lighter. So by the time you'd finish, because I know you you'd have to badmouth the bags that you had. But you certainly changed your your your bags halfway around because of various reasons. And other notes on your blog, you do kind of, say a few choice words about the brand you had. But did you come back with? Did you come out with a lot more lightweight than you went? On much more lightweight? Jonathan Kambskarð-Bennett  57:00   I would say I might have shaved off like a kilo. Like in general, I pretty much had the same amount of stuff with me. And yeah, it couldn't have bothered me that much. Because otherwise I would have gotten rid of an awful lot of stuff. So no, I actually, I actually think I returned with a fairly similar amount of weight on my bike. That's Carlton Reid  57:22   interesting, because that's totally opposite to the way I did it. So when I started out, I had so much kit, I had like a wooden hammer for hammering in the tent pegs I had, like, we just get a rock, you know, I had so many things that I just I was chucking stuff you know, from the very, very start and you've kind of quickly got used to you know, what was necessary and what wasn't. And you don't know that until you're actually on the road. So I was ended up with with a lot less kit. So I taught myself minimalism, just because, cuz, whereas you're saying you don't, it doesn't matter, you can just pedal up a hill, I was the opposite as like, No, I'm not the crane brothers. Famously, when they went up Kilimanjaro and their stuff, they they would, you know, drill holes in toothbrushes, I was never that extreme. But I would definitely want to be lightweight, as much as possible. And so I am kind of interested in taking a chopping board. So I wouldn't have done that. This is interesting about how different people approach these things. And like, I have come down to the minimalist and caring such a little like I wouldn't, personally I wouldn't, not even going on like a camping trip. Now. I won't take cooking equipment, for instance, I will generally buy what I need, and eat that and then have to then scrambled to get, you know, fresh supplies. And I know it's much more efficient to take rice and what have you and then be able to boil this up. But to me just carrying any amount of cooking equipment to me in my head, just that's too much weight, I can do this much lighter. And clearly you're you're not you're a different each to their own, isn't it? It's just different people want to do different things. And that's fine. Definitely. Jonathan Kambskarð-Bennett  59:22   And we need to make sure that we always sort of accommodate that. Because people are so different. And and I think it's difficult, you know, in life, for example, in the cycling industry, it's a consumer driven industry, we need to convince people we brands need to convince people that they need to do things in a different way or a better way or an improved way. But really all of it comes down to like giving people options so they can do things in the way that they want to do it. And you know, there is absolutely no reason why one type of bike travelling is superior than another. They are yeah complete The different ways of doing things for different people. So ever people navigate in one particular way, if they choose one kind of route, it's not about that it's about giving people the options. And the same, like if someone wants to go on a road bike really fast with nothing on their bike, that's totally fine. And if someone wants to chuck for massive panniers on their bike, they'll probably be a bit slower. But that's, but that's totally okay. Carlton Reid  1:00:26   And so what are you doing now? During what what? How would you describe your riding, and your adventuring now, Jonathan Kambskarð-Bennett  1:00:33   my, I still try. And when I travel, I always want to be on a bike. If I'm not on a bike, I've fully compromised a little bit. But I also like spending time walking around being a normal person, especially if I'm on holiday with my with my girlfriend. But I do try and have one or two bike trips, big bike trips a year. Over the last few years, I've developed a sort of real love for exploring, I guess, capturing the essence of a big adventure closer to home. But in general, I'm sort of a casual cyclist I like to get out for provides every once a week if I can. I think working at QMU is quite is wonderful, but a bit dangerous for someone like me who enjoys spending time looking at maps, because the list of places to visit is evergrowing. But commute has this amazing interface. We have this route planner, which is wonderful gives people all these advanced tools to make informed decisions about where they're going and how they get there. But we also have this discovery interface where you can have these these created routes for you based on your sort of parameters, the smart, this kind of smart solutions, and does have a really big impact on me, since we launched it last year, I'm much more inclined to take a train out from London to a random station and say, load it up on commute and say, Hey, I'm in a new area. I've got three hours, give me something. So while I'm going on less epic adventures, and finding new kind of creative ways of exploring familiar places. I'm doing that a lot at the moment. And I'm extremely excited about doing more of that as the weather improves. Carlton Reid  1:02:19   And is that a curated thing? Or is that an algorithm thing. So Jonathan Kambskarð-Bennett  1:02:24   it's a kind of a combination of stuff. commute, we have so much user data, because we have millions and billions and billions of of users, the number of recorded tours is kind of such a big number. It's it's kind of hard to get your head around. So we're able to give people these. These like personalised suggestions so I can take the train out if I'm with a no fun with friends go out for a walk at the weekend, I can look at which train line takes me to a village that looks somewhere Scenic. I don't own a car. So I can just say I'm at this station, it will see where the people who use Komoot are heading when they record their tours. So it's very easy to get a feel for where people actually walk. Where do people go for their recreational weekend straws. And it will give me a clever or suitable solution to get kind of onto that, navigate the route and then return to the train station. And it's incredibly clever how it works. If I go on where I live now and say I want to go for a four hour cycle, starting for I live. I've lived in London for a long time and I've cycled in London for a long time. I know what all of the common roadie routes are that people take wherever they're going off to Windsor or Kent or sorry, Essex and, and if I let Komoot do this for me automatically. It's kind of amazing how it basically gives me the routes that people most commonly do. But it won't just give me three or four options, it will give me hundreds of options, which means I can go out for a new ride. And I can always find something that's slightly different to what I've done in the past. And I find that really inspiring for my, like motivation to explore. Carlton Reid  1:04:12   And then if you were in Iran, would it do the same? Or was it does it need that you know, lots and lots of people have done this before or kind of just glower three people who've done this, okay, that'll be the route we curate for this. This person has just ended up in Iran, for instance, such as yourself a few years ago. Yeah, you Jonathan Kambskarð-Bennett  1:04:28   need to have the use of data because it's based on what people actually do. So if we didn't have that it wouldn't we only want to do it when we're confident we give people a good experience. Otherwise, no one benefits from it. You can obviously still use the route panoramic, your own tool in Iran. The what I would say in certain regions where there is less user data, we have an editorial team that make it they're the the we create the content so we'll find what are the classic like walking routes based on like variety of sources, we have an extensive editorial team that will add this content. And they will add suitable highlights, which is what we call the contributions that the community creates to add on to the map. So that this is an amazing viewpoint, this is a great cafe to stop out if you're a cyclist, this is a really beautiful, rich line stroll. So we will help to populate the map so that the people who are used to kind of a circular thing, the better the map data is, the better that the attributions are on commute, the more local people will find, have a good user experience. And then the more they use it, the more they'll contributes. And that's how we kind of launch in in new places where there's less of an active community, if that makes sense. Carlton Reid  1:05:48   Yes, your heat mapping then, in effect, so you're you're working out where people are going, and you see you perhaps, you know, and your your fellow app. This this ecosystem we talked about before, you know, where people are cycling, you know, like the Strava, type heatmap. Jonathan Kambskarð-Bennett  1:06:06   Exactly. So we can I mean, it's all obviously, like, it's only when people choose to share stuff publicly. It's all like completely anonymized. But you know, we have so much data, we're just trying to harness it. And yes, we do know where people cycle we have that information that's great is quite hard to sort of digest. But if you can take that and turn it into something actionable, the end result for the user is that they can say, I'm a beginner, I've got two hours, I've got a new phone mount to go on my handlebars, I can select this tool, I can just press go. And I can head off and have an amazing bike ride for two hours. And we can be really confident that it's going to be suitable because that's what other people are doing when they, for example, select bike touring as a sport type. And the same for hiking, we won't have people won't be walking down the road, because we'll only be looking at data that's come from hikers. It's a very Yeah, it's an incredible solution is very clever. And I think it's just a great way of mobilising people, whether they're like really experienced cyclists who are just looking for something new and and bored of doing the same kind of loop over and over again, or newbies who need their handheld a little bit. And once I have a solution that they can just go off and do with five minutes of planning instead of an hour of planning for a two hour excursion. Carlton Reid  1:07:33   Now right now the bike and I don't know how much you know, this, but the bike industry, certainly in the UK, and in many other places in the world is is suffering just incredibly bad. It's just it is it is dire out there at retail. It's dire out there for suppliers, you know, post COVID, we basically just got a huge, huge, low a complete slump. You know, I did a story on Forbes of the day talking about how to 40 year low in the UK. You know, the last time we were as low as this in bike sales was in 1985. So 39 years. And that's that's that's pretty poor. Do. Do you recognise that? Is that something you can look at and say, oh, people aren't writing as much? Or is that just purely at retail and people still riding that is not buying? Jonathan Kambskarð-Bennett  1:08:24   Is a good? It's a good question. I actually saw that Forbes article and is it's definitely bleak reading. But I've worked in the bike industry for a number of years. It's like, I know many people who share the same kind of anecdotal experiences that things are changing. It is a problem with retail and definitely like have these hangover kind of effects from the pandemic that still making it really hard for people to forecast well. And, and it's just been so unpredictable for a few years now. Komoot is lucky because we don't deal with a physical product. But we are subject to the same the same kind of you know, these kind of cultural shifts, whether people are collectively interested in exploring or cycling, we're not immune to that we might not have the same issues that a bike manufacturer has, but we still get impacted by the same changes. And it's hard for us to predict these major shifts in usage in the same way that it's hard for an

This is a recap of the top 10 posts on Hacker News on February 11th, 2024.This podcast was generated by wondercraft.ai(00:53): I designed a cube that balances itself on a cornerOriginal post: https://news.ycombinator.com/item?id=39336139&utm_source=wondercraft_ai(02:28): What it was like working for GitlabOriginal post: https://news.ycombinator.com/item?id=39333220&utm_source=wondercraft_ai(04:17): Finding a new software developer jobOriginal post: https://news.ycombinator.com/item?id=39337696&utm_source=wondercraft_ai(06:14): Keycloak SSO with Docker Compose and NginxOriginal post: https://news.ycombinator.com/item?id=39333360&utm_source=wondercraft_ai(07:55): 2024: The year of the OpenStreetMap vector mapsOriginal post: https://news.ycombinator.com/item?id=39339182&utm_source=wondercraft_ai(09:34): RLHF a LLM in

Geoffrey Litt thinks browser extensions are underrated, Adolfo Ochagavía on being a generalist in a specialist's world, Jack Garbus praises the Arch Wiki, Terence Eden tries to rebuild FourSquare for ActivityPub using OpenStreetMap & Sebastien Dubois teaches us how to connect ideas together.

Geoffrey Litt thinks browser extensions are underrated, Adolfo Ochagavía on being a generalist in a specialist's world, Jack Garbus praises the Arch Wiki, Terence Eden tries to rebuild FourSquare for ActivityPub using OpenStreetMap & Sebastien Dubois teaches us how to connect ideas together.

Geoffrey Litt thinks browser extensions are underrated, Adolfo Ochagavía on being a generalist in a specialist's world, Jack Garbus praises the Arch Wiki, Terence Eden tries to rebuild FourSquare for ActivityPub using OpenStreetMap & Sebastien Dubois teaches us how to connect ideas together.

This episode features a panel discussion with Stefano Maffulli, Executive Director of the Open Source Initiative (OSI); and Stephen O'Grady, Co-founder of RedMonk. Stefano has decades of experience in open source advocacy. He co-founded the Italian chapter of Free Software Foundation Europe, built the developer community of the OpenStack Foundation, and led open source marketing teams at several international companies. Stephen has been an industry analyst for several decades and is author of the developer playbook, The New Kingmakers: How Developers Conquered the World.In this episode, Sam, Stefano, and Stephen discuss the intersection of open source and AI, good data for everyone, and open data foundations.-------------------“Internet Archive, Wikipedia, they have that mission to accumulate data. The OpenStreetMap is another big one with a lot of interesting data. It's a fascinating space, though. There are so many facets of the word ‘data.' One of the reasons why open data is so hard to manage and hasn't had that same impact of open source is because, like Stephen, the stories that he was telling about the startups having a hard time assembling the mixing and matching, or modifying of data has a different connotation. It's completely different from being able to do the same with software.” – Stefano Maffulli“It's also not clear how said foundation would get buy-in. Because, as far as a lot of the model holders themselves, they've been able to do most of what they want already. What's the foundation really going to offer them? They've done what they wanted. Not having any inside information here, but just judging by the fact that they are willing to indemnify their users, they feel very confident legally in their stance. Therefore, it at least takes one of the major cards off the table for them.” – Stephen O'Grady-------------------Episode Timestamps:(01:44): What open source in the context of AI means to each guest(16:21): Stefano explains OSI's opportunity to shine a light on models and teams(21:22): The next step of open source AI according to Stephen(25:38): Creating better definitions in order to modify software(33:09): The case of funding an open data foundation(42:31): The future of open source data(51:54): Executive producer, Audra Montenegro's backstage takeaways-------------------Links:LinkedIn - Connect with StefanoVisit Open Source InitiativeLinkedIn - Connect with StephenVisit RedMonk

Welcome to the 4th ever P.A.Z.NIA Second Realm Assembly, another meeting of our Department of Technology! Herein, we convene to discuss important infrastructure items, including: Attendees/panel members included: Jamin Biconik, Matthew Raymer, JJ, Dave from StartOS, Thomas Freedman, & more Thanks for tuning in — check out PAZNIA.com to learn… The post TVP #188: [P.A.Z.NIA Second Realm Assembly #4] P.A.Z.NIA Infrastructure – NextCloud As The Backbone, Second Realm OpenStreetMap, & “Darklance 2.0” appeared first on The Vonu Podcast.

El Euro digital avanza / Hyperloop resucita / Threads tiene casi 100 millones de usuarios / Apple sube precios / MG estudia fábrica en España Patrocinador: Si no tienes aún instalado miBP en tu Android o iPhone estás perdiendo dinero. Puedes ahorrar hasta 20 céntimos por litro repostando carburante BP Ultimate con tecnología Active, cada vez que bepeas con tu móvil. Es fácil: muestras tu app gratuita al pagar y recibes el ahorro al instante. — Porque ahora la tarjeta de miBP es mucho mejor, todos a Bepear al máximo este otoño. El Euro digital avanza / Hyperloop resucita / Threads tiene casi 100 millones de usuarios / Apple sube precios / MG estudia fábrica en España

This is a recap of the top 10 posts on Hacker News on September 24th, 2023.This podcast was generated by wondercraft.ai(00:34): Text editing on mobile: the invisible problemOriginal post: https://news.ycombinator.com/item?id=37630804&utm_source=wondercraft_ai(02:24): Gene-Engineered Mouth BacteriaOriginal post: https://news.ycombinator.com/item?id=37634713&utm_source=wondercraft_ai(04:02): Choose Postgres queue technologyOriginal post: https://news.ycombinator.com/item?id=37636841&utm_source=wondercraft_ai(05:40): Two photographers captured the same millisecond in time (2018)Original post: https://news.ycombinator.com/item?id=37636124&utm_source=wondercraft_ai(07:25): Full Resolution Photo ArchiveOriginal post: https://news.ycombinator.com/item?id=37633028&utm_source=wondercraft_ai(08:54): Workers who cut countertops are dying of silicosisOriginal post: https://news.ycombinator.com/item?id=37634161&utm_source=wondercraft_ai(10:43): Texas death row inmate at mercy of supreme court, and junk scienceOriginal post: https://news.ycombinator.com/item?id=37632122&utm_source=wondercraft_ai(12:30): There's a new map style on OpenStreetMap.orgOriginal post: https://news.ycombinator.com/item?id=37636551&utm_source=wondercraft_ai(14:06): Croatia demolished houses of libertarian project “Liberland”, seized propertyOriginal post: https://news.ycombinator.com/item?id=37631078&utm_source=wondercraft_ai(15:37): μMon: Stupid simple monitoring (2022)Original post: https://news.ycombinator.com/item?id=37636013&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

James Killick worked at Apple from 2013 to 2022 on the Maps team and has worked in mapping for the past 40 years. I've been wondering why Apple has gotten so much into Maps; Google makes sense to me, they're just the same ad business as search, but on a map. So, why -and how- did Apple get into Map?Sponsor: FeltTry out collaborative online mapping with FeltCheck out their Youtube Channel for walkthroughs of their latest featuresAbout JamesLinkedInTwitterShownotesNote: Links to books are Amazon Affiliate links. I earn a small commission if you buy any of these books.Map HappeningsTim Cook apologises for Apple Maps (2012)The Underlying Angst of Google Maps and Apple MapsBook & podcast recommendations:Build by Tony Fadell (Affiliate Link)Daring FireballDitheringLex FridmanTimestamps(00:00) - Introduction(01:15) - Sponsor: Felt(02:20) - James Describes Himself(04:37) - Car navigation in 1985(12:25) - Etak's customers(14:33) - Analog Maps(22:22) - From Analog to Digital(29:07) - MapQuest's business model: Ads on a map(32:36) - MapQuest after the Dot Com Bubble(41:28) - The Origins of Apple Maps(45:04) - Shortcomings with Google's data(46:29) - Apple wanting full control of their own maps(47:36) - Justifying the costs of owning everything(51:11) - A Rocky Apple Maps launch(54:24) - James's role joining Apple in 2013(59:45) - Indoor mapping(01:02:29) - Crafted vs automated approaches(01:06:38) - The OpenStreetMap approach(01:10:56) - Contribution vs Curation(01:15:09) - So why does Apple have Apple Maps?(01:19:25) - Would Apple move towards more advertising?(01:27:41) - Anti-consumerism in Apple's products(01:29:39) - Shortcomings of Google's model(01:31:51) - Apple Maps reviews(01:34:51) - Incentivizing contributions(01:41:08) - Michelin Stars comparison(01:46:36) - Apple's Spatial computing(01:52:11) - Books/podcasts(01:57:19) - James' blog: Map Happenings- Support the podcast on Patreon- Website- My Twitter- Podcast Twitter- Read Previous Issues of the Newsletter- Edited by Peter Xiong. Find more of his work

The geospatial world of Postgres is so much more than mapping. Paul Ramsey and Regina Obe join Claire Giordano and Pino de Candia to explore the "where" on Path To Citus Con, the podcast for developers who love Postgres. What are some of the unexpected use cases for PostGIS, one of the most popular extensions to Postgres? How have Large Language Models helped in the geospatial world? Can you really model almost anything with pgRouting? “Where” is the universal foreign key. They talk about communities and governments using geospatial data and how it's very difficult to build a database that does not have some sort of spatial component to it. Why do people care about PostGIS? Find out more about OpenStreetMap and its place in the open source geospatial world. Finally, Paul and Regina share the origin story for the PostGIS extension to Postgres. Links mentioned in this episode, in the order they were covered:PostGIS: https://postgis.net/  FOSS4G NA: https://foss4gna.org/ Ushahidi: https://www.ushahidi.com/  Humanitarian Open Street Map: https://www.hotosm.org/  OpenStreetMap: https://www.openstreetmap.org/ pgRouting: https://pgrouting.org/ Regina Obe's books: https://locatepress.com/book/pgr  Regina's book “PostGIS In Action”: https://www.manning.com/books/postgis-in-action-third-edition?experiment=B MobilityDB: https://github.com/MobilityDB/MobilityDB Blog: Analyzing GPS trajectories at scale with Postgres, PostGIS, MobilityDB, & Citus: https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/analyzing-gps-trajectories-at-scale-with-postgres-mobilitydb-amp/ba-p/1859278  OSGeo: https://www.osgeo.org/  Simon Willison's presentation on "The weird world of LLMs": https://simonwillison.net/2023/Aug/3/weird-world-of-llms/ QGIS: https://qgis.org/en/site/ QGIS “Gentle Introduction” documentation: https://docs.qgis.org/3.28/en/docs/gentle_gis_introduction/ PostGIS Workshops: https://postgis.net/documentation/training/#workshop Locate Press: https://locatepress.com/ FedGeoDay 2023: https://www.fedgeo.us/about-2023 Schedule of FOSS4G NA 2023: https://foss4gna.org/schedule.html#schedule FOSS4G Brazil, December 2024: https://www.osgeo.org/foundation-news/foss4g-2024-has-been-awarded-to-belem-brazil/  Paul's keynote talk at PGConfEU in Lisbon in 2018, titled "Put some "where" in your WHERE clause": https://docs.google.com/presentation/d/1xyXA4-0wmNX7WfiLeH9h10bIkZxrej278-mMaClagys/edit?usp=sharing 

In this podcast episode, Jennings Anderson, a research scientist at Meta, discusses the Overture Maps Foundation, a downstream product of OpenStreetMap. He explains his background in open map data and his interest in studying collaboration within the OpenStreetMap community. Jennings then dives into the Daylight Distribution, an open data product produced by Meta, and how it combines building data sets from various sources into one unified theme. Jennings emphasizes the importance of a stable ID system within the Overture Maps Foundation and the potential for easy conflation and integration of third-party data. Jennings also explains the relationship between OpenStreetMap and Overture Maps, highlighting how they complement each other.   Relevant podcast episodes  OpenStreetMap Is A Community Of Communities Cloud Native Geospatial Cloud Optimized Point Clouds The Rapid Editor With regards to accessing Overture Map data, you might find this YouTube video helpful https://youtu.be/fZj6kTwXN1U?feature=shared   Just in case you are interested in the Google building footprints here is a link to that :)  https://sites.research.google/open-buildings/

We daily drive Asahi Linux on a MacBook, chat about how the team beat Apple to a major GPU milestone, and an easy way to self-host open-source ChatGPT alternatives. Special Guest: Neal Gompa.

This is a recap of the top 10 posts on Hacker News on August 22nd, 2023.This podcast was generated by wondercraft.ai(00:39): The first conformant M1 GPU driverOriginal post: https://news.ycombinator.com/item?id=37224042&utm_source=wondercraft_ai(02:41): Microsoft is bringing Python to ExcelOriginal post: https://news.ycombinator.com/item?id=37222191&utm_source=wondercraft_ai(04:27): Hackers can use credit bureaus to dox nearly anyone in AmericaOriginal post: https://news.ycombinator.com/item?id=37222672&utm_source=wondercraft_ai(06:12): A good measurement culture where numbers don't replace common senseOriginal post: https://news.ycombinator.com/item?id=37220667&utm_source=wondercraft_ai(08:28): I walked across LuxembourgOriginal post: https://news.ycombinator.com/item?id=37218841&utm_source=wondercraft_ai(10:15): Electrolyzer efficiently converts CO2 into renewable propane fuelOriginal post: https://news.ycombinator.com/item?id=37218727&utm_source=wondercraft_ai(12:16): The feds asked TikTok for lots of domestic spying featuresOriginal post: https://news.ycombinator.com/item?id=37222393&utm_source=wondercraft_ai(14:11): Arm Announces Public Filing for Proposed Initial Public OfferingOriginal post: https://news.ycombinator.com/item?id=37219779&utm_source=wondercraft_ai(15:57): GPT-3.5 Turbo fine-tuning and API updatesOriginal post: https://news.ycombinator.com/item?id=37227139&utm_source=wondercraft_ai(17:43): Prettymapp – Create maps from OpenStreetMap data in a Streamlit webappOriginal post: https://news.ycombinator.com/item?id=37222823&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

Introducing thoughtbot's ongoing maintenance service. Need reliable support and maintenance for your software? Look no further. Our expert team handles upgrades, bug fixes, UI adjustments, and new feature development. And the best part? Our maintenance packages start at just 5k per month for companies of all sizes. From Ruby on Rails to Node, React, and, yes, even PHP, we've got you covered. Trust thoughtbot for top-notch support and optimized performance. To receive a custom quote, contact sales@thoughtbot.com. __ Maggie Bachenberg, CEO, and Trisha Ballakur, CTO, are the co-founders of Pointz, a mobile mapping app that helps navigate bike and scooter riders through safe routes in cities. Victoria talks to Maggie and Trisha about their cycling backgrounds, how they met and became co-founders, and what they feel is the differentiator for their app versus what was/is already on the market for biking-related apps. Pointz (https://www.bikepointz.com/) Follow Pointz (https://www.instagram.com/bikepointz/) on Instagram (https://www.instagram.com/bikepointz/), Facebook (https://www.facebook.com/bikepointz/), LinkedIn (https://www.linkedin.com/company/bikepointz/), or TikTok (https://www.tiktok.com/@bikepointz) Follow Maggie Bachenberg on LinkedIn (https://www.linkedin.com/in/maggiebachenberg/). Follow Trisha Ballakur on LinkedIn (https://www.linkedin.com/in/trisha-ballakur-070138187/). Follow thoughtbot on Twitter (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. With me today is Maggie Bachenberg, CEO and Co-Founder of Pointz, and Trisha Ballakur, CTO and Co-Founder of Pointz, a mobile mapping app that helps navigate bike and scooter riders through safe routes in cities. Just to get us started here, are you both cyclists? And if so, where do you do that at? What's your city? Where do you bike around? MAGGIE: Yeah, we both bike. So I live in Providence, Rhode Island, along with Trisha, and use my bike primarily as a transportation device. So I'm riding around from my house to work, to get groceries, to my friend's house, kind of all different types of purposes. TRISHA: Yeah, and I grew up biking but kind of stopped after age, like, six or seven. And it was only when I got to college at Brown, where I met Maggie, that I got back into it and felt more confident to get back on the bike. And that was completely actually because of Pointz. VICTORIA: Oh, that's nice. Yeah, speaking of confidence, I am not confident on a bicycle. I actually only learned after college. [laughs] And there's a video out there of my college friends helping me learn how to ride a bike. It's very cute. But still not my expertise. So I'm excited to learn more about it and learn about how Pointz could give you that confidence. So, whoever who'd like to start, why don't you tell me about what caused you to want to create Pointz? MAGGIE: Pointz was originally kind of my idea. And I got into biking in 2017 when I did a long-distance bike trip. I biked from Virginia to California. And it was my first time doing long-distance cycling, and I just kind of fell in love with it. But I realized that when I was riding, it was pretty scary to navigate cities in particular. And so, a lot of locals would redirect me onto different routes that were safer. And I was confused why this wasn't captured in a mapping app already. And so, that's kind of where the idea was seeded. But I didn't start working on it until I got to college and met Trisha. VICTORIA: Great. So you got to college, and you saw that there was a need to have easier access to biking and biking information in an area, right? MAGGIE: Yeah, exactly. VICTORIA: Very cool. What was that initial process like? It was just the two of you, and you started building stuff? How did you really get the traction going early on? MAGGIE: It started with doing some customer discovery interviews with local cyclists. And so we interviewed over 100 initially and just asked kind of what their biggest barrier was to start riding. And we kept hearing this recurring theme of people not feeling safe enough to go on different routes. And so we brainstormed a bunch of different ideas in a class that Trisha and I were in together. But we ended up landing on the one that we're working on today, which is, like, you know, the rating system, and then also putting the rating system of bike friendliness into a routing algorithm where people could actually find routes. VICTORIA: That's very cool. And was there anything that really surprised you in that customer discovery process? MAGGIE: Just maybe the consistency around people's fear and, like, I guess, being nervous on a bike because we were interviewing people of all types of backgrounds and experiences. And even people that were more experienced had this fear of getting hit by a car because of lack of infrastructure and that sort of thing. TRISHA: Doing customer discovery and chatting with so many different types of riders...and we call them riders, bike riders, rather than cyclists for the distinction that, you know, in the bike riding community, there's a lot of very avid fitness-geared cyclists, maybe who want to go on their bikes to burn calories and challenge themselves. A lot of people they would call themselves someone who rides a bike. And it's to those types of people where safety is really critical, especially in allowing new people to go and try to ride a bike for the first time or the first time in many years. And so, that's something else that we noticed from those customer discovery interviews is identifying the different types of riders. VICTORIA: Thank you. That clears it up for me because I never know to call someone a cyclist or a rider, but it makes sense that cyclist is more, like, the athletic pursuit versus riding and, you know, just trying to get about your day. [laughs] And it also makes me feel better that even people who are really experienced riders have fear of being unsafe or getting hit by a car because that's certainly what I'm thinking about when I'm [laughs] venturing out there. So, what was your initial build like for the app solving this problem? TRISHA: Initially, we had a couple of different Brown University interns or students working on it together one summer and myself included. And that evolved to me and this one other student who was working with us figuring out how to transition the app from, like, an iOS Swift native app to React Native so it could be cross-platform. And we had to teach ourselves React Native for that. So our intern at the time he had done an internship during the summer at this one startup where they taught him React Native. So he had done a couple of projects there. And I had a little bit of experience writing in JavaScript but really not as much as him. And so, together, we worked on coding the app from what we had in iOS in Swift, which was pretty limiting. But, at the time, it wasn't very much. But we were able to replicate that in React Native during; I think it was my junior...Maggie in my junior winter break. That became the start of our MVP, which had many, many more iterations to get all the features in and was a little bit slow to build until when we released it out, which was our senior year in about March or so. VICTORIA: So that's really exciting. So, like, how long did it take you to really get to that initial MVP with the team that you have? TRISHA: It took quite a bit longer than expected, as with all sorts of technology when you're building it for the first time. So what was important to us throughout the process was making sure that all the features we put out there were really well tested, and were useful, and were actually solving the problem of providing safer routing. And to get to that stage, at first, we, you know, we had an app in Swift. Then we wanted to make it cross-platformed, and we needed to have the routing algorithm actually take those different weights, the different bike friendliness ratings of the roads into account. And that took a lot of researching and talking to mentors. So there were quite a few really hard challenges to get to the MVP, which is why it spanned about a year to get to that point. But throughout it all, we worked with other students at Brown. Then we pulled in some front-end contractors from online, like contractor sites, who were awesome. And we were just focused on being really scrappy to get it out in March of 2022. VICTORIA: That's great. And maybe it felt like a long time, but I feel like a year for a really solid MVP is pretty good, [laughs] especially when you have those safety concerns, and the quality of your data, and what you're giving out is super important. So now you've got the MVP, and I believe you just raised your round of seed funding last year. What was that process like for you? MAGGIE: Yes, so the round of funding that we did, we raised the first initial amount actually going into our senior year, and that was from a firm called Rogue Venture Partners. And we also got a little bit of it from their Women's Fund. And, yeah, that was the kind of piece of funding that got us started and allowed us to really, you know, add additional resources to the product to get it out there, at least the MVP. And then, after that, we got a little bit more funding from them. And then we raised money from Techstars as well because we got into their accelerator at The Roux Institute. That's kind of in association with Northeastern, and that was out of Portland, Maine. I guess it wasn't really necessarily, like, a cohesive round. It was, like, a couple of different checks that all kind of went into, like, our early funding for Pointz. And I would say it was very much so based on, you know, our relationship that we had with our initial venture firm that were working with Rogue. They actually mentored us for quite a few months before they invested in us. So they started mentoring us our junior year when we were in school. And then we got the deal together September of 2021. VICTORIA: That's awesome. Well, congratulations. And I'm glad you were able to find the right partnerships, and mentors, and funding that you needed. What did you find was really the differentiator for your app versus what was already on the market for biking-related apps? MAGGIE: There are a couple of different types of competitors, so there are the biking-related apps that you just mentioned, and then there are the general kind of use case apps like Google Maps or Apple Maps. And so, for the bike-related apps, the main thing that's different about Pointz is that we're more focused on, like, bike riders in general, so people that are riding around for transportation and recreation, not so much the cyclist type of a person that Trisha described earlier. So, you know, a lot of our features are geared towards people that are getting around the city or maybe are exploring a city or a neighborhood. It doesn't necessarily have to be a city, but that's kind of the focus. Whereas for other cycling-specific apps, like Komoot or Ride with GPS, it's focused a lot on, like, the fitness side of things and the recreation fitness side of riders. And so, at least the Ride with GPS and a few other of, like, the technologies that are available to more hardcore cyclists tend to have a more sharp learning curve. And ours was built more as, like, a general use case in navigating and exploring. VICTORIA: That makes sense. So it's more for people like me who are trying to go the most scenic [laughs] or the flattest and the safest way, not necessarily the fastest or the more fitness-focused aspect of cycling and biking. MAGGIE: Yeah, exactly. And, you know, we actually built this for people like us. Granted, I did do that long-distance bike trip. But, generally, I don't consider myself that hardcore of a rider, I mean, in my daily life. So it's for people who don't really identify as a cyclist and are more just, like, riding their bike around and, honestly, for people who are new to riding in general. Because a lot of our riders have recently gotten into biking or have recently moved to a new area, and so, they're just trying to figure out, you know, where are the good places to ride? Where do I feel safe? And, you know, how can I get more comfortable on my bike? VICTORIA: I'm loving this idea because I have a bike that's been sitting in my patio for over a year. [laughs] I haven't used...my partner is like, "Can we get rid of it? Because you don't use it." But I'm like, "I will. I will use it." I know my neighborhood problem is that there are giant hills if we leave our street here. So getting out is fine. But getting back in [laughs], it's like you need an electric bike. So that's very exciting. So, tell me more about now that you've graduated and you're taking this up full time; what does the future look like? What's on your horizon? MAGGIE: I mean, we've been working a lot with one of our advisors on, you know, getting to the point where people really love the product, and that's been kind of happening over the last year. We met Anuj Adhiya from Lenny's Newsletter. We've been working with him to really hone in on what the thing is that people really love about Pointz and make that experience better. And then also figure out what exactly the persona is so we can target them eventually with marketing, which is kind of the stage that we're at right now. So we were seeing our retention curves really evening out in especially a couple of cities that we're targeting. And so, this summer, we're focusing on getting our user base up in Los Angeles and then trying to figure out how, like, a playbook for scaling up a user base in a specific geography. Right now, a lot of our users are distributed throughout the United States. And there are clusters, but there's not, like, a huge spike in one city. And so, that's what we're working on right now is figuring out how to get a geographic kind of density to happen. VICTORIA: That makes sense. And it sounded like the app also uses a lot of user-generated data for safety ratings and things like that. Am I getting that accurately? TRISHA: Yep, that's correct. And what we do is we have a bunch of different layers of our data that we pull from. We have a base layer of data that comes from OpenStreetMap, and then we build on top of that. We rate all roads on a one through five bike friendliness scale. And building on top of that, we pull from city-specific data sets from cities, and towns, and municipalities. And then, we layer on the crowdsourcing similar to how Waze does at the top. VICTORIA: Got it. So taking advantage of that open data, the open city data, and what other data the city is putting out there. Are you finding that you're using whether or not a city has open data to inform if you're going to expand into that location? MAGGIE: Kind of as a focus point. So, the way it works right now is Pointz is available actually anywhere in the U.S. So; it doesn't matter if you're in a city or a rural area, you can use Pointz. And you can use it for routing and navigation and all the features that are available. However, we only have visualized the ratings in all 350 or so urban areas in the U.S., and so those are all visualized, but not all of them have the supplemental city-data. And so, the way we decide when we pull in city data is based on gaps in, like, the base layer. So, if we're seeing that there are a lot of accuracy issues in a specific city, we'll go, and we'll look and see if there's a more accurate map that the city has put out or that an advocacy group has put out. And so, we've done this recently in Chicago, Minneapolis, Portland, Oregon, just to supplement the base layer of data, and it has helped a lot in terms of accuracy. And users or our riders really like it. VICTORIA: That's great. And what is your current level of usage in the app? How well have you been adopted? MAGGIE: Are you talking in terms of, like, user numbers or just, like, our engagement levels? VICTORIA: Yeah, whatever you're using to measure your level of engagement or number of users on the app. Like, what are your stats looking like? MAGGIE: Yeah, so, we use...we have our overall signups. And then we have a subcategory of, like, active and engaged users. And so, for our overall signups, we're at just over 9,000 total signups since we launched the MVP, and we haven't marketed it at all kind of until right now, where we're trying to push it out in LA a bit more. And then, in terms of our engaged cohort, I'd have to pull up the exact number. But last I checked, it was around 1,800 monthly active users. We kind of look at that cohort, and then we break it down into, you know, who's even more engaged in that? Who's coming back every week, every day? Mid-Roll Ad: VICTORIA: Introducing thoughtbot's ongoing maintenance service. Need reliable support and maintenance for your software? Look no further. Our expert team handles upgrades, bug fixes, UI adjustments, and new feature development. And the best part? Our maintenance packages start at just 5K per month for companies of all sizes. From Ruby on Rails to Node, React, and, yes, even PHP, we've got you covered. Trust thoughtbot for top-notch support and optimized performance. To receive a custom quote, contact sales@thoughtbot.com. VICTORIA: And with me here, I have Richard Newman, who is the Development Director on our Boost Team, to talk to me a little bit more about what maintenance actually looks like once you've built your software application, right? RICHARD: Hi, Victoria. VICTORIA: Hi, Richard. You have experience building applications. I wonder if you could describe to a founder who's considering to build an application, like, what should they consider for their long-term maintenance? RICHARD: Well, like you said earlier, part of what you're going for with that long-term maintenance is making sure the health of your project, of your application, is always there. And you don't want to be surprised as you're continuing to work with your users and so forth. And so, a number of things that we pay attention to in maintenance are, we're paying attention to keeping the application secure, providing security updates. We want to make sure that the ecosystem, basically, all of the tools and third-party services that are tied to your application that, we're responding to those sorts of changes as we go along. And then part of it is, occasionally, you're going to find some smaller issues or bugs or so forth as your user group continues to grow or as needs continue to change. You want to be able to respond to those quickly as well. And so, a lot of what goes into maintenance is making sure that you're paying attention and you're ahead of those things before they surprise you. VICTORIA: Because what can happen? Like, what are the consequences if you don't do that ongoing maintenance? RICHARD: Well, the security updates those happen across gems and in the platform sort of tools that are there. And so, if you're not keeping those up to date, your exposure, your vulnerability to being hacked, or having a bad actor come into your application start growing on you if you're not doing the maintenance. The other ones that can come up is there's new interfaces that these third-party services...they may be updating their APIs. They may be updating how you're supposed to work with their tool. And so, those can occasionally break if you're not paying attention to what's going on or you're suddenly surprised by an upgrade that you have to make. And then, finally, there's this long-term sort of code change that just builds up over time if you're not keeping it refactored for the changes that are upcoming in a language or the gems that you work with. And then, suddenly, after a while, it suddenly gets to the point where you have a lot of work that you might have to do to rehabilitate the application to take on some of the newer features that are being released. And so, that makes it that much more difficult, that much more friction about being able to deliver updates for your users or to be able to respond to changes that are happening out there in your application. VICTORIA: Right. So, if you don't have that ongoing maintenance, you could run into a situation where, suddenly, you need to make a very large investment and fixing whatever is broken. RICHARD: Absolutely. It's going to be very tough to plan for if you weren't keeping up all the way along and, yes, absolutely ends up being much slower if you have to remediate it. VICTORIA: That makes sense. I wonder if you have any examples of a project you've walked into and said, "Wow, I wish we had been doing a little bit more maintenance." [laughs] And maybe you can share some details. RICHARD: Yeah. We had a fairly large application that involved a number of clinic services. So, we had an application that users were going in every day and counting on our fast response. And, over time, we've got surprised by a database upgrade that had to happen. Basically, the database was going to be changed by our third-party hosting service, and that hadn't been tested. There hadn't been procedures in place when we discovered this need. And there was a very hard date that that change had to be done or else the entire application was going to go down. And it came at a very inconvenient time, at the end of the year around Christmas, that we had to respond to all of that. And had we been in front of it and just updated it every quarter and staying current with it, it wouldn't have been nearly the lift that it turned out to be. We were facing a pretty hard deadline [laughs] there to keep things going. It was very, very stressful and disruptive for the team and potentially for the clinics. VICTORIA: Right. And it always happens around a big holiday or something like that, right? When it all comes to a head. So... [laughter] RICHARD: Absolutely. You want to be in control of the timeframe and not have the timeframe be in control of you. VICTORIA: Right. And if you have a team like thoughtbot supporting you, you can go on your vacation with a little bit more knowledge that if something breaks, there's someone there who can respond and fix things, and you don't have to interrupt your very valuable time off. So... RICHARD: [chuckles] Absolutely. VICTORIA: Yeah. Well, thank you so much, Richard, for joining me today. I appreciate you coming here to talk with us. And we'll talk to you again soon. RICHARD: Yeah, it was a pleasure. Thank you. VICTORIA: I'm wondering if you have any incentives built into the app for users who are, like, contributing data back, or maybe they're writing every single day. Are there any little challenges or achievements that you could unlock within the app right now? MAGGIE: We do have some gamification, yes. And so, the way that people can earn points on the app...we call them points with a Z because of the name. The way that they can earn those points are a couple of ways. So, one is through riding their bike and using Pointz as a navigation tool or as a tool to record their ride. And so, for that, you get one point for every mile. And then the second way is by contributing to the map, so either crowdsourcing an amenity like a bike parking that isn't on the map already or by adding information about a hazard that might be on the map, like, for example, a car parked in the bike lane. And for each of those, you know, you get one point. And so, yeah, we have that gamification system built out and a couple of...like, we have a leaderboard. And then, also, we have, like, a way for you to kind of go up in your avatar on the app. But besides that, we do monthly contests. And so, this past month, we partnered up with a company called Po Campo, which makes stylish bike bags that can be taken off your bike and then worn as, like, a purse or a handbag. And so, they sponsored the prize, which is one of their bags, and whoever kind of gave the highest quality and quantity of crowdsourcing reviews and miles ridden they're the winner of the contest for this month of June. VICTORIA: That's very cool. I love to see that and hear about what strategies people have for engaging with their users within the app. I'm curious to go back to, you know when you two first met, how did you know that you were going to be good partners to work on this project together? TRISHA: One of the ways that we knew that was because we had first been introduced to each other from our mutual friend who is a close friend of both of ours, and she had been telling the other person about each other. And it was one day where we just met up, and we really clicked. But, at that point, Maggie was looking for someone who could work on the mobile development, and I didn't have any experience with that. However, I joined a club, which Maggie was leading, which was called The Women's Entrepreneurship Group. And we got a chance to work together and plan out many events, including a large conference right before COVID hit. Like, we saw how we'd worked together. We really enjoyed it. And we had very similar aspirations and motivations towards entrepreneurship. When I had the chance to basically join what Maggie was already working on with Pointz in the summer of 2020, I knew that that was going to be a great opportunity. And we decided to become co-founders by the end of the summer. VICTORIA: That's very cool. And I know how important it is to have the right team together to work on a project like this and to start something up from scratch. So, were there other big turning points? And you mentioned COVID, so I'm curious how that affected the growth and progress of this effort. MAGGIE: Yeah, to be honest, in the heart of COVID, like 2020, we weren't really built yet. So, it didn't quite affect us a whole lot, just because the product didn't get launched until the spring of 2020 to actually, you know, kind of publicly. But there were a couple of other turning points in our company, one of them was Techstars and kind of the progress we made during Techstars. We joined the accelerator, and we were having a bit of a hard time getting tech kind of pushed out really quickly. It was taking us a long time to build the features. And so, Trisha and I kind of evaluated why that was happening. And we came up with a process that worked a lot better, which we still use today. And speaking of team, we got a couple of really awesome teammates that made a huge difference on how quickly we could turn around features and bug fixes. And so, that was a really big turning point because we were able to iterate much more quickly and get feedback from our riders a lot faster. So that happened November, December of last year, of 2022. The other big turning point, I would say, is the slider that we released in March of this past year of 2023. And so we were having a hard time retaining users and getting them to really like the routing because people who bike tend to be very opinionated. And if the route isn't exactly kind of how they wanted it, they would be upset. And so, we'd fix it for one group of users, and then we would upset another group that didn't want that, you know, added to the routing. What we ended up doing was releasing this safety slider, which has the fastest routes on the left side of the slider and then the safest or the longest routes on the right side of the slider. And that really helped people get a wide variety of routes that fit their use case. And it's helped a ton with retention. And also, the feedback we were getting from users really changed from, like, really honing in on a very specific issue with routes that they were getting to general feedback about how we could enhance the app and keep people coming back more consistently. TRISHA: I just want to emphasize again that, yeah, the team is really critical. And, like, on our team, we have really awesome people who are 10xers and just great. Also, have someone who worked at MapQuest and has...I think our combined mapping experience is around 20-plus years. So it's really awesome to have that sort of a team together. VICTORIA: Yes. And, you know, talking about it now on the podcast, in retrospect, I'm sure it all seems like it came together, and it was kismet, and everything just worked. But was that how it really felt? Or were there moments where you doubted it and thought, maybe this isn't going to come together? MAGGIE: Yeah, definitely. There were moments of that feeling. One thing that gave us a lot of confidence was getting to the point where we felt like we could really iterate quickly and release features at a consistent and predictable cadence. So that gave us confidence that you know, there is a process for this, and there's a process of gathering user feedback and rider feedback, and then translating that into features, or bug fixes, or UI fixes. I think that gave me a lot of confidence that we could solve it. But, of course, it always takes a lot longer than you expect. And our advisor, Anuj, always says that 80% of what you're going to do won't work and 20% of it will. And it's all about how quickly you can iterate and figure out what works. And sometimes you get lucky, and it happens quicker. Or maybe you have unique insight into the problem, and you can guess, and it works out quicker. But I don't know; I definitely think it's been a learning process for everyone on our team. VICTORIA: That's great advice. And now that you've got your velocity up and you have your confidence, what's on the horizon? Are there new features that you all are working on that you're excited about? TRISHA: Yeah, so we're really excited about leaning into the whole generative AI trends that are happening, especially with ChatGPT and others. One thing that we've been hearing from most of our riders, people who use Pointz, is that using the app to create routes, which will allow them to explore new places, go to a new coffee shop that they've been hoping to go to but just don't know how to actually get there is critical. And most of our riders on Pointz are people who are new to a city. Maybe they've only lived there for a max of one year or less. So, exploring the area around them is really important to them, and that's why they use Pointz. And so, leaning into that, we're going to be releasing, in the next couple of weeks, a new explore feature where someone can go and, you know, describe to Pointz what type of route or...not even route, what type of things they want to see in a city, and Pointz will come up with that. It'll learn their preferences and continue to suggest really awesome places to get to, which they can do car-free, basically, through bikes, because they can be safe and, you know, they can rely on this app to get them through the city safely. VICTORIA: That's really exciting. And I'm excited to try it out myself [laughs] once you have that feature launched. Maybe you can tell me how that feature plays into...or what your success really looks like for Pointz in the next six months. MAGGIE: Yeah, so I think that feature is something that will be, I mean, of course, we got to test it, but I think that it will help people kind of use Pointz as an exploration tool more effectively. People are already using it for that, but it's not specifically built for exploration. Right now, it's built more for, I guess, routing to, you know, new places but not specifically, like, oh, let's go on a route that takes me through all these tourist destinations in the city I'm visiting. But this new feature will allow people to use it for that more. And I think, overall, you know, our mission at Pointz is to help people feel comfortable riding bikes so that they can drive less and feel like they can get around in a sustainable fashion, rather than having to rely on their car so often. And this feature is tied to that in the sense of, like, people can use it as a tool to help them, you know, find the safe route or a route they're comfortable with, and then use it to explore an area but maybe a bit more geared towards, like, tourists or, you know, more recreational-type use cases. VICTORIA: That's very cool. Thank you so much for sharing that. And what is your biggest challenge to achieving that success? MAGGIE: I think biking is a first step in that process of helping people feel like they can be more car-light or car-free, you know, use their car less. There are obviously a ton of other factors that go into whether or not you're driving, or you're taking a bike, or you're taking public transportation. And, you know, our next steps after we have really nailed this product are to explore those opportunities and build tools that help people choose alternative transportation more often. That's what we're excited about going into the future. You know, there's a ton happening in cities all across the U.S., not only for biking but also investments in transit, infrastructure, and whatnot. So, you know, young people and people of all ages...I think a lot of people feel comfortable and that they don't want to be sitting in traffic a whole lot [laughs] because that's not fun for anyone. And, you know, traffic and congestion is always frustrating. So, as much as we can reduce that, I think that's the mission of our company. And, of course, it takes a ton of scale. But it's a big goal, but we're going after it. VICTORIA: That's great. You know, I heard about a town in the U.S. that actually had banned cars and was pedestrians only for the whole town. It's like, what a great idea. [laughs] But I love it. I love that you're working on it. And I wonder now, you know, you're a couple of years into it. If you could go back in time and give advice to yourself when you first started this project, what advice would you give yourself? MAGGIE: For me, I would say to get a minimal viable product more minimal, [chuckles] so reduce it to, like, a single feature, get it out quickly, and start getting feedback more quickly from, like, a very practical, you know, piece of advice. And then, like, an overall piece of advice would be just to be more confident earlier on. It took a long time for me to gain the confidence of, like, being a thought leader in the space. And, you know, I felt like I was young, so there were all these people that knew more than me. But I think everyone has a really unique perspective, and if you really lean into that and share that with the world, it can inspire a lot of people. And you just have to be confident enough to do that. TRISHA: Yeah, I definitely second what Maggie just said. I think also from the tech perspective, if you're someone who is maybe more inexperienced, like, I just got out of college and did this, and I have never worked a full-time job before anywhere except this. And so I think there was a lot of doubt that I had of being able to lead the technical side because I didn't have 20 years experience working somewhere. But, actually, at the end of the day, that doesn't matter. It just matters that you're able to be in touch with what it takes to build certain features and talk to the users, or your riders, or whoever because they're the ones who are going to be dictating whether this is a success or not based on what you build. It's really not good if you're building and wasting a lot of resources and time on features which nobody wants or nobody uses. And so, that's been core to why I think I've gotten a lot of confidence in being able to be, like, the tech leader in this app and in this space. VICTORIA: Yeah, I'm curious to hear more about that. You touched on this really being your first full-time job. So, how do you build your personal brand as an executive leader in this company that you're building? TRISHA: For anyone who does startups, they'll know that it's a lot of figuring it out as you go, and things that you're taught in school don't necessarily translate well to the startup world because, like, I did, like, a Bachelor of Science in Computer Science. I did operating systems. I built a whole bunch of random stuff in school, and I studied for hours and hours. Of a lot of that, the most important thing, which actually translates to working in my field, is the perseverance to, like, keep going and working really hard. Otherwise, none of that stuff which I learned honestly translates. I had to learn everything myself with regards to building mobile apps. And I think the foundations were really critical from school but not really much of the hours of studying. I don't think that that's necessary, but I think it's necessary to build that sort of perseverance mindset. VICTORIA: That makes sense sort of to reflect that back a little bit, just having the perseverance to keep pushing, and keep learning, and keep understanding what is it going to take to build the features that you want? And that's really the core of being a CTO, right? TRISHA: Exactly. Exactly. Yeah. VICTORIA: And, Maggie, I wonder about you as well, like, what resources are you drawing on to really perform as a CEO for this company? TRISHA: One thing that I read a lot is...it's more product-focused, actually, but it's product and growth-focused. It's Lenny's Newsletter, which I mentioned earlier. I use that as a resource a lot. I listen to their podcasts, and I read their articles. And then secondly, I interact a lot with other CEOs and founders because I think that's one of the best ways you can learn is from other people who are in it right now, maybe are a couple of steps ahead of you, or who have done it before. And so, I lean into that quite a bit. And just, you know, try to get advice from people, take what makes sense, and apply it to what we're working on. VICTORIA: That sounds great, yeah. I can relate to that; just building your personal network with people who are in similar roles helps you stay in touch and understand what other challenges people are facing and what you might face someday, right? [laughs] That's really cool. I love that you have all that set up. And is there anything else that you all would like to promote today? MAGGIE: I would just say to anybody who's interested in biking or maybe is, like, a beginner rider, we'd love to have you try out the app and then explore your area and give it a try one weekend when you have some time and see if you feel more confident, you know, given the routes that are on more green and protected roads. VICTORIA: I'm really excited to be talking to you because I am that person. I need this app. [laughs] I'm excited to try it out. Thank you, Maggie and Trisha, for joining us today. [laughs] It was a really great conversation, and I'm excited to follow along and see what happens with Pointz in the coming years. You can subscribe to the show and find notes along with a complete transcript for this episode at giantrobots.fm. If you have questions or comments, email us at hosts@giantrobots.fm. And you can find me on Twitter @victori_ousg. This podcast is brought to you by thoughtbot and produced and edited by Mandy Moore. Thank you for listening. See you next time. ANNOUNCER: This podcast is brought to you by thoughtbot, your expert strategy, design, development, and product management partner. We bring digital products from idea to success and teach you how because we care. Learn more at thoughtbot.com. Special Guests: Maggie Bachenberg and Trisha Ballakur.

Königs Wusterhausen mapmaker Simon Polster discusses falling into his first topo mapping project after hitchhiking from Iran to Berlin, using Soviet topographic maps as a starting point to map Armenian hiking trails, donating data to OpenStreetMap, the eternal method of “play around with it ‘til it looks okay,” completing most of his map layouts in QGIS, spending hours in the map shop inspecting good topos, and turning order fulfillment into a geography lesson for his kid. See Simon's maps at https://cartisan.org Dilijan National Park Hiking Topo Map QGIS OpenStreetMap JOSM editor Geonames Swisstopo maps Ordnance Survey maps Daniel Huffman Anita Graser Andrew Tyrell Tom Patterson Sarah Bell Klas Karlsson Need maps for your org's reports, decks, walls and events? ⁠⁠⁠⁠⁠⁠⁠⁠⁠The Map Consultancy makes real nice maps, real fast.⁠⁠⁠⁠⁠⁠⁠⁠⁠ See what good maps can do for you at themapconsultancy.com I have three words for you: Big. Glowing. Maps. Depending on how that makes you feel, you might like two more words: ⁠⁠⁠⁠⁠⁠⁠⁠⁠Radiant Maps⁠⁠⁠⁠⁠⁠⁠⁠⁠. See ultra-detailed backlit maps at radiantmaps.co Time for some map gifts: get 15% off woven map blankets and backlit map decor with code 15OFF, everything ships free – ⁠⁠https://www.etsy.com/shop/RadiantMaps?coupon=15OFF

Rapid is a free open-source web-based editor for an OpenStreetMap. In the past the focus was on conflating AI-generated datasets with OpenStreetMap data but the future for this editor is conflating authoritative datasets with OpenStreetMap.  Humans are in the loop, people reviewing data authoritative datasets and adding them to OpenStreetMap with a few clicks!  So you might be wondering, what is Authoritative data? And perhaps it doesn't even matter what authoritative means maybe the most important thing is it correct. If you are interested in OpenStreetMap you might enjoy this episode  https://mapscaping.com/podcast/openstreetmap-is-a-community-of-communities/ which is a great introduction to OpenStreetMap as a project but also explains some of the commercial interest in updating the map which adds a lot of context to Rapid and its development and future.   Humanitarian OpenStreetMap Team If you have not heard of Humanitarian OpenStreetMap Team this is well worth checking out!  https://www.hotosm.org/   Segment Anything  (SAM) can segment objects by simply clicking or interactively selecting points to include or exclude from the object. This makes it a user-friendly tool for image segmentation. https://segment-anything.com/   Mapillary Mapillary is a platform that provides street-level imagery and map data from all over the world. The platform is powered by collaboration and computer vision, which helps in generating and maintaining up-to-date, detailed maps. https://mapscaping.com/podcast/scaling-map-data-generation-using-computer-vision/   GeoSpatial Jobs! Drone Deploy's Earthworks team is looking for an experienced Back End Engineer Full time / Remote NV5 is looking for a Senior GIS Analyst https://mapscaping.com/jobs/ Want to help? I could really use some support!    

Another terrific illustration of open-source collaboration in the latest updates to gptstudio, and a comprehensive journey of web scraping in R to bring much-needed automation to a practical research problem. Episode Links This week's curator: Jon Calder (@jonmcalder (https://twitter.com/jonmcalder)) (Twitter) On updating a chat assistant app for the RStudio IDE (https://samuelenrique.com/posts/2023-06-02-updating-gptstudio/) Static and Dynamic Web Scraping with R (https://tim-tiefenbach.de/post/2023-web-scraping/) Entire issue available at rweekly.org/2023-W23 (https://rweekly.org/2023-W23.html) Supplement Resources GPT RStudio addins that enable GPT assisted coding, writing & analysis https://github.com/MichelNivard/gptstudio A Twitter and Mastodon bot posting random R packages on CRAN https://github.com/TimTeaFan/rstatspkgbot CRAN Task Views: The next generation (https://www.zeileis.org/news/ctv/) How to make fancy road trip maps with R and OpenStreetMap (https://www.andrewheiss.com/blog/2023/06/01/geocoding-routing-openstreetmap-r/): Use R to get geocoded location and routing data from OpenStreetMap and explore a 5,000 mile road trip around the USA Supporting the show Use the contact page at https://rweekly.fireside.fm/contact to send us your feedback R-Weekly Highlights on the Podcastindex.org (https://podcastindex.org/podcast/1062040) - You can send a boost into the show directly in the Podcast Index. First, top-up with Alby (https://getalby.com/), and then head over to the R-Weekly Highlights podcast entry on the index. Support creators with boostagrams using Podverse and Alby: https://blog.podverse.fm/support-creators-with-boostagrams-and-streaming-sats-using-podverse-and-alby A new way to think about value: https://value4value.info Get in touch with us on social media Eric Nantz: @theRcast (https://twitter.com/theRcast) (Twitter) and @rpodcast@podcastindex.social (https://podcastindex.social/@rpodcast) (Mastodon) Mike Thomas: @mike_ketchbrook (https://twitter.com/mike_ketchbrook) (Twitter) and @mike_thomas@fosstodon.org (https://fosstodon.org/@mike_thomas) (Mastodon)

Marc Prioleau is the newly appointed Executive Director to the Overture Maps Foundation (at the date this episode comes out). Overture was originally announced in December 2022, founded by Amazon, Meta, Microsoft and TomTom, with the goal of providing a open map data. That sounds a lot like what OpenStreetMap set out to achieve... so why start something new? Marc has some answers to that question, and it isn't his first time thinking about the future of mappingSupport the podcast on Patreon---Episode Sponsor: OpenCageUse OpenCage for your geocoding needs with their API. They have a generous Free trial you can sign up to!---About MarcLinkedInTwitterOverture Maps FoundationShownotesNote: Links to books are Amazon Affiliate links. I earn a small commission if you buy any of these books.Overture Maps FoundationSegment Anythingsegment-geospatialTackle the monkey firstBooks & Podcast recommendationsNever lost again by Bill Kilday (Affiliate Link)The Good Fight podcastTimestamps(00:00) - Introduction(01:42) - Sponsorship: OpenCage(03:22) - Conversation begins(06:10) - From Chemical Engineering to Mapping(09:00) - Early Days of GPS: Innovating despite Limitations(11:02) - Having a Long Term Vision(13:12) - Science Fiction as a Tool to Imagine the Future(14:07) - Defining the Overture Maps Foundation(17:56) - But OpenStreetMap already Exists, why make something new?(22:54) - Artist vs Merchant Analogy(27:23) - Companies already are involved in OSM(30:38) - Users don't care how their map was made(33:05) - The face of updates keeps increasing(35:22) - 10 years ago you'd be lucky to have an Estimated Time of Arrival(40:06) - Overture's value: Data or Tools?(44:32) - New tools: Example of Segment Anything(46:35) - Why a Foundation rather than a For Profit?(51:28) - Open means wider adoption(51:28) - Open means wider adoption(55:07) - Google & Apple aren't a part of Overture(59:22) - There are precedents to map "domination"(01:03:18) - Making Decisions as a Foundation(01:10:45) - How many people work at the foundation(01:13:11) - Engineering contributors(01:14:16) - Hiring engineers within the foundation?(01:17:34) - Copyright & Licensing(01:21:30) - Commonalities with Earth Observation & Satellite Images(01:28:20) - Books/podcasts(01:32:36) - Back to Science Fiction & Making Predictions(01:33:23) - Bonus question: Do you ever think about how far we've come?- Support the podcast on Patreon- Website- My Twitter- Podcast Twitter- Read Previous Issues of the Newsletter- Edited by Peter Xiong. Find more of his work

Nextcloud moves to the front of the pack with their new release, a moment to appreciate curl, and Amazon goes all in with Fedora. Special Guest: Brent Gervais.

AndrewMaus: https://www.amazon.com/Complete-Maus-Art-Spiegelman/dp/0679406417Shieldaig Kosher Whiskey: https://www.totalwine.com/spirits/scotch/blended-scotch/shieldaig-kosher-blended-malt-scotch-whisky/p/240582750Slyrs Whiskey: https://slyrs.com/en/Pop Culture Wish ListLaurenHere To Slay: https://www.unstablegames.com/collections/here-to-slayThe Crown: https://www.imdb.com/title/tt4786824/?ref_=fn_al_tt_1Andor: https://www.imdb.com/title/tt9253284/?ref_=nv_sr_srsg_0D&D One Shot: https://www.youtube.com/watch?v=4lHQpzKS8EcSantiago Calatrava: https://calatrava.com/Milwaukee Art Museum: https://mam.org/info/calatrava.phpPatrickThe Watcher: https://www.imdb.com/title/tt14852808/?ref_=nv_sr_srsg_0Pokemon Go: https://pokemongolive.com/en/Open Street Map: https://www.openstreetmap.orgYoutube Premium: https://www.youtube.com/premiumTwitch - Live Every Monday at 7pmhttps://www.twitch.tv/mof1podcast

We've gone deep to find our perfect Google Photos replacement. This week we'll share our setup that we think works great, is easy to use, and is fully backed up.