Problem How it works Data sources Use cases Who it is for Questions Sign in Create account Request a demo

Every system in the town, in one 3D model

FOGLE layers a town's real infrastructure and risk data into a single interactive 3D model so planners can see how one decision affects everything else.

Roads, zoning, traffic, water and flood risk currently sit in separate systems. Second order effects surface after the money is spent.

Built on USGS, FEMA, MassDOT and NLCD public data.

ZONING / Districts as adopted in the zoning bylaw.
Assembling model
Drag to rotate. Scroll to zoom.
Interactive illustration of the FOGLE model. The geometry stays fixed while the colour of every parcel, road and water body changes with the selected view mode.

The problem

Municipal data is accurate and disconnected

Planning and public works departments hold good records. Those records live in different systems, on different schedules, in different formats. The interactions between them stay invisible until a project is already under way.

  • Road data sits apart from flood maps. A resurfacing schedule is set without knowing which segments sit inside a hazard area.
  • Zoning sits apart from traffic. A density change is approved without the count data for the corridor it feeds.
  • Water systems sit apart from both. Main replacements and street work land in different years on the same street.
  • Failure risk is discovered late. The cost of a missed interaction lands in the next capital cycle.

WHAT THIS COSTS

Decisions get made one layer at a time

A planner comparing a paving list against a flood map against an assessing roll is doing that comparison by hand, in three windows, from three exports of three different vintages. The comparison is slow enough that it often does not happen at all, and the result is a capital plan that treats each system as if it stood alone.

FOGLE puts those layers on one geometry so the comparison takes a click.

How it works

One model. Switchable view modes.

FOGLE assembles a single 3D model of your municipality from authoritative data. Every analytical view draws on that same geometry, so what you learn in one mode stays true in the next.

Assemble the model

Elevation, hydrography, road centrelines, land cover, parcels and zoning are pulled into one geometry for the whole town. Your own municipal layers are added on top.

Study it through view modes

Road condition, zoning, traffic, water, flood risk, density, income and assessed value each recolour the same model. Nothing moves between modes, so patterns line up across them.

Simulate the interaction

Change a zoning district, a road segment or a utility run and watch what the change touches. The model reports the systems and parcels affected.

Predict where it fails

The model flags where systems are likely to fail under stress, before the work is scheduled and before the budget is committed.

TRY THE VIEW MODES

The model above is live

The illustration at the top of this page runs the same idea in miniature. Drag it to rotate, scroll to zoom, and use the buttons underneath to switch view mode. Watch the geometry hold still while the reading of it changes.

The production model carries real parcel geometry, real road centrelines and real hazard boundaries for your town.

Data sources

Authoritative public data, not estimates

The base model is assembled from published federal and state datasets. Every layer keeps its source and its vintage, so any number on screen can be traced back to the agency that issued it.

USGS

United States Geological Survey

Elevation and hydrography

FEMA

Federal Emergency Management Agency

Flood hazard layers

MassDOT

Massachusetts Department of Transportation

Roads and traffic counts

NLCD

National Land Cover Database

Land cover and impervious surface

Municipal layers such as assessing records, zoning districts, pavement condition and utility networks come from your own department. Agency names identify the origin of each dataset and do not indicate endorsement.

Use cases

What departments do with it

Infrastructure planning

See how a road, zoning or utility change ripples across the other systems on the same street, in the same view, before the project is scoped.

Flood and risk assessment

Overlay FEMA hazard areas on the built model and read off which roads, parcels and utility segments sit inside them.

Capital budget decisions

Study assessed value, density and condition together so the allocation reflects what the money protects, not only what is worn out.

Failure prediction

Identify where systems are likely to fail under stress, with the load, condition and hazard layers that produced the flag shown alongside it.

Who it is for

Town and city departments

FOGLE is built for the people who hold the capital plan and answer for it in public.

Planning departments

Test a zoning change against traffic, density and hazard exposure before it reaches the board.

Public works

Sequence paving, drainage and water work on one calendar instead of three.

Municipal engineers

Check a design against the surrounding systems with the source layers open beside it.

GIS and IT staff

Feed existing shapefiles, GeoJSON and parcel exports into a model the whole department can read.

Questions

Common questions from departments

Where does the data come from?

The base model uses published federal and state datasets: USGS elevation and hydrography, FEMA flood hazard layers, MassDOT road and traffic data, and NLCD land cover. Municipal layers such as assessing records, zoning districts and pavement condition come from your department. Each layer keeps its source and vintage on record.

How long does it take to get a model of our town?

A first model built from public data is usually ready before the first call, so a walkthrough can run on your own geography. Adding municipal layers happens afterwards on a schedule agreed with your department.

What does it cost?

FOGLE is licensed as an annual subscription per municipality, scoped to the size of the town and the layers included. Every quote is written for the specific scope. Use the form below and we will send pricing and the procurement documents your finance office needs.

What file formats can we send you?

Shapefiles, GeoJSON, GeoPackage, CSV parcel and assessing exports, and standard CAD exports for utility networks. If your data lives in an ArcGIS or QGIS project, that project is a fine starting point.

Where is our data stored and who can see it?

Municipal data is held in private storage with no public object access. It is encrypted in transit and at rest and reachable only through authenticated accounts scoped to your municipality. Access is granted by your own administrator. The privacy policy sets out the processors involved.

Does FOGLE use AI, and can we check its output?

Yes. FOGLE uses machine learning to detect patterns across infrastructure layers, for example segments whose condition, load and hazard exposure combine into elevated failure risk. Every flagged result is shown together with the source layers that produced it, so staff can verify the reasoning before it informs a decision. Automated output is treated as an input to professional judgement.

Request a demo

Book a walkthrough of your town

Tell us where you work and we will build a first model from public data before the call, so the walkthrough runs on geography you recognise.

A walkthrough takes about thirty minutes. We will show the view modes on your own town, answer procurement questions, and send written pricing afterwards.

Prefer email?

Fogle.HQ@gmail.com

We reply from a person, not an autoresponder.

By sending this you agree to the terms and the privacy policy. We use what you send to answer your request. Nothing is sold.

FOGLE assistant

Automated. Answers from this site.

Automated answers can be wrong. Do not send personal or sensitive data.