# geolocation Published articles for geolocation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chrome 144's Element: Declarative Location Access DevFeed: [Chrome 144's Element: Declarative Location Access]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2026-02-24T00:00:00Z Content type: article Language: en Sources: [Ratn Labs]() Topics: [Chrome](), [HTML](), [Web Development]() Tags: [chrome](), [declarative](), [geolocation](), [html](), [imperative](), [location](), [privacy](), [web-development]() ### AI overview This article describes Chrome 144's new HTML element for declarative, user-driven location access. It explains that the element can simplify geolocation access, improve privacy, and replace imperative navigator.geolocation calls. ### Source excerpt Learn how Chrome 144's new HTML element simplifies location access, improves privacy, and replaces imperative navigator.geolocation calls with a declarative, user-driven approach. ## "Like night and day": How Auditzy made queries 33x faster by switching from Postgres to ClickHouse DevFeed: ["Like night and day": How Auditzy made queries 33x faster by switching from Postgres to ClickHouse]() Original publisher: [Read original article]() Author: Mayank Joshi, Co-Founder and CTO, Auditzy Published: 2025-10-09T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [data-architecture](), [Latency](), [Back end](), [data](), [real-time](), [datasets](), [Amazon Web Services](), [Azure](), [browser](), [Operating system]() Tags: [architecture](), [aws](), [azure](), [backend](), [browser](), [clickhouse](), [compression](), [data](), [data-architecture](), [datasets](), [geolocation](), [golang](), [india](), [latency](), [metrics](), [performance](), [postgres](), [real-time](), [scalable-architecture](), [switching]() ### AI overview Auditzy migrated from a Postgres-based architecture to ClickHouse after query latency and ingestion problems emerged as data volumes grew. The migration delivered queries that were 33x faster and 10x better compression, supporting scalable, real-time website performance analytics. ### Source excerpt When Mumbai-based startup Auditzy hit Postgres performance limits, they switched to ClickHouse--and saw queries run 33x faster with 10x better compression. ## How to Use User Location in Applications and Assess Its Limitations DevFeed: [How to Use User Location in Applications and Assess Its Limitations]() Original publisher: [Read original article]() Author: Austin Published: 2024-07-25T14:10:28Z Content type: article Language: en Sources: [Back End - Austin Gil]() Topics: [Programming](), [App]() Tags: [app](), [back-end](), [business-logic](), [coding](), [compliance](), [development](), [edge-compute](), [front-end](), [geolocation](), [html](), [ip](), [javascript](), [js](), [location](), [location-based](), [privacy](), [programming](), [software](), [web-development]() ### AI overview This article examines location-based programming, including use cases such as regional language, currency, store locators, weather data, and geofencing. It distinguishes user-experience, application-logic, and policy or compliance concerns, then discusses four ways to obtain location: user reporting, device heuristics, IP address, and edge compute. ### Source excerpt A post discussing the nuances around location-based programming. Various ways to access user location, how they can fail, and what to do about it. ## How to use Postgres at the Edge DevFeed: [How to use Postgres at the Edge]() Original publisher: [Read original article]() Author: Paul Scanlon Published: 2023-09-19T15:33:04Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Databases](), [Next.js](), [Serverless](), [Vercel](), [WebSocket](), [API](), [SQL]() Tags: [3d](), [api](), [community](), [data](), [demo](), [geolocation](), [how-to](), [http](), [next-js](), [npm](), [postgres](), [serverless](), [sql](), [statistics](), [tcp](), [tcp-ip](), [vercel]() ### AI overview This tutorial explains how to use Neon's serverless driver with Next.js and Vercel Edge Functions to access a serverless Postgres database. It shows how HTTP and WebSockets connect Edge-based applications to Postgres through a Neon proxy, and includes a demo that records geolocation data and visualizes the request journey. ### Source excerpt In this post, I'd like to introduce Neon's serverless driver which is suitable for use with Vercel Edge Functions. I'll explain how to use it with Next.js and a free Neon serverless Postgres database Here's a demo I created. I've called it Ping Thing. What does Ping Thing do? Whe... ## Maximizing Mobile Code Reuse with Compose Multiplatform and MOKO Libraries DevFeed: [Maximizing Mobile Code Reuse with Compose Multiplatform and MOKO Libraries]() Original publisher: [Read original article]() Author: Aleksey Mikhailov Published: 2023-04-13T06:46:01Z Content type: tutorial Language: en Sources: [IceRock Development - Medium]() Topics: [compose-multiplatform](), [Mobile](), [cross-platform](), [Kotlin Multiplatform](), [Kotlin](), [Android](), [Framework](), [interfaces](), [Development](), [iOS](), [Code](), [App]() Tags: [android](), [authentication](), [biometric-authentication](), [compose-multiplatform](), [cross-platform](), [geolocation](), [interfaces](), [ios](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [mobile](), [multiplatform](), [ui](), [ui-framework]() ### AI overview This article explains how Compose Multiplatform can share Kotlin UI code across Android, iOS, Desktop, and experimental Web targets. It describes its declarative UI capabilities and limitations for non-UI mobile features, then presents MOKO Kotlin Multiplatform Mobile libraries as a way to address features such as permissions, geolocation, and biometric authentication. ### Source excerpt Mobile application development can be a complex and time-consuming process, requiring developers to write separate code for each platform they want to target. To help streamline this process, JetBrains recently released Compose Multiplatform, a UI framework that allows developers to write UI for Android, iOS (Alpha), Desktop, Web (Experimental) in Kotlin common code. While Compose Multiplatform is a powerful tool for creating cross-platform user interfaces, it has some limitations when it comes to handling non-UI mobile features like permissions, geolocation, and biometric authentication. To address these limitations, developers can turn to the MOKO libraries, a set of Kotlin Multiplatform Mobile (KMM) libraries that are designed to work seamlessly with Compose Multiplatform. What Compose Multiplatform Allows You to Do Compose Multiplatform provides a powerful UI framework that enables developers to create consistent and responsive user interfaces across multiple platforms using Kotlin common code. This means that developers can write a single codebase that can be used to create UIs for both Android and iOS platforms. With Compose Multiplatform, developers can use a declarative approach to build UI components, making it easier to create complex UIs with less code. Compose Multiplatform also provides support for animations, theming, and custom layouts, making it a versatile and flexible tool for creating cross-platform UIs. Starts from Compose Multiplatform 1.4.0 all material ui that was developer for Android now available for iOS too. What Compose Multiplatform Does Not Do While Compose Multiplatform is a powerful tool for creating cross-platform user interfaces, it has some limitations when it comes to handling non-UI mobile features like permissions, geolocation, and biometric authentication. For example, Compose Multiplatform does not handle Android configuration changes. Additionally, Compose Multiplatform does not provide built-in support for requesting runtime ## Deploy a Nuxt 3 and Turso app on Vercel DevFeed: [Deploy a Nuxt 3 and Turso app on Vercel]() Original publisher: [Read original article]() Author: James Sinkala Published: 2023-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [Nuxt.js](), [Turso](), [Vercel](), [App](), [Network]() Tags: [app](), [geolocation](), [integration](), [network](), [nuxt](), [nuxt-js](), [turso](), [vercel](), [web-development]() ### AI overview A guide to deploying a Nuxt 3 and Turso app on Vercel, using Vercel's Edge Network to display geolocation information. The supplied text notes that the post references an older version of Turso. ### Source excerpt A guide to deploying a Nuxt 3 and Turso app on Vercel while leveraging Vercel's Edge Network to display geolocation information ## Geo Queries with PostGIS in Ionic Angular DevFeed: [Geo Queries with PostGIS in Ionic Angular]() Original publisher: [Read original article]() Author: Simon Grimm Published: 2023-03-01T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Angular](), [Ionic](), [Databases](), [SQL](), [App](), [cross-platform]() Tags: [angular](), [app](), [code](), [cross-platform](), [data](), [database](), [geo-queries](), [geolocation](), [github](), [postgres](), [sql](), [storage](), [tutorial]() ### AI overview A tutorial showing how to use Supabase with the PostGIS extension in an Ionic Angular application to store and query geographic data. It covers geolocation storage, database functions for geo-queries, map markers, file uploads, and image transformations. ### Source excerpt Using the PostGIS extension to build a cross-platform application with Ionic Angular. ## Geolocation with PostgreSQL DevFeed: [Geolocation with PostgreSQL]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2018-08-24T10:11:33Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [SQL](), [Databases]() Tags: [database](), [geolocation](), [postgresql](), [query](), [sql]() ### AI overview This tutorial shows how to load geolocation data from GeoLite CSV files into PostgreSQL with pgloader, define suitable tables, and query IP address ranges. It also describes using the ip4r extension and loading indexes in parallel. ### Source excerpt We have loaded Open Street Map points of interests in the article The Most Popular Pub Names -- which compares PostgreSQL with MongoDB for simple geographical queries, and is part of our PostgreSQL Extensions article series. In today's article, look at how to geolocalize an IP address and locate the nearest pub, all within a single SQL query! For that, we are going to use the awesome ip4r extension from RhodiumToad. ## PostgreSQL FOSDEM 2014 DevFeed: [PostgreSQL FOSDEM 2014]() Original publisher: [Read original article]() Published: 2014-01-30T23:00:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Extension](), [FOSDEM]() Tags: [advanced](), [auto-completion](), [contributors](), [developers](), [extensions](), [fosdem](), [geolocation](), [indexing](), [postgresql](), [practical](), [text](), [users]() ### AI overview A talk about advanced uses of PostgreSQL extensions, including practical solutions for geolocation and text indexing for auto-completion. ### Source excerpt This talk is about Advanced Uses Cases for PostgreSQL Extensions. It shows how to use extensions to solve practical problems such as geolocation or text indexing for auto-completion.