Property Intelligence Source Schedule
This schedule defines the standard source and field boundary for noise-intelligence-v1, flood-intelligence-v1, bushfire-screening-v1 and full-property-intelligence-v1. The response-specific inventory in meta.attribution.sources, coverage status and source currency identify what actually contributed to an individual response and must be read with this schedule.
1. Product and source boundary
| Product | Licensed components | Principal source classes | Required interpretation |
|---|---|---|---|
| Noise Intelligence | scores.noisescores.aircraft_noise | Published road networks and traffic counters; government/public-transport GTFS; civil ANEF and Defence aircraft contours; terrain, land-cover and built-form context; OpenStreetMap-derived nearby source context where identified in the response. | Modelled screening, not a measurement or acoustic compliance assessment. Read confidence and measured-validation fields. Aircraft assessment and traffic/GTFS coverage vary by jurisdiction. |
| Flood Intelligence | scores.floodhazards.flood | National terrain, drainage, water-proximity and rainfall context; jurisdictional flood controls; 55 production study rasters (48 Brisbane and 7 NSW); Newcastle published H1–H6 hazard where covered. | National screening is not a nationwide hydraulic model. Official modelled depth exists only where a production study raster covers the point. Missing depth is not zero depth or zero risk. Newcastle classes are not converted to metres. |
| Bushfire Screening | scores.bushfirehazards.bushfire | Deliverable jurisdictional bushfire-prone mapping; ESA WorldCover vegetation/fuel context; government/Geoscience Australia elevation inputs; available published fire-history inputs. | Screening only. Official mapping and the model score remain separate. Fire history is not integrated uniformly. A preliminary indicative BAL band (with range and confidence) is included, delivered with a mandatory disclaimer; certified BAL is excluded, and building approval, construction and insurance decisions remain excluded uses. |
| Full Property Intelligence | Nine Property Core factual groups; four explicit Noise/aircraft/Flood/Bushfire score components; suburb_intelligence; property_core. | The three schedules above plus deliverable G-NAF address identity, jurisdictional cadastre/planning/open-register sources, council and state DA registers, official facility and infrastructure sources, and ABS statistical/Census sources used by Core or Suburb. | Only the explicit versioned union is licensed. There is no scores wildcard. Source- and field-level gates continue to withhold restricted geometry and other non-deliverable material. |
2. Full Self-Serve closed selectors
full-property-intelligence-v1 grants exactly: das, poi, planning, hazards.bushfire, hazards.flood, hazards.coastal, hazards.landslide, hazards.fire_history, hazards.contaminated, hazards.landfill, hazards.groundwater_restricted, hazards.groundwater_vulnerability, environment.contaminated_nearby, environment.historical_business_nearby, environment.landfill_nearby, environment.licensed_activity, environment.licensed_activity_nearby, environment.petroleum_storage, environment.petroleum_storage_nearby, environment.soil_regional, environment.protected, environment.aboriginal_heritage, environment.soil, environment.world_heritage, environment.threatened_species, environment.ramsar, environment.national_heritage, environment.koala_habitat, environment.key_ecological, environment.indigenous_protected, environment.cultural_heritage, environment.epbc_referral, environment.bioregion, environment.bv_map, environment.bio_important, environment.commonwealth_heritage, transport, utilities, administrative, public_housing, scores.noise, scores.aircraft_noise, scores.flood and scores.bushfire, plus the separate suburb_intelligence and property_core capabilities.
No top-level hazards, environment or scores wildcard is granted. Rights-gated factual official register and nearby context can therefore be delivered where listed above, while future factual categories and every unlisted score remain closed until a new product version is accepted.
3. Explicit Full exclusions
scores.solar, scores.contamination, scores.heat_island, scores.view_quality (Landscape Openness) and scores.walkability Preview/Pilot are not included in Full. Full and Bushfire Screening include a preliminary indicative BAL band (with range and confidence), delivered with a mandatory disclaimer. Neither includes a certified BAL assessment, and the preliminary band cannot be used for building approval. A factual official hazard/register entry delivered inside Property Core does not create a licence to the excluded Contamination Screening score or product.
4. Field and geometry gates
Underlying rights are applied per source and field. WA cadastral geometry, restricted flood or consultant geometry, raw Overture rows, model-internal values and any source marked withheld are not made deliverable by buying a broader product. Geometry is returned only where the key, request and individual source all permit it. An empty geometry array can therefore mean withheld or unavailable and must be read with meta.geometry and coverage status.
5. Attribution
The subscriber must preserve the attribution emitted for fields it uses. OpenStreetMap-derived names or coordinates are subject to the Open Database License 1.0 and require “© OpenStreetMap contributors” on produced works; a publicly used derived database may carry share-alike obligations. Government and Creative Commons sources require the response-specific publisher credit and any change notice supplied by the API. DA Leads model outputs remain subject to the accepted Self-Serve licence.
6. Currency and coverage
Source currency follows publisher refresh schedules and may vary across jurisdictions. The API reports response-level source dates where known and does not invent a date where a publisher supplies none. “No hit”, “not assessed”, “not integrated”, “partial coverage” and “source unavailable” are distinct states and must not be collapsed into a clear result.
7. Version control
This file is immutable for the version shown above. Adding a source, expanding a licensed field set or commercialising a Preview/Pilot requires a new schedule and, where scope changes, a new product version. Technical deployment alone does not amend this schedule.