First, understand the structure
A /layers response describes the layers and their fields. It does not include the records themselves. The maxRecordCount setting limits records in a single response, so it may not be the size of the dataset.
ALLEN, TEXAS / PUBLIC MAP DATA
Explore Allen.
Police districts, fire stations, streets and parks, all in one place.
Explore the public data behind your city.
↗
See what is included
in each map layer.
Loading the verified catalog…
01 / EXPLORE THE MAP
Choose what to explore
Click a place or boundary to see its details
Choose a layer from the list
Mapped features come from saved City of Allen and ArcGIS Online data.The OpenStreetMap background loads as you explore.
02 / DATA CATALOG
Browse the public data
Browse 118 services listed in the City of Allen public data directory and one linked ArcGIS Online service. MapServer and FeatureServer interfaces with the same name share a card. Empty datasets, unavailable record counts and missing map coordinates are shown separately.
03 / DATA & CONNECTIONS
Inside the data
Choose a dataset to see where it comes from, how its features are mapped and which details are stored for each record.
VERIFIED CONNECTIONS
How the public maps fit together
These connections are documented in the public app and Web Map configurations. They show which data sources the maps use. They do not establish connections to police dispatch or records systems (CAD/RMS).
POSSIBLE DATA CONNECTIONS
Addresses ↔ streets ↔ districts
Matching field names and types suggest possible ways to connect datasets. The actual values, uniqueness of the keys and completeness of the matches have not been checked.
Address_Points.ExternalStreetKeyString(36) · possible matchRoads.ExternalStreetKeyAddress_Points.RoutingStreetExtKeyString(36) · possible matchRoads.RoutingStreetExtKeyRoads.Left/RightPoliceExternalKeyString(30) → String(5) · mapping neededPolice_Response_Districts.Code04 / ABOUT THE DATA
What we checked
Then, check the record count
A separate request, /query?where=1%3D1&returnCountOnly=true, asks the source for its total number of records. If that request fails, the total stays unknown.
Finally, place it on the map
Coordinates were downloaded separately in WGS84, a standard latitude and longitude system. Each saved dataset is marked complete or partial. A partial dataset is not an evenly distributed sample of the city.
A small dataset can cover a whole city
A single record can describe a boundary with thousands of coordinates. A short list of districts or stations may still be the full published dataset.
The police district layer shows area boundaries. A crime map would need separate incident records with dates, types and locations. Fire districts and station locations alone do not tell us response times.
Why there is no single citywide total
Combined maps, historical layers and individual services can repeat the same addresses, streets and parcels. Adding all their record counts would count some places more than once.
What the labels mean
- Complete
- The number of downloaded records matched the source count when collected.
- Partial
- Only a limited sequence of records was downloaded. The source total is shown separately when available.
- Empty
- The source returned a record count of zero.
- Unknown
- The record count was unavailable. Group layers do not have a count of their own.
When the data was collected
The snapshot date shows when the source was checked. Metadata dates, app modification dates and layer edit dates describe different things. None guarantees that every record is up to date.
COVERAGE
Explore the coverage by topic
Sources and downloads
City of Allen · REST directory ↗Esri · Query documentation ↗Catalog, record counts and fields · JSON ↓Request log · JSON ↓
Layer details link to the original source, record-count request, field list and saved GeoJSON where available. Downloads contain selected attributes. Customer and property-owner details are not included in the map snapshots.