Gleipnir/nidus-sync

Fork 0

Look for ideas #179

New issue

Open

opened 2026-07-29 20:38:53 +00:00 by benjaminsperry · 1 comment

benjaminsperry commented

2026-07-29 20:38:53 +00:00

Owner

Hello @ned,

I would like you to please look at this competitor: https://www.acres.com

Look through their entire offering and determine all the features and data sources that would be useful in Nidus Reveal.

Make a list of everything you can find and then for each feature or item suggest what it would take to build somethings similar in Nidus Reveal.

Thanks

Hello @ned, I would like you to please look at this competitor: https://www.acres.com Look through their entire offering and determine all the features and data sources that would be useful in Nidus Reveal. Make a list of everything you can find and then for each feature or item suggest what it would take to build somethings similar in Nidus Reveal. Thanks

ned was assigned by benjaminsperry

2026-07-29 20:38:53 +00:00

ned commented

2026-07-29 20:40:19 +00:00

Member

Howdy Benjamin! 🎯

I did a thorough dig through everything acres.com has to offer. Here is my full inventory of features and data sources, with what it would take to build something similar in Nidus Reveal.

The Big Caveat: Acres is a general-purpose land intelligence platform covering all 150M+ US parcels across every industry (homebuilding, energy, finance, agriculture). Nidus Reveal is a specialized tool focused on satellite-based pool detection for municipal vector control. The scope difference is enormous — but there are some genuinely useful ideas to borrow.

1. CORE DATA LAYERS (Acres: 13,000+ layers from 1,000+ sources)

What Acres has: Nationwide parcel boundaries, ownership records, tax assessments, zoning, FEMA flood zones, elevation/lidar topography, soil maps (NCCPI + state-specific), historic satellite imagery, historic land cover, vegetation index (NDVI), timber site index, water districts/wells, sewer infrastructure, FEMA flood risk, wildfire risk, environmental constraints, building permits, mortgages/deeds.

What it would take in Nidus Reveal:

Parcel boundaries — Already in-progress (ArcGIS parcel services, Fresno situs data) — this is our foundation
Satellite imagery — Already planned per Benjamin (weekly Planet data tile layers per detection event). Acres uses historic imagery too — could add pre-built tile layers showing pool conditions over time
Elevation/topography — Could integrate USGS 3DEP lidar via WMTS — lower priority but useful for flood-prone district analysis
Flood zones — FEMA NFHL WMS is free and easy to overlay — could be a toggle in the map layer panel
Zoning — Not relevant for vector control districts
Soil maps — Not relevant for pool detection
Vegetation/land cover — Actually somewhat useful — could correlate with mosquito habitat (wetlands, vegetation density near pools)
Water districts/wells — Potentially useful — standing water sources correlate with mosquito breeding

Priority for Nidus Reveal: Low-to-Medium. Adding FEMA flood zones and water bodies as optional map layers would be the most impactful for vector control.

2. AI PARCEL SUMMARIES (Acres Intelligence)

What Acres has: AI-powered parcel detail panel showing every data point — ownership, zoning, risk, transactions. AI answers natural language questions about zoning, development constraints, etc.

