Open311 GeoReport v2
GeoReport v2 describes API services and fields for discovering service types and creating, querying, and tracking location-based requests.
What the authority record establishes
GeoReport v2 describes API services and fields for discovering service types and creating, querying, and tracking location-based requests.
Voluntary unless required by an implementing authority, contract, or procurement
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Complaint intake and service requests often touch code enforcement or property records, but their identifiers, confidentiality, location, evidence, routing, and legal case status need explicit boundaries.
Affected operating stages
- Service Discovery
- Request Intake
- Location
- Routing
- Status
- Publication
Capabilities to examine
Applicant Portal And Guided Intake
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for applicant portal and guided intake.
Parcel Property And Address Master
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for parcel property and address master.
Code Enforcement And Case Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for code enforcement and case management.
Public Search Status And Communications
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for public search status and communications.
APIs Integrations And Data Export
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for APIs integrations and data export.
Documents Records Retention And Public Disclosure
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for documents records retention and public disclosure.
Affected buyer audiences
- digital-service teams
- 311 and code-enforcement leaders
- integrators
- vendors
- open-data teams
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
A service request is not a verified violation, notice, enforcement case, inspection result, permit condition, or legal finding.