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.
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.
The problem
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.
WHAT THIS COSTS
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
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.
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.
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.
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.
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 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
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.
United States Geological Survey
Elevation and hydrography
Federal Emergency Management Agency
Flood hazard layers
Massachusetts Department of Transportation
Roads and traffic counts
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
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.
Overlay FEMA hazard areas on the built model and read off which roads, parcels and utility segments sit inside them.
Study assessed value, density and condition together so the allocation reflects what the money protects, not only what is worn out.
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
FOGLE is built for the people who hold the capital plan and answer for it in public.
Test a zoning change against traffic, density and hazard exposure before it reaches the board.
Sequence paving, drainage and water work on one calendar instead of three.
Check a design against the surrounding systems with the source layers open beside it.
Feed existing shapefiles, GeoJSON and parcel exports into a model the whole department can read.
Questions
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.
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.
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.
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.
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.
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
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.comAutomated answers can be wrong. Do not send personal or sensitive data.