Macrostrat Geology Units Scraper
Pricing
from $3.00 / 1,000 results
Macrostrat Geology Units Scraper
Scrapes geologic unit records from Macrostrat by latitude/longitude or stratigraphic name. Returns each unit as a flat row with attributes like name, age, and lithology.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Macrostrat Geology Units Scraper
Scrape geologic unit data from Macrostrat by location or stratigraphic name. Get formation names, ages, lithologies, and more for any point on Earth, up to a million units per run. No API key required. Export to CSV, JSON, Excel, or XML.
Macrostrat's geology database holds detailed records on rock units worldwide, but querying it manually is slow and hard to scale. This Actor pulls unit data directly from Macrostrat's public API, letting you collect stratigraphic information for any latitude/longitude or by formation name. Each result is returned as a flat row with consistent fields, ready for analysis or export.
| Who uses it | What they scrape Macrostrat for |
|---|---|
| Geologists | Compile regional stratigraphic columns for field mapping projects. |
| GIS analysts | Extract bedrock geology attributes for points of interest in spatial models. |
| Earth science researchers | Gather unit ages and lithologies across study areas for statistical analysis. |
| Educators | Build teaching datasets of local rock formations for classroom exercises. |
What it does
This Actor collects geologic unit records from Macrostrat by location point or stratigraphic name, returning each unit as a flat row with its attributes.
- 📍 Location query: Provide latitude and longitude to get all units in the Macrostrat column at that point.
- 🔍 Stratigraphic name lookup: Search by formation or group name (e.g., 'Mancos', 'St Peter') instead of coordinates.
- 📊 Flexible output: Export results as CSV, JSON, Excel, or XML for downstream use.
- ⚙️ Configurable limits: Set a maximum number of units to collect per run, from 1 to 1,000,000.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Macrostrat data
🗺️ Build regional stratigraphic columns.
A field geologist runs the Actor with coordinates for a mapping area to quickly assemble the local sequence of rock units for a report.
📈 Analyze unit distribution for research.
An earth science researcher collects unit ages and lithologies across multiple points to study spatial patterns in basin evolution.
🏫 Create teaching datasets.
An educator gathers all formations near a campus location to develop a lab exercise on local geology.
🛰️ Enrich GIS point data.
A GIS analyst extracts bedrock unit names and attributes for sample locations to add geologic context to a spatial database.
Why choose this scraper
| What you get | |
|---|---|
| No API key needed | Access Macrostrat's public data without registration or authentication. |
| Scalable collection | Retrieve up to a million units in a single run, limited only by your maxItems setting. |
| Consistent schema | Every unit is returned as a flat row with the same fields, simplifying data processing. |
| Two query modes | Query by location to get a full stratigraphic column, or by name to find all matching units. |
How it compares
No other Store actor targets Macrostrat the same way, so the honest comparison is with the alternatives teams actually weigh.
| Macrostrat Geology Units Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Macrostrat changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with either a latitude/longitude point or a stratigraphic name, and set a maximum number of units to collect per run. The Input tab lists every parameter.
A first run with the defaults:
{"lat": "43","lng": "-89.3","maxItems": 10}
A larger pull:
{"lat": "43","lng": "-89.3","maxItems": 200}
Pricing
Pay-per-result: $0.004 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.40 |
| 1,000 results | $4.00 |
| 10,000 results | $40.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Macrostrat Geology Units Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Macrostrat through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/macrostrat-geology-units-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that your latitude and longitude are in decimal degrees and within valid ranges (-90 to 90 for lat, -180 to 180 for lng). If using a stratigraphic name, ensure it is spelled correctly and exists in Macrostrat.
The Actor returns fewer units than expected.
The maxItems setting limits the number of units collected. Increase maxItems if you need more. Also, some locations may have fewer units in the Macrostrat column.
I get an error about invalid input.
Verify that latitude and longitude are numeric strings (e.g., '43' not '43N'). For stratigraphic name, avoid special characters unless part of the official name.
The run takes a long time.
Large maxItems values can increase runtime. Reduce maxItems or query a more specific location to speed up collection.
FAQ
| Question | Answer |
|---|---|
| Do I need an API key to use this Actor? | No. The Actor uses Macrostrat's public API endpoints, which do not require authentication. |
| Can I query by both location and stratigraphic name? | No. The Actor uses one mode at a time. If you provide a stratigraphic name, it takes precedence and the latitude/longitude are ignored. |
| What coordinate system should I use for latitude and longitude? | Use decimal degrees in the WGS84 datum. For example, 43.0 and -89.3 for Madison, Wisconsin. |
| How many units can I collect in one run? | You can set maxItems to any value from 1 to 1,000,000. The Actor will stop after reaching that number of units. |
| What data fields are returned for each unit? | Each unit includes attributes such as stratigraphic name, age, lithology, and other properties available from Macrostrat. The exact fields are shown in the sample output. |
| Can I export the results to a spreadsheet? | Yes. The Actor supports CSV, JSON, Excel, and XML output formats, which you can download from the run's dataset. |
| Is there a rate limit on Macrostrat's API? | Macrostrat's public API is generally open, but heavy usage may be throttled. The Actor handles requests sequentially to avoid overwhelming the service. |
| What if my location returns no units? | Some points, such as oceans or areas with no mapped bedrock, may return zero units. Try a nearby location or use a stratigraphic name query instead. |
Related actors
- usgs-earthquake-scraper: Use this to collect earthquake data from USGS, which complements geologic unit information for hazard analysis.
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Macrostrat. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

