The package retrieves public ArcGIS data; it does not host or archive the records. This dashboard describes the selective checked catalog bundled with this package. It never represents a complete inventory of any publisher’s datasets.
The checked catalog lists layers curated for direct use by ID. A successful health check means one layer’s endpoint and metadata passed a recent check; it does not establish that its records are fresh or that a full download will succeed. Live discovery searches publisher portals for additional items when you call it. Portal indexing, service availability, and search limits affect those results, so neither this dashboard nor live discovery measures complete publisher coverage.
No matching health report was available for this build. All current health statuses are unverified; dated catalog checks remain visible below.
| Publisher | Checked entries | Last verification | Healthy | Problematic | Unverified |
|---|---|---|---|---|---|
| City of Clearwater | 6 | catalog check | 0 | 0 | 6 |
| City of St. Petersburg | 7 | catalog check | 0 | 0 | 7 |
| City of Tampa | 20 | catalog check | 0 | 0 | 20 |
| Hillsborough County | 8 | catalog check | 0 | 0 | 8 |
| Pinellas County | 7 | catalog check | 0 | 0 | 7 |
| Tampa Bay Regional Planning Council | 4 | catalog check | 0 | 0 | 4 |
| Dataset | Publisher | Category | ArcGIS endpoint | Last verification | Status | Known issues or limits |
|---|---|---|---|---|---|---|
| Permits (active GIS view) | City of Tampa | Development | https://arcgis.tampagov.net/arcgis/rest/services/Planning/PermitsAll/FeatureServer/0 | catalog check | Unverified |
Read notesThe upstream service is described as data for an internal active-permits viewer, although its public Query endpoint is accessible without a token. The date fields are LASTUPDATE and CREATEDDATE; no permit issue-date field is advertised. No explicit dataset license was found on this exact FeatureServer service or in the selected public ArcGIS organization catalog. Do not infer the license of a separate MapServer layer. |
| Active development coordination cases | City of Tampa | Development | https://arcgis.tampagov.net/arcgis/rest/services/Planning/ActiveEntitlementLocations/FeatureServer/0 | catalog check | Unverified |
Read notesThis is an active application view, not a historical ledger of all development cases. TENTATIVEHEARING and TENTATIVETIME are strings, despite their date-like names. No explicit dataset license was found on this exact FeatureServer service or in the selected public ArcGIS organization catalog. Do not infer the license of a separate MapServer layer. |
| Capital improvement projects | City of Tampa | Infrastructure | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/CapitalProjects/MapServer/0 | catalog check | Unverified |
Read notesThe service description says its definition query selects Show to Public = Yes, while the layer metadata does not expose that definition expression. Coordinates use ArcGIS WKID 103023 / latestWKID 6443, in feet, rather than the Web Mercator CRS used by the other selected layers. |
| Tampa boundary (shoreline representation) | City of Tampa | Boundaries | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Boundary/MapServer/6 | catalog check | Unverified |
Read notesThis is a shoreline-modified representation; it must not be labeled the legal incorporated boundary or used as a survey. |
| Neighborhood association boundaries | City of Tampa | Boundaries | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Boundary/MapServer/5 | catalog check | Unverified |
Read notesNeighborhood association boundaries are not an assertion that every Tampa location belongs to a named neighborhood. Public source fields include association contact details; values are passed through without enrichment. |
| City council districts | City of Tampa | Boundaries | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Boundary/MapServer/0 | catalog check | Unverified |
Read notesPolygons represent the four geographic City Council districts (4–7). Districts 1–3 are elected at large citywide and appear only as attributes, not separate district polygons. Representative names may change between GIS updates; consult the City for current representation and official boundaries. |
| Tampa Riverwalk segments | City of Tampa | Infrastructure | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Planning/MapServer/4 | catalog check | Unverified |
Read notesStatus reflects the current upstream GIS representation; catalog item modification time is not a statement of feature freshness. |
| Park polygons | City of Tampa | Recreation | https://arcgis.tampagov.net/arcgis/rest/services/Parks/ParksPolygons/MapServer/0 | catalog check | Unverified |
Read notesThe source includes OWNER, OWNERTYPE, and PUBLIC_ attributes; publisher City of Tampa does not imply every mapped park is City-owned. |
| City of Tampa fire stations | City of Tampa | Public safety | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Fire/MapServer/10 | catalog check | Unverified |
Read notesThe Fire service base layer maps station locations; it does not establish current operational status, incidents, or response coverage. It has unqualified field names and omits the GovServiceInfo attributes previously exposed by the joined Location layer. Existing requests using GIS.FacilitySitePoint.* or GIS.GovServiceInfo.* fields must be updated. |
| Bicycle network segments | City of Tampa | Transportation | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Transportation/MapServer/0 | catalog check | Unverified |
Read notesCONN_TYPE includes shared roadways, paths, trails, and other connections; not every segment is a dedicated bike lane. The item modification date does not establish feature freshness. |
| Recycling pickup service areas | City of Tampa | Solid waste | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/SolidWaste/MapServer/3 | catalog check | Unverified |
Read notesThese are GIS schedule service areas, not an address-level guarantee of a current pickup day. Confirm operational collection information with the City. |
| Community redevelopment areas | City of Tampa | Planning | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Planning/MapServer/0 | catalog check | Unverified |
Read notesThese are GIS representations of community redevelopment areas. Confirm operative boundaries and ordinances with the City; the catalog item modification date is not a feature update date. |
| High Injury Network road segments | City of Tampa | Transportation | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Transportation/MapServer/10 | catalog check | Unverified |
Read notesThis is a source-defined safety screening network, not a complete crash record or a live prediction of roadway risk. FATAL, INCAP, KSI, and HINYEAR are source attributes; consult the City for methodology before comparing segments or years. |
| Local historic districts | City of Tampa | Planning | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Planning/MapServer/1 | catalog check | Unverified |
Read notesThis is a local historic district layer, not a national designation inventory. Confirm current designation, boundaries, and applicable rules with the City. |
| Local historic landmarks | City of Tampa | Planning | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Planning/MapServer/29 | catalog check | Unverified |
Read notesORD_DATE is a string in the source schema, despite its date-like name; LASTUPDATE is the advertised date field. Points do not establish the full extent of designated properties; confirm legal designations with the City. |
| Police districts | City of Tampa | Public safety | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/LawEnforcement/MapServer/1 | catalog check | Unverified |
Read notesThese are GIS district boundaries, not station locations, incident data, or a guarantee of current response coverage. |
| Street speed limit reductions | City of Tampa | Transportation | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Transportation/MapServer/4 | catalog check | Unverified |
Read notesSPEEDLIMIT, REDUCEDSPEED, PROPSPEED, and SPEEDLIMITSTATUS are source strings; DATEREDUCED is a date field. Confirm current legally posted limits from City signage or records before operational use. |
| Truck routes | City of Tampa | Transportation | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Transportation/MapServer/5 | catalog check | Unverified |
Read notesThis GIS route layer does not establish current signage, vehicle-specific restrictions, or permit requirements. Check City rules for operational routing. |
| Tampa water service area | City of Tampa | Utilities | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/UtilityWater/MapServer/1 | catalog check | Unverified |
Read notesThe water service area may extend beyond incorporated City limits; it is not a city-boundary layer or address-specific proof of service. The item says no data update is planned while its feed is refreshed daily, so refresh frequency does not establish geometry freshness. Coordinates use ArcGIS WKID 102659 / latestWKID 2237, in feet. |
| Zoning districts | City of Tampa | Planning | https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Planning/MapServer/28 | catalog check | Unverified |
Read notesThis GIS layer is a planning reference, not an official legal determination of parcel zoning or permitted use. Confirm current zoning and ordinances with the City; the catalog item modification date does not establish feature freshness. |
| St. Petersburg parks | City of St. Petersburg | Recreation | https://services2.arcgis.com/9qPLjNtocjo438CJ/arcgis/rest/services/Parks_view/FeatureServer/0 | catalog check | Unverified |
Read notesPark polygons are GIS reference data, not a guarantee of facilities, opening hours, public access, or legal property boundaries. |
| St. Petersburg city boundary | City of St. Petersburg | Boundaries | https://services2.arcgis.com/9qPLjNtocjo438CJ/arcgis/rest/services/CityLimits_view/FeatureServer/0 | catalog check | Unverified |
Read notesThis GIS municipal boundary is a geographic reference rather than an official legal determination of jurisdiction for a particular property. |
| St. Petersburg streets | City of St. Petersburg | Transportation | https://services2.arcgis.com/9qPLjNtocjo438CJ/arcgis/rest/services/Streets_view/FeatureServer/0 | catalog check | Unverified |
Read notesStreet attributes are source GIS values; they do not establish current posted speed limits, closures, vehicle restrictions, or safe routing. |
| Clearwater park buffers | City of Clearwater | Recreation | https://gis.myclearwater.com/arcgis/rest/services/ArcGISMapServices/Clearwater_Park_Buffers/MapServer/0 | catalog check | Unverified |
Read notesThese are park buffers rather than park property boundaries. Source buffer distances and acreage require the service metadata for their interpretation. |
| Clearwater zoning | City of Clearwater | Planning | https://gis.myclearwater.com/arcgis/rest/services/ArcGISMapServices/Zoning_WGS84/MapServer/0 | catalog check | Unverified |
Read notesThis GIS zoning layer is a planning reference. Confirm current zoning and permitted uses with the City; the service response uses Web Mercator rather than its stored source CRS. |
| Clearwater libraries | City of Clearwater | Public facilities | https://gis.myclearwater.com/arcgis/rest/services/ArcGISMapServices/ClearwaterServicesApp_WGS84/MapServer/1 | catalog check | Unverified |
Read notesLibrary points are facility locations, not a guarantee of opening hours or currently available services. The response uses Web Mercator; the stored source CRS is different. |
| Hillsborough County libraries | Hillsborough County | Public facilities | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/Libraries_hc/FeatureServer/0 | catalog check | Unverified |
Read notesThese are reference locations for cooperative libraries; consult the library system for current hours and services. The item includes Plant City and Temple Terrace partners. |
| Hillsborough County sidewalks | Hillsborough County | Transportation | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/Sidewalks/FeatureServer/0 | catalog check | Unverified |
Read notesThe source compiled centerlines from aerial photography and multiple edits at varying scales and accuracies. These GIS assets do not establish current access, accessibility compliance, or safe routing. |
| Hillsborough County parks and recreation properties | Hillsborough County | Recreation | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/Parks_and_Recreation/FeatureServer/0 | catalog check | Unverified |
Read notesThese are managed property polygons, not legal boundaries or a guarantee of public access or operating hours. The publisher says updates occur as property status changes. |
| Pinellas County fire stations | Pinellas County | Public safety | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_PSSFireStation_view/FeatureServer/0 | catalog check | Unverified |
Read notesThe county describes station locations and attributes. Operational status is a source attribute, not a guarantee of current response availability. Public fields include contact information, which retrieval passes through without enrichment. |
| Pinellas County park boundaries | Pinellas County | Recreation | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_ParkBoundaries_view/FeatureServer/0 | catalog check | Unverified |
Read notesThe county says these boundaries are primarily parcel based and sometimes extend through rights-of-way. They are planning and visual reference data, not survey-precision property boundaries or a guarantee of public access. |
| Pinellas Trail segments | Pinellas County | Recreation | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_PinellasTrail_view/FeatureServer/0 | catalog check | Unverified |
Read notesThis is a county parks asset layer; its condition and lifecycle fields should not be read as current trail openings, safety advice, or survey-precision rights-of-way. |
| Developments of regional impact | Tampa Bay Regional Planning Council | Development | https://services3.arcgis.com/RgIBbQIF0Y6T3AX6/arcgis/rest/services/Developments_of_Regional_Impact/FeatureServer/0 | catalog check | Unverified |
Read notesThis is a DRI planning boundary snapshot whose ArcGIS item was last modified in March 2023. It is not a current inventory of all development applications or a legal parcel boundary. Confirm project status, scale, and accuracy with the Council and local reviewing agencies. |
| Regional storm-surge zones (historical model) | Tampa Bay Regional Planning Council | Hazards | https://services3.arcgis.com/RgIBbQIF0Y6T3AX6/arcgis/rest/services/region_storm_surge_zones/FeatureServer/0 | catalog check | Unverified |
Read notesHistorical SLOSH maximum-of-maximums planning product. The layer description says it was clipped against a 2004 shoreline, and its ArcGIS item was last modified in November 2021. These polygons are not a current forecast, an evacuation order, or current emergency guidance. Use current official county and emergency-management sources for decisions. The native CRS is FDEP Albers HARN supplied as WKT only; request out_sr = 4326 for a standard output CRS. |
| Tampa Bay region data centers | Tampa Bay Regional Planning Council | Infrastructure | https://services3.arcgis.com/RgIBbQIF0Y6T3AX6/arcgis/rest/services/Tampa_Bay_Region_Data_Centers/FeatureServer/0 | catalog check | Unverified |
Read notesResearch inventory based on websites, Google Maps, Gemini comparison, visual checks, property information, and news reports for planned sites, as described by the Council. Locations, operational status, and estimated size require independent confirmation; this is not a comprehensive or authoritative facility register. |
| St. Petersburg zoning districts | City of St. Petersburg | Planning | https://services2.arcgis.com/9qPLjNtocjo438CJ/ArcGIS/rest/services/ZoningDistricts_view/FeatureServer/0 | catalog check | Unverified |
Read notesPlanning reference only: confirm current permitted uses and legal zoning with the City. This public view has no record-date field. |
| St. Petersburg future land use | City of St. Petersburg | Planning | https://services2.arcgis.com/9qPLjNtocjo438CJ/ArcGIS/rest/services/FutureLandUse_view/FeatureServer/0 | catalog check | Unverified |
Read notesA plan classification, distinct from current zoning or a parcel-level legal determination. The public view has no record-date field. |
| St. Petersburg sidewalks | City of St. Petersburg | Transportation | https://services2.arcgis.com/9qPLjNtocjo438CJ/ArcGIS/rest/services/Sidewalks_view/FeatureServer/0 | catalog check | Unverified |
Read notesAn inventory of mapped segments, not a guarantee of present condition, ADA accessibility, or route safety. Ownership and maintenance codes require the source domains. |
| St. Petersburg mapped public works projects | City of St. Petersburg | Infrastructure | https://services2.arcgis.com/9qPLjNtocjo438CJ/ArcGIS/rest/services/PWAProjectTracking/FeatureServer/0 | catalog check | Unverified |
Read notesOnly spatially mapped projects are included. The publisher identifies a separate PWACitywideProjectTracking table needed for a complete citywide portfolio. Status, scope, budget, and timelines may change; confirm with the managing department. |
| Clearwater future land use | City of Clearwater | Planning | https://gis.myclearwater.com/arcgis/rest/services/ArcGISMapServices/FLU_w_PPC_Colors_WGS84/MapServer/0 | catalog check | Unverified |
Read notesUse as a planning reference, not a legal parcel determination or current zoning. The portal item was last modified in 2016, which does not establish the feature update date. |
| Clearwater vulnerability-assessment critical assets | City of Clearwater | Hazards | https://services1.arcgis.com/3GsNorcb0Mn5rMt8/arcgis/rest/services/Vulnerability_Assessment/FeatureServer/11 | catalog check | Unverified |
Read notesThis service contains 406 asset polygons and is not the full City assessment or a complete infrastructure inventory. Scenario codes require the City's methodology. It is not live hazard or emergency guidance. |
| Clearwater sidewalks | City of Clearwater | Transportation | https://gis.myclearwater.com/arcgis/rest/services/PublicWorksServices/PW_Sup_Sidewalks_NAD83/MapServer/0 | catalog check | Unverified |
Read notesThe layer description reports 2011 field collection and aerial verification and says the City maintains the data. Present completeness, condition, and ADA accessibility are not guaranteed. |
| Pinellas countywide plan map categories | Pinellas County | Planning | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_Countywide_Plan_Map_Categories_view/FeatureServer/0 | catalog check | Unverified |
Read notesCountywide plan categories support regional analysis but are not parcel zoning or a legal survey. The hosted view may change as Forward Pinellas updates its plan. |
| Pinellas bicycle facilities | Pinellas County | Transportation | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_BicycleFacilities_view/FeatureServer/0 | catalog check | Unverified |
Read notesFacility classes vary and mapped segments do not establish current safety or continuity. This inventory complements, rather than duplicates, the Pinellas Trail layer. |
| Pinellas sidewalks | Pinellas County | Transportation | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_Sidewalk_view/FeatureServer/0 | catalog check | Unverified |
Read notesMapped inventory and source attributes are for planning; accessibility and condition classifications do not guarantee current on-the-ground conditions. |
| Pinellas assisted housing | Pinellas County | Housing | https://services.arcgis.com/f5HgUpxURgEzTccH/ArcGIS/rest/services/Pinellas_AssistedHousing_view/FeatureServer/0 | catalog check | Unverified |
Read notesProgram participation, assisted-unit counts, and subsidy expiration may change. This layer does not establish current eligibility, availability, or a complete affordable-housing inventory. |
| Hillsborough HART bus routes | Hillsborough County | Transportation | https://services.arcgis.com/apTfC6SUmnNfnxuF/ArcGIS/rest/services/HART_Bus_Stops_and_Routes/FeatureServer/21 | catalog check | Unverified |
Read notesThe item identifies a March 2025 HART source even though the hosted layer was edited later. Use for route-planning research, not live schedules, stops, or navigation. |
| Hillsborough FEMA flood hazard zones | Hillsborough County | Hazards | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/FloodZone_FEMA/FeatureServer/0 | catalog check | Unverified |
Read notesThe item identifies a latest Letter of Map Revision effective September 28, 2026. A GIS copy is for planning only; use FEMA and County official records for property or legal determinations and current emergency guidance. |
| Hillsborough unincorporated zoning | Hillsborough County | Planning | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/Zoning/FeatureServer/0 | catalog check | Unverified |
Read notesUnincorporated county coverage only; municipal zoning is separate. GIS may lag approved zoning-atlas changes, and cross-government zoning labels have different meanings. |
| Hillsborough EPC water-quality observations | Hillsborough County | Environment | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/EPC_WQM_DATA/FeatureServer/0 | catalog check | Unverified |
Read notesThe Environmental Protection Commission's item describes the latest staff-reviewed samples at monitoring stations, not the complete sample history. Methods, units, detection limits, and site coverage require source review. |
| Hillsborough 2023 land use and land cover | Hillsborough County | Environment | https://services.arcgis.com/apTfC6SUmnNfnxuF/arcgis/rest/services/LandUseLandCover_SWFWMD2023/FeatureServer/64 | catalog check | Unverified |
Read notesA 2023 SWFWMD classification snapshot downloaded by the County in 2025. It is observed land cover, not adopted future land use, zoning, or a current-condition guarantee. |
| TBRPC six-county regional boundary | Tampa Bay Regional Planning Council | Boundaries | https://services3.arcgis.com/RgIBbQIF0Y6T3AX6/arcgis/rest/services/tbrpc_regional_boundary/FeatureServer/0 | catalog check | Unverified |
Read notesDerived from 2022 Census boundaries and suitable as a regional analysis frame. It is not a legal boundary survey or current parcel boundary. |
Counts and publisher names come directly from the bundled checked
catalog at site build time. This page uses the latest usable health
report when one is supplied to the build. A report row must match the
current catalog publisher, jurisdiction, dataset ID, and ArcGIS
endpoint. A result is healthy or
problematic only when it is no older than 30 days and
no older than the catalog’s dated check. Recent
unavailable, schema_changed, and
unsupported results count as problematic.
unknown, older, mismatched, and absent results are
unverified. A timeout alone remains inconclusive. The
last verification column labels catalog checks separately from health
reports; catalog dates never imply a recent successful health check.
Some publisher datasets have not been curated into the checked catalog. Publisher portals and services may be only partly represented, and discovery can miss unindexed or unavailable items. The dashboard counts layers without a saved schema baseline; those layers cannot receive a field and geometry comparison until a baseline is curated. Health checks read layer metadata and do not run record count or object-ID queries. Each dataset’s notes include its curated scope limits and relevant recent failure diagnostics. The catalog policy records selection criteria; the discovery article explains live search limits.
Tampa’s permits and development cases are active views, not complete
historical ledgers. Its city-boundary follows a shoreline
representation, not a legal survey, and water-service-area
extends beyond city limits. Clearwater’s park buffers are not park
footprints; its critical-assets layer locates assets, not hazards. The
Pinellas housing layer is a program inventory, not all housing.
Hillsborough transit routes are not a live schedule. The regional
planning council’s storm surge layer is a historical planning model, not
current emergency guidance.
These layers alone do not establish legal boundaries, road
restrictions, service eligibility, or facility status. Comparable
demographic coverage and current flood and environmental coverage across
all six publishers remain limited. Inspect each layer’s
scope_note and source metadata for its own limits. The
current Tampa fire-stations source uses unqualified fields
such as NAME; older joined
GIS.GovServiceInfo.* fields are unavailable.
library(tampaBayOpenData)
info <- tbod_dataset_info("construction-permits")
info[c("title", "source_url", "scope_note", "terms", "verified")]Read scope_note and terms before analysis.
verified records an endpoint check, not feature freshness.
A portal item’s modified date can also differ from its
records’ dates; modified_source distinguishes live item
timestamps from saved catalog snapshots.
Discovered items may change, disappear, or lack clear reuse terms. Inspect their source metadata and publisher terms. The checked catalog remains available offline if a live portal fails.
tbod_provenance() reads a record attached to a retrieved
tibble or sf object. It includes publisher and source URLs,
portal and item ID when known, validation status, query, retrieval time,
row counts, integrity method, and completeness. Direct URL retrieval has
not_checked status.
projects <- tbod_get_dataset("development-cases", spatial = TRUE, out_sr = 4326)
source <- tbod_provenance(projects)
saveRDS(list(data = projects, provenance = source), "development-cases.rds")Save provenance separately before transformations or exports that may discard attributes. A finite subset is marked incomplete when more rows match. Object-ID checks detect missing, duplicate, or unexpected records, but cannot freeze live attributes across requests. See retrieval and downloads for the integrity methods.
Use tbod_check_catalog() for a current metadata and
schema check of the bundled catalog, or pass ids to inspect
selected layers:
health <- tbod_check_catalog(ids = c("construction-permits", "stpete-parks"))
health[, c("dataset_id", "status", "schema_status", "details")]This contacts the publishers and returns one row per checked entry.
Statuses include healthy, unavailable,
schema_changed, unsupported, and
unknown; transient failures remain unknown
after bounded retries. Inspect schema_issues for field or
geometry changes and failure_type and the service and layer
status columns for request failures. The check reads layer metadata and
does not run count or object-ID queries. A healthy row describes that
moment’s endpoint and schema; it does not certify record freshness, full
retrieval support, or future availability.
Twice weekly monitoring checks the selected layers in the checked catalog, bounded live discovery, and county facility retrieval by descriptor and stable ID. It also checks server projection to EPSG:4326. Retrievals request at most two rows; scans inspect at most one service item per publisher. The test guide describes these bounds and the manual live suite. The validation record dates completed checks; they cannot guarantee future availability or record freshness.
A separate weekly catalog
health workflow uses tbod_check_catalog() and uploads
timestamped RDS, CSV, and Markdown reports. It does not change the
bundled catalog.
For published work, cite the package version you used. R provides citation text and BibTeX after installation:
Cite the original data publisher and dataset separately.
tbod_dataset_info(id) gives source details;
tbod_provenance(result) records source and retrieval time.
The MIT license applies to the package software, not
government datasets. Publishers set their data terms. The package is
independent of them and of rOpenSci.
For implementation details, see the architecture and research basis.