BMAP Uplift Project Release Details and Resources
Project updates
See the latest project updates.
Surveys
- What’s in a name? (Naming the new BMAP System) - closes 31 July
- Engagement Survey - BMAP Uplift Project - closes 31 July
- Release 1 User Survey - BMAP Uplift Project - closes 14 August
- Next Gen BMAP Suggestion Box – Fill out form - ongoing
Engagement Opportunities
BIP Pilot Release 1
| Date | Event | Location |
|---|---|---|
| 11 August | Wireframe/User Interface Session with Nova Systems | Teams online |
| 14 August | Wireframe/User Interface Session with Nova Systems | Teams online |
| 14 August | State Bushfire Coordination Committee | ESS Headquarters |
Note: Schedule subject to change.
Drop-in sessions FAQs
What is this system?
The BMAP BIP Pilot — Release 1 is an initial web portal and mapping interface to support bushfire management planning, stakeholder engagement and early-stage risk assessment workshops.
Who is this release for?
Stakeholders involved in Bushfire Management Committees, deputies, nominated organisational subject matter experts and invited users who will participate in workshops, review maps and provide feedback.
Is the pilot interface final?
No. The Release 1 interface is a pilot based on an existing NSW RFS prototype and will be contextualised for South Australia. The layout, available tools and datasets will be refined through upcoming engagement with the supplier and stakeholder feedback.
Access and learning resources
How do I access the portal?
Stakeholders should have received login details. The landing page hosts release notes, surveys, micro lessons and PDF instructions.
Are there training materials and support options?
Yes. Short micro-lessons (video plus PDF) cover navigation, layers, comments, drawing/measuring, pilot areas, and report generation. One-on-one sessions and dedicated support can be arranged for organisations that want a deeper walkthrough.
Where can I give feedback or request features?
Use the Release 1 user survey, the engagement survey, the ongoing suggestion box, email the project team or raise items during drop-in sessions. Include steps to reproduce bugs, screenshots and browser/device details when reporting issues.
Map tools and user actions
What map tools are available in Release 1?
- Base maps: OpenStreetMap, SA street maps, topographic and satellite imagery with labels.
- Layer controls: toggle on/off, opacity, swipe, reorder layers using arrow keys.
- Favorites: add frequently used layers to your favourites for quick access.
- Measure: length and area in metres, kilometres and hectares. Measurements are temporary.
- Draw / Edit / Remove: point, line, polygon, circle. Saved pilot areas persist.
- Comments: add, reply, like; users with permissions can action, reject, block replies or delete.
- Pilot areas: draw polygons and add attributes including name, status, description, standards, methodologies and risk drivers.
- Reports: map/legend exports, pilot areas list, feedback/comments export.
Can I search by address, road name or coordinates?
- Address search: the current search works best with a full physical address. Street name only searches are limited.
- Latitude/Longitude: there is no dedicated lat/long input field yet. The map displays decimal degree coordinates in the status bar, which you can use to locate positions. Improving search functionality is on the feedback list.
How do comments work and when should I use them?
Use the comments tool to flag missing assets, note local changes, provide context or raise data validation issues. Comments show author, date/time, replies and likes. Comments are useful during the data validation stage and for ongoing collaborative review.
Are measurement drawings persistent?
No. Measurement lines and temporary drawings are non-persistent and disappear when you navigate away. Pilot areas and saved features persist when saved through the pilot area workflow.
How do I create and manage pilot areas?
Draw the polygon, complete the attribute form with name, status (Drafted; Supported by BMC; Approved for public exhibition; Modified after exhibition; Endorsed final; Withdrawn), description, standards/methodologies and risk drivers. Saved pilot areas appear in the left-hand list. You can edit attributes, change status and delete pilot areas. Deleting a pilot area prompts for a reason which is logged.
Data, layers and risk information
Are the datasets in Release 1 real or mock data?
Many layers in Release 1 are mock or demo data to demonstrate functionality. Real, authoritative datasets will be ingested during the data validation and production stages.
Will other agency plans and datasets be included?
Yes. The project team is working with DEW, CFS and other agencies to incorporate state authoritative datasets for assets, parks, fire management zones and other relevant layers.
Can I request my organisation’s datasets be added?
Yes. Submit available datasets via email, the surveys or the suggestion box. The team will review datasets for inclusion subject to relevance, licensing and technical fit.
Will fire history and prescribed burns be included?
Yes. Fire history and prescribed burn information are planned to be incorporated. Symbolisation and display conventions will be refined with stakeholder feedback.
What fuel data underpins the risk assessment?
The initial risk assessment will use a CFS-procured fuel data layer in an AFDRS compatible format as the single source of truth. Implementation reporting will update residual fuel where treatments occur.
How are cropping and land use represented?
Asset layers include land parcel and land use data sourced from valuation and cadastre datasets that indicate cropping and livestock parcels. These datasets inform fuel modelling and economic impact assessments.
Will the system show the effect of treatments such as prescribed burns?
Yes, when the risk assessment methodology and implementation reporting are applied. Displaying treatment effects depends on the scale and extent of treatments and on re-analysis of risk rasters. This capability is tied to later releases and the risk methodology rather than the UI alone.
Will existing BMAP polygons and asset points be migrated?
Existing BMAP asset points and some polygons will be considered during data validation. Many legacy assets are expected to be represented in state authoritative property and land use datasets. Migration of legacy polygons is possible but depends on data format and ingestion approach.
Assets, environmental values and cultural information
Will environmental and heritage assets be included?
The team is sourcing environmental and heritage datasets through state data sharing arrangements. Initial Release 1 contains a light set of environmental layers. Stakeholders should submit suggestions for specific datasets to include. Inclusion of cultural heritage and First Nations knowledge will be developed in partnership with First Nations representatives and scoped for culturally safe approaches.
How will community assets be represented?
Community assets such as schools, hospitals and care facilities are planned as part of the asset layers. The system supports a two-stage assessment approach: a landscape scale risk assessment to identify priority areas and a site level assessment for critical community assets where a more detailed, bespoke evaluation is required.
How will biodiversity and conservation sites be handled?
Environmental assets have two roles: they are values at risk and they may require bespoke treatment approaches. The project will work with biodiversity and conservation stakeholders to identify which environmental datasets should be included and how they should influence strategy development and risk modelling.
Roles, permissions and reporting
Who can add or edit content?
BMC members and deputies will be granted BMC member permissions. Organisations can nominate additional SMEs with comparable privileges. Editing and deletion rights are controlled and may vary by project stage.
Can I run reports filtered by organisation, action type or administrative boundary?
- Release 1: Map and legend exports for selected areas or the full BMA, pilot areas export and feedback/comments export.
- Release 2: Implementation planning and activity sequencing by organisation and year.
- Release 3: Full reporting and status tracking including organisational filters, completion status and standardised outputs for reporting to SBCC and ministers.
What report types are available now?
- Map report: A3/A4 portrait or landscape for a selected area or full BMA.
- Legend only report: Exports the active legend for printing or reference.
- Pilot areas report: Lists all pilot areas with attributes and map thumbnails.
- Feedback report: Exports all comments and replies for a BMA.
Imagery, updates and data currency
What aerial imagery is used and how often is it updated?
The portal uses state authoritative imagery via existing data sharing agreements. Commercial near real time imagery such as quarterly Nearmap is unlikely to be provided to all users due to licensing and cost. The team will seek to increase refresh frequency where feasible.
How do I flag missing or out-of-date data such as new subdivisions?
Use the comments tool, submit datasets via email or the surveys, or add feedback through the suggestion box. Local subject matter experts and BMC members are encouraged to flag discrepancies during the data validation stage.
Engagement, stages and next steps
What are the rollout stages and what happens in each stage?
- Stage 1: Familiarisation with the software and basic functionality.
- Stage 2: Define system behaviour for producing BMAPs and develop implementation planning features.
- Stage 3: Produce BMAPs and deliver full reporting and implementation tracking. Data validation and authoritative dataset ingestion occur during Stage 2.
How will stakeholder input be used?
Feedback from surveys, drop-in sessions and direct submissions will shape the user interface, dataset selection, reporting requirements and the approach to integrating cultural and environmental values.
Practical tips and quick guidance
How should I report bugs or usability issues?
Use the Release 1 user survey or suggestion box and include steps to reproduce, screenshots and the browser/device used.
How do I request a dataset or raise a data gap?
Email the project team, use the suggestion box or raise it in a drop-in session. Provide dataset metadata, custodianship and licensing details where possible.
Who can I contact for more help or a tailored session?
Contact details are on the SBCC Webpage. The project team can arrange dedicated walkthroughs for organisations.