Use case
Right for a park.
Not for a whole city.
Citywide urban forest asset management is a different job than what LogLog does — that's TreePlotter, TreeKeeper, or Esri's Tree Management territory, with GIS staff and a procurement process behind it. LogLog is built for the plan-based job: one park, one right-of-way segment, one contract survey with a defined boundary and a client waiting on a deliverable.
Where this actually fits
A parks department contracts out a survey of one park's trees ahead of a budget ask. A small municipality's public works crew needs a right-of-way tree inventory for a street reconstruction project. A contractor is hired to survey trees along a defined segment for a storm-response readiness review. All of these have a bounded site and a plan you can load — the exact shape of job LogLog handles well.
Load the parcel map or park boundary plan, pin every tree, record condition and risk fields the same way a consulting arborist would for a private client. Export gives you a clean spreadsheet — species, DBH, condition, risk rating — that a small public works office can use directly, or hand off to whoever compiles the annual budget request.
Where it stops being the right tool
LogLog is plan-based capture, not a citywide GIS asset-management system. It has no public-facing map, no coordinate-system-aware GPS layer, no work-order tracking tied to 311 requests, and no integration with a municipal GIS server. If your department is maintaining a live, map-based inventory of every street tree across the whole city with multiple crews updating it continuously, that's a genuinely different product category — the enterprise GIS platforms exist for exactly that scale and workflow.
Where LogLog earns its place is the bounded job: a defined site, a plan you can load, a survey with a start and an end date, and a deliverable at the finish. If that's your job, it's a much lighter, cheaper way to run it than standing up an enterprise GIS contract for a single park.
Multiple crews on one survey
A team account lets a small crew split a park between two or three people, each working their own section of the plan. Trees merge into one project once everyone's back online, since sync resolves per tree rather than per whole document.
A defensible record
Condition, risk rating, and photos tied to a dated survey give a public works office something to point to if a tree's condition is ever questioned after the fact — a documented inspection with a date, not a memory.
Built for the budget-cycle deliverable, not the GIS server
A small municipality's annual budget ask usually needs one thing: current, credible numbers on tree condition and count to justify a maintenance line item. LogLog's export — a spreadsheet with condition and risk fields per tree — is built to feed that exact ask, without requiring the department to first stand up a GIS platform just to produce one report. If the request grows into an ongoing, map-based public asset system later, that's the point to evaluate an enterprise GIS platform — LogLog isn't trying to grow into that role.
The old way
Paper forms across multiple crew members, a data-entry contractor to reconcile them afterward, and an inconsistent spreadsheet by the time it reaches whoever's writing the budget request.
With LogLog
Every crew member's records land in the same structured format from day one. No cleanup pass, no reconciliation, no data-entry contractor.
See how a small crew shares one survey on team accounts. Considering an enterprise GIS platform instead? Read TreePlotter alternative — for small jobs. Doing campus or estate work instead of a public contract? See campus and estates.
A good fit for the contractor bidding the job, too
A private consulting firm bidding on a municipal contract for a bounded survey — one park, one corridor — can run the whole engagement on LogLog without needing the municipality's own GIS licensing or training. Deliver a clean spreadsheet and annotated plan at the end of the contract; what the municipality does with that data afterward is their call.
Run the bounded job without the GIS overhead.
Free forever for solo use. See if it fits your next park or right-of-way survey.