I work in the field and got tired of expensive paywalls for maps, so I built my own offline GeoPDF app. The core app is 100% free.

Most people who work with maps in the field—forest road builders, land surveyors, county inspectors, ranchers managing water infrastructure—hit the same wall eventually. You buy a mapping app. You import your own GeoPDFs. Then the subscription renews, the paywall tightens, and you realize you're paying $15–30 a month just to look at data you already own.

The Reddit thread that sparked this post tells that story exactly. A forest-road coordinator got tired of Avenza's aggressive subscription model and built an offline GeoPDF viewer from scratch. Free. Open-source. No login, no recurring charge, no feature gates behind a pro tier.

That's the kind of decision that reveals something important: the mapping-software market has a structural problem. It assumes field professionals have unlimited budgets and no alternatives. Most of them don't, and increasingly, they do.

This post is about why that matters for your workflow—and what it means when the tools you actually need start appearing outside the traditional paywall ecosystem.

The Avenza Problem (And Why It's Not Really About Avenza)

Avenza Maps is legitimately useful software. It handles GeoPDFs well, syncs across devices, and has been the industry standard for field teams who need to work offline with their own map data. But the business model has tightened over the years. A single user subscription runs about $180 annually, or $15 a month. If you have a crew of five, that's $900 a year for the privilege of viewing PDFs you created yourself.

For small operations—a two-person survey team, a rancher managing a 5,000-acre spread, a county permitting office with a handful of field inspectors—that math gets ugly fast. You're not paying for features you don't use. You're paying for the convenience of not having to build an alternative.

But here's the thing: if your only use case is offline GeoPDF viewing with basic annotation, the barrier to building an alternative is lower than it's ever been. The Reddit author did it. They built FO Maps—a free, open-source GeoPDF viewer—because the existing solution had stopped making sense for their team.

The broader pattern: when a SaaS product locks essential functionality behind a subscription, field professionals start asking whether they can solve it differently. Sometimes they can. Sometimes they do. And when they do, it changes what "industry standard" means.

What Avenza Actually Does (And What It Doesn't)

Before you decide whether an alternative like FO Maps makes sense for your team, you need to understand what you're actually paying for with Avenza.

Avenza excels at:

• Cross-platform syncing: Work on a desktop, sync to your phone, pick up in the field where you left off.
• Raster and vector layer support: Import multiple map types, overlay them, toggle visibility.
• Advanced annotation tools: Draw, measure, add metadata to your field observations.
• Cloud storage integration: Save your work to the cloud, collaborate with teammates.

What Avenza doesn't do: it doesn't create your maps, it doesn't process your GIS data, and it doesn't manage your parcel records or zoning overlays. It's a viewer and a field notebook.

That distinction matters. If your workflow is "I have a GeoPDF, I need to look at it offline, I need to mark up what I see," Avenza is overkill. If your workflow is "I need to sync marked-up field data back to my office, merge it with other layers, and track changes across a team," Avenza's cloud features start to justify the cost.

The Reddit author's use case was the former: forest road building. Offline viewing. Offline annotation. No cloud sync needed. For that, a lightweight free tool makes complete sense.

The Open-Source GeoPDF Opportunity

What's interesting about FO Maps and similar tools is not that they're free—it's that they're possible.

The technical barrier to building a GeoPDF viewer has dropped significantly. The GDAL library (Geospatial Data Abstraction Library) handles the heavy lifting of parsing raster and vector formats. Web-based mapping libraries like Leaflet or Mapbox GL make it feasible to build a functional viewer in a few hundred lines of code. The author of FO Maps likely spent a few weeks on this, not months.

That means the competitive advantage for a tool like Avenza can't be "we're the only ones who can do this." It has to be "we do this better, faster, with more features, and with cloud infrastructure backing it up." If they're just relying on paywall inertia, they're vulnerable.

For field professionals, this is good news. It means you have options. If your team's mapping needs are straightforward—offline viewing, basic annotation, no cloud sync—a free open-source tool might be enough. If you need advanced features, cloud collaboration, or enterprise support, a paid tool still makes sense. But the paywall is no longer the only path.

When a Free Tool Is Enough (And When It Isn't)

The key question for your team: what does "enough" actually mean?

A free offline GeoPDF viewer is enough if:

• Your maps are already created (you're not building them in the field).
• Your team works offline or on unreliable connectivity.
• You need basic annotation and measurement tools.
• You don't need to sync field data back to a central database in real time.
• You're a small operation (1–10 people) where email-based data sharing works fine.

You probably still need a paid solution if:

• Your team is large and needs real-time collaboration.
• You need to push field observations back to a central GIS database.
• You're working with live data feeds (weather, traffic, real-time sensor data).
• You need enterprise support and guaranteed uptime.
• Your maps are generated dynamically based on queries (not static PDFs).

For a forest-road-building crew, a county surveying team, or a rancher managing water infrastructure, the first list usually wins. You have your maps. You work offline. You need to mark things up. You sync back to the office at day's end via email or a shared drive.

That's the workflow where a free tool becomes genuinely sufficient.

What Plotnode Does Differently

Here's where this connects to how we think about field-accessible geospatial data.

Plotnode is not a mapping viewer. We're a unified parcel and overlay browser—a digital twin that pulls public-record GIS layers (parcel boundaries, zoning, ADWR well registry, elevation, soils, flood overlays) into one view. We handle the data aggregation and layer unification. You don't create the maps; they're built from public records.

That's a fundamentally different problem than "I need to view my own GeoPDFs offline."

But the principle is the same: field professionals shouldn't have to pay aggressively for tools that solve straightforward problems. If you're a county inspector trying to cross-reference parcel boundaries with zoning before you visit a site, you shouldn't need a $200 annual subscription just to see what's public record anyway.

For Plotnode users, the browser viewer is free forever. You can search any U.S. parcel, pull up zoning, wells, elevation, soils, flood overlays—all without logging in, all without a credit card. The paid tier (for build planners and GIS researchers who need exports and advanced queries) exists for people who need more. But the baseline is free, because the baseline should be free.

That's the same logic that drove the Reddit author to build FO Maps. If the tool solves a real problem and the paywall is arbitrary, the market will find a way around it.

Building Your Own Tools vs. Buying Them

The forest-road coordinator who built FO Maps made a deliberate choice: instead of paying Avenza, they invested a few weeks of their own time in building something simpler and free.

That trade-off is worth thinking through for your own team.

Building your own tool makes sense if:

• You have someone on staff with software development skills (or access to a developer).
• Your requirements are narrow and unlikely to change dramatically.
• You're willing to maintain the tool yourself (bug fixes, updates for OS changes, etc.).
• The time investment pays off in under a year (for a team of 5+, that's usually true).

Buying a tool makes sense if:

• You don't have development resources in-house.
• You need professional support and guaranteed uptime.
• Your requirements are complex or likely to evolve.
• You value your team's time more than the subscription cost.

For most field teams, the answer is "a mix." Use free or low-cost tools where they exist and solve your actual problem. Invest in paid tools where they genuinely save time or enable work you couldn't do otherwise. Don't pay for features you'll never use, and don't build tools you could buy for less than the cost of the developer time.

The Reddit author's decision—build it themselves—was rational for their specific situation. For a larger operation or one without development resources, buying Avenza might still be the right call. But the fact that building it themselves was an option changes the negotiation. It means Avenza has to justify its price against a real alternative, not just against "paying nothing and using paper maps."

The Broader Shift in Field Software

What's happening in the GeoPDF viewer market is part of a larger shift: field professionals are getting less tolerant of aggressive paywalls for tools that solve simple, well-defined problems.

In the county permitting world, in land surveying, in forest management, in ranching—the teams that work with maps and land data every day are increasingly asking: "Why am I paying for this?" And when the answer is "because you have to," they start looking for alternatives.

Open-source tools, free web-based viewers, and lightweight apps are filling that gap. Not all of them are as polished as the commercial alternatives, but many of them are good enough. And "good enough" at zero cost beats "great" at $180 a year when your budget is tight.

For vendors in this space, it's a wake-up call. You can't compete on paywall inertia alone. You have to compete on features, reliability, support, and ease of use. The free alternatives are getting better, and field professionals have more choices than they used to.

What to Do If You're Tired of Paywalls

If you're in a field role—surveying, permitting, land management, forest coordination—and you're paying for mapping software you resent, here's a practical framework:

1. List your actual requirements. Not "what does the software do" but "what does my team need to do every day." Offline viewing? Annotation? Cloud sync? Real-time collaboration?

2. Audit your current tool. Are you using 20% of the features and paying 100% of the price? Or are you genuinely using most of what you pay for?

3. Look for free or low-cost alternatives. Check GitHub, r/gis, and open-source GIS communities. FO Maps is one example; there are others.

4. Do the math. If a free tool solves 80% of your problem, it's worth the 20% gap. If it solves 40%, it probably isn't.

5. If you build your own, document it. Open-source it. Let others benefit from the work. The forest-road coordinator did this, and now hundreds of field professionals have access to a tool they didn't have to build themselves.

The mapping-software market is shifting. Paywalls that made sense five years ago are starting to feel arbitrary. Field professionals have options now. Use that leverage.

Search any U.S. parcel. See zoning, wells, elevation, soils, and flood overlays before you offer. Free forever for browser viewers — pro tier when you're ready to plan a build.