Open Catchment Accessibility Analyzer avatar
Open Catchment Accessibility Analyzer
Under maintenance

Pricing

from $0.01 / 1,000 results

Go to Apify Store
Open Catchment Accessibility Analyzer

Open Catchment Accessibility Analyzer

Under maintenance

Analyze service coverage and accessibility around any location using OpenStreetMap. Generate distance-based catchment metrics and export results as Dataset, CSV, XLSX, and summary JSON for planning and site selection.

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

Artashes Arakelyan

Artashes Arakelyan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 days ago

Last modified

Share

Open Catchment & Accessibility Analyzer

Analyze service coverage and accessibility around any location using OpenStreetMap (OSM) data. This Actor computes distance-based catchment metrics (e.g. 300 m, 500 m, 1 km) and exports results as:

📊 Apify Dataset (interactive)

📁 CSV

📘 Excel (XLSX)

🧾 Summary JSON

Designed for urban planning, site selection, retail analysis, and accessibility studies.

🚀 Key Features

📍 Analyze accessibility around any point or address

📏 Distance-based catchments (buffers in meters)

🏪 Multiple service categories (businesses, retail, food, transport, etc.)

🗺️ Powered by OpenStreetMap Overpass API

📤 Clean exports: Dataset + CSV + XLSX + summary JSON

⚙️ Preset-based workflows for common use cases

🧠 Typical Use Cases

Business / retail site selection

Service gap analysis (where services are missing)

Urban accessibility studies

Transport & walkability analysis

Preliminary spatial analysis without GIS software

▶️ How It Works

You provide one or more anchors (latitude / longitude)

You define catchment radii (e.g. 300 m, 500 m, 1000 m)

You select service categories

The Actor:

Fetches POIs from OpenStreetMap

Counts services within each radius

Generates structured outputs

🧪 Example Input (Austin, TX – ZIP 78753)

⚠️ Note: Some fields expect JSON arrays encoded as strings, as indicated in the input form.

{ "presetId": "business_placement", "studyName": "Austin TX 78753 – Catchment Demo", "anchors": "[{"id":"austin_78753","name":"Austin TX 78753","lat":30.38353,"lon":-97.67335,"type":"zip_center"}]", "radiiMeters": "[300,500,1000,3000]", "serviceCategories": "["businesses","pharmacy","post_office","public_transport_stop"]", "outputFormats": "["dataset","csv","xlsx","summaryJson"]", "outputMode": "summary", "includeGeometries": true, "servicesSource": "overpass", "maxResultsPerCategory": 2000 }

⚙️ Input Parameters anchors (required, stringified JSON array)

List of points to analyze.

[ { "id": "site_1", "name": "My location", "lat": 40.18, "lon": 44.51 } ]

radiiMeters (stringified JSON array)

Catchment distances in meters.

[300, 500, 1000]

serviceCategories

OSM-based service groups, e.g.:

businesses

business_retail

business_food

business_services

pharmacy

post_office

public_transport_stop

outputFormats

Any combination of:

dataset

csv

xlsx

summaryJson

📤 Outputs 📊 Dataset

Each row represents:

Anchor × radius × service category

Typical fields:

study_name

anchor_name

radius_m

service_category

services_count

coverage_adequate

📁 Key-Value Store Files File Description catchment_metrics.csv Tabular metrics catchment_metrics.xlsx Excel version summary.json High-level summary INPUT Stored input for reproducibility 🌍 Data Source

OpenStreetMap (OSM) via Overpass API

Data quality depends on OSM community coverage in each region

⚠️ Notes & Limitations

This Actor performs distance-based (Euclidean) analysis

Network-based travel time analysis is not included (yet)

Population metrics are placeholders (future extension)

🧩 Roadmap Ideas

Travel-time catchments (walk / drive)

Population-weighted accessibility

Custom POI uploads (user-provided GeoJSON)

More business-specific presets

📬 Support & Feedback

If you have ideas, feature requests, or encounter issues, feel free to contact the author via Apify.

📜 License & Compliance

Uses open data from OpenStreetMap

Does not scrape restricted websites

Fully compliant with Apify Store rules

✅ You are now Store-ready

Next steps (optional):

Improve input UX (arrays instead of stringified JSON)

Add monetization

Use this Actor as a template for future spatial tools