Sharing, Exporting, and ArcGIS Online Integration

Why Export Formats Matter

GIS data rarely stays inside one application. Surveyors send parcel boundaries to engineers who use different software; drone pilots attach flight-area polygons to FAA waivers; clients expect deliverables they can open without a GIS license. Choosing the right export format—and verifying the result—is a core professional skill. Three formats appear constantly in surveying and geospatial work: Shapefile, GeoJSON, and KMZ. Each serves a different audience.

Shapefile

The Shapefile format was developed by Esri and became an industry-wide exchange standard decades ago. A Shapefile is not a single file; it is a collection of at least three required files sharing the same base name: the `.shp` file stores geometry, the `.dbf` file stores attribute data in dBASE table format, and the `.shx` file stores the index linking geometry to attributes. A `.prj` file stores the coordinate reference system and must accompany the set whenever you share it—without it, receiving software must guess the projection, which causes positional errors. When you zip a Shapefile for delivery, include all files.

Shapefiles have well-known limitations: field names are capped at ten characters, files cannot exceed 2 GB, and a single Shapefile can hold only one geometry type. Despite these limits, Shapefiles remain widely accepted by clients, government agencies, and older GIS platforms.

GeoJSON

GeoJSON is an open, text-based format built on JSON (JavaScript Object Notation). Because it is plain text, you can open it in any text editor and read the coordinate pairs and attribute values directly. Web developers use GeoJSON extensively; many online mapping APIs accept it natively. GeoJSON stores geometry and attributes in a single file, which simplifies sharing. One important limitation: GeoJSON uses only the WGS 84 geographic coordinate system (EPSG:4326) by specification. If your data is in a state plane or UTM projection, ArcGIS Pro will reproject it to WGS 84 on export. Verify coordinate values in the exported file to confirm the conversion was correct.

KMZ

KMZ is the compressed version of KML (Keyhole Markup Language), the format used by Google Earth and many field data collectors. KMZ files preserve geometry and basic attribute data, and they display symbology and descriptive pop-ups inside Google Earth. KMZ is not designed for precision analysis—Google Earth renders features for visualization, not measurement. Use KMZ to share boundary context with non-GIS users, for client presentations, or to communicate flight-area polygons to drone crew members in the field who have Google Earth on a tablet.

Exporting from ArcGIS Pro

In ArcGIS Pro, right-click any feature class or layer in the Contents pane and choose Data → Export Features. The Geoprocessing dialog opens. Set the Output Location and Output Name, then use the Output Format drop-down to select Shapefile, GeoJSON, or KML (which ArcGIS Pro packages as KMZ). For GeoJSON, confirm that the coordinate system will convert to WGS 84. Run the tool, then open the result in the appropriate viewer to verify geometry and attributes before delivering to a client.

Sharing to ArcGIS Online

ArcGIS Online is Esri's cloud-based mapping platform. Publishing a feature layer to ArcGIS Online lets stakeholders view, query, and in some cases edit data through a web browser without installing any desktop software. From ArcGIS Pro, sign in to your organizational account using Project → Sign In. In the Share tab, select Web Layer → Publish Web Layer. Give the layer a clear name, choose Feature as the layer type, set the sharing level (organization or public), and click Publish.

After publishing, open ArcGIS Online in a browser, locate the layer in My Content, and open it in Map Viewer. Configure the pop-up by clicking the layer options and selecting Configure Pop-ups. Add the fields you want users to see—such as parcel ID and owner name—and arrange them clearly. Then create a web map, add the layer, and use Share Map to generate a link. Test the link in a private browser window to confirm a colleague can access it without additional permissions.

Data Licensing and Attribution

GIS data is intellectual property. Government agencies such as USGS publish data under open-license terms that generally permit free use, but most require attribution—a credit line identifying the data source on any map or report that uses it. State GIS portals vary: some use Creative Commons licenses, others use custom terms. Always read the data-use page before including someone else's data in a deliverable.

Attribution text typically appears in the map's legend area or in a credits note at a corner of the layout. A correct credit line names the originating agency, the dataset title, the publication date or version, and the URL if the terms require it. Failing to attribute data correctly can constitute a license violation and reflects poorly on the professional producing the map.

Safety and Data Handling

Digital data safety follows the same principle as physical safety: control hazards before they cause harm. Always keep a backup copy of original data before exporting or editing. Never share a web layer set to Public if it contains personally identifiable information such as property-owner names or addresses unless your organization and applicable law permit it. Confirm with your supervisor or client what sharing level is appropriate. These practices protect both the data subjects and your professional reputation.