Road Closure Solution producing error in Waze

[Jennifer_Parmeley]

I deployed Road Closures for our organization so we could use RC schema to feed Waze. There's a push to use Waze in our area.

During testing I found an error in the Waze Partner space. The "Work Area" value is not accepted by Waze, it appears, but I'll be honest that reading an xsd is not something I have a great deal of experience doing. I'm not sure at this point if I should update the domain list in the ESRI solution (what else will this break?) or try to add the subtype information that Waze might be looking for. I had a support ticket with ESRI about the solution and they were very specific about schema changes and not making them. I've made several because we need them. I cannot 100% redesign our product for our smaller community, the change needs to happen more slowly. We are only using the feature service (and related view) in our local solution, so I don't care if the map and ExB part of the solution don't work, I've got my own solutions there, but I want Waze to get the data we are sending.

Has anyone else found this? Any suggestions on getting this to work? Maybe I'm missing something basic?!

Updating the feature to a "hazard" does not fix the error in Waze. Hazard is in the solution and Waze xsd.

part of the Waze xsd, with I think, the related info.

[Joshua-Young]

Waze has finally accepted our feed. The format URL parameter must be JSON for Waze to import the geometry correctly.

/query?where=1%3D1&outFields=objectid,street,subtype,description,direction,starttime,endtime,type,reference&outSR=4326&returnZ=false&f=json

I had to go back and split a few of our road closures because Waze uses slightly different road names than what we had. For example, we have just G Street in our system, but Waze has G Street, G Street West, and G Street South. I left our road name as just G Street, but I split the closure close to where Waze was changing the names.

Also, be careful if you are filling out closure times in ArcGIS Pro. Hosted feature services are in UTC time and ArcGIS Pro is sadly not smart enough to convert UTC to local time and vice versa. ArcGIS Pro shows the time in UTC and it must be updated in UTC. ArcGIS Enterprise and ArcGIS Online are smart enough to convert UTC to and from local time, so enter the times there.