Nearmap

Commercial AI Packs and preprocessed property-feature data available in MapBrowser, by AI Feature and Rollup APIs, and through licensed offline exports. The API supports distributed buyer-selected property AOIs, address geocoding, date filters, real-time retrieval, bulk mode, and flat single-row Rollup CSV/JSON output. GeoJSON feature arrays and geometries remain in Source prose; proposed output Features are only exact scalar columns from the officially linked Gen 6 flat Rollup data dictionary.

Distinct transaction-priced roof-condition assessment product for a buyer-selected land parcel, delivered as CSV, JSON, or PDF through an API and also surfaced in Betterview and MapBrowser. Current product copy identifies materials, shapes, rusting, staining, ponding, repairs, missing tiles, affected-roof percentage, confidence, and visual references. No exact public flat output schema was found, so this Source intentionally has zero Features; similarly named Nearmap AI Rollup fields remain owned by `nearmap/nearmap-ai`.

Standing catastrophe-intelligence subscription providing post-disaster survey imagery and optional AI damage classification/detection modules. The current system identifies properties in event zones, supplies high-resolution post-cat imagery, and describes FEMA five-tier classifications and detections such as structural roof damage, exposed deck, and tarps. Legal terms provide term-based access after qualifying wildfire, hurricane, or tornado events and permit ImpactResponse AI through Transactional Content API, AI Feature API, or licensed offline vector delivery. Survey capture is discretionary and weather/airspace dependent; no event is guaranteed. No exact flat scalar damage schema was found, so this Source has zero Features.

Distinct portfolio roof-asset assessment product using current high-resolution imagery and AI to identify 40+ roof characteristics and export CSV results. A customer selects roof-square areas within its subscribed Territory. The 0–100 Roof Spotlight Index is not proposed as a Feature because public documentation does not provide thresholds or a model/release version; detection lists are not an exact flat wire schema.

Current Nearmap-owned property intelligence and risk-management platform for insurers, with UI, REST API, SFTP, external warehouse, and core-system delivery. Nearmap's current legal terms let a licensee submit arbitrary property addresses and retrieve property information; the API supports arrays of addresses or coordinates and as-of dates. The full response documents imagery capture dates and per-building roof-age objects with an explicit `changed` boolean, before/after date array, age, installation date, evidence category, and capture count. Because the request and roof outputs are nested/repeated, they are retained in Source prose and not flattened into Features.

Standing subscription to current and historical vertical, panorama, oblique, and true-ortho aerial imagery. Buyers select unrelated locations through MapBrowser or authenticated Coverage, Tile, WMS, and Transactional Content APIs. Coverage results expose captureDate, firstPhotoTime, lastPhotoTime, survey/resource IDs, pixelSize/GSD, onlineTime, imagery type, and location metadata inside repeated survey/resource structures; imagery is raster. Those repeated and raster structures are retained here in prose and are not flattened into Features. MapBrowser and API families are delivery surfaces, not separate Sources.

Distinct US-only commercial API product predicting residential and commercial roof installation date and age from Nearmap imagery, Gen 6 AI, climate, permits, and assessor data. It accepts an address object or polygon AOI and can return the latest or a specified historical resource. Repeated GeoJSON feature results document installationDate, asOfDate, evidenceType/evidenceTypeDescription, min/max captures, before/after installation captures, numberOfCaptures, permit/assessor flags, and explicit multiple-images-with-change or no-change categories. Those nested feature-array values are preserved in prose rather than flattened; only top-level scalar response/request fields are proposed as Features.