Shapefiles are the file type that is uploaded to your organization's Geography and will define your organization's service area. If you are looking for information on how to add a Shapefile to your organization, take a look at the Prepare and Upload a Shapefile article.
Before You Begin
Your shapefile must meet the following requirements:
Include one shapefile bundle in a single ZIP archive. Send the full bundle: .SHP, the shapefile itself, holding the geometry; .SHX, the shape index; .DBF, the attribute database; and .PRJ, the projection definition. The upload requires the .SHP and .SHX files. The .PRJ file is required unless you select Process as EPSG 4326 projection (WGS84) during upload. The .DBF file is optional, but without it you must enter auto as the Title Attribute.
Use the WGS84 coordinate system, also identified as EPSG:4326 or SRID 4326. WGS84 is the World Geodetic System, and SRID is a spatial reference identifier.
Use Polygon geometry for service-area boundaries. If your source data carries Z (elevation) or M (measure) values, ask your GIS staff to remove them before exporting. Files with these values are rejected.
Make sure every polygon is valid. Ask your GIS staff to repair self-intersecting polygons and other geometry errors before exporting. A single invalid polygon can stop the upload partway through.
Include no more than 30 features. The standard upload accepts up to 10 features unless you select Allow more than 10 features.
Important Note:
Polyline files create a single road corridor, not separate boundaries. If you upload a Polyline shapefile, such as road or highway centerlines, the upload combines all of the lines into one geography and buffers it into a corridor around them. This is useful only if a single corridor of fixed width is what you want. Otherwise, convert the lines to polygons before uploading. Keep the following in mind:
The corridor width is fixed and cannot be changed. It extends roughly 100 meters (330 feet) on each side of the lines, and is somewhat narrower for north-south lines.
The result is always one geography, named "Road Shapefile Uploaded" followed by the date, regardless of the Title Attribute you enter.
The feature limit applies to the number of features in your file before the lines are combined. A file with 40 separate road segments is blocked even though it would produce one geography.
PolylineZ and PolylineM geometry is rejected.
A file with several line features may display a message saying duplicate polygons were found and one unique polygon was imported. This message is expected for Polyline files.
If you need a boundary of a specific width, ask your GIS staff to buffer the lines into polygons at that width before uploading.
Supported Geometry
Polygon (Esri shape type 5) is the only supported type for service-area boundaries. A single Polygon feature can contain multiple parts, rings, and holes. PolygonZ (15) and PolygonM (25) carry elevation or measure values and are rejected with an error naming the type. In ArcGIS Pro, turn off Z and M values in the environment settings before exporting. Point, MultiPoint, and MultiPatch are rejected before any geographies are created. Polyline (3) is accepted but behaves differently. See the note above.
For additional technical information about the shapefile format, refer to Esri's shapefile technical description.
Geometry Complexity and Performance
CivicPlus does not simplify boundaries after upload, so simplify the geometry before you export it. Use the lowest level of detail that still supports your operational needs, and keep each resulting geography well below approximately 150,000 vertices. This is a practical guideline, not a guarantee. Very detailed boundaries can load slowly and make the map unresponsive, so test the result before relying on it.
Complex boundaries mainly slow processing, and very large ones also load slowly on maps. Complexity can slow the upload itself, saving or editing a geography, assigning and filtering requests by geography, targeting notices to residents inside a geography, and displaying the boundary on maps. Vertex count is the largest factor, but the number of features, multipart geometry, rings, holes, and overall shape matter too. A file with only a handful of features is not necessarily a simple one.
Work with your GIS staff to simplify the geometry while preserving the boundary's intended meaning. Keep a copy of the original data and validate the simplified version before using it in production.
Troubleshooting
The shapefile is rejected
Check the requirements in the Before You Begin section. The error message names the unsupported type (for example, PolygonZ). Also confirm that:
The . PRJ file describes a projection the system recognizes, or you selected Process as EPSG 4326 projection (WGS84).
The Title Attribute matches an attribute in the .DBF file, or is set to auto. If the shapefile has no .DBF file, use auto.
The upload fails with "Shapefile errored while processing," or only some geographies were created
A polygon with self-intersections or other invalid geometry can stop processing partway through. Geographies created before the problem feature remain in your organization. Ask your GIS staff to repair the geometry, then check for partial results from the earlier attempt before uploading again to avoid duplicates. If you are unsure what was created, contact CivicPlus Support.
The upload takes too long, or maps and workflows are slow
The geometry may be too complex even if the shapefile is structurally valid. Ask your GIS staff to reduce the number of vertices and simplify multipart geometry, rings, and holes. If your service area follows a dense street grid, upload a single simplified boundary, such as a citywide or countywide polygon, rather than one that traces every street. A simpler boundary includes locations that a street-traced boundary would have excluded, so confirm it still makes the eligibility distinctions you need.
The geography appears in the wrong location
Do not use the geography for production routing. Confirm the source coordinate system with your GIS staff. Select Process as EPSG 4326 projection (WGS84) only when the underlying coordinates already use EPSG:4326.
The geography appears as a single narrow corridor
The source shapefile contains Polyline features. See the Important Note about Polyline features in the Before You Begin section, and ask your GIS staff to convert the lines to polygons if you need separate boundaries or a different width.
If you continue to experience problems, contact CivicPlus Support. Include the shapefile ZIP archive, your organization name, the approximate time of the upload, and any error message you received.
Need Help?
View answers to questions frequently asked by users, or contact Support if you have additional questions.
Frequently Asked Questions
Can I use a highway or street shapefile as my geography boundary?
Usually not as is. Road networks are most often stored as centerlines, which produce a single fixed-width corridor rather than boundaries. See the Polyline note above.
If your street data is already polygons, such as a right-of-way, pavement, or curb-to-curb layer, it can be uploaded, but these layers are usually drawn one feature per segment, which exceeds the 30-feature maximum, and they carry far more detail than a service-area boundary needs. Ask your GIS staff to dissolve the segments into a single boundary and simplify it. For most dense street networks, a simplified citywide or countywide boundary is the better choice.
Can we use more than one boundary?
Yes. Each agency in your organization can have its own shapefile and geography, so departments such as Streets, Parks and Recreation, and Code Enforcement can each work from a service area that matches how they operate. Boundaries are independent of one another, with no parent and child relationship, so separate boundaries also mean configuring request types separately for each agency.