diff --git a/Best-Practices-Procedures/AGOL-Technical-Resources.md b/Best-Practices-Procedures/AGOL-Technical-Resources.md deleted file mode 100644 index 9b41667..0000000 --- a/Best-Practices-Procedures/AGOL-Technical-Resources.md +++ /dev/null @@ -1,59 +0,0 @@ - - -# AGOL Technical Resources - -The intent of this page is to provide a practical guide on using and managing AGOL. Additionally, tips, best practices, or hacks should be documented and shared here. This page is a work-in-progress. - -### Features Vs. Feature Services in ArcGIS Online -[Features Vs. Feature Services in ArcGIS Online](https://blogs.esri.com/esri/arcgis/2016/01/25/about-features-and-feature-services/ -) - -### Share with ArcGIS Pro - -ArcGIS Pro provides numerous options for sharing your work with others. Using ArcGIS Pro, you can: -- Share web layers -- Share web maps -- Share web scenes -- Share packages -- Share web tools -- Share locators -- Create new item files - -[Share with ArcGIS Pro](http://pro.arcgis.com/en/pro-app/help/sharing/overview/share-with-arcgis-pro.htm -) - -### Publishing Web Layers to AGOL with ArcGIS Pro - -[Publishing Web Layers to AGOL with ArcGIS Pro](http://pro.arcgis.com/en/pro-app/help/sharing/overview/introduction-to-sharing-web-layers.htm -) - -### Overwrite Existing AGOL Web Layer with ArcGIS Pro - -[Overwrite Existing AGOL Web Layer with ArcGIS Pro](http://pro.arcgis.com/en/pro-app/help/sharing/overview/overwrite-a-web-layer.htm -) - - Save a copy of existing metadata before overwriting an existing AGOL web layer as AGOL deletes some information. Once existing web layer has been overwritten; open web layer Overview, click Metadata button, click Overwrite link (next to Save button), check 'Populate metadata with item details,' browse to saved copy of web layer metadata, and then make edits relevent to updated web layer. - -### Share Content through AGOL Portal - -[Share Content through AGOL Portal](http://doc.arcgis.com/en/arcgis-online/share-maps/share-items.htm) - -### Publish Web Maps to AGOL with ArcGIS Pro - -[Publish Web Maps to AGOL with ArcGIS Pro](http://pro.arcgis.com/en/pro-app/help/sharing/overview/share-a-web-map.htm -) - -### Publish Packages to AGOL with ArcGIS Pro - -The following link provides an introduction to sharing packages, which is a general information resource for sharing packages through email, FTP, the cloud, thumb drives, etc. To publish a package to ArcGIS Online, follow the steps outlined below. - -[Publish Packages to AGOL with ArcGIS Pro](http://pro.arcgis.com/en/pro-app/help/sharing/overview/introduction-to-sharing-packages.htm -) - -### Recalculate Feature Class Extent - -A feature class has a spatial extent that is based upon all the coordinates within the feature class. This spatial extent is used when adding a feature class to a map in order to recenter and display all the features within. Rather than examining every feature in the feature class each time the feature class is added to a map (a potentially long process), a feature class has an extent property containing the last known spatial extent. However, this extent property is not always updated when features within the feature class are edited. This means that the values in the extent property might not contain the actual spatial extent of the features. Executing this tool reads all the features and updates the extent property. - -[Recalculate Feature Class Extent with ArcGIS Pro](http://pro.arcgis.com/en/pro-app/tool-reference/data-management/recalculate-feature-class-extent.htm) - - - diff --git a/Best-Practices-Procedures/Admin-Publishing-Sharing-AGOL.md b/Best-Practices-Procedures/Admin-Publishing-Sharing-AGOL.md deleted file mode 100644 index 4766347..0000000 --- a/Best-Practices-Procedures/Admin-Publishing-Sharing-AGOL.md +++ /dev/null @@ -1,62 +0,0 @@ - - -# Best Practices for ArcGIS Online Administrators - -## Table of contents -- [Publishing Curated Content to an External Audience](#publishing-curated-content-to-an-external-audience) - - [Web Layers](#web-layers) - - [Web Maps](#web-maps) - - [PDF Maps](#pdf-maps) -- [Publishing Content to MTC's Open Data Portal](opendata/openDataSite.md) - -## Publishing Curated Content to an External Audience - -**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. - -### Web Layers - -***Steps to follow while publishing from ArcGIS Pro*** - -1. Coordinate with data owner to ensure layer(s) should be shared with a public audience -2. If layer not already available in AGOL, follow guide on [sharing with ArcGIS Pro](AGOL-Technical-Resources.md#publishing-web-layers-to-agol-with-arcgis-pro) -3. Ensure that content is tagged appropriately. See [tag strategy](https://mtcdrive.app.box.com/file/198480762097) -4. Share with [public group(s)](Creating-Groups.md#create-broadcast-groups) that best suites the content topic area(s). - - | Content Topic Areas | | | - |----------------------|---------------|----------| - | Administrative | Demographic | Policy | - | Transportation | Environmental | Projects | -5. Add content to a relevant folder. -6. 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](AGOL-Technical-Resources.md#recalculate-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. -7. 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](http://pro.arcgis.com/en/pro-app/tool-reference/data-management/project.htm). 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](https://support.esri.com/en/technical-article/000005929) - -***Steps to follow using ArcGIS Online once web layer is published*** - -8. 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 -9. Ensure that web layer meets minimum documentation requirements for curated content. See [detailed documentation requirements](Documentation.md##basic-documentation) -10. Under feature layer settings, ensure that delete protection is enabled and editing is disabled -11. Under feature layer settings, check box next to layer name under Optimize Layer Drawing and click Save button to increase layer drawing performance -12. Mark content status as **Authoratative** - -### Web Maps - -1. Ensure web layers used in web map have followed the process outlined in the [Web Layers Section](#web-layers) -2. Ensure web map is documented, following the basic documentation requirements. See [basic documentation requirements](Documentation.md#basic-documentation) - - 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 -3. Ensure that content is tagged appropriately. See [tag strategy](https://mtcdrive.app.box.com/file/198480762097) -4. Share with [MTC Map Gallery Groups](http://mtc.maps.arcgis.com/home/group.html?id=4bb2944ff35348c3847859b48d28336d#overview) - -### PDF Maps - -1. Ensure web map is documented, following the basic documentation requirements. See [basic documentation requirements](Documentation.md#basic-documentation) - - PDFs at minimum should have the following: - - Title - - Summary - - Description (write up) - - Link to project documentation on github (if available) -2. Ensure that content is tagged appropriately. See [tag strategy](https://mtcdrive.app.box.com/file/198480762097) - - Ensure that month and year are included as seperate tags (ex July, 2017) -3. Share with [MTC Map Gallery Groups](http://mtc.maps.arcgis.com/home/group.html?id=4bb2944ff35348c3847859b48d28336d#overview) diff --git a/Best-Practices-Procedures/Creating-Groups.md b/Best-Practices-Procedures/Creating-Groups.md deleted file mode 100644 index 30bdd9a..0000000 --- a/Best-Practices-Procedures/Creating-Groups.md +++ /dev/null @@ -1,55 +0,0 @@ - - -# Table of Contents -- [Creating Groups](#creating-groups) - - [Create Working Groups](#create-working-groups) - - [Create Broadcast Groups](#create-broadcast-groups) - - [Group Naming Conventions](#group-naming-conventions) - - [Group Summary Matrix](#group-summary-matrix) - -## Creating Groups - -Groups allow AGOL users to manage a collection of maps, scenes, layers, analytics, and apps. Groups can be created by theme, or topic, or project. When creating groups, the purpose and audience of the group is worth considering. At MTC, our audience(s) can generally be categorized into two groups – [working groups](#create-working-groups), and [broadcast groups](#create-broadcast-groups). - -### Create Working Groups - -Working Group – for sharing in-progress work with a specific group of collaborators (your work colleagues). These groups will be ad-hoc groups which will have owners other than the DataViz Team or content curator. Audience for these groups will be limited to members of the group. - -### Create Broadcast Groups - -**Broadcast groups are created and managed only by the DataViz team's content curators** - -Broadcast Group – for sharing finished content with an identified audience (everyone, our organization, or a specific collection of individuals) Broadcast groups will be organized by the following topic areas: - - | Content Topic Areas | | | - |----------------------|---------------|----------| - | Administrative | Demographic | Policy | - | Transportation | Environmental | Projects | - - | Enterprise Topic Areas | | - |------------------------|-------------------------------| - | Administrative | Cadastral | - | Environmental | Hydrography | - | Planning | Structures and Infrastructure | - | Surface Overlay | Transportation | - -### Group Naming Conventions - -It is important to clearly distinguish between working and broadcast groups for project participants since they may be members of both. Even though group permissions support using a single group for in-progress content (shared to group only) and finished items (shared to group AND organization), it is difficult for the project team to keep this straight since they can see both sets of items. - -A good way to organize this is to use **two groups** and a naming convention for your **working groups (in progress content)** and **broadcast groups (final content)**. For example: - -- Broadcast group: "My Mapping Project" -- Working group: "My Mapping Project (Private - Working)" -- Final web map: "My Web Map" -- In-progress web map: "My Web Map (Draft)" - -### Group Summary Matrix - -| Use Case | Purpose | Group Owner | Group Members | Permissions | Sharing | -|-----------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------|------------------------------------------------------|------------------------------------------| -| Working Groups (Smaller Projects) | Sharing in-progress work with a specific group of collaborators | Project Manager | Project Team (Invite Only) | Group: Private | Content: Group Only | -| Working Groups (Larger Projects) | Collaborating on projects with ad-hoc project team | Project Manager | Project Team (Invite & Request) | Group: Organization | Content: Group Only | -| Broadcast Groups (Limited) | Sharing finished content, proprietary data, or third-party data that should not be re-distributed | Content Manager | Content Users (Invite Only) | Group: Private and contributions by group owner only | Content: Group | -| Broadcast Groups (Organization) | Sharing finished content or proprietary data for viewing, analysis and map-making purposes only | Content Manager | Contributors | Group: Private and contributions by group owner only | Content: Group and Organization | -| Broadcast Groups (Public) | Sharing finished, authoritative content which is not proprietary or readily accessible outside the organization | Content Manager | Contributors | Group: Organization/Public | Content: Organization, Public, and Group | diff --git a/Best-Practices-Procedures/Documentation.md b/Best-Practices-Procedures/Documentation.md deleted file mode 100644 index 87b4acc..0000000 --- a/Best-Practices-Procedures/Documentation.md +++ /dev/null @@ -1,95 +0,0 @@ - - -# Documenting Content - -The purpose of this page is to define types of documentation and documentation requirements for each type. Content documentation can be split into two types: **basic documentation** and **detailed documentation**. - -## Basic Documentation - - - Title: State what it is. Often times, this will simply be the name of the layer, or association of layers. - - Summary: A one-line description of the content - - **Draft Content** - - Include "draft" in all capital letters at beginning of summary: DRAFT or [DRAFT] - - **Final Content** - - Remove "draft" from the summary and include a year statement for when the content was created at end of summary: examples - "_Content_Title_ was created in 2018" or "_Content_Title_ was created in April 2018" - - Description: Additional information that supports summary. - - Link to project documentation (if any). - - ~~Project or program content was created to support.~~ - - Content owner (the person responsible for the data) ~~project or program the content supports.~~ - Enter contact information on Contact tab under Resource in metadata form: - - Contact name - - Organization name - - Position name - - Role - - E-mail - - Address - - Phone number - - Source Files (if available): Link to source files used to generate content. This will generally apply only to static content such as images or pdfs. - - Content source (if available): Link to the webpage, portal, or download site if content is owned by an organization other than MTC/ABAG. - - Credits (Attribution): Acknowledge the source of the content and include the year content was created (if known). (ex. Federal Highway Administration - Freight Analysis Framework, 2012) - - Tags: Related keywords to support content discovery See: [Content Tagging Strategy](https://mtcdrive.app.box.com/file/198480762097) - - **If content is considered draft include "draft" as a tag** - -## Detailed Documentation - - MTC has enabled metadata for all content published to portal or AGOL. When the metadata editor is opened online, metadata fields are organized within nested pages. Below are pages the fields that should be populated in order to meet detailed documentation requirements. - - **Titles and Dates** - - ***Titles and Dates*** - - - Creation Date - - Publication Date _(Required)_ - - Revision Date _(If Applicable)_ - - ***Contact*** - - - MTC address - - GIS Content Curator name - - Organization name (Metropolitan Transportatin Commission or Association of Bay Area Governments; do not use acronym) - - GIS Content Curator phone number - - GIS Content Curator e-mail address - - Online resource - - DataViz website ( _insert URL, as text, here_ ) - - Hours and Instructions - - Hours of Service (ex. 9:00 AM - 5:00 PM (PST) Monday through Friday) - - **Citation** - - - Details - - Description - - Abstract - - Link to github docs (if any) - - If link to github unavailable: - - Source: Where the data was accessed and who is responsible for it - - Purpose: Why was the data created? - - Methodology: how was the data created? - - Summary: A one-line description of the content - - Acknowledge the source of the content. (ex. Federal Highway Administration - Freight Analysis Framework, 2012) - - Status - - Is development complete, for archival reference, continually updated, etcetera - - Keywords - - Tags- See: [Content Tagging Strategy](https://mtcdrive.app.box.com/file/198480762097) - - Extent - - Geographic (will auto populate) - - ~~Contact (Should be one added for content owner and one added for content publisher)~~ - - ~~Contact Name~~ - - ~~Individual Name~~ - - ~~Organization Name~~ - - ~~Role (Owner / Publisher)~~ - - ~~Contact Information~~ - - ~~Email~~ - - ~~Address~~ - - ~~Phone~~ - - ~~Online Resource (Link to pertinent website / link to DataViz website)~~ - - ~~Hours & Instructions~~ - - Maintenance - - Update Frequency - - Constraints - - General Constraints - - **Resource** - - - Distribution - - Distribution Information (will auto populate) - - Fields - - Domain (if field contains coded values, for instances) diff --git a/Best-Practices-Procedures/Getting-Started-Mapping-Software-Resources.md b/Best-Practices-Procedures/Getting-Started-Mapping-Software-Resources.md deleted file mode 100644 index fd75737..0000000 --- a/Best-Practices-Procedures/Getting-Started-Mapping-Software-Resources.md +++ /dev/null @@ -1,30 +0,0 @@ - - -# Getting Started - Mapping Software and Resources - -1. Install Adobe Creative Cloud Desktop App - - * Install - https://helpx.adobe.com/creative-cloud/help/manage-apps-services-desktop.html - * Select / Install Adobe Illustrator from the **Apps** Tab - -2. Install MAPPublisher Plugin - -http://www.avenza.com/help/mapublisher/9.7/installation.htm - -3. Connect to MAPPublisher - Avenza License Server - -4. Install Universal Type Client - Manages all MTC Fonts - -http://www.extensis.com/downloads/release-notes/universal-type-client-5-mac/ - -5. Ensure you have access to the MTC Templates Directory on Box - -https://mtcdrive.box.com/s/u7vucdezcgi0l4ywjqpp3xqu8x29mo7z - -6. Connect to MTC Symbol Library? - -TBD - -7. Connect to MTC Graphic Style Library? - -TBD \ No newline at end of file diff --git a/Best-Practices-Procedures/Map-Creation.md b/Best-Practices-Procedures/Map-Creation.md deleted file mode 100644 index 60e04f5..0000000 --- a/Best-Practices-Procedures/Map-Creation.md +++ /dev/null @@ -1,10 +0,0 @@ - - -# Map Creation - -This page is intended to be used as a resource when getting started with a mapping project. This page is very very drafty and is mostly a placeholder currently. Stay tuned... - -### Create 11 x 17 Map Book (Tabloid) - County Scale - -1. Navigate to [Individual Bay Area County Templates](https://mtcdrive.box.com/s/p9qlcusb1cpv2nnp6080zg65oawir7wz) directory on Box -2. \ No newline at end of file diff --git a/Best-Practices-Procedures/Publishing-Sharing-AGOL.md b/Best-Practices-Procedures/Publishing-Sharing-AGOL.md deleted file mode 100644 index e6c1fa2..0000000 --- a/Best-Practices-Procedures/Publishing-Sharing-AGOL.md +++ /dev/null @@ -1,28 +0,0 @@ - - - -# Publishing and Sharing Content to ArcGIS Online for All Users - -## Table of contents -- [Publishing Content to ArcGIS Online](#publishing-content-to-arcgis-online) - - [Web Layers](#draft-web-maps) - - [Web Maps](#draft-web-maps) - -## Publishing Content to ArcGIS Online - -### Web Layers - -1. Publish web layer to AGOL through ArcGIS Pro, following guide on [sharing with ArcGIS Pro](AGOL-Technical-Resources.md#publishing-web-layers-to-agol-with-arcgis-pro) -2. Ensure web layer meets minimum basic documentation requirements for draft content. See [basic documentation requirements](Documentation.md#basic-documentation) - - Name, summary, and tag field are required to be completed before you can publish to AGOL from ArcGIS Pro. -3. Select sharing options: - - To share with **only** a select group of stakeholders, share content to a [working group](Creating-Groups.md#create-working-groups) only. Do not share with **organization** or **public**. If an appropriate working group does not exist, create one following guidelines for [creating working groups](Creating-Groups.md#create-working-groups) - - To share with a wider audience, or a stakeholder not part of the MTC AGOL Organization, share content to **organization**, **public**, or both if necessary. -4. 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](AGOL-Technical-Resources.md#recalculate-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 the selected subset of features. - -### Web Maps - -1. Ensure web map meets minimum basic documentation requirements for draft content. See [basic documentation requirements](Documentation.md#basic-documentation) -2. Select sharing options: - - To share with **only** a select group of stakeholders, share content to a [working group](Creating-Groups.md#create-working-groups) only. Do not share with **organization** or **public**. If an appropriate working group does not exist, create one following guidelines for [creating working groups](Creating-Groups.md#create-working-groups) - - To share with a wider audience, or a stakeholder not part of the MTC AGOL Organization, share content to **organization**, **public**, or both if necessary. diff --git a/Best-Practices-Procedures/README.md b/Best-Practices-Procedures/README.md deleted file mode 100644 index 269e981..0000000 --- a/Best-Practices-Procedures/README.md +++ /dev/null @@ -1,23 +0,0 @@ - - -# Spatial Analysis & Mapping - -This page is intended as a resource when beginning a spatial analysis or mapping project. This sub-repository contains standard operating proceedures (SOPs), best-practices, guidelines, and technical resources that should guide and inform your work. - -For questions or to ask for help with getting started, contact someone from the Data and Visulization Team by email dataviz@bayareametro.gov - -## Table of Contents - -**Data and Content Management** - - - [Publishing and Sharing Content to ArcGIS Online **(For All Users)**](Publishing-Sharing-AGOL.md) - - [Publishing and Sharing Content to ArcGIS Online **(For Administrative Users)**](Admin-Publishing-Sharing-AGOL.md) - -**Mapping and Cartography** - - - [Getting Started - Mapping Software and Resources](Getting-Started-Mapping-Software-Resources.md) - - [Map Creation](Map-Creation.md) - -**Technical Resources and Best Practices** - - - [AGOL Technical Resources](AGOL-Technical-Resources.md) diff --git a/Best-Practices-Procedures/Tag-Strategy.md b/Best-Practices-Procedures/Tag-Strategy.md deleted file mode 100644 index 65028fe..0000000 --- a/Best-Practices-Procedures/Tag-Strategy.md +++ /dev/null @@ -1 +0,0 @@ - diff --git a/Best-Practices-Procedures/opendata/openDataSite.md b/Best-Practices-Procedures/opendata/openDataSite.md deleted file mode 100644 index 03733b0..0000000 --- a/Best-Practices-Procedures/opendata/openDataSite.md +++ /dev/null @@ -1,22 +0,0 @@ -# Open Data -MTC makes content available to the public through its [ArcGIS Online](http://mtc.maps.arcgis.com/home/index.html) and [Open Data](http://opendata.mtc.ca.gov/) sites. - -This section covers content promoted to the Open Data site. Requirements and process related to public sharing of content through ArcGIS Online are found at [Publishing and Sharing Content with ArcGIS Online](../Publishing-Sharing-AGOL.md). The terms data and resource are interchangable and encompass spatial features, non-spatial tables, web maps, map applications, feature services, maps (PDF and images), etcetera that can be accessed, viewed, and/or downloaded by the public. - -## Qualifications for Posting as Public Resource: -For the most part, resources that are developed/created by Metropolitan Transportation Commission (MTC) staff and used to produce a final/adopted document, plan, or policy released/implemented by the Commission are acceptable for sharing to the public. The exception regards the inability of the MTC to distribute proprietary, licensed data to the public, regardless of whether is was used to produce a final/adopted document, plan, or policy. - -While there is a preference for regional data sets, resources produced for subregional geographies can be posted as well. If a subregional resource is a subset of a regional data set, only the regional version will be distributed, unless the size of the resource would be better distributed in multiple parts. - -## Restrictions on the Public Posting of Third-Party resources: -Resources obtained from a third-party that are included in the Enterprise Database, or files used by MTC staff, in an unmodified form will not be distributed as a public resource by the MTC. The only exception to this prohibition relates to a resource used to produce a final/adopted document, plan, or policy released/implemented by the Commission in its original state. Its use to create the document, plan, or policy places it in the public sphere to the extent that its original licensing, as applied by the third-party creator/originator, allows. That stated, while such a resource could be made available to the public through visual services that match their use in an MTC product, the resource itself will not be made available for download. The Metropolitan Transportation Commission WILL NOT distribute third-party resources! - -Third-party resources that qualify for posting as a public service can only be made available as a feature layer, web map, or both, and it must be presented as it is in the published document, plan, or policy. In order to provide public access to the resource itself, download and/or contact information for the resource producer will be provided in the data service documentation. - -## Sharing Requirements and Processes -- Requirements - - [Metadata (Documentation)](requirements_openDataMetadata.md) -- Processes - - [ArcGIS Online to Open Data](process_agol2OpenData.md) - - [File (Shapefile, Table, PDF, etc.) to Open Data](process_file2OpenData.md) - - [Enterprise Database to Open Data](process_edb2OpenData.md) diff --git a/Best-Practices-Procedures/opendata/process_agol2OpenData.md b/Best-Practices-Procedures/opendata/process_agol2OpenData.md deleted file mode 100644 index 94bb2b0..0000000 --- a/Best-Practices-Procedures/opendata/process_agol2OpenData.md +++ /dev/null @@ -1,17 +0,0 @@ -## Promoting Content from ArcGIS Online to MTC's Open Data Site -1. Ensure content meets minimum requirements for publishing content to an external audience. - - [General posting requirements](openDataSite.md) - - [Metadata requirements](requirements_openDataMetadata.md) -2. If publishing a web layer, ensure coordinate reference system is set to WGS84 (EPSG/SRID: 4326) -3. Tag with appropriate open data category tag - **Note: if content not tagged, content will not be organized by category on open data site** - - | Open Data Categories | | | - |----------------------|---------------|----------| - | Administrative | Demographic | Policy | - | Transportation | Environmental | Projects | - -4. Share resource with Open Data Review group and send and e-mail to msmith@bayareametro.gov letting them know a new resource has been added to the group. If posting the resource to the Open Data site needs to be completed by a specific date, be sure and include that information. - -As a reminder, no content will be posted to the MTC Open Data site until it and its metadata have been reviewed and approved for posting. Make sure to include 1-3 days in your production schedule for review if posting is time-sensitive. The more work done upfront to make sure documentation is complete and data properly structured, the more likely time-sensitive postings will occur on time. - -The reviewer will contact the person in the content's metadata that was identified as the resource creator regarding any questions or requests for more detail the reviewer has. diff --git a/Best-Practices-Procedures/opendata/process_edb2OpenData.md b/Best-Practices-Procedures/opendata/process_edb2OpenData.md deleted file mode 100644 index 6d09af8..0000000 --- a/Best-Practices-Procedures/opendata/process_edb2OpenData.md +++ /dev/null @@ -1,2 +0,0 @@ -## Velit vehicula malesuada -Quisque duis vitae. Cupidatat qui nulla dui mauris sapien sit elit et. Rhoncus lorem vehicula. Dictum sociis consequat justo et ipsum vestibulum aliquam laborum praesent nam diam mauris est curabitur. Tincidunt faucibus risus et iaculis sociis. Nisl semper quis commodo etiam ac lacus molestias convallis. Eget ut eveniet. Id dui ut etiam tincidunt morbi ultrices nunc inceptos. Vitae dui nam donec bibendum rutrum. Nulla enim nec mauris eu fusce mi in magna in varius cras. Morbi ac dolor aliquam curabitur facilisi posuere mauris quam pulvinar pede ultricies. Quis ullamcorper sit. Magna in sit. Dignissim at duis. Mauris ac commodo. Dolor quis feugiat. Dolor eleifend venenatis condimentum felis iaculis sapien ipsum ipsum. Blandit massa molestie. Aenean natoque praesent. diff --git a/Best-Practices-Procedures/opendata/process_file2OpenData.md b/Best-Practices-Procedures/opendata/process_file2OpenData.md deleted file mode 100644 index 0496211..0000000 --- a/Best-Practices-Procedures/opendata/process_file2OpenData.md +++ /dev/null @@ -1,2 +0,0 @@ -* The Open Data manager, will work with the data creator to determine which license to apply to data and add it to metadata information along with agency disclaimer. -* The Open Data manager, will work with data creator to determine how data will be made availble to public (download only, generic feature service, symbolized feature set, web map, multiple subsets, etcetera). diff --git a/Best-Practices-Procedures/opendata/requirements_openDataMetadata.md b/Best-Practices-Procedures/opendata/requirements_openDataMetadata.md deleted file mode 100644 index 73ac3f1..0000000 --- a/Best-Practices-Procedures/opendata/requirements_openDataMetadata.md +++ /dev/null @@ -1,26 +0,0 @@ -# Metadata -Metadata (data about data) is required for all content posted to the MTC Open Data site. Content will not be posted until its metadata has been reviewed and approved so be sure to include the time required to review the metadata if it needs to be posted by a specific date. - -Placeholders for next section -Prefer metadata created in ArcGIS product -For non-spatial resources, metadata can be submitted using Microsoft Word or other text document -How GitHub relates - -## Default metadata requirements for Open Data content: - 1. Title- Limited to the name of the content itself. For point-in-time and serial releases a date, as either year, month and year, or version number can be included. All other information is to be placed in the summary or/and description metadata sections. - 2. Summary/Purpose - 1-2 lines describing the resource. - 3. Description/Abstract - Detailed information regarding the resource. Information can include, but is not limited to, the following: What it is, intended uses, limitations on use, and how it was developed (including identification of third-party data/resources used in its development). - 4. Contact information for resource developer - Name, title, phone number, e-mail address, agency name, and building address. Position or unit names can also be used, and in some cases are preferrable as the creator may leave or change roles and the time cost of updating resource metadata is not insignificant if the person was a prolific developer of public resources. - 5. Date of resource - Day, month, and year of the resource. One thing to consider here is the date of any source data used in its development. A resource created today using data that is six months old is really six months old, not current. - 6. Date of resource release - Day, month, and year the resource was approved as final, released as part of a document, or received official status in some form. If posting to the Open Data site constitutes release of the resource the Data Administrator will fill out the release date. - 7. Date of update - For a resource that has been updated, rather than released as a new version, the day, month, and year the update was completed. - 8. Field descriptions - A definition must be provided for every table column. This covers both shapefile/feature set attribute tables and stand-alone data (spreadsheet, DBF, CSV, etc.). If the values in a column use codes to represent a limited range of values (i.e. numeric codes used for counties, acronymns used for housing types, etc.) then definitions need to be provided for each code value as well. - -## Metadata related to content using one or more third-party resources must: - 1. Prominantly state the third-party that created it, - 2. Identify the final/adopted document, plan, or policy the resource was used for, - 3. State that the data may not be the most current version available as it is not an MTC resource, - 4. State that the third-party is responsible for the content and quality of the resource, - 5. Include either a either a URL to the third-party's website where the public can obtain the resource for themselves or provide contact information for the third-party person/department the public can contact to obtain the resource, - 6. Utilize the same metadata generated by the resource creator/originator (MTC specific information can be added if necessary), and - 7. Apply the license used by the third-party for their data. If the third-party does not have a set license, the MTC will use the most restrictive open data license as a default. diff --git a/README.md b/README.md index 1197893..344e6b6 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,6 @@ # Spatial Analysis & Mapping -## Table of Contents +### [Project Documentation](Project-Documentation) -- [Project Documentation](Project-Documentation) -- [Best Practices and Procedures](Best-Practices-Procedures) +Note: Best Practices and Procedures have been migrated to [Best Practices + Procedures](https://github.com/BayAreaMetro/dataviz-project-resources/tree/main/Best%20Practices%20%2B%20Procedures) in **dataviz-project-resources**