What it would take in Nidus Reveal:
We already have the parcel detail view designed in the UI mockup (PR #175) — address, owner, pool condition status, timeline. The Acres equivalent would be:

Enhanced pool detail panel: AI-generated summary — condition history, detection confidence trends, adjacent pool density, risk score
Natural language query: "Show me all pools in the northwest quadrant that have been green for 3+ weeks" — more powerful than filter buttons. Could use our existing full_text_search GIN index + LLM query parsing
Risk scoring: Acres has risk layers (flood, wildfire). Nidus Reveal could have a mosquito risk score per pool — combining condition, duration of neglect, proximity to standing water, historical treatment gaps

Effort: Medium. Detail panel already designed. Risk scoring needs data model + algorithm.

3. SALES DATA and VALUATION

What Acres has: 45M+ land transactions nationwide, weekly curated sales data, even in non-disclosure states. Builds valuation reports with comparable sales.

Doesn't directly apply — Nidus districts don't buy/sell pools. But parallel concepts:

Pool condition history as "valuation": Track condition state changes over time, rate severity
Export reports: Acres does branded PDF/CSV reports. We're already building CSV/KML/PDF export for selected pools (PR #175/176)

Effort: Already in progress via export feature.

4. PROSPECTING and LEAD GENERATION

What Acres has: Search by land use, acreage, owner location. Build targeted lead lists. Skip tracing (phone/email for landowners). LLC/trust ownership tracing.

Not directly applicable — but the analog is:

Pool watchlist: District users create watchlists of high-priority pools (chronic offenders, pools near schools/hospitals). Acres' lead list builder maps directly to "find all unmaintained pools over X sq ft within 500m of a school"
Skip tracing for owners: We have owner names from tax rolls but not phone/email. Integrating a service (TLOxp, LexisNexis) would let districts contact owners

Effort: Medium. Watchlist = new DB model + UI. Skip tracing = third-party API integration.

5. MAPPING TOOLS

What Acres has: Draw/merge boundaries, upload KML/KMZ, overlay custom imagery, 3D maps, embed maps, DeedAI (automated deed plotting), Site Planner (lot yield calculations), shareable map links.

What would translate:

Boundary drawing — District users may draw inspection/treatment zones. MapLibre supports drawing — needs UI exposure
Upload KML/KMZ — Import district boundaries, treatment zone maps
Custom imagery overlay — Related to our satellite imagery timeline
Shareable/embed maps — Districts share pool maps with public/agencies
3D maps and Site Planner — Not relevant

Effort: Low-to-Medium. Incremental additions to existing map infrastructure.

6. PORTFOLIO MANAGEMENT / TEAM COLLABORATION

What Acres has: Shared portfolios with custom columns/tags, commenting, document management, team permissions, collaborative maps, activity tracking.

Highly relevant because multiple district staff need to work on the same pool data.

Shared pool portfolios — Organize pools by zone, inspector assignment, or status
Comments/notes on pools — Nidus Notes for iOS captures field observations. Connecting notes to specific pools in Reveal is the web counterpart
Assignment/tagging — Tag pools with inspector assignments, priority levels
Activity history — Log who looked at what pool, when, what actions taken

Effort: Medium-High. Overlaps with Nidus Notes backend integration.

7. RISK MANAGEMENT

What Acres has: Flood zones, wildfire risk, environmental constraints. Ownership/financial exposure tracking. Competitor activity monitoring.

Vector control equivalents:

Mosquito-borne disease risk overlay — Pools near schools, daycares, parks, hospitals get higher risk scores. GIS buffering + condition history weighting
Emerging outbreak monitoring — Pools going from maintained to unmaintained in spatial clusters. Early warning system
District coverage gaps — Identify neighborhoods with low inspection coverage, high pool density, long gaps between satellite passes

Effort: Medium. Risk scoring algorithm needs spatial joins + temporal analysis.

8. REPORTS and EXPORTS

What Acres has: Custom branded PDF property reports, market valuation reports, CSV exports, large reports.

Already in progress (PR #175/176). Could add:

District summary report: PDF with pool counts by status, detection dates, map, statistics
Custom branding: District logo/name on reports
Large batch exports: Handle entire district in one export

Effort: Low (extensions of existing export work).

9. MOBILE APP

What Acres has: iOS + Android native apps. Offline maps, parcel lookup on-the-go, geotagged photos, waypoints, route tracking, driving directions, offline mode.

Overlaps with Nidus Notes (iOS field technician app):

Pool lookup mobile: Field inspectors look up pool details, condition history, owner info on-site
Geotagged photos: Already planned for Nidus Notes
Offline mode: Download pool data for rural areas with spotty coverage
Driving directions: Navigate to specific pools — deep link to Apple/Google Maps
Route planning: Optimize daily routes based on pool assignments

Effort: High for full app, but Nidus Notes iOS exists — extending it is incremental.

10. MARKET INDICES (Home Builder Index, Data Center Index)

Nidus Pool Index — District-level trends:

Pool counts by condition over time (time series chart)
Detection rate (new pools found per satellite pass)
Compliance rate (pools going from unmaintained to maintained)
Hotspot migration (where problem pools cluster over time)

A district health dashboard with trend analytics — valuable for managers reporting to city/county government.

Effort: Medium. Time-series aggregation + charting library.

11. DATA INTEGRATIONS and API

What Acres has: API integrations (enterprise add-on), SOC 2 Type II, embeddable maps, partner program.

Public API — Expose pool detection data for district integration. Extension of existing internal APIs
Embeddable maps — Districts embed pool maps on public websites
SOC 2 — Relevant if districts have compliance needs

Effort: Medium-High. API gateway + auth + rate limiting.

12. SKIP TRACING (Owner Contact Data)

What Acres has: Phone numbers and email addresses for landowners.

Districts need to contact pool owners about violations. We have names from tax rolls but not phone/email. Integrating a skip tracing API would let districts send automated violation notices.

Effort: Medium. Third-party API + TCPA compliance.

13-14. SITE PLANNER and COMPETITIVE INTELLIGENCE

Image overlay is relevant (treatment plan diagrams on satellite view). Site Planner (lot yield) and 3D maps are not relevant.

Neighboring district activity tracking is a follow-on, not MVP.

PRIORITIZATION SUMMARY

Feature	Acres Feature	Relevance	Effort	Priority
Enhanced Pool Detail Panel	AI Parcel Summaries	High	Medium	High
Map layer library (flood, water)	Layer Library	Medium	Low	Medium
Pool watchlists / saved filters	Prospecting / Lead Lists	High	Medium	High
Team collaboration (comments, tags)	Portfolio Management	High	Med-High	High
District health dashboard / trends	Market Indices	High	Medium	High
Mobile pool lookup	Mobile App	High	High	High
Risk scoring (mosquito hazard)	Risk Management	Medium	Medium	Medium
Owner contact (skip tracing)	Skip Tracing	Medium	Medium	Medium
Embeddable public pool maps	Embed Maps	Medium	Low-Med	Low
Image overlay / boundary drawing	Mapping Tools	Low	Low	Low
Public API	API Integrations	Low	Med-High	Low
3D maps / Site Planner / Zoning	Various	Not relevant	-	Never

IMMEDIATE TAKEAWAYS

Three features from Acres that would most benefit Nidus Reveal right now:

Pool Risk Scoring — Combine condition + duration + proximity to sensitive sites into a weighted score. Surfaced in the pool detail panel. Turns raw detection data into actionable enforcement priority.
Saved Filters / Watchlists — Let district users save complex filter combinations ("pools green >2 weeks, area >400sqft, in zone 7") as named watchlists. Acres does this with lead lists. We have the filter controls already mocked up.
District Dashboard — Time-series trends of pool counts by status, detection rates, compliance rates. Acres' home builder index concept but applied to mosquito control KPIs. High-value for district managers reporting to city councils.

None of these would require a fundamentally different architecture — just incremental work on top of what we're already building.

Okaly-dokely, let me know which of these you'd like me to dig deeper on or start designing a spec for!

Howdy Benjamin! :dart: I did a thorough dig through everything acres.com has to offer. Here is my full inventory of features and data sources, with what it would take to build something similar in Nidus Reveal. **The Big Caveat:** Acres is a general-purpose land intelligence platform covering all 150M+ US parcels across every industry (homebuilding, energy, finance, agriculture). Nidus Reveal is a specialized tool focused on satellite-based pool detection for municipal vector control. The scope difference is enormous — but there are some genuinely useful ideas to borrow. --- ## 1. CORE DATA LAYERS (Acres: 13,000+ layers from 1,000+ sources) **What Acres has:** Nationwide parcel boundaries, ownership records, tax assessments, zoning, FEMA flood zones, elevation/lidar topography, soil maps (NCCPI + state-specific), historic satellite imagery, historic land cover, vegetation index (NDVI), timber site index, water districts/wells, sewer infrastructure, FEMA flood risk, wildfire risk, environmental constraints, building permits, mortgages/deeds. **What it would take in Nidus Reveal:** - Parcel boundaries — Already in-progress (ArcGIS parcel services, Fresno situs data) — this is our foundation - Satellite imagery — Already planned per Benjamin (weekly Planet data tile layers per detection event). Acres uses historic imagery too — could add pre-built tile layers showing pool conditions over time - Elevation/topography — Could integrate USGS 3DEP lidar via WMTS — lower priority but useful for flood-prone district analysis - Flood zones — FEMA NFHL WMS is free and easy to overlay — could be a toggle in the map layer panel - Zoning — Not relevant for vector control districts - Soil maps — Not relevant for pool detection - Vegetation/land cover — Actually somewhat useful — could correlate with mosquito habitat (wetlands, vegetation density near pools) - Water districts/wells — Potentially useful — standing water sources correlate with mosquito breeding **Priority for Nidus Reveal:** Low-to-Medium. Adding FEMA flood zones and water bodies as optional map layers would be the most impactful for vector control. --- ## 2. AI PARCEL SUMMARIES (Acres Intelligence) **What Acres has:** AI-powered parcel detail panel showing every data point — ownership, zoning, risk, transactions. AI answers natural language questions about zoning, development constraints, etc. **What it would take in Nidus Reveal:** We already have the parcel detail view designed in the UI mockup (PR #175) — address, owner, pool condition status, timeline. The Acres equivalent would be: - Enhanced pool detail panel: AI-generated summary — condition history, detection confidence trends, adjacent pool density, risk score - Natural language query: "Show me all pools in the northwest quadrant that have been green for 3+ weeks" — more powerful than filter buttons. Could use our existing full_text_search GIN index + LLM query parsing - Risk scoring: Acres has risk layers (flood, wildfire). Nidus Reveal could have a mosquito risk score per pool — combining condition, duration of neglect, proximity to standing water, historical treatment gaps **Effort:** Medium. Detail panel already designed. Risk scoring needs data model + algorithm. --- ## 3. SALES DATA and VALUATION **What Acres has:** 45M+ land transactions nationwide, weekly curated sales data, even in non-disclosure states. Builds valuation reports with comparable sales. **Doesn't directly apply** — Nidus districts don't buy/sell pools. But parallel concepts: - Pool condition history as "valuation": Track condition state changes over time, rate severity - Export reports: Acres does branded PDF/CSV reports. We're already building CSV/KML/PDF export for selected pools (PR #175/176) **Effort:** Already in progress via export feature. --- ## 4. PROSPECTING and LEAD GENERATION **What Acres has:** Search by land use, acreage, owner location. Build targeted lead lists. Skip tracing (phone/email for landowners). LLC/trust ownership tracing. **Not directly applicable** — but the analog is: - Pool watchlist: District users create watchlists of high-priority pools (chronic offenders, pools near schools/hospitals). Acres' lead list builder maps directly to "find all unmaintained pools over X sq ft within 500m of a school" - Skip tracing for owners: We have owner names from tax rolls but not phone/email. Integrating a service (TLOxp, LexisNexis) would let districts contact owners **Effort:** Medium. Watchlist = new DB model + UI. Skip tracing = third-party API integration. --- ## 5. MAPPING TOOLS **What Acres has:** Draw/merge boundaries, upload KML/KMZ, overlay custom imagery, 3D maps, embed maps, DeedAI (automated deed plotting), Site Planner (lot yield calculations), shareable map links. **What would translate:** - Boundary drawing — District users may draw inspection/treatment zones. MapLibre supports drawing — needs UI exposure - Upload KML/KMZ — Import district boundaries, treatment zone maps - Custom imagery overlay — Related to our satellite imagery timeline - Shareable/embed maps — Districts share pool maps with public/agencies - 3D maps and Site Planner — Not relevant **Effort:** Low-to-Medium. Incremental additions to existing map infrastructure. --- ## 6. PORTFOLIO MANAGEMENT / TEAM COLLABORATION **What Acres has:** Shared portfolios with custom columns/tags, commenting, document management, team permissions, collaborative maps, activity tracking. **Highly relevant** because multiple district staff need to work on the same pool data. - Shared pool portfolios — Organize pools by zone, inspector assignment, or status - Comments/notes on pools — Nidus Notes for iOS captures field observations. Connecting notes to specific pools in Reveal is the web counterpart - Assignment/tagging — Tag pools with inspector assignments, priority levels - Activity history — Log who looked at what pool, when, what actions taken **Effort:** Medium-High. Overlaps with Nidus Notes backend integration. --- ## 7. RISK MANAGEMENT **What Acres has:** Flood zones, wildfire risk, environmental constraints. Ownership/financial exposure tracking. Competitor activity monitoring. **Vector control equivalents:** - Mosquito-borne disease risk overlay — Pools near schools, daycares, parks, hospitals get higher risk scores. GIS buffering + condition history weighting - Emerging outbreak monitoring — Pools going from maintained to unmaintained in spatial clusters. Early warning system - District coverage gaps — Identify neighborhoods with low inspection coverage, high pool density, long gaps between satellite passes **Effort:** Medium. Risk scoring algorithm needs spatial joins + temporal analysis. --- ## 8. REPORTS and EXPORTS **What Acres has:** Custom branded PDF property reports, market valuation reports, CSV exports, large reports. Already in progress (PR #175/176). Could add: - District summary report: PDF with pool counts by status, detection dates, map, statistics - Custom branding: District logo/name on reports - Large batch exports: Handle entire district in one export **Effort:** Low (extensions of existing export work). --- ## 9. MOBILE APP **What Acres has:** iOS + Android native apps. Offline maps, parcel lookup on-the-go, geotagged photos, waypoints, route tracking, driving directions, offline mode. Overlaps with Nidus Notes (iOS field technician app): - Pool lookup mobile: Field inspectors look up pool details, condition history, owner info on-site - Geotagged photos: Already planned for Nidus Notes - Offline mode: Download pool data for rural areas with spotty coverage - Driving directions: Navigate to specific pools — deep link to Apple/Google Maps - Route planning: Optimize daily routes based on pool assignments **Effort:** High for full app, but Nidus Notes iOS exists — extending it is incremental. --- ## 10. MARKET INDICES (Home Builder Index, Data Center Index) **Nidus Pool Index** — District-level trends: - Pool counts by condition over time (time series chart) - Detection rate (new pools found per satellite pass) - Compliance rate (pools going from unmaintained to maintained) - Hotspot migration (where problem pools cluster over time) A district health dashboard with trend analytics — valuable for managers reporting to city/county government. **Effort:** Medium. Time-series aggregation + charting library. --- ## 11. DATA INTEGRATIONS and API **What Acres has:** API integrations (enterprise add-on), SOC 2 Type II, embeddable maps, partner program. - Public API — Expose pool detection data for district integration. Extension of existing internal APIs - Embeddable maps — Districts embed pool maps on public websites - SOC 2 — Relevant if districts have compliance needs **Effort:** Medium-High. API gateway + auth + rate limiting. --- ## 12. SKIP TRACING (Owner Contact Data) **What Acres has:** Phone numbers and email addresses for landowners. Districts need to contact pool owners about violations. We have names from tax rolls but not phone/email. Integrating a skip tracing API would let districts send automated violation notices. **Effort:** Medium. Third-party API + TCPA compliance. --- ## 13-14. SITE PLANNER and COMPETITIVE INTELLIGENCE Image overlay is relevant (treatment plan diagrams on satellite view). Site Planner (lot yield) and 3D maps are not relevant. Neighboring district activity tracking is a follow-on, not MVP. --- ## PRIORITIZATION SUMMARY | Feature | Acres Feature | Relevance | Effort | Priority | |---|---|---|---|---| | Enhanced Pool Detail Panel | AI Parcel Summaries | High | Medium | High | | Map layer library (flood, water) | Layer Library | Medium | Low | Medium | | Pool watchlists / saved filters | Prospecting / Lead Lists | High | Medium | High | | Team collaboration (comments, tags) | Portfolio Management | High | Med-High | High | | District health dashboard / trends | Market Indices | High | Medium | High | | Mobile pool lookup | Mobile App | High | High | High | | Risk scoring (mosquito hazard) | Risk Management | Medium | Medium | Medium | | Owner contact (skip tracing) | Skip Tracing | Medium | Medium | Medium | | Embeddable public pool maps | Embed Maps | Medium | Low-Med | Low | | Image overlay / boundary drawing | Mapping Tools | Low | Low | Low | | Public API | API Integrations | Low | Med-High | Low | | 3D maps / Site Planner / Zoning | Various | Not relevant | - | Never | --- ## IMMEDIATE TAKEAWAYS Three features from Acres that would most benefit Nidus Reveal right now: 1. **Pool Risk Scoring** — Combine condition + duration + proximity to sensitive sites into a weighted score. Surfaced in the pool detail panel. Turns raw detection data into actionable enforcement priority. 2. **Saved Filters / Watchlists** — Let district users save complex filter combinations ("pools green >2 weeks, area >400sqft, in zone 7") as named watchlists. Acres does this with lead lists. We have the filter controls already mocked up. 3. **District Dashboard** — Time-series trends of pool counts by status, detection rates, compliance rates. Acres' home builder index concept but applied to mosquito control KPIs. High-value for district managers reporting to city councils. None of these would require a fundamentally different architecture — just incremental work on top of what we're already building. Okaly-dokely, let me know which of these you'd like me to dig deeper on or start designing a spec for!