Menchaca Street Name Change

[SurbhiBakshi]

as per JohnC, the easiest approach would be to export the affected records to csv, modify them, and import them back into each application. we only need to update the primary objects, and the connected objects should be updated accordingly:

banner_locations (banners)

street_segments (signs & markings) street_names (signs & markings)

street_segments (data tracker) tmc_issues (data tracker)

Can you work on this? You'll definitely want to do this in test first.

[SurbhiBakshi]

No	Application	Test - Records	Field Names	Production - Records
1.	banner_locations (banners)
2.	street_segments (signs & markings)	4 DEC 2019 - 63147 records, MANCHACA (72), OLD MANCHACA (14) , MANCHACA SPRINGS (3), MANCHACA TO BEN WHITE EB (1)	STREET_NAME, FULL_STREET_NAME
3.	street_names (signs & markings)	4 DEC 2019 - 18, 409 records, 1 (MANCHACA RD), 1 (MANCHACA SPRINGS RD), 1 (OLD MANCHACA RD)	STREET_NAME
4.	street_segments (data tracker)	13 Aug 2019 - 48 of 5794 (1 - Old Manchaca Road)	STREET_NAME, FULL_STREET_NAME
5.	street_names (data tracker)	2 (1 - Old Manchaca Road)	STREET_NAME
6.	tmc_issues (data tracker)

• [x] Not sure what to do about Old Manchaca Road? GIS in DM has not renamed.
• [x] Manchaca Springs - GIS in DM has not renamed, don't think this is in Austin Juris.
• [ ] Leaving fields like Instructions and Location Details in work_order_markings alone for right now, some have notes with the words Manchaca in them.
• [ ] Location field in locations object in Data Tracker has addresses with Manchaca that come from a location field, not sure if partial updates work.
• [ ] Not sure if Manchaca in the Corridor field in locations in Data Tracker needs to change.

[SurbhiBakshi]

• [x] @Diana will contact @jaime-mckeown for GIS connection to Banners.

Emailed Jaime to update the GIS feature layer that had the No.31 OTS banner location

[SurbhiBakshi]

I went over the Data Tracker app and tried to gauge which of the objects was the main location provider based on connections, and it looks like the street_segment object is the primary, with locations being a secondary source. I have tried to see how many existing records would be affected, but not sure if this is comprehensive. Let me know if there is something I am missing, because I am looking at the objects one by one. Not sure if there is a ~simpler~ better way.

Name of Application	Location Object	Location Object Connects To	Connects to Location Object	Connection Field	No. of Records Affected
Data Tracker	locations	street_segments		PRIMARY_ST_SEGMENT_DISPLAY_NAME
		street_segments		CROSS_ST_SEGMENT_DISPLAY_NAME
			cameras	ATD_LOCATION_ID	17
			construction_cost_estimate_reports	ATD_LOCATION_ID	0
			damage_reports	ATD_LOCATION_ID	2
		dms	ATD_LOCATION_ID	0
		hazard_flashers	ATD_LOCATION_ID	1
			pole_attachments	ATD_LOCATION_ID	1
			school_beacons	ATD_LOCATION_ID	0
			signals	ATD_LOCATION_ID	22
			signal_requests	location	29
			tmc_issues	location	551
			travel_sensors	ATD_LOCATION_ID	3
			work_orders_signals	ATD_LOCATION_ID
	locations_traffic_counts	street_segments		PRIMARY_ST_SEGMENT_DISPLAY_NAME
	locations_traffic_counts	street_segments		CROSS_ST_SEGMENT_DISPLAY_NAME
			traffic_counts	ATD_LOCATION_ID	2
	street_segments		locations	PRIMARY_ST_SEGMENT_DISPLAY_NAME	52
				CROSS_ST_SEGMENT_DISPLAY_NAME	4
			locations_traffic_counts	PRIMARY_ST_SEGMENT_DISPLAY_NAME
				PRIMARY_ST_SEGMENT_DISPLAY_NAME
			traffic_counts	STREET_SEGMENT_IDS
			vision_zero_enforcements	enforcement_primary_street_segment
				enforcement_cross_street_segment
	tmc_activities				1611
	street_segments			STREET_NAME	49

[dianamartin]

The other day I updated the banner_locations and banners_over_the_street_location objects from "Manchaca" to "Menchaca".

18 records banner locations were updated. All descriptions were also updated.

[SurbhiBakshi]

Updated Test for Signs and Markings, @Diana will be doing some random checks to see if things look alright.

[SurbhiBakshi]

Test

