SPB Git forge
38commits 1branches 0releases
338.7 MBsize
maindefault branch
3 h agolast push
HTML 53.9% TypeScript 44.5% JavaScript 0.6% SQL 0.5%
2.4 KB

# Evocative Data Centers (evocative)

  • Domain: evocative.com · Kind: operator · Priority: 2 · Enabled: yes
  • License / attribution: Publicly accessible operator pages; factual data only; © Evocative — attribution “Evocative Data Centers”
  • Coverage: US

# What it collects

Facility records (kind: facility) via parser(s) evocative_facility_v1 in apps/worker/src/connectors/operators2/americas.ts.

Fields published by the pages and captured: name, code, city, regionName, postalCode, address (Google Maps embed query), itCapacityMw and buildingSqm from the meta description, tier, certifications.

Every field carries an extraction method in methods (e.g. json-ld:PostalAddress, regex:it_mw_v1, attr:data-value+MW, lookup:city-country) for provenance. Coordinates are only taken from JSON-LD / embedded JSON / map links published by the operator — never geocoded. Status defaults to operational unless the page uses pipeline wording (under construction / coming soon / planned).

# Discovery

  • Sitemaps: https://evocative.com/page-sitemap.xml, https://evocative.com/post-sitemap.xml
  • Include: /data-centers/[a-z-]+-data-center-[a-z]{3}\d+/$, /news/, /press-releases?/
  • Exclude: \?, #
  • Classify: /data-centers/[a-z-]+-data-center-[a-z]{3}\d+/$ → facility_pages (facility_page); /(news|press-releases?)/. → newsroom (press_release)

Newsroom URLs (when configured) rely on the GenericConnector news fallback (press_release → news_event when data-center relevant).

# Schedule & fetch

  • Schedule: facility_pages weekly, newsroom daily, sitemap weekly
  • Fetch: L1→L2, 15 rpm, concurrency 2, robots.txt respected, max 30 premium credits/run. All pages are served at L1 (plain HTTP); maxLevel is capped at 2 so false-positive “blocked” heuristics (HubSpot / cookie-consent strings) never spend Scrapfly credits.

# Quirks

Facility pages /data-centers/--data-center-/ ; address from the Google Maps embed query, critical MW and sq ft from the meta description. Some pages contain HubSpot 'enable JavaScript' strings that trip the blocked-page heuristic — maxLevel 2 keeps them off premium fetchers.

# Verification (live, 2026-09-11)

try-connector --limit N: discovered 68 URLs (default=1, facility_pages=13, newsroom=54); sampled pages → 4 entities, 4 valid, 0 rejected, 0 premium credits.