---
description: Listing and description of all data used by Alan on G Drive
---

# Alan De Anda's G Drive

### Table of Contents

* [Common Sub-folders](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#common-sub-folders-in-atd_gis)
* [Folders in ATD](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#folders-in-atd)

## Common Sub-folders in ATD\_GIS

* [Active\_Transportation](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#active_transportation)
* [MetroBike](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#metrobike)
* [CIP](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#cip)
* [CTN](https://app.gitbook.com/@atd-dts/s/atd-geospatial/miscelaneous/alan-de-andas-g-drive#ctn)
* [DATA\_COLLECTION](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#data_collection)
* [Vision\_Zero](https://app.gitbook.com/@atd-dts/s/atd-geospatial/alan-de-andas-g-drive#vision_zero)

### Active\_Transportation

* Most requests from the Active Transportation & Street Design Division live here. However, there are some exceptions, like the design files for the print bike map. These files and others are housed in ATSD's G Drive under `ATD/ACTIVE_TRANS` . More on this later.
* Bike\_Maps
  * archive\_online\_bike\_map
    * This folder contains mxds and data used to generate the first versions of the online bike map, which published a queried export of the CTN symbolized by level of comfort.
  * Vector\_Online\_BikeMap
    * This folder contains the ArcPro project for making a vector tile layer of the CTN with scaled symbology that matches the symbology of the printed bike map. This will allow for easier exports of GIS data to Illustrator to create the Print Bike Map. The print bike map has another wiki.
    * This folder will either need to move to `ATD/ACTIVE_TRANS` or ATSD staff will need write permission to this folder to allow for collaboration on the printed and online versions of the bike map.
* Bike\_Racks
  * This mxd was used to published the data for the [Bike Racks Web Map](https://austin.maps.arcgis.com/home/webmap/viewer.html?webmap=b890742f771e438ab4047c3ff07ac0a5). It is unlikely that this mxd will need revisiting, but this folder should host any bike parking related projects.
* Projects
  * This folder contains maps and data related to ATSD projects that the public will receive an update on through virtual open houses, web map applications like Crowdsource Reporter and Polling, and Story Maps. ATSD sends us an mxd with CAD data of the project, which we transform to GIS and publish. After review, it's possible that the CAD data in the mxd will be updated by ATSD. Once the data is published, the web maps are created in collaboration with ATSD and PIO staff as necessary. More on this in a separate wiki.
  * The name of the folders mimic the name of the projects in `ATD/ACTIVE_TRANS/Projects`&#x20;
* OSM\_Mapathons
  * In December 2019, ATSD and DTS held an OSM Mapathon to update bike data on Open Street Maps to update the Bicycle Network Analysis score.&#x20;
  * The people that participated in the mapathon have continued to map new facilities on their own.
  * ATSD may want to coordinate a new mapathon. It may only be necessary to send the team the data, though. The data in these folders can be used as a template for future exports.  [Rémy Greinhofer](https://app.slack.com/team/UMEPM1XLZ) is a good contact to get in touch with the group.
* Strava
  * This is where the Strava data lives. More info on Strava Data can be found [here](https://app.gitbook.com/@atd-dts/s/atd-geospatial/active-transportation/strava-metro-data).
* SRTS
  * Safe Routes to School data lives here.
* Bike Facilities for Google Maps
  * This data was submitted to Google Maps in the summer of 2020 to include new bike facilities. The wiki for setting up a Google Partner account and schema for data can be found [here](https://app.gitbook.com/@atd-dts/s/atd-geospatial/google-maps-partner/google-partner-account). Since Google Maps integrated this data onto the map, it's recommended that future updates use this schema/data format. The data will come from the CTN's Bike Facilities, which are updated through a different process.
* Healthy Streets
  * All data that is live on the AGOL apps was designed in  Healthy\_Streets.gdb
  * The data includes features, related tables, and their relationship classes. Once the data was published, it has not been overwritten to not delete the public record.
  * If any data from the apps needs to be updated, like the Candidates for Batch 3, and the COA\_HEALTHY\_STREETS data once candidates for batch 3 are installed, this should be opened in ArcPro.
  * AGOL:&#x20;
    *   HealthyStreets\_Point\_Line\_Tables Feature Service

        * This Feature Service contains the suggest a street/destination input feature services, and the COA\_HEALTHY\_STREETS. COA\_HEALTHY\_STREETS is the official feature for Healthy Streets that are active in the field. New candidates, if any should be added HealthyStreets\_Point\_Line\_Tables in ArcPro and editing the COA Healthy Streets layer.

        The data is shared with 3 groups:

        * ATD\_Healthy\_Streets: This includes the public-facing Crowdsource Reporter App “Healthy Streets Public Input Web App. This app is fed by the “Identify a Healthy Street” and “Identify an Important Destination” webmaps.  These maps don’t get a lot of traffic these days.
        * ATD\_Healthy\_Streets\_mgmt: this group holds several Crowdsource Polling apps, like “Review Top Candidates for Healthy Streets”, “Review Temporary Protected Bike Lanes on Congress”, and “Review Existing Healthy Streets App”. If any changes are needed to the data feeding these apps, the best way to edit them is to open the layers in Pro to not lose the public record.
        * ATD\_Healthy\_Streets Collab: This is a collaboration group, and users are able to fully edit the data in it. The “Healthy Streets TCP map” and much of its data live in this group. It’s possible to get requests to add data to this map. You may also get questions about exporting TCP data.



### MetroBike

* This folder contains B-Cycle and dockless/micromobility data and maps. The maps were generated at David Orr's requests to aide ATD and CapMetro determine B-Cycle locations in proximity to transit stops.
* B-Cycle has been renamed MetroBike after ownership transferred to CapMetro.&#x20;

### CIP

* Every year we digitize new projects that will receive CIP funding, and the maps and data live here. A wiki dedicated to the CIP digitizing project lives [here](https://app.gitbook.com/@atd-dts/s/atd-geospatial/capital-improvements-program-cip-digitization).

### CTN

* The Comprehensive Transportation Network (CTN) is a base geometry for streets, trails and transit rail lines. The CTN is currently updated to reflect newly installed bike facilities and to record any changes to the the city's biking level of comfort. The CTN was used as the base geometry for the Austin Stragetic Mobility Plan (ASMP), which was developed by the Systems Development Division. The wiki for the CTN can be found [here](https://app.gitbook.com/@atd-dts/s/atd-geospatial/comprehensive-transportation-network/ctn-data-dictionary).
* Cole Kitten's legacy CTN documentation lives in `G:\ATD\ATD_GIS\01_ADMIN\Comprehensive_Transportation_Network` and in `G:\ATD\Planning\DATMS\Transportation_Network` &#x20;



### DATA\_COLLECTION

* Most data found here is for old workflows for digitizing signs and markings.

### Vision\_Zero

* Vector Tiles
  * Vector Tiles used in the Vision Zero Viewer are saved here.

### Folders in ATD

* A lot of the work done for divisions within ATD are saved to their own folder in ATD. Typically, staff only has write permission to their own folder, and DTS staff can request write access to these folders from Scott Reedy.

### ACTIVE\_TRANS

* Bicycle/Bike Map/Bike Map Design Files
  * The print version of the bike map is saved in these folders.  The process for developing the print bike map has a separate wiki page.
* GIS
  * Base Maps
    * ATSD uses these basemaps to display their various projects in different ways - by facility, by project status, etc. The resulting mxds are somewhat clunky, and they are being phased out in favor of MOPED. MOPED's documentation can be found [here](https://app.gitbook.com/@atd-dts/s/moped-technical-docs/).
  * Bike Map
    * This folder contains a shapefile that shows the correct extents that GIS exports to Illustrator should be in.
* Projects
  * Every ATSD project lives here in its own separate folder.

### Planning

* DATMS
  * Legacy folder from when DTS was known as DATMS
* Transportation Network
  * Legacy folder for the CTN.
