GIS mapping
RangerOS puts patrols, zones, burns, sightings and land access planning maps on one workspace. Import property and site boundaries from GeoJSON or KML, export planning maps as GeoJSON or KML for company reports, and keep working with ArcGIS if that's where your GIS lives.
Search intent
Sightings, incidents, feral and weed control logs and fire hotspots show on map views, with the date, time and coordinates on each marker. Patrols keep their GPS tracks, and burns keep their polygon boundaries. Property and site boundaries also show together on one overview map, with road and satellite views.
Import GeoJSON for zones and boundaries, bring in property and site boundaries from GeoJSON or KML, or draw patrol zones and burn areas directly in RangerOS. Drone data can sit with the field records it relates to, and RangerOS works with ArcGIS if that's where your program's GIS lives.
Land access planning covers areas of interest, protected areas, landmarks and cultural sites. Export only the records you mark as shareable as GeoJSON, KML, SVG or a printable HTML report. Leave sensitive records out, strip identifying text, or shift markers by a set distance so company maps don't hand over exact cultural-site locations. Exports are planning information only. They don't grant land access or approval to build.
Patrol zones and burn boundaries are sent to the mobile app for offline map use, so rangers still have them when there's no reception.
No. RangerOS is ranger operations software with GIS mapping built in, and it works with ArcGIS for teams that use it for deeper spatial analysis. RangerOS isn't made by or affiliated with Esri.
Yes. RangerOS supports GeoJSON import for zones and boundaries, properties and sites can be imported from GeoJSON, KML, CSV or XLSX, and you can draw patrol zones and burn areas in the app. Selected land access planning records can also be exported as GeoJSON, KML, SVG or a printable HTML report. Only shareable records are included, and you can protect sensitive locations before export. The file is planning information, not a permit to enter or build.
Yes. Drone data can be kept with the patrols, burns and control work it belongs to. Book a walkthrough to see how it fits your program's drone workflow.