Application	Object	Export All Records	Total Number of Records	Number of Specific Records	Filter Specific Records	Export Specific Records	Find and Replace Specific Records	Import Specific Records	Check Related Objects
Signs and Markings
Signs and Markings
Data Tracker	street_segments (STREET_NAME, FULL STREET NAME)	x	5865	48 Manchaca Rd, 1 Old Manachca Rd	x	x	x	x (don't include text formula fields STREET_SEGMENT_DISPLAY_NAME	locations, locations_traffic_counts,traffic_counts, visions-zero_enforcements
Data Tracker	street_names (STREET_NAME)	-	-	1 Manchaca Rd, 1 Manchaca Springs Rd, 1 Old Manhaca Rd	-	-	-	Manual update of Manchaca Rd to Menchaca Rd	traffic counts
Data Tracker	tmc_issues (CSR_ADDRESS,

[SurbhiBakshi]

• [x] @SurbhiBakshi, document new environment, share copy of Data Tracker when completed with yourself and then proceed.

[SurbhiBakshi]

[SurbhiBakshi]

@johnclary and @dianamartin - I have updated Signs and Markings, as well as Data Tracker reflect the name change. Had some questions about tmc_issues which I have documented in the comments below.

Production

Application	Object	Export All Records	Total Number of Records	Number of Specific Records	Filter Specific Records	Export Specific Records	Find and Replace Specific Records	Import Specific Records	Check Related Objects
Signs and Markings	street_segments (STREET_NAME, FULL_STREET_NAME)	x	63, 148	90(14 Old Manchaca, 1 Manchaca to Ben White EB, 3 Manchaca Springs, 72 Manchaca Rd)	x	x	x	x	work_order_markings
Signs and Markings	street_names (STREET_NAME)	-	18, 409	1 Manchaca Rd, 1 Old Manchaca Rd, 1 Manchaca Springs Rd	-	-	-	Manual change to Manchaca Rd	work_order_markings, work_order_signs, on the app user interface, some Location are Manchaca and some are Menchaca https://atd.knack.com/signs-markings#work-order-signs/ and https://atd.knack.com/signs-markings#work-orders-markings/markings/
Data Tracker	street_segments (STREET_NAME, FULL STREET NAME)	x	5,872	1 Old Manchaca Rd, 48 Manchaca Rd	x	x	x	x	locations LOCATION filed comes from in - app address, does this need to be changed?, location_traffic_counts, traffic_counts, vision_zero_enforcements
Data Tracker	street_names (STREET_NAME)	-	18, 049	1 Old Manchaca Rd, 1 Manchaca Springs, 1 Manchaca Rd	-	-	-	manual update of Manchaca Rd record	traffic_counts
Data Tracker	tmc_issues (CSR_ADDRESS,

[SurbhiBakshi]

[SurbhiBakshi]

[SurbhiBakshi]

[SurbhiBakshi]

[SurbhiBakshi]

@johnclary Does the paragraph text in the CSR_DETAILS and CSR_ADDRESS FIELDS IN tmc_issues need to be changed as well? Is the validation not happening because of the name change?

The associated location fields show the name change -

[SurbhiBakshi]

@johnclary There are a few of these as well -

[SurbhiBakshi]

@johnclary - instances of Manchaca that I can still see.

Data Tracker

• [ ] camera - LAMAR BLVD / BARTON SKWY (Manchaca Rd) - LOC16-000630

  I think we can manually change these without issue, right @johnclary ?

• [ ] Landmark - West of Manchaca - LOC16-006875

  I think we can manually change these without issue, right?

• [ ] Corridor - Manchaca - Corridor ID - 27

Notes: DM - 12/30/19

[SurbhiBakshi]

@dianamartin - instances of Manchaca I can still see

Signs and Markings

• [ ] Looks like the location field comes from a CSR input

- [ ] The 311-SR locations are still Manchaca, but the Maintainence locations are Menchaca .

• [ ]

[dianamartin]

@SurbhiBakshi @johnclary The SR locations are being pulled from the 311 System, so they have it as "Manchaca".

[johnclary]

Good catch. No, let’s leave as is since the data is from 311. Any CSR connected to one of our assets will be updated properly. Thanks!

On Dec 27, 2019, at 09:11, Surbhi notifications@github.com wrote:

 External Email - Exercise Caution

@johnclaryhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjohnclary&data=02%7C01%7CJohn.Clary%40austintexas.gov%7Ce8836ede8d81435f851608d78adf0f66%7C5c5e19f6a6ab4b45b1d0be4608a9a67f%7C0%7C1%7C637130562948391073&sdata=9dUOTKMWaeLRAIEHpxUZ85xkjFpxgnBg6SL9d1hgIqE%3D&reserved=0 Does the paragraph text in tmc_issues need to be changed as well? [image.png] https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamo.githubusercontent.com%2Fc25d07e56737e27a46de2ceb6ca78cadaa41d3da%2F68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3564356165626535353766393562303030313166386535372f30623437343332342d366664652d343339632d623130622d623731326666346535666661&data=02%7C01%7CJohn.Clary%40austintexas.gov%7Ce8836ede8d81435f851608d78adf0f66%7C5c5e19f6a6ab4b45b1d0be4608a9a67f%7C0%7C1%7C637130562948401027&sdata=Y9HCn2iYkFZ6x6scc3fYEr5N46uApNZbug9wQz9wIXw%3D&reserved=0

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcityofaustin%2Fatd-data-tech%2Fissues%2F968%3Femail_source%3Dnotifications%26email_token%3DADQ3TICMWOR3UVEXFLPICKTQ2YLKJA5CNFSM4JUZG7J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHXKNSA%23issuecomment-569288392&data=02%7C01%7CJohn.Clary%40austintexas.gov%7Ce8836ede8d81435f851608d78adf0f66%7C5c5e19f6a6ab4b45b1d0be4608a9a67f%7C0%7C1%7C637130562948401027&sdata=CXqkKa9eeZ5h3gTWk%2B4icVykZO4vf78qDlpJryGarJ4%3D&reserved=0, or unsubscribehttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADQ3TIF32NI65NMQKWGOH5LQ2YLKJANCNFSM4JUZG7JQ&data=02%7C01%7CJohn.Clary%40austintexas.gov%7Ce8836ede8d81435f851608d78adf0f66%7C5c5e19f6a6ab4b45b1d0be4608a9a67f%7C0%7C1%7C637130562948410984&sdata=9KM6E%2BLGA1vDLMm2c9R0jOCFaZO4N5atytgeBvZW6YQ%3D&reserved=0.

CAUTION:This email was received at the City of Austin, from an EXTERNAL source. Please use caution when clicking links or opening attachments. If you believe this to be a malicious and/or phishing email, please forward this email to CSIRT@austintexas.gov.