Atlas Systems logoAtlas Systems

Technologies

What we’ll use to build and deliver the solution.

Frontend

Website (Archival)

  • HTML + CSS (no framework): lightweight, long-term maintainable.
  • Responsive layout: custom CSS with system fonts, dark-mode vars.
  • Accessibility: semantic tags, high-contrast palette, focus states.

Maps & Location

  • Web Maps SDK: Currently Undecided: Tech Feasibility research in progress

Data & POIs

  • Primary Source: Overpass API (OpenStreetMap) pulling nationwide landmarks, parks, public art, and other POI tags.
  • Enrichment: Wikidata API queries supply descriptions, imagery links, and metadata for each POI.
  • Storage: Lightweight cache (JSON/SQLite, tooling TBD) refreshed on schedule so the mobile app ships with nationwide data.
  • Sync: Scheduled jobs mirror updates from Overpass/Wikidata, so no manual submission or approval workflow is required.

Dev Workflow

Source Control

  • GitHub (private repo, protected main).
  • Branch strategy: feature branches + PR reviews.

Deployment

  • Web Maps SDK: Currently Undecided: Tech Feasibility research in progress

Privacy & Safety (Initial)

  • Privacy Features: As with any app that uses GPS and Personally Identifiable Information privacy is paramount. Specifics will be planned in the Tech Feasibility phase of the project.