Create New Feature Layer for Contractor Work Orders API

[KaroEngstrom]

This is part 2 of #7441

• [x] Export all fields from here for GIS (Contractor Work Orders table at the bottom of the page)
• [x] contractor_work_orders.csv
  • [x] Request feature layer to match those fields

[dianamartin]

@andrewshensky We would like to request a new feature layer for the "Contractor Work Orders"

• feature type: line (like pavement markings work orders)
• you can name the fields how you need to in AGOL (ex. underbars)
• Using this schema: https://data.austintexas.gov/Transportation-and-Mobility/Roadway-Markings-Work-Orders/nyhn-669r

Let me know if you have any questions. SMD would like to have this soonish. I can ask Christina the time frame.

[andrewshensky]

@dianamartin I have a couple questions below:

• Will this just need to be an empty dataset that will eventually be populated with data coming from knack?
• Will the fields need to match those included in the csv provided in the link above?
• In the schema link you provided it looks like nearly all numeric/ID fields, except one length field, are being captured as text, is that how this layer should be created or should I just use the field format coming from the csv?

[dianamartin]

@andrewshensky

• it should be an empty dataset, will be populated from data in Knack
• This a resource article about the AGOL Integration steps..so we're both on the same page

These are the field types from Knack

Work_Order_ID	Text
Created By	Text
Created Date	Date
Modified Date	Date
Work_Order_ID	Text
Parent WO	Text
Parent WO - FIELD	Text
Work_Authorization_Number	Number
Assigned Contractor	Text
Assigned To	Text
GIS_ID	Text
Instructions Comments	Text	Max length
Follow-up Instructions	Text	Max length
From Street	Text
To Street	Text
Street Display Name	Text
Area	Text
Centerline Miles	Number
Work Order Status	Text
ATD Issued Date	Date
Contractor Submitted Date	Date
Contractor Submitted By	Text
Count Attachments	Number
Count Comments	Number
Count Inspections	Number
Count Work log	Number
Work Status	Text
Primary Parent WO	Text
recordID	Text
GIS QA	Text
STREET_SEGMENT_IDS	Text
WORK_GROUPS	Text

@andrewshensky cc: @johnclary there is a Marking Work Order feature class but it's not showing up properly in AGOL, she submitted a new bug issue #9907

[andrewshensky]

@dianamartin I have created a the new feature in layer in AGOL through the link below. It is currently shared to the public to match other similar layers. Let me know if any changes need to be made to the data or settings.

https://austin.maps.arcgis.com/home/item.html?id=65457b568fb94e92a7790a947c7b6690

[dianamartin]

@andrewshensky I finally figured out where the markings work order feature layer information is, I'm wondering if you need to create the feature layer under this ATD_Publisher_Scripts account instead.

I was looking at the field names and it's all caps with all underbars, do you think we need to match it to be the same?

[dianamartin]

Pavement Markings Work Order Feature

Contractor Work Orders

[andrewshensky]

@dianamartin I have updated the Contractor Work Order data structure to be in all caps for consistency with other datasets. The dataset is also published through the ATD_Publisher_Scripts account. Let me know if any other modifications are needed. The link to the data in AGOL is below:

https://austin.maps.arcgis.com/home/item.html?id=7eb2da1d8e6c4f79b368d8e295dec969

[dianamartin]

Thanks Andrew, I'll check it out - if all seems well I can ask the devs to make the ETL happen