Map My Lot

Find your property boundary from any street address

1 follower

Find your property boundary from any street address

1 follower

MapMyLot shows property boundaries, lot size and perimeter from a plain street address - no lot number, no account needed. Free tier: 5 lookups/day. Covers Australia, New Zealand, British Columbia and England & Wales from official cadastral data.

Free Options

Launch tags:Web App•SaaS•Maps

Launch Team

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Promoted

Maker

📌

Hi Product Hunt! I'm the founder of MapMyLot - a property boundary viewer I built because I kept hitting the same wall: government portals require a lot-on-plan number, which almost no one knows off the top of their head. MapMyLot lets you type a street address and see the boundary polygon, lot size (m2 / ha), and perimeter in seconds - on your phone. No account needed for the first 5 lookups per day. The product covers 10 jurisdictions across Australia (QLD, NSW, VIC, TAS, ACT), New Zealand, British Columbia, Manitoba, New Brunswick, and England & Wales. The data comes from official government cadastral sources in each jurisdiction. Would love feedback from the PH community - especially from anyone in property, real estate, or land development. What else would you want to see?

Report

1mo ago

Maker

How it's built:

The core challenge was processing government spatial data across 10 very different formats into a single PostGIS database:
- NZ: WFS API (LINZ), EPSG:4326 natively, 4.26M parcels
- AU states: Shapefiles, GDA94 (EPSG:4283), 8M+ parcels across QLD/NSW/VIC
- BC: Shapefiles, EPSG:3005 (BC Albers), 2.48M parcels
- England & Wales: GML format from 5,800 zip files, EPSG:27700 (British National Grid)

For the large AU + BC datasets I had to stream the GeoJSON using `ijson` to avoid OOM (2.4M features = OOM with json.load). The UK GML data required specifying `-s_srs EPSG:27700` in ogr2ogr explicitly or the coordinates came out wrong.

Tiles are served as PMTiles on Cloudflare R2 (zero egress cost vs S3). The parcel lookup at query time is a PostGIS point-in-polygon using a GiST index - fast enough for a synchronous API response.

Stack: FastAPI + PostGIS + MapLibre GL JS. Auth via Clerk. Billing via Stripe. PDF export via WeasyPrint. Running on Contabo Singapore (90ms to Sydney).

Repo is private for now but happy to answer questions about any part of the ETL or serving stack.

Report

1mo ago

Reviews

Most Informative

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Promoted

Maker

📌

Report

1mo ago

Maker

How it's built:

The core challenge was processing government spatial data across 10 very different formats into a single PostGIS database:
- NZ: WFS API (LINZ), EPSG:4326 natively, 4.26M parcels
- AU states: Shapefiles, GDA94 (EPSG:4283), 8M+ parcels across QLD/NSW/VIC
- BC: Shapefiles, EPSG:3005 (BC Albers), 2.48M parcels
- England & Wales: GML format from 5,800 zip files, EPSG:27700 (British National Grid)

For the large AU + BC datasets I had to stream the GeoJSON using `ijson` to avoid OOM (2.4M features = OOM with json.load). The UK GML data required specifying `-s_srs EPSG:27700` in ogr2ogr explicitly or the coordinates came out wrong.

Tiles are served as PMTiles on Cloudflare R2 (zero egress cost vs S3). The parcel lookup at query time is a PostGIS point-in-polygon using a GiST index - fast enough for a synchronous API response.

Stack: FastAPI + PostGIS + MapLibre GL JS. Auth via Clerk. Billing via Stripe. PDF export via WeasyPrint. Running on Contabo Singapore (90ms to Sydney).

Repo is private for now but happy to answer questions about any part of the ETL or serving stack.

Report

1mo ago