Working With Forsyth County NC GIS Data: What Actually Works
Forsyth County runs their GIS through Esri's infrastructure, which means most of their public-facing tools sit on ArcGIS Online. If you're trying to pull parcel data, aerial imagery, or elevation layers for projects around Winston-Salem and the surrounding area, you're going through their web map first before you ever touch raw data. The workflow is straightforward until it isn't. The county's main portal is at forsythcounty.org/gis. From there you get to their web viewer, which has parcel layers, zoning, flood zones, and transportation data pre-loaded. It's decent for quick lookups. Not great for bulk extraction. If you need actual datasets, the county publishes shapefiles and geodatabases through their data portal. The parcel layer is the one people always want. It updates quarterly from the assessor's office, and the attribute table is fairly complete. Tax parcel IDs, ownership info, land value, building value, zoning codes. Standard stuff. The geometry is in NAD 1983 HARN StatePlane North Carolina FIPS 3100 feet. Most people forget to check that and try to plot everything in WGS84, which throws your coordinates off by a few meters. Don't do that.
Aerial imagery is available through the county at roughly 1-foot resolution for most of the urbanized area. Rural portions drop down to 3 feet. The imagery is orthorectified, which matters if you're doing any kind of measurement work. But it's usually a couple years old at best, so if you need something current for a site plan, you're better off pulling NAIP data from the USDA or using your own drone. One thing the county does well is their elevation data. They have LiDAR coverage for most of Forsyth County, and you can access it through their web map or download it as point clouds. This is actually useful. A lot of counties don't bother keeping their LiDAR current, but Forsyth has run at least one full revisit cycle since the original acquisition. The point density is decent for general topographic work. Not survey-grade, but enough for drainage analysis and cut-and-fill estimates. I ran into a problem last year where I was trying to join parcel data to a flood zone layer for a client. The parcel layer had a "FIRM Zone" attribute field, but the values didn't match up with the actual FEMA flood maps. Turns out the county's parcel attributes are self-reported from the assessor's data and haven't been synced with the latest FIRMs. The workaround was to pull the FEMA map overlays separately and do the join by geometry instead of by attribute. Took about twenty minutes with a spatial join in QGIS rather than relying on whatever the county pre-populated. Saves you from making assumptions about what the attribute field actually represents.
For zoning data, the county publishes separate shapefiles for each zoning district. The attribute table includes the district code and a description field. That's about it. No cross-reference to the actual zoning ordinance text, which would have been helpful. If you're doing anything beyond a basic overlay, you'll need the PDF ordinances from the planning department anyway. The water and sewer infrastructure layers are another story. They exist but they're not particularly detailed. You'll get trunk mains and major laterals, but if you're designing a subdivision, don't count on the GIS data to tell you exactly where your tie-in points are. Call the county engineering department directly. The GIS mapper won't have that level of detail and probably hasn't visited the valve in question. Right-of-way data is available but it's sourced from multiple agencies. The county maintains its own road network, but municipal streets within Winston-Salem's city limits are maintained by the city. There are occasional gaps where the county layer just stops at the municipal boundary. If you're working near the edge of the county, check both sources. I've seen projects where someone used only the county data and ended up routing a driveway through city property because the parcel boundaries didn't align perfectly at the edge.
Get the Full Details
Downloads are free but there's no API for bulk operations. You export individual layers as shapefiles or geodatabases through the web portal. The export function works, but large datasets like the full parcel layer or high-resolution LiDAR will time out if your connection is slow. Use a wired connection. I usually do my exports overnight and come back to a completed file in the morning rather than fighting with a browser session that drops after three minutes of active processing. For automated workflows, the county does publish some of their data through Esri's ArcGIS Hub, which means you can connect directly to their hosted features if you have an ArcGIS account. That's faster than downloading shapefiles every time you need fresh data. The catch is that the hosted features don't always update on the same schedule as the downloadable files. There's sometimes a two to four week lag between when the county updates their source data and when it reflects in the hosted layer. Factor that in if accuracy matters for your project timeline. The tree canopy layer is one of those datasets people find unexpectedly useful. Forsyth County has an annual tree canopy map derived from aerial imagery classification. It's not hyper-accurate for individual trees, but it's solid for ward-level or neighborhood-level analysis. Stormwater management plans often reference it, and it's useful for heat island studies too.
There's no mobile app for field data collection from the county side. If you're doing field verification work, you'll want to load the layers you need into Survey123 or ArcGIS Field Maps yourself using the county's hosted feature services as basemaps. The county doesn't provide a turnkey field tool, which is standard for most counties of this size. One counter-intuitive thing about working with this data: the more precise you try to be, the more you should ignore the county's on-screen measurement tool. It's fine for rough estimates. Not fine if you need to demonstrate compliance with setback requirements or calculate lot area for a plat. The Web GIS measurements are based on the displayed projection, which may not match the legal description's coordinate system. Download the parcel shapefile, project it properly, and measure from that. Five extra minutes of setup and you avoid a field review issue later. The county also has a historical imagery arc in their web map. It goes back maybe ten to fifteen years depending on the area. Useful for tracking development patterns or verifying when a parcel was subdivided. Not reliable for anything older than that. If you need to prove what was on a piece of land in 1995 or earlier, you're looking at Sanborn maps or county deed records, not the GIS imagery archive.
Practical Steps For Getting Started
Go to the GIS portal. Register for a free account if you want to save custom maps or export data. Browse to the layer list. Start with parcels and zoning for most projects. Add flood zones and elevation if your work involves grading or drainage. Download the spatial reference information before you open anything in another program, because the metadata isn't always easy to find once you're exporting. Use QGIS for anything beyond quick viewing. It handles the coordinate systems correctly and lets you do the spatial joins without fighting Esri's web interface. The county data is standard Esri format, so it opens clean. No weird projections or corrupted geometries that I've noticed in the few years I've been pulling from it. If your project requires legal descriptions or boundary verification, go to the tax assessor's office or the register of deeds. The GIS parcel data is for planning and analysis purposes. It's not a substitute for a surveyed boundary. The county will tell you that in their disclaimer, but people skip the disclaimer every time.
