Vancouver Property Signal Monitor

Monitor City of Vancouver Open Data for property, rental, and redevelopment signals. The Actor turns public rental standards issues, recent building permits, and property assessment records into lead-scored, CRM-ready property records.

This is not a foreclosure or tax-delinquency scraper. Vancouver's public data is better for property intelligence, rental standards monitoring, redevelopment scouting, and contractor/vendor lead generation.

By default, the Actor emits one aggregated lead per normalized property address. It joins matching rental standards issues, building permits, and assessment signals into a stronger property-level lead with signal_types, signal_count, source_records, and combined lead_reasons. Use outputMode: "raw" for one record per source row, or outputMode: "both" to emit aggregate leads plus raw source records.

Address enrichment is enabled by default. The Actor takes high-scoring seed addresses and queries the other Vancouver datasets by address, so a rental-standards lead can intentionally pick up matching permit and assessment records instead of relying on unrelated top-N source queries to overlap by chance.

Sources

Source	Dataset	What it contributes
Rental standards	rental-standards-current-issues	Active rental buildings with outstanding standards issues, issue counts, units, operator, source detail URL.
Building permits	issued-building-permits	Recent issued permits, project value, type of work, project description, applicant, contractor, neighbourhood.
Property assessment	property-tax-report	Land/improvement value, year built, zoning, PID/folio, assessment year. Useful for land-heavy redevelopment signals.

Example: rental + permit signals

{
  "signals": ["rental_standards", "building_permits"],
  "neighbourhoods": "Downtown, West End, Mount Pleasant",
  "minOutstandingIssues": 1,
  "minProjectValue": 50000,
  "sinceDays": 30,
  "outputMode": "aggregated",
  "enableAddressEnrichment": true,
  "maxEnrichmentAddresses": 20,
  "enrichmentLimit": 5,
  "onlyChanges": true,
  "compareWithPreviousRun": true,
  "stateStoreName": "vancouver-property-signal-monitor-state",
  "stateKey": "vancouver-core-property-signals"
}

Example: redevelopment scouting

{
  "signals": ["tax_assessment", "building_permits"],
  "minLandValue": 1500000,
  "minProjectValue": 250000,
  "permitKeywords": "demolition, new building, multiplex, change of use",
  "sinceDays": 60,
  "maxItemsPerSource": 100
}

Output fields

Each dataset item includes normalized fields where available:

• change_type: new, updated, unchanged, or missing_from_current_run
• signal_score: 0-100 lead score
• signal_type: aggregated_property, rental_standards, building_permit, or tax_assessment
• signal_types: source signal types joined into an aggregate lead
• signal_count: number of source records joined into an aggregate lead
• property_address
• neighbourhood
• lead_reasons
• recommended_buyer
• business_operator
• total_outstanding_issues
• total_units
• project_value
• permit_number
• issue_date
• type_of_work
• permit_category
• applicant
• contractor
• pid, folio
• land_value, improvement_value, year_built, zoning_district
• source_url
• source_urls
• source_records: compact source-record references for aggregate leads
• raw

The run summary is written to key-value store key OUTPUT.

Change detection

When compareWithPreviousRun is enabled, this Actor stores fingerprints in a named key-value store (stateStoreName) under stateKey. Later runs mark records as new, updated, unchanged, or missing. Keep both values stable for scheduled monitors and use different keys for different watchlist/filter sets.

Caveats

• City source schemas can change.
• Vancouver Open Data does not expose the same foreclosure/tax-delinquency signals available in many US counties.
• Owner names are generally not available in these datasets.
• Treat this as lead intelligence and research, not legal/financial advice. Verify source URLs before acting on high-stakes decisions.