How cahcai/geo works
GeoPortal is a full-stack HCAI geospatial-data portal. Analysts use the React interface to search healthcare and district data, upload workbooks, and manage coordinate overrides; downstream clients use the REST API. The API combines geocoding, spatial lookup, override management, and API-key controls, with data persisted in Django models. The README documents several capabilities whose detailed implementation was not sampled, so those links are shown as documented rather than inferred from unseen code.
Main entry points: routers.py API endpoints · App.tsx Portal app · models.py Portal data models · HpsaSearch.tsx HPSA search
Components 21
Portal interface
- Portal app
react-front-end-wip/Geo_app/src/App.tsx - HPSA search
react-front-end-wip/Geo_app/src/components/HpsaSearch.tsx - Facility search
react-front-end-wip/Geo_app/src/components/LicensedHealthcareFacilities.tsx - Map viewer
react-front-end-wip/Geo_app/src/components/MapViewer.tsx - Admin dashboard
react-front-end-wip/Geo_app/src/components/AdminDashboard.tsx - Override editor
react-front-end-wip/Geo_app/src/components/CordOverride.tsx - Login
react-front-end-wip/Geo_app/src/components/Login.tsx - API reference
react-front-end-wip/Geo_app/src/components/APIReference.tsx - Theme state
react-front-end-wip/Geo_app/src/utils/ThemeContext.tsx
API and access
- API endpoints
Geo/api/routers.py - API-key auth
Geo/api/auth.py - Key management
Geo/api/management/commands/generate_api_key.py
Geospatial services
- Address geocoding
GIS API/geocoding.py - Spatial lookup
Geo/api/routers.py - Workbook upload
Geo/api/routers.py
Domain data
- Portal data models
Geo/api/models.py - Redis cache
Geo/Geo/cache.py
Other components
- HCAI analyst
- API client
- Azure Maps
- Spatial database
Connections 30
- HCAI analyst → Portal app: uses
- API client → API endpoints: calls API
- Portal app → HPSA search: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → Facility search: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → Map viewer: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → Admin dashboard: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → Override editor: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → Login: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → API reference: renders
react-front-end-wip/Geo_app/src/App.tsx - Portal app → Theme state: wraps with
react-front-end-wip/Geo_app/src/main.tsx - API endpoints → API-key auth: imports auth
Geo/api/routers.py - API endpoints → Portal data models: uses models
Geo/api/routers.py - API endpoints → Redis cache: uses cache
Geo/api/routers.py - API endpoints → Spatial lookup: dispatches
Geo/api/routers.py - API endpoints → Workbook upload: accepts uploads
Geo/api/routers.py - API endpoints → Address geocoding: geocodes addresses
- Address geocoding → Azure Maps: queries
- API endpoints → Azure Maps: queries maps
Geo/api/routers.py - API endpoints → Spatial database: queries and writes
Geo/api/routers.py - Portal data models → Spatial database: maps entities
Geo/api/models.py - Redis cache → Spatial database: caches lookups
- Key management → Portal data models: generates keys
Geo/api/management/commands/generate_api_key.py - API-key auth → Portal data models: checks keys
Geo/api/auth.py - HPSA search → API endpoints: searches API
- Facility search → API endpoints: searches API
- Map viewer → API endpoints: requests map data
- Admin dashboard → API endpoints: manages usage
- Override editor → API endpoints: edits overrides
- Login → API endpoints: authenticates
- API reference → API client: documents API