Dashboard
Overview of all data
Coverage gaps — what to upload next
Two complementary lists. Upload the polygon for the first one; upload the data for the second one. Both lists refresh automatically after every upload and after “Re-run exact match”.
Subdivisions in the data with NO polygon
These names appear in the uploaded rows but no polygon carries them → upload the polygon in Area Metrics.
Loading…
| Subdivision | ZIP | Rows | Why |
|---|
Polygons with NO data
These polygons exist in the boundary file but no uploaded data falls inside them → upload the CSVs that cover them.
Loading…
| Polygon | ZIP | Rows |
|---|
Rows by dataset year
| Year | Rows | Committed | Pending |
|---|
Why you see that number when you click the row:
1. The Year column shows
dataset_year. An active rental has no
lease date, so its year is 0 — displayed as “Current (no date)”.
2. The old Rent section counted every rent row, including Current, so those 9,832 rows appeared inside Rent. The rows were always fine; the bucket they were counted in was misleading.
How it is fixed — step by step:
1. The importer now files every row under the year of the file it came from. Only Current files use year 0, so a row without a date can never fall into 2025 or 2026 by accident.
2. The Rent section now counts only
dataset_year > 0:
2021–2026, with no “undated” row.
3. Current Listings → Rent counts
dataset_year = 0:
the 9,832 active rentals, labelled “Current (no date)”.
4. Restart the app so the new code and labels load.
5. When you re-upload the Current files they will always land in the Current bucket — never in 2025/2026.
Do those rows still show on the map? Yes. Current rentals are part of the map dataset and are counted whenever the period is “All data”. They are not counted inside a specific calendar year (2025, 2026, …) because they have no year. Nothing was deleted or hidden.
Polygon assignment
Coverage gaps are listed at the top of the Dashboard in “Coverage gaps — what to upload next”.
Pending upload sessions
Sales Data
Sold prices & history
This changes on the map
Expected CSV files
Rows already in the database
| Year | Rows |
|---|
The map still shows them: they count under “All data”, not inside a single calendar year, because they have no year. Nothing was deleted.
Data not uploaded — this section
Exact file names that could not be uploaded, with the reason in English exactly as the server reported it.
Missing data for this section
Only rows and files of this section.
Rows with NO polygon
Loading…
| Subdivision | ZIP | Rows | Why |
|---|
Polygons with NO data — by year
Loading…
| Polygon | ZIP |
|---|
⬆ Upload
Uploaded files
Edit Manually
Manual property edits live in the main CMS. From here you can still review the uploaded files in this section and delete them.
Uploaded files
Area Metrics
Boundary GeoJSON uploads
This changes on the map
- Boundary polygons drawn on the map
- Which row belongs to which area (point-in-polygon)
- Every per-area median and count
Expected GeoJSON files
One FeatureCollection per boundary class. The file name the map reads is fixed per class.
Replace a boundary file
Uploaded boundary files
Advertising Campaigns
Manage banner and video ads shown on the map
System Users
Manage who can access the system
🛡 Access Control
The map (/map) is always reachable. User management decides whether plans are enforced: off means everyone sees every filter and report for free. It applies live.
User management
Free visitors get a read-only map; filters and reports need a plan.
○ Open — anyone can enter
Admin login
Require admin sign-in to open the CMS (/admin).
● Required