Any content that MTC indends to publish to external audiences via ArcGIS Online should be reviewed and shared publicly by the ArcGIS Online content administrators, not individual users.
In the sections following, processes for publishing content to external audiences are documented. These processes are not final, and will likely be updated over time.
Steps to follow while publishing from ArcGIS Pro
-
Coordinate with data owner to ensure layer(s) should be shared with a public audience
-
If layer not already available in AGOL, follow guide on sharing with ArcGIS Pro
-
Ensure that content is tagged appropriately. See tag strategy
-
Share with public group(s) that best suites the content topic area(s).
Content Topic Areas Administrative Demographic Policy Transportation Environmental Projects -
Add content to a relevant folder.
-
Confirm spatial extent for all web layers prior to publishing. If spatial extent is larger than your target extent (ex California extent when web layer is Bay Area centric), follow guide on Recalculating Feature Class Extent. For ArcGIS Pro layers formed using 'Make Layer From Selected Features' function, first export data to a temporary shapefile or file geodatabase feature class or resulting ArcGIS Online web layer will contain extent of source data, not the extent of selected subset of features.
-
Check the spatial reference of the layer - if layer's spatial reference is not EPSG 4326 (WGS 84), project layer using the Project Geoprocessing Tool. If reprojecting from NAD 83, choose the Geographic Transformation NAD_1983_To_WGS_1984_5 for datasets within the contitential United States. For more information on geographic transformations, see the ESRI Technical Support page on How To: Determine which NAD_1983_To_WGS_1984 transformation to use
Steps to follow using ArcGIS Online once web layer is published
- Update ownership of web layer from current owner to content_MTC (if not already owned by that user) for PDF maps and ArcGIS Online web maps; change current owner to orgData for enterprise and open data web layers
- Ensure that web layer meets minimum documentation requirements for curated content. See detailed documentation requirements
- Under feature layer settings, ensure that delete protection is enabled and editing is disabled
- Under feature layer settings, check box next to layer name under Optimize Layer Drawing and click Save button to increase layer drawing performance
- Mark content status as Authoratative
- Ensure web layers used in web map have followed the process outlined in the Web Layers Section
- Ensure web map is documented, following the basic documentation requirements. See basic documentation requirements
- Detailed documentation not necessary for web maps as layers supporting the web map should be well - documented.
- Provide links to supporting layers in Description for quick access to their information
- Ensure that content is tagged appropriately. See tag strategy
- Share with MTC Map Gallery Groups
- Ensure web map is documented, following the basic documentation requirements. See basic documentation requirements
- PDFs at minimum should have the following:
- Title
- Summary
- Description (write up)
- Link to project documentation on github (if available)
- PDFs at minimum should have the following:
- Ensure that content is tagged appropriately. See tag strategy
- Ensure that month and year are included as seperate tags (ex July, 2017)
- Share with MTC Map Gallery Groups