Query a city's park locations/amenities from a public ArcGIS REST FeatureServer layer
domain: developers.arcgis.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Find the city's GIS open-data portal or ArcGIS Online item for its Parks feature layer and note its FeatureServer layer URL
Call the layer's root (…/FeatureServer/0?f=json) first to discover its actual field names and maxRecordCount, since schemas aren't standardized
Call …/FeatureServer/0/query with f=json (or f=geojson) and a where clause (e.g., 1=1) to fetch matching features
Use outFields to select only the amenity attributes you need and returnGeometry=false if you don't need shapes
Paginate with resultOffset and resultRecordCount whenever the returned feature count hits the layer's maxRecordCount
Known gotchas
Each city's service enforces its own maxRecordCount (often 1,000–2,000 features per call), so a naive single query silently truncates results for larger cities
Field names, park categories, and amenity taxonomies vary city to city with no shared standard, so code written against one city's layer usually needs rework for another
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?