GeoSite

Evidence-led AI site selection for retail and service businesses.

Live product · Methodology · Privacy

GeoSite helps founders and commercial teams screen potential store locations in China and Singapore. A user can evaluate a specific address or describe a broader location brief in natural language. The system then retrieves mapped evidence, calculates pedestrian catchments, applies explicit scoring rules, and produces a traceable recommendation.

The language model does not guess which location is best. It structures the brief; deterministic GIS tools resolve places, retrieve POIs, calculate walking networks, apply hard constraints, score candidates, compare scenarios, and audit the evidence.

Why GeoSite

Traditional site selection often depends on fragmented map searches, spreadsheets, and intuition. GeoSite turns that workflow into a repeatable decision process:

• start from a specific place, address, or postal code;
• evaluate suitability for a chosen business type;
• inspect transport, demand proxies, relevant amenities, and competitors;
• compare 5, 10, and 15-minute pedestrian-network catchments;
• understand the evidence, risks, and missing information behind every result;
• adjust priorities and recalculate the ranking without inventing new facts;
• print or export an evidence-led location report.

Product capabilities

• Bilingual English and Simplified Chinese interface
• Place evaluation as the primary workflow
• Natural-language location brief parsing with DeepSeek
• Real POI retrieval and candidate-area discovery
• 5, 10, and 15-minute pedestrian-network isochrones
• Demand-proxy, transport, industry-fit, and competitor analysis
• Deterministic multi-criteria scoring and hard-constraint checks
• Scenario comparison with adjustable weights
• Evidence coverage and consistency audit
• Candidate maps, layer controls, nearby-place inspection, and printable reports
• Responsive desktop and mobile layouts
• Search-indexable methodology, industry guides, city pages, and public report pages

Supported regions and data sources

GeoSite uses different providers for each supported market instead of forcing one global dataset into every region.

China

• AMap Place Search and Geocoding for addresses, POIs, and nearby evidence
• AMap JavaScript API for the interactive map
• AMap routing and reachability services for walking-network evidence

Singapore

• Singapore Land Authority OneMap for the official national basemap and optional address search
• OpenStreetMap via Overpass for named POIs, amenities, businesses, and pedestrian-road evidence
• Nominatim as a bounded fallback for place resolution

Provider availability, coverage, freshness, quotas, and licensing determine what can be shown. Unsupported rent, observed footfall, revenue, conversion, and growth estimates are deliberately omitted rather than simulated.

Agent workflow

The agent exposes an explicit tool-oriented decision process:

1. resolve_location
2. parse_requirements
3. search_candidate_areas
4. search_poi
5. calculate_walk_isochrone
6. analyze_demand_proxies
7. analyze_competition
8. check_hard_constraints
9. score_candidates
10. compare_scenarios
11. verify_evidence
12. generate_report

Only sourced metrics enter the ranking. Evidence checks cover location matching, duplicated records, coordinate validity, spatial scope, and missing fields. If the evidence threshold is not met, GeoSite withholds the recommendation.

Architecture

User brief or place
        |
        v
DeepSeek requirement parser
        |
        v
Regional data adapter
  |                    |
  | China              | Singapore
  v                    v
AMap APIs       OneMap + OSM/Overpass
  |                    |
  +----------+---------+
             |
             v
Deterministic GIS tools
             |
             v
Scoring + evidence audit
             |
             v
Interactive map + report

The application is built with React, Next.js-compatible routing through Vinext, TypeScript, Leaflet, and a Cloudflare Worker-compatible runtime. The current production deployment is hosted on OpenAI Sites.

Local development

Requirements

• Node.js 22.13 or newer
• npm
• Provider credentials for the regional capabilities you want to test

Setup

git clone https://github.com/L930861/Geosite.git
cd Geosite
npm install
cp .env.example .env.local
npm run dev

On Windows PowerShell, replace the copy command with:

Copy-Item .env.example .env.local

Open the local URL printed by the development server.

Environment variables

Variable	Required	Exposure	Purpose
DEEPSEEK_API_KEY	For AI parsing	Server only	DeepSeek API credential
DEEPSEEK_MODEL	No	Server only	Model name; defaults to the configured project value
AMAP_WEB_KEY	For China analysis	Server only	AMap Web Service credential
AMAP_JS_KEY	For China map UI	Browser-visible	Domain-restricted AMap JavaScript key
AMAP_SECURITY_JS_CODE	For China map UI	Server only	AMap JS security proxy value
ONEMAP_ACCESS_TOKEN	Optional	Server only	OneMap address-search enrichment
GOOGLE_SITE_VERIFICATION	Optional	Public metadata	Google Search Console verification token
BAIDU_SITE_VERIFICATION	Optional	Public metadata	Baidu Search Resource Platform verification token
NEXT_PUBLIC_DEVELOPER_EMAIL	Optional	Browser-visible	Public contact address shown in the site footer

Never commit .env.local, .dev.vars, service-account files, private keys, access tokens, or production credentials. Configure secrets in the deployment platform and restrict provider keys by domain, API, quota, and billing limits whenever supported.

Quality checks

npm run lint
npm test

The test suite covers the production build, rendered HTML, agent readiness, evidence integrity, commercial-safety checks, bilingual Singapore behavior, English-output cleanliness, responsive layouts, SEO pages, and more than 60 user scenarios.

Important decision limits

GeoSite is an early-screening and fieldwork-prioritisation tool. It does not predict revenue or replace property inspection, lease review, licensing checks, planning advice, or professional due diligence.

Before signing a lease, independently verify at least:

• permitted use and local licensing requirements;
• rent, service charges, deposit, and lease terms;
• observed footfall at relevant hours;
• frontage, visibility, access, deliveries, and parking;
• utilities, drainage, ventilation, loading, fire safety, and structural limits;
• whether the mapped businesses and facilities are current.

Commercial and data licensing

Do not operate a paid product using personal or evaluation-only provider licences. Before commercial launch, confirm AMap enterprise licensing and the permitted use of POI results, cached data, maps, route outputs, and exported reports. Review the applicable OneMap, OpenStreetMap/ODbL, Overpass, Nominatim, and DeepSeek terms for the deployed use case.

Operational preparation documents are included in:

• docs/COMMERCIAL_LAUNCH.md
• docs/DATA_GOVERNANCE.md
• docs/INCIDENT_RUNBOOK.md
• SECURITY.md

Security

Please do not open a public issue containing credentials or exploitable details. Follow SECURITY.md for responsible reporting guidance.

The repository intentionally contains only empty environment-variable placeholders. Runtime secrets are managed outside Git.

Repository status

GeoSite is an actively developed personal project and public technical portfolio. No open-source licence has been granted at this time; all rights are reserved by the project owner.