ArcGIS Export with Completeness Audit

Export records from a public ArcGIS FeatureServer or MapServer layer, and check the delivered IDs against the IDs reported by the source. Get a dataset plus a separate coverage report so a capped or incomplete export is visible before you use it in a pipeline.

Useful for GIS analysts and developers who need repeatable exports of public infrastructure, boundary, asset or planning layers. This tool does not supply a proprietary database; you choose the source and remain responsible for its access and reuse permissions.

Quick start

1. Paste a public HTTPS layer URL ending in FeatureServer/<number> or MapServer/<number>.
2. Optionally choose a WHERE filter, fields and record cap.
3. Run, then open the dataset and EXPORT-REPORT in the run's storage.

An example using Esri's public sample service:

{
  "url": "https://sampleserver6.arcgisonline.com/arcgis/rest/services/USA/MapServer/2",
  "where": "1=1",
  "outFields": "objectid,state_name",
  "maxRecords": 100,
  "batchSize": 20
}

What you receive

Each dataset row contains attributes (the source fields), geometry (ArcGIS JSON, or null) and export (source URL and ID-enumeration time). These are separate objects so source field names are preserved. Integers beyond JavaScript's exact numeric range are represented as decimal strings. Geometry is not converted to GeoJSON or reprojected.

Use JSON to retain nested geometry and exact string IDs. Apify also offers CSV and spreadsheet exports; flatten the attributes fields you need, and check your spreadsheet's numeric import settings.

The coverage report includes expected, selected and delivered counts; missing, duplicate and unexpected IDs; request counts; limits; and these completion flags:

Flag	Meaning
selectionComplete	All selected source IDs were retrieved, with no unexpected IDs.
deliveryComplete	All selected rows were acknowledged as delivered to the dataset.
complete	The entire enumerated matching ID set was delivered without duplicate-ID warnings.
truncated	The matching source contains more records than the selected cap.

Records are selected in ascending object-ID order. Missing IDs are retried once. Duplicate rows are deduplicated and reported. If selected source coverage cannot be verified, the run fails before any feature charges. If delivery later fails, partial rows can exist; consult the report and run status. The tool does not claim that a changing service is an atomic snapshot.

Pricing

The intended launch price is $0.02 per run start plus $0.001 per delivered feature ($1 per 1,000 features). The pricing panel in Apify is authoritative. A 1,000-feature run is $1.02 at these rates, before applicable taxes. The start charge applies even if a run returns no records or fails. Set a spending limit before running. A limit can reduce the selected count or stop delivery; inspect the report.

No proxy subscription, external API key or language-model account is needed.

Scope and limits

• Public HTTPS on port 443 only. No authentication tokens, redirects, private-network destinations or IPv6-only hosts.
• At most 10,000 selected records and 200,000 enumerated source IDs.
• At most 100 source requests, 15 seconds per request and 120 seconds of extraction time.
• At most 8 MiB per response and 20 MiB of total source responses. Large geometries may reach these limits; use a smaller filter.
• No attachments, historical snapshots, incremental monitoring, joins, related tables or completeness claims about records the source omits from its ID response.

The source must support ArcGIS layer queries and object IDs. Some services reject batch requests or change while a run is in progress. A failed run is visible and should not be treated as a complete export.

For support, open an issue on this Actor with the run ID and a public example URL. Do not include access tokens or private records.