Sightline
sightline-maps.vercel.app- Category
- Cybersecurity
- Rank
- No. 1460Tools index
- Pricing
- Free
- Type
- APP
- Use case
- Data, Retrieval & Knowledge
- Interfaces
- Web
- Builder
- @ni5arga
- GitHub
- 567 stars
- Date
About
An OSINT search engine that allows users to discover and map real-world infrastructure using OpenStreetMap data. It provides intelligence gathering capabilities for analyzing physical locations and infrastructure patterns.
What it does
Sightline turns plain-language or fielded place queries into OpenStreetMap tag searches. It geocodes locations, asks Overpass for matching assets, then presents results on a Leaflet map with lists, operator and type filters, and editable radius searches.
Why it's ranked here
The appeal comes from breadth and practical query handling. More than 200 listed asset types, natural and structured syntax, responsive map views, caching, request timeouts, and backup Overpass endpoints make it useful for quick reconnaissance. Its value remains bounded by external services and crowd-sourced data quality.
What's good
Users can begin with ordinary phrases, then switch to explicit type, operator, region, country, proximity, and radius fields for repeatable searches. Results expose coordinates, names, operators, tags, type counts, and operator counts. Shared query URLs, mobile tabs, endpoint fallback, geocoder rate limiting, and short-lived caching support practical investigation sessions.
Tradeoffs
OpenStreetMap may contain inaccuracies or gaps, so apparent absence is not reliable evidence. Searches also depend on Nominatim and public Overpass services, with their latency, availability, and rate limits. The cache lives only in application memory. The shown workflow provides discovery and filtering, not independent verification or durable monitoring history.
How to use it well
Use Sightline for fast geographic scoping before deeper research. Start with natural language, refine promising searches with structured fields, inspect raw tags and operators, then corroborate important findings elsewhere. It suits researchers comfortable treating map data as leads. It does not replace authoritative asset registries, source validation, or persistent historical analysis.
Technical notes+
package.json defines a private Next.js 16 application using React 19, TypeScript, Leaflet, marker clustering, Tailwind CSS, and Vercel Analytics. app/page.tsx implements the client search workflow, URL query sharing, responsive tabs, result selection, and POST requests to /api/search. lib/parser.ts uses regular-expression rules for natural-language asset recognition, while lib/types.ts maps asset names to OSM tags. lib/geo.ts calls Nominatim directly on the server, proxies browser requests, applies a 10-second timeout and server-side one-request-per-second limiter, and currently has isBoundingBoxTooLarge() always return false. lib/overpass.ts builds Overpass QL for nodes, ways, and relations, tries three endpoints, and applies a 30-second HTTP timeout. lib/cache.ts provides a process-local Map capped at 500 entries, with five-minute search and 24-hour geocoding TTLs.
Observed
- Primary language
- TypeScript, with TSX for the React interface.
- Packaging
- Private npm package configured as a Next.js application with development, build, start, and lint scripts.
- Interfaces
- Browser-based map interface plus a JSON POST search endpoint.
- Frontend stack
- React, Leaflet, React Leaflet, marker clustering, and Tailwind CSS.
- External services
- OpenStreetMap data queried through Overpass, with Nominatim for geocoding.
- Platform support
- Responsive browser layout with separate mobile map, results, and filter tabs.
- Cache structure
- Process-local in-memory cache capped at 500 entries.
Read from README.md, package.json, lib/geo.ts, lib/cache.ts, lib/types.ts, lib/utils.ts, lib/parser.ts, lib/overpass.ts, lib/search-index.ts, next.config.ts, eslint.config.mjs, postcss.config.mjs, app/page.tsx, app/layout.tsx, components/Filters.tsx.
What it can do
Search for real-world infrastructure
Location queries or geographic coordinates → Infrastructure data and locations
Map physical locations and infrastructure
OpenStreetMap data and search parameters → Visual maps with infrastructure overlays
Analyze infrastructure patterns
Geographic region or area of interest → Pattern analysis and infrastructure insights
Discover infrastructure connections
Target locations or infrastructure elements → Network of connected infrastructure elements
Gather intelligence on physical locations
Target addresses or coordinates → Comprehensive location intelligence reports
Query OpenStreetMap database
Search terms and geographic filters → Filtered OpenStreetMap data results
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.