Web Conference 2026.10.13 Curb

• 00:08:00 Michael Schnuerle (OMF): Agenda page https://github.com/openmobilityfoundation/curb-data-specification/wiki/Web-Conference-2026.10.13-Curb
• 00:10:45 Andrew Glass Hastings (OMF): Hello everyone! Thanks for joining this CDS Working Group! We hope to see many of you in LA for the OMF Summit at CoMotion! OMF commercial membership incudes tickets to the event and public sector attendees can attend for free! Let us know if you have any questions!
• 00:10:47 Aylene McCallum (OMF): Reminder to OMF Members: Please make sure to utilize your OMF membership benefits and register for CoMotion LA 2026.
• 00:14:47 John Lundstrom (Minneapolis): Love the snowplow tracking!
• 00:15:07 Max Holperin: Does this include tracking which streets have already been cleared (and how long ago_?
• 00:15:20 Andrew Glass Hastings (OMF): 2027 City Curb Collaborative - we are planning for the Curb Collaborative next year - a valuable peer learning and sharing program! We have a strong contingent of cities continuing and also have room for new cities to join. If you are interested in your city participating next year please let us know and fill out this quick and easy form - https://docs.google.com/forms/d/e/1FAIpQLSdrFRVVCArU_4_jQqGCVLJ5GjuTQCQi2Ol5h6O4dNB_HOjatg/viewform?usp=header
• 00:15:42 Eliot Mueting (Populus): Reacted to "2027 City Curb Colla..." with 👍
• 00:15:51 Brian Hamlin | Seattle DOT: Reacted to "2027 City Curb Collaborative - we are planning for the Curb Collaborative next year - a valuable peer learning and sharing program! We have a strong contingent of cities continuing and also have room for new cities to join. If you are interested in your city participating next year please let us know and fill out this quick and easy form - https://docs.google.com/forms/d/e/1FAIpQLSdrFRVVCArU_4_jQqGCVLJ5GjuTQCQi2Ol5h6O4dNB_HOjatg/viewform?usp=header" with 👍
• 00:17:05 Angel Yang - SFMTA: How many of those digital screens do you have up?
• 00:18:07 Jason Peckham (Umojo): 3 up in Buffalo, with 7 more slated complete before the end of next week for a total of 10. These are the 55 inch signs. The eInk, smaller form factor signs, we are slated to install 20 of those in January.
• 00:18:55 Lisa Hood - City of San Jose: Are those black zones with the zeros, pay stations?
• 00:20:40 Angel Yang - SFMTA: Reacted to "3 up in Buffalo, wit..." with 👍
• 00:22:51 Lisa Hood - City of San Jose: Can you speak more about the Loading Zone Permits layer?
• 00:23:16 Christopher Shelley | City of Philadelphia: What are the limitations on what kind of infrastructure the signs can be attached to?
• 00:23:32 Hélène Mercier Brulotte: Reacted to "Can you speak more about the Loading Zone Permits layer?" with 👍
• 00:27:32 Christopher Shelley | City of Philadelphia: Are they actually replacing the physical signs? How is that possible from a regulatory framework?
• 00:30:55 Kelly Drew ( City of Toronto): What type of messaging is going on the signs?
• 00:33:16 Brian Hamlin | Seattle DOT: 😲
• 00:33:30 Wendy Grus - Seattle (SDOT): Reacted to "😲" with 💯
• 00:37:08 John Lundstrom (Minneapolis): We are very keen on proliferation of digital signage
• 00:37:33 Lawrence Fan (CurbIQ / Arcadis): 511 ontario?
• 00:38:02 John Lundstrom (Minneapolis): Beyond regulatory communication, we see e-ink/paper signs as an effective parking rate/QR code delivery tool
• 00:38:17 Andrew Glass Hastings (OMF): Reacted to "Beyond regulatory communication, we see e-ink/paper signs as an effective parking rate/QR code delivery tool" with 👍
• 00:38:38 Jason Peckham (Umojo): The integration partner that Rick was referring to is NITTEC.
• 00:42:34 Kenya Wheeler (SFMTA): Reacted to "Beyond regulatory communication, we see e-ink/paper signs as an effective parking rate/QR code delivery tool" with 👍
• 00:45:16 Lawrence Fan (CurbIQ / Arcadis): Reacted to "The integration pa..." with 👍
• 01:01:19 John Lundstrom (Minneapolis): I am heavily in favor of this sort of standardization as best as we can achieve it
• 01:02:21 Brian Hamlin | Seattle DOT: Reacted to "I am heavily in favor of this sort of standardization as best as we can achieve it" with 👍🏻
• 01:03:46 Brian Hamlin | Seattle DOT: Love to see this work. Thanks all

WEBVTT

1 00:00:03.160 --> 00:00:07.979 Michael Schnuerle (OMF): All right, welcome everybody. My name is Michael Schnurla. I work for the Open Mobility Foundation.

2 00:00:08.119 --> 00:00:23.989 Michael Schnuerle (OMF): And this is the Curb Working Group monthly meeting. Thanks for participating and, and watching today. We'll get into some things. The main topic is about 4 new issues that have been opened.

3 00:00:24.240 --> 00:00:31.320 Michael Schnuerle (OMF): around the Curbs API, maybe the Events API parts of CVS, and we're gonna just…

4 00:00:31.320 --> 00:00:45.499 Michael Schnuerle (OMF): talk about those to get you familiar with them. This may be the start of another release, so it might be the first things we talk about in the working group that could lead to a future release.

5 00:00:45.600 --> 00:00:50.110 Michael Schnuerle (OMF): And then we have a city presentation as well. So…

6 00:00:50.380 --> 00:00:57.740 Michael Schnuerle (OMF): Little housekeeping, set your name and organization in the participant list, so if your organization isn't after your full name.

7 00:00:57.850 --> 00:01:03.899 Michael Schnuerle (OMF): Go ahead and edit that in the participant list, and add who you're representing, the city, the company.

8 00:01:04.670 --> 00:01:05.990 Michael Schnuerle (OMF): Mute yourself.

9 00:01:06.190 --> 00:01:15.049 Michael Schnuerle (OMF): But feel free to introduce yourself in the chat, so leave a comment about who you are, why you're here, what your title is, etc.

10 00:01:15.810 --> 00:01:24.180 Michael Schnuerle (OMF): use the chat to let us know if you want to speak, or the raise hand feature. When we go through the issues, depending on the timing, we might

11 00:01:24.250 --> 00:01:38.410 Michael Schnuerle (OMF): take most questions in the chat, but if you have a… if you're really interested in the topic, you can feel free to raise your hand and we can talk about it. And this meeting is being recorded and will be published with the notes.

12 00:01:41.290 --> 00:01:57.619 Michael Schnuerle (OMF): All right, a little bit about the Curb Working Group. This is meant to steward the Curb Data Specification, CDS, which is a structured way to catalog and track activity in city streets, curbs, and how things are being used.

13 00:01:58.130 --> 00:02:07.499 Michael Schnuerle (OMF): And version 1.1 is out, and the steering committee has been elected, and they're on the right here. So thanks to all of our volunteer steering committee members.

14 00:02:09.509 --> 00:02:23.870 Michael Schnuerle (OMF): CDS allows cities to code the curb, represent them digitally, and then track events and activity at those curbs, and use metrics to provide insights and improve policies.

15 00:02:24.480 --> 00:02:32.779 Michael Schnuerle (OMF): It's been built in the open between local governments, Curb users and operators, and tech and service providers and vendors.

16 00:02:34.290 --> 00:02:46.569 Michael Schnuerle (OMF): lots of… maybe two dozen, cities so far are using, and then more companies are using CDS in some way, so, here's a little bit of a highlight, but let us know if you're using it.

17 00:02:49.010 --> 00:03:07.640 Michael Schnuerle (OMF): And for CDS 1.1, which was released this past year, we have a ton of resources. These… these all link to different places, on this slide, and you'll get the slides later. It's actually already… the slides are already in our Agenda page, so I'm just gonna put those in chat.

18 00:03:08.040 --> 00:03:13.290 Michael Schnuerle (OMF): right now, a link to the agenda page and meeting page there.

19 00:03:16.880 --> 00:03:27.400 Michael Schnuerle (OMF): And CDS works in conjunction with our other data specification, MDS. MDS is about where vehicles are and what they're doing across an entire jurisdiction.

20 00:03:27.620 --> 00:03:33.530 Michael Schnuerle (OMF): Things that happen with them, and how they interact, incidents, trips, crashes. And CDS

21 00:03:33.750 --> 00:03:44.379 Michael Schnuerle (OMF): Basically defines physical pieces of infrastructure and how those vehicles interact with those pieces of infrastructure. They can be used independently or cooperatively.

22 00:03:46.500 --> 00:03:54.740 Michael Schnuerle (OMF): Some quick announcements. I just want to thank our Premier and Associate Commercial members. You can see our Premier members here.

23 00:03:55.950 --> 00:03:58.930 Michael Schnuerle (OMF): And our associate members,

24 00:03:59.540 --> 00:04:07.779 Michael Schnuerle (OMF): No changes since the last meeting, but happy to have all these members be part of the OMF and help us drive our mission together collectively.

25 00:04:08.640 --> 00:04:15.890 Michael Schnuerle (OMF): We have an OMF calendar. It's, has all of our events, like this one, and other places we're gonna be.

26 00:04:16.070 --> 00:04:24.920 Michael Schnuerle (OMF): We have tomorrow mobility coming up in Barcelona. We have Polis coming up in

27 00:04:25.840 --> 00:04:34.970 Michael Schnuerle (OMF): Oh, actually, I'll wait. We have a slide about that. Here's where we're going to be through 2026. Tomorrow Mobility in Barcelona is coming up.

28 00:04:35.350 --> 00:04:47.879 Michael Schnuerle (OMF): The OMF Summit, of course, with CoMotion in Los Angeles, November 17th to 19th, and then in Polis and Brussels, September 1st to 4th, and these are prior meetings here.

29 00:04:49.010 --> 00:05:07.360 Michael Schnuerle (OMF): And then, if you're an OMF member, we have a benefit for you for OMF Academy sessions. We have completed many of these already, in the last few months. We've done a CDS 101, an MDS 101, and a Digital Infrastructure 101. We're going to be repeating the CDS 101.

30 00:05:07.480 --> 00:05:23.359 Michael Schnuerle (OMF): Academy session tomorrow, so if you have staff or others who are interested in learning about CDS and maybe aren't too familiar with it, this is a good place to send them if you're an OMF member. You can reach out in the chat or email us if you don't have access to that yet.

31 00:05:27.990 --> 00:05:29.999 Michael Schnuerle (OMF): Alright, that's it for the announcements.

32 00:05:30.110 --> 00:05:34.910 Michael Schnuerle (OMF): We are going to do a city presentation.

33 00:05:34.950 --> 00:05:54.019 Michael Schnuerle (OMF): that we have today. Today, the City of Buffalo and Umojo have been working on some things, and so I'd like to ask any of them… I don't know who's going to actually present, or who… what combination of people, but I know Rick is here, so Rick, you could take it away. Thanks.

34 00:05:54.020 --> 00:06:13.950 Rick Neubauer (Umojo): Thank you, sir. Hey, everybody. Happy Tuesday. I've… it's gonna be a couple of us, and I… I was gonna try and put a nice deck together, and I ran out of time, but we're just gonna jump in and do a demo of what we're doing live with what's deployed, and then, Jason that's here, who's the project manager for this, is gonna talk about

35 00:06:14.110 --> 00:06:26.209 Rick Neubauer (Umojo): a lot of the trials and tribulations we've ran into with dealing with, different, entities involved in the project over the last 9 months, and then, go from there. We're also going to talk about

36 00:06:26.210 --> 00:06:35.329 Rick Neubauer (Umojo): Some of the stuff that's in the issues that I've submitted are things that we've done our own way to solve it inside of what I'm going to show you here in a minute as well.

37 00:06:35.340 --> 00:06:40.920 Rick Neubauer (Umojo): Which are part of the, of the, the issues that I've been submitting lately. Excuse me. And then.

38 00:06:41.140 --> 00:06:50.999 Rick Neubauer (Umojo): we'll talk a little bit about the digital signage that we're deploying, and what the city's planning on doing for that, there. So, without further ado, let me share my screen, and we'll jump right into it.

39 00:06:51.660 --> 00:07:05.299 Jason Peckham (Umojo): I think, Rick, as just an addendum there before you get going, just to be clear, the project is currently in flight, so you're going to be looking at an install that is currently approaching completion, with a targeted completion of March 15th, so you're going to be looking at a work in progress.

40 00:07:06.270 --> 00:07:07.809 Rick Neubauer (Umojo): Yes, fair, good point.

41 00:07:08.370 --> 00:07:12.020 Rick Neubauer (Umojo): Sorry, let me just get my right screen up here. Okay.

42 00:07:13.210 --> 00:07:14.410 Rick Neubauer (Umojo): And…

43 00:07:18.470 --> 00:07:20.299 Rick Neubauer (Umojo): Okay, there we go, sorry about that.

44 00:07:21.650 --> 00:07:24.280 Rick Neubauer (Umojo): Get my browser windows all straightened out here.

45 00:07:27.920 --> 00:07:29.850 Rick Neubauer (Umojo): Alright.

46 00:07:30.060 --> 00:07:49.790 Rick Neubauer (Umojo): Couple interesting things. This is a newer version of the mapping system that we're using. It's actually tied to the real-time weather, so if it's raining, it rains. If it's sunny, it's sunny. Just some cool… you can turn all that stuff off, but I thought I'd just show it off a little bit today. The areas that we're showing here are the primary study areas, which is Canal District, Chippewa.

47 00:07:49.790 --> 00:08:08.160 Rick Neubauer (Umojo): and medical district, and then these are just different divisions or districts around the city that the city has. A lot of the stuff has just been all… has been tracked, so if you look at, like, for example, districts of the city, where there's different data that's CDS-related are tied at the district level, or also down into each

48 00:08:08.160 --> 00:08:12.059 Rick Neubauer (Umojo): area. You'll see one thing also here, that there's a lot of

49 00:08:12.060 --> 00:08:18.770 Rick Neubauer (Umojo): weird wordings in here. This is our object IDs that we're using for names, but, you know, we've been… we've submitted some…

50 00:08:19.000 --> 00:08:32.010 Rick Neubauer (Umojo): Standardization ideas on how to come up with names, so I think I'd love for people to review some of those. This was actually in the free 1.1, but there's still some, things I think would make

51 00:08:32.039 --> 00:08:48.639 Rick Neubauer (Umojo): some ideas to make things more human-readable would be good, because these are really just, you know, the CDS data as it sits today, and it's a little hard on the eyes, as you guys all know. And then to jump into a couple of the other layers that we're doing, study areas here, like we talked about.

52 00:08:48.640 --> 00:09:08.290 Rick Neubauer (Umojo): I'll talk about the objects. So we've imported and LiDAR scanned a lot of the city, and then we've extracted and imported everything into CDS 1.1. So we talked about the objects, so loading signs, fire hydrants, you can see them all down here on the far right as well. Bike lanes, street poles, bike racks.

53 00:09:08.290 --> 00:09:16.620 Rick Neubauer (Umojo): bus stops, crosswalks, EV chargers, you name it, it's in here, and it's all in a CDS

54 00:09:16.810 --> 00:09:29.660 Rick Neubauer (Umojo): data that's stored inside of our asset management tool, which I'll show a little bit later, and then the data that came from the city, as far as where those signs are located, the types, MUTCD, you know, all the normal things that we're putting in there.

55 00:09:30.170 --> 00:09:44.700 Rick Neubauer (Umojo): Secondly, buses. They wanted us to do the bus routes, bus stops. Bus routes are generally also the snowplow routes as well, so, we're gonna be adding in here real-time tracking of snowplows for the upcoming winter, so you'll be able to see

56 00:09:44.700 --> 00:09:51.110 Rick Neubauer (Umojo): where the snow plows are currently in real time. Something that's interesting with the signage, which I'll drop in here.

57 00:09:51.110 --> 00:09:54.600 Rick Neubauer (Umojo): And Jason will talk to this. We've got 10 signs getting deployed.

58 00:09:54.600 --> 00:10:12.610 Rick Neubauer (Umojo): We've only got 3 because we ran into some bureaucracy issues in the city, and you'll see here, if you look at camera deployments, we've got about 140 cameras deployed across those different study areas, and I'll turn those on as well, just to give you an idea. But what's interesting is, you know, we've got

59 00:10:12.690 --> 00:10:20.489 Rick Neubauer (Umojo): I don't know, 150, 160 cameras deployed, no one said a word, and as soon as we start putting up the signage, they're starting to ask us for permits and things, so…

60 00:10:20.490 --> 00:10:43.849 Rick Neubauer (Umojo): Jason can talk more about that when we get there. The cool thing about the signage is they are really designed for the city to be able to provide real-time updates to people. You know, there's a lot of bad weather in Buffalo in the wintertime. I think they get tons and tons of snow. Interestingly enough, they don't… if you're in the snow area… plow area, they don't tow you and charge you for it, they tow you to the closest

61 00:10:43.870 --> 00:11:01.970 Rick Neubauer (Umojo): parking lot that you can go pick up your car at, so you can still get to work, you know, in a reasonable amount of time. And so, in the signage that we're putting up, they are using things like air quality, you know, alerts for flash flooding or storms that are coming, streets that may be closed.

62 00:11:01.970 --> 00:11:11.840 Rick Neubauer (Umojo): Their system is called Buff Alert, so that you can subscribe to Buff Alert and get these on your phone and what have you, but then we're also pushing them to digital signage that's around the city.

63 00:11:12.220 --> 00:11:26.030 Rick Neubauer (Umojo): And that's what these will look like that are animated. I have a video of one, for example, that we've deployed. These are 55-inch, screens, but we can also do up anywhere down to 32 inch up to 85 inch, and those are deployed, on the street light poles.

64 00:11:26.220 --> 00:11:40.200 Rick Neubauer (Umojo): Vincent Naylin, And, where we're able to get, you know, real-time, information to the customer, or to the citizen, excuse me. And then we're also using it for just general occupancy of zones in the area, how many spaces are available, what have you.

65 00:11:40.910 --> 00:11:43.350 Rick Neubauer (Umojo): Let me get back to my screen here.

66 00:11:43.710 --> 00:11:52.920 Rick Neubauer (Umojo): Now, if we go talk and look at some of the other things here, we talked about street objects. If we look at spaces and zones, this will take a second to load up. We're also doing real-time

67 00:11:52.920 --> 00:12:03.949 Rick Neubauer (Umojo): availability of spaces at the zone level, or at the per space level, depending on what that is. Again, these are all in CDS format, so you can see the current occupancy.

68 00:12:03.950 --> 00:12:16.029 Rick Neubauer (Umojo): Kyle O'by camera or by sensor transaction. We have had some interesting, adjustments that have had to happen with the, transactional stuff. They have parking meters deployed.

69 00:12:16.110 --> 00:12:22.959 Rick Neubauer (Umojo): But they're, coin meters, and they collect the data, but don't actually…

70 00:12:23.010 --> 00:12:40.649 Rick Neubauer (Umojo): grid out where they collected money at, so they handed us this Excel spreadsheet that says, here's how much money we collected across the whole city this week, but there's no way for us to map that, right? So, it's been interesting. Also, they've converted from, I think Passport to ParkMobile. I guess it's technically the same company now, but…

71 00:12:40.650 --> 00:12:44.940 Rick Neubauer (Umojo): Park Mobile had… came out and wanted to put in

72 00:12:45.150 --> 00:12:58.779 Rick Neubauer (Umojo): zones that were basically, like, two blocks around, so everybody that parked around a block or two together would all be in the same parking zone, and then we wouldn't really be able to understand transactional data. So parking

73 00:12:58.780 --> 00:13:09.309 Rick Neubauer (Umojo): transactions based by cameras down to per zone, or per block, or what have you. So, we've added in about another… I want to say, I think we've doubled or time and a half the.

74 00:13:09.360 --> 00:13:22.409 Rick Neubauer (Umojo): the amount of parking zones that are there, so that also came with some interesting side effects, like having to create more signage to put out there, and then getting those signs deployed with more zones on them. So, there's just been some very interesting

75 00:13:22.810 --> 00:13:39.009 Rick Neubauer (Umojo): things that have had to evolve and change, and some of the side effects around that, and deploying those at scale. And then this is some of the things we've been talking about in what I submitted was, you know, we were, if you look here, if you look at the CDS data for a zone, excuse me, we were using

76 00:13:39.420 --> 00:13:59.000 Rick Neubauer (Umojo): available spaces as the number of spaces, not the number of available spaces, right? And so we've changed that on our side, so now we're using, available spaces as the current amount of spaces available, and then we're also using num spaces, which I don't think is in this UI… been updated to the UI yet, but that's the total number of spaces.

77 00:13:59.000 --> 00:14:05.520 Rick Neubauer (Umojo): So that you can see that. Let me just try one and see if we go to one where we do have some cameras up to see if that value's in there.

78 00:14:06.290 --> 00:14:09.410 Rick Neubauer (Umojo): Available spaces is 6, but…

79 00:14:09.600 --> 00:14:24.479 Rick Neubauer (Umojo): Yeah, so it's not quite done yet, but this is one of the things that we submitted was, you know, these are areas where you can park, but one of the interesting things that we were interested about is understanding no parking areas and where you can't park, because we've got cameras up there too, and then defining

80 00:14:24.860 --> 00:14:28.320 Rick Neubauer (Umojo): What can we… how many vehicles are there? How many…

81 00:14:28.530 --> 00:14:34.380 Rick Neubauer (Umojo): spaces can there be in there? And coming up with a methodology for figuring that part out.

82 00:14:34.860 --> 00:14:46.069 Rick Neubauer (Umojo): Obviously, a lot of the no parking spaces don't have a, you know, designated, spaces, they're not tipped, they're not marked, and so we'd have to come up with a way to

83 00:14:46.070 --> 00:14:55.350 Rick Neubauer (Umojo): Define that, or define the number of spaces. Same thing with bus stops. If you look at those, let me see if I can pull one up here… bus routes…

84 00:14:55.430 --> 00:14:57.160 Rick Neubauer (Umojo): And bus stops, sorry.

85 00:14:58.350 --> 00:15:01.469 Rick Neubauer (Umojo): We go here to just, like, Google Street Maps and take a look at it.

86 00:15:02.910 --> 00:15:11.200 Rick Neubauer (Umojo): Wherever this bus stop is, there's no marked spaces for that, or the size of the bus stop, or what have you, and so we're trying to figure out what's the best way for us to

87 00:15:11.200 --> 00:15:23.800 Rick Neubauer (Umojo): Understand how many buses can park at this bus stop, so that we can understand when people park there and block the bus stop, are they blocking the bus stop? Are they blocking the area behind the bus stop? You know, so on and so forth. And so there's some interesting

88 00:15:23.800 --> 00:15:40.159 Rick Neubauer (Umojo): methodologies, we've put together ideas on how to solve that. And then the last one I think that's important here, too, is areas. So, we've gotten a lot of requests for custom areas. If you zoom out here, and I'll just show you a little bit more of the city, then you can see the custom areas here, like Chippewa or Washington's

89 00:15:40.220 --> 00:15:52.990 Rick Neubauer (Umojo): Street, which are these areas here. And we are also aggregating all the data. These are all the cameras, these are all the meters, the zones, the spaces that are in those custom areas. Same with this one over here.

90 00:15:52.990 --> 00:16:02.649 Rick Neubauer (Umojo): What's interesting is that we… and we've got this tied into an asset management tool, which I'll show you as well. So, in our asset management tool, which is 100% CDS-driven.

91 00:16:02.690 --> 00:16:08.790 Rick Neubauer (Umojo): You can create custom areas in here, so if you go into areas, create a custom area.

92 00:16:08.790 --> 00:16:10.579 Rick Neubauer (Umojo): say, okay, I'm gonna add a new one.

93 00:16:10.580 --> 00:16:29.250 Rick Neubauer (Umojo): They can be nested, they can include the layers that you want of objects. We're going to be making it where you could also drill down and select certain… I probably want certain bus stops, or certain meters, or certain bike racks in a particular area. And then you can, go in here and draw that, you know, in the map, wherever you want that… those areas to be.

94 00:16:29.640 --> 00:16:32.710 Rick Neubauer (Umojo): Save that as a custom area. Oop.

95 00:16:32.920 --> 00:16:51.540 Rick Neubauer (Umojo): And then, you know, save it, put a color on it, a border, just like all the CDS stuff. But what we wanted to do was also make it where it could be, have a parent-child relationship. And the reason we're doing that is that if we're doing, let's just say, if I go back to the map for a second and look at all these areas.

96 00:16:51.770 --> 00:16:56.440 Rick Neubauer (Umojo): separate. So, for example, the study areas here… let's pull them up.

97 00:16:57.410 --> 00:16:58.649 Rick Neubauer (Umojo): Turn these off.

98 00:16:58.870 --> 00:17:07.929 Rick Neubauer (Umojo): then these 3 areas are all separate, and I can click on them and get enforcement data, occupancy data, once we start, you know, getting the rest of the transactional data in there.

99 00:17:07.930 --> 00:17:31.560 Rick Neubauer (Umojo): But I also would want to see it across all of the study areas aggregated together. So you could still create a super area, if you will, at a higher level than these three, and then when you clicked on that higher level area, it would aggregate all of the data from the sub-areas, so you could see all the statistical information and CDS information, number of assets, you know, transactions, things like that, that were part of that as well. So, that's one of the other

100 00:17:31.640 --> 00:17:41.500 Rick Neubauer (Umojo): Rory Bilocerkowycz, things that we submitted as an additional need that we… that customers are asking us for, that we think makes sense and, is a good direction to go.

101 00:17:41.840 --> 00:17:56.599 Rick Neubauer (Umojo): That's kind of all I have today. I think, you know, we've still got some cameras that we're finishing on getting deployed, and I'll have a lot more information in about a month or so from now, as well as, like, historical data, analytics from the cameras, and, you know, matched with transactional data.

102 00:17:56.600 --> 00:18:03.710 Rick Neubauer (Umojo): But at least for now, this is where we're at at this point, and I'll hand it over to Jason for a minute to talk about some of the…

103 00:18:03.710 --> 00:18:07.540 Rick Neubauer (Umojo): Trials and tribulations we've had with this project.

104 00:18:08.470 --> 00:18:21.439 Jason Peckham (Umojo): Perfect, thanks, Rick. Yeah, I'd like to… I'm kind of boots on the ground, been delivering now, for a little over a year with Buffalo. Just some high points I'd like to speak to for individuals who are approaching

105 00:18:21.440 --> 00:18:33.999 Jason Peckham (Umojo): What we're going through, which is, primarily at this point a migration away from solar to AC, one of the key deliverables… so I… my primary focus is, schedule, budget, and risk.

106 00:18:34.190 --> 00:18:42.870 Jason Peckham (Umojo): When you're looking at schedule, every single, every single city that we interface with has a different landscape in relation to light standards or light poles.

107 00:18:42.900 --> 00:18:58.709 Jason Peckham (Umojo): In terms of ownership, or partial ownership, or collections of ownership. In some cases, you're looking at dealing with the power company. Other cases, you're looking at dealing with a combination of the power company, as well as the city's own electricians.

108 00:18:58.710 --> 00:19:06.989 Jason Peckham (Umojo): And so then you end up in a hybrid environment where you've got a power company and interfacing with them and their approval timelines. And if I was to give an estimate.

109 00:19:07.270 --> 00:19:19.539 Jason Peckham (Umojo): if you're forecasting a timeline for project delivery and you have to interface with your local utility, 12 to 18 months. You have to be fortunate to be able to intersect with their tariff schedule, which happens on an annual basis.

110 00:19:19.540 --> 00:19:31.730 Jason Peckham (Umojo): And if you happen to have just missed it, there is no capacity for exception or moderation. You need to wait for the next cycle to come around before you're going to get approval for the deployment of hardware, so on and so forth.

111 00:19:31.730 --> 00:19:40.139 Jason Peckham (Umojo): Our general approach is to provide the hardware for the install, the powering of the install. In our experience with larger utilities.

112 00:19:40.140 --> 00:19:46.189 Jason Peckham (Umojo): They want to, they themselves want to procure and deliver the hardware.

113 00:19:46.190 --> 00:20:00.369 Jason Peckham (Umojo): And then they would dole it out to the municipality in a subscription-based service. So when it comes to your ongoing operating costs, it it it definitely has an impact in relation to increasing the carrying cost of the of the solution that's passed through from the carrier.

114 00:20:00.950 --> 00:20:24.130 Jason Peckham (Umojo): Or the utility. The other piece is the quality of the light standards you're dealing with. You know, our goal at this point is moving everything to NEMA. You approach poles that are in various states of disarray. They have AC sockets, fuses that are blown. We are currently operating in a hybrid environment where we have solar AC switched, where we're dealing with power that comes on at night when the light comes on, as opposed to during

115 00:20:24.130 --> 00:20:27.569 Jason Peckham (Umojo): the day, and then our goal, obviously, to move towards AC full.

116 00:20:27.610 --> 00:20:43.750 Jason Peckham (Umojo): Some key observations from some of our key customers were, originally capturing a 2-minute increment simply just did not provide, a level of detail in relation to the data, such that it was usable from a planning perspective, and as such, we've moved to 30-second increments.

117 00:20:43.750 --> 00:20:54.619 Jason Peckham (Umojo): We can… we can support 30-second increments on AC switched, but we're gravitating towards a standard of AC full. AC switched, with 30 seconds.

118 00:20:54.620 --> 00:21:11.519 Jason Peckham (Umojo): If you don't augment the device with additional battery battery capacity, then you're just operating with too thin of a margin, which puts you in a situation where from a sustainment perspective, you're just not going to see the uptime that you're you would be looking for in terms of using it on a day-to-day basis to support your operational activities.

119 00:21:11.590 --> 00:21:20.810 Jason Peckham (Umojo): To Rick's point, we are approaching the digital signage install. The key learning here for us in relation to that was Buffalo has recently had an administration change.

120 00:21:20.810 --> 00:21:32.219 Jason Peckham (Umojo): So as a result of an administration change from a project management perspective, it probably bodes well to just revisit the departments you had the standing agreements with at the beginning of the project to ensure that it still stands.

121 00:21:32.220 --> 00:21:46.740 Jason Peckham (Umojo): We're in a situation where, we've just simply been required to pull some additional permits that weren't required for the previous 200 installs that we've done, and it put a small wrinkle on our timeline, but it's not something that, we can, we can work through.

122 00:21:46.740 --> 00:22:02.969 Jason Peckham (Umojo): As an addendum to the digital signage subject, we have 3 installed. Our goal was to complete the other 10 55-inch, last week. As I mentioned, I'm just working through the details associated with that permit. We'll complete that, in the next 8 to 10 business days.

123 00:22:02.970 --> 00:22:18.310 Jason Peckham (Umojo): And then in the first quarter of next year, we have, 20 smaller, E-Ink signs that we refer to, more kind of replacing your form factor, red and white, parking signs on the side of the… on the side of the road, and we'll put those in the first part of next year.

124 00:22:18.310 --> 00:22:31.719 Jason Peckham (Umojo): One of the key considerations for the larger digital signs is the same way that there's a vast amount of variability in terms of the power and the quality of the devices that we have in the field.

125 00:22:31.740 --> 00:22:41.269 Jason Peckham (Umojo): Putting those large digital signs on light standards, we need to ensure that the base is strong enough to be able to hold that sign when it catches wind during a winter storm.

126 00:22:42.740 --> 00:22:43.290 Rick Neubauer (Umojo): Yep.

127 00:22:43.440 --> 00:23:07.750 Rick Neubauer (Umojo): Yeah, I think one of the things with that was just, like, even to the point where we had to get an engineering team to look at the models of the signs, the weight of the… sorry, models of the poles, the weight of the signs, and then certify that they're okay up to 100 miles an hour versus of wind for safety concerns. One other interesting one here I'll show you, real last thing here is… is the mounting system. We were toying around with different mounting systems, and it just…

128 00:23:07.950 --> 00:23:18.919 Rick Neubauer (Umojo): became apparent that what we were seeing out there that you, you know, that's available was not very good, so, we ended up building our own. I'll pull one up here real quick, here it is.

129 00:23:19.150 --> 00:23:26.940 Rick Neubauer (Umojo): There it is. So you can see here that we've got a very hard, sturdy, you know, machined metal steel mount. I know that sounds…

130 00:23:26.940 --> 00:23:43.750 Rick Neubauer (Umojo): like, not important, but man, if these things fly off and hit somebody or whatever, it's a lot of, you know, very dangerous. So, that was one of the interesting other scenarios that we had to… or issues we had to resolve as well, which turned out great, but again, just to have, again, another engineer involved to build some

131 00:23:43.750 --> 00:23:46.369 Rick Neubauer (Umojo): Some designs, and then get them manufactured, so…

132 00:23:50.070 --> 00:24:02.599 Michael Schnuerle (OMF): Well, thank you, Rick and Jason. Let's take some questions. I've got a few, and then you all, Rick and Jason, if you want to go through the chat and answer some of the questions there, and then we can elevate

133 00:24:02.700 --> 00:24:06.180 Michael Schnuerle (OMF): You could share vocally some things if you'd like.

134 00:24:06.320 --> 00:24:11.389 Michael Schnuerle (OMF): One of the things I'll… I'll just say, like, when you showed the map of

135 00:24:11.660 --> 00:24:15.790 Michael Schnuerle (OMF): Every curb zone, you've got some curb areas, and then you've got

136 00:24:16.090 --> 00:24:30.339 Michael Schnuerle (OMF): thousands of objects on there, and then some bus routes. That's, like, peak CDS right there, peak coding. It's nice to see all that in one place. You know, raise your hand if you're a city and you want to see that for your city.

137 00:24:30.470 --> 00:24:39.580 Michael Schnuerle (OMF): And I know you're working behind the scenes to sort of… with that… the internal workflow for how signs get updated and all that.

138 00:24:39.730 --> 00:24:43.450 Michael Schnuerle (OMF): I'm curious, is anyone from Buffalo on the call?

139 00:24:44.690 --> 00:24:45.380 Michael Schnuerle (OMF): Or no?

140 00:24:45.380 --> 00:24:47.480 Rick Neubauer (Umojo): I don't think anybody from Buffalo's on the call today, no.

141 00:24:47.480 --> 00:24:53.440 Michael Schnuerle (OMF): Right. But I'm sure they'd be willing to talk about it as well. Yeah, we'll get them on the next call.

142 00:24:53.440 --> 00:25:01.000 Rick Neubauer (Umojo): call for sure. It was, I just, I dropped the ball on my side to get everything, everybody lined up for this in time. So.

143 00:25:01.000 --> 00:25:04.940 Michael Schnuerle (OMF): Yeah, that's fine. And… but it's nice to see all that together.

144 00:25:06.650 --> 00:25:07.270 Jason Peckham (Umojo): Oh, no.

145 00:25:07.270 --> 00:25:18.569 Michael Schnuerle (OMF): I know that you've been using MDS a little bit as well. Are you using MDS for any of this? Like, maybe the bus stops, or bus routes, or GTFS?

146 00:25:19.010 --> 00:25:34.250 Rick Neubauer (Umojo): Yeah, no, there's nothing in here for MDS or GTFS today. Well, I'm not saying that… we're gonna be adding that in. They're right in the middle of moving from one, real-time notification system to another. We haven't even looked at the GTFS for the bus stuff yet.

147 00:25:34.250 --> 00:25:39.249 Rick Neubauer (Umojo): But we, like I said, we're, they're moving, I forgot the name of the new one, but they're gonna be moving to all the snow plows.

148 00:25:39.310 --> 00:25:56.109 Rick Neubauer (Umojo): Because that's where the bigger… I guess my point is that the problems they're trying to solve are issues happening in the winter with bus routes and snowplow routes and people's cars being left in the street and understanding where those problem areas are. And so that's been the first one for us to tackle with a real-time.

149 00:25:56.110 --> 00:25:56.620 Michael Schnuerle (OMF): Yes.

150 00:25:56.620 --> 00:26:04.979 Rick Neubauer (Umojo): And, but we are, we will add in some of the, the, the other, sharing systems as well, of course, the other data shares.

151 00:26:05.630 --> 00:26:18.089 Michael Schnuerle (OMF): And if you're not… if anyone's not aware, MDS supports, fixed route transit and connects to GTFS, so if you knew where the buses are gonna be, and then you wanted to monitor

152 00:26:18.540 --> 00:26:35.040 Michael Schnuerle (OMF): When a bus is actually at a stop, you can define the stops in MDS, link over to how they're defined in GTFS, and then track activity there as well. And that activity, of course, can be tracked in some ways in CDS, but MDS supports that.

153 00:26:35.040 --> 00:26:48.009 Michael Schnuerle (OMF): For things like even passenger counts on and off and things like that. Alright, so I'll stop there. I could ask more questions, but let's see. Do you want to elevate anything from the chat, or does anyone want to…

154 00:26:48.110 --> 00:26:51.849 Michael Schnuerle (OMF): Bring up, something they've asked, and ask.

155 00:26:52.390 --> 00:26:53.840 Michael Schnuerle (OMF): In their own words.

156 00:26:55.790 --> 00:27:09.729 Rick Neubauer (Umojo): Yes, I'm looking through, like, Lisa Hood from San Jose asks, are those black zones with the zeros pay stations? Yes, those are pay stations. If you turn them on here, meters, those are little dots, and if you click on them, actually, you can also turn on the.

157 00:27:10.650 --> 00:27:19.299 Rick Neubauer (Umojo): unless we changed it. You should be able to change even the the logo. But if you click on that device and see the meter, then there's the meter Id, and that's a flow bird meter.

158 00:27:19.400 --> 00:27:22.449 Rick Neubauer (Umojo): With the current policy that's applied there.

159 00:27:25.780 --> 00:27:38.399 Rick Neubauer (Umojo): Next question was more about the loading zone permits. Oh, yeah, sure. So, okay, this, well, loading zone permits are interesting in Buffalo because… and let me kind of narrow it down to just those.

160 00:27:39.980 --> 00:27:41.299 Rick Neubauer (Umojo): You can see them here.

161 00:27:41.610 --> 00:27:43.489 Rick Neubauer (Umojo): The interesting part is, is that

162 00:27:44.310 --> 00:27:47.800 Rick Neubauer (Umojo): It's a very rudimentary system, and…

163 00:27:48.510 --> 00:27:51.470 Rick Neubauer (Umojo): If you're a business, you can apply for a permit.

164 00:27:51.600 --> 00:28:05.090 Rick Neubauer (Umojo): and then you go and buy your own signs, and put your own signs in front of your building and where they are. Now, these are the ones that are… that we knew about, or we've been told about, but when we did the signage, the extraction for the LiDAR.

165 00:28:05.200 --> 00:28:20.649 Rick Neubauer (Umojo): There was hundreds of them out there from really old time, from years ago that hadn't been changed. There was fake ones that were deployed that no one ever got a permit for, so it's, it's taken a little bit of time to kind of clean all that up and come back, and then what we're introducing to the city is an actual permit.

166 00:28:20.820 --> 00:28:35.199 Rick Neubauer (Umojo): permitting system that they can, have customers or citizens or business owners request a permit and then manage it properly, so that when permits expire, they're getting notified properly, people aren't putting just permits up.

167 00:28:35.200 --> 00:28:48.779 Rick Neubauer (Umojo): Or I'm sorry, loading zone signs up, ad hoc without getting a permit. And so this was just a display, you know, what's what's been out there today, that we knew about or were told about when we, took this project on.

168 00:28:48.780 --> 00:29:01.659 Jason Peckham (Umojo): Buffalo's intent is to use the system as the system… as the system of record. This is one of the current, one of the current, administrative realities that they currently don't have a system to manage, so as such, it's.

169 00:29:01.660 --> 00:29:08.930 Jason Peckham (Umojo): somewhat a little bit ad hoc, but as they're working through, ramping up on using the system, they're hoping to manage this better through using Next City.

170 00:29:10.940 --> 00:29:25.629 Rick Neubauer (Umojo): Chris from Philadelphia asked about, what are the limitations on the kind of infrastructure the signs can be attached to? I think it's really about just the weight. I mean, the signs are about 85 pounds for a 55 inch, so, you know, you want to make sure that it's, it's

171 00:29:25.630 --> 00:29:33.840 Rick Neubauer (Umojo): dirty enough to hold it up, whatever it is, but we can build a mount that will work however, you know, that needs to be… however it needs to be done. I think

172 00:29:33.880 --> 00:29:36.749 Rick Neubauer (Umojo): The the caveat is gonna be excuse me.

173 00:29:37.120 --> 00:29:42.790 Rick Neubauer (Umojo): is the type of mount. I mean, what I showed you on the mounting pole was, you know, static mount.

174 00:29:43.030 --> 00:29:55.089 Rick Neubauer (Umojo): It does, tilt the screen down, so you can adjust it, vertically to aim down to, like, focus on people driving versus, you know, looking up in the sky because of the… of the… of the, the.

175 00:29:55.090 --> 00:30:10.910 Rick Neubauer (Umojo): of how the street lights work, you know, they're tapered from narrow at the top to a little bit wider at the bottom, so we adjusted for… countered for that. So I think just whatever… wherever you want to mount it to, we just gotta take some measurements, look at it, make sure that it's structurally sound, and then figure out the best way

176 00:30:10.910 --> 00:30:26.579 Rick Neubauer (Umojo): to, mount to it. The signs themselves are a standard VESA mount, like you would find on a Samsung or, you know, a TV you buy at the electronics store. Same standard VESA 100mm or 200mm mount, depending on the size of the screen.

177 00:30:27.020 --> 00:30:33.840 Rick Neubauer (Umojo): Joe McCormick, And so, you could put it on a regular old TV mount if you wanted to, but I just, you know, obviously wouldn't recommend it out in the wild.

178 00:30:37.000 --> 00:30:42.349 Rick Neubauer (Umojo): These are not replacing physical signs, these are just another layer of…

179 00:30:42.570 --> 00:30:53.290 Rick Neubauer (Umojo): user updates, there's some digital… there's a management system that we have where you can, set up the signage the way you want, you know, Happy Holidays.

180 00:30:53.290 --> 00:31:04.089 Rick Neubauer (Umojo): scan this QR code to subscribe to Buff Alert, you know, can do seasonal types of things, and then the emergency notification system is integrated into Buff Alert, so if they send out

181 00:31:04.090 --> 00:31:19.809 Rick Neubauer (Umojo): a notification with text messaging or whatever, then it pops up on the signs that are associated with those areas that are affected, with the messaging. And so, they aren't replacing anything from a signage perspective today, it's just an additional layer, including the.

182 00:31:20.000 --> 00:31:29.420 Rick Neubauer (Umojo): Joe Schilling, parking, availability at different parking areas around that, too, if they're not being used for emergency type of, of needs.

183 00:31:30.770 --> 00:31:47.049 Rick Neubauer (Umojo): What types of messaging go on the sides? I sent a pic… I showed a couple of pictures. I mean, it could also be tied into a few of the different standards. I think Minneapolis had a, in their RFP for Stage 2. They're using a… I forgot the particular protocol off the top of my head, but we wrote a connector for that.

184 00:31:47.060 --> 00:31:52.780 Rick Neubauer (Umojo): So that it can tie into the standardized messaging, just like you see on highway.

185 00:31:52.810 --> 00:32:07.229 Rick Neubauer (Umojo): on highways or in, you know, over exits and entrances, or wherever there's DOT matrix signage, it can be tied into that. An interesting one here, too, that we're working with is, you know, obviously, Buffalo's right across the river from

186 00:32:07.230 --> 00:32:20.750 Rick Neubauer (Umojo): Canada, and so sometimes the bridges get shut down, so we're working on an integration with, Jason, what's the name of that, group that manages all of the roads in Canada and Buffalo?

187 00:32:20.980 --> 00:32:23.350 Jason Peckham (Umojo): Oh, I don't have the acronym at the top of my head, Rick, sorry.

188 00:32:23.350 --> 00:32:47.169 Rick Neubauer (Umojo): Yeah, I forgot that acronym, but they have a full, we're integrating to that so we can provide real-time notifications to them about air issues happening in Buffalo, and the same for them providing to us, so that if, you know, the highway, gets shut down and trucks are driving through Buffalo to go north to take this other bridge up to get into Canada, then we're sending alerts to the signage about that as to… that's not quite finished yet, but another interesting

189 00:32:47.170 --> 00:32:49.450 Rick Neubauer (Umojo): Side note about how we're using that.

190 00:32:49.900 --> 00:32:51.100 Rick Neubauer (Umojo): I can see it.

191 00:32:51.390 --> 00:32:59.259 Michael Schnuerle (OMF): Do you… are you using it all for occupancy, to say, like, you know, 3 of 6 spaces available on this block, or something like that? Yeah.

192 00:32:59.260 --> 00:33:04.659 Rick Neubauer (Umojo): Yeah, yeah, let me show you… I've got another… let me… and this is a different sign for… I mean, this is on a different,

193 00:33:04.760 --> 00:33:24.260 Rick Neubauer (Umojo): But yes, I mean, the catch is I didn't have any of the signs deployed that I wanted to show, or that have the off-street locations close enough to where I could show it to you, but I'll give you an example of what it would look like. I mean, and they can be branded however the city wants, but, you can see on this one here that it looks like this, for example.

194 00:33:24.260 --> 00:33:36.519 Rick Neubauer (Umojo): So it would say, hey, here's the courthouse lot, Clarendon Boulevard, North Adams, current rate, you know, is there parking available? How many spaces available? Is there a special event? How much is that special event? What have you.

195 00:33:36.520 --> 00:33:41.050 Michael Schnuerle (OMF): Yeah, so it's useful not just for where it's mounted, but areas nearby, too.

196 00:33:41.170 --> 00:33:42.250 Michael Schnuerle (OMF): Yep, exactly.

197 00:33:42.400 --> 00:33:43.490 Rick Neubauer (Umojo): Exactly.

198 00:33:44.500 --> 00:33:51.150 Michael Schnuerle (OMF): All right, well, let's pause there on the presentation side of things. If people have more questions, leave them in the chat.

199 00:33:51.380 --> 00:33:57.660 Michael Schnuerle (OMF): And, what I'd like to do is go on to… Rick, if you wanna…

200 00:33:57.940 --> 00:34:01.000 Michael Schnuerle (OMF): I'm gonna replace your share with…

201 00:34:01.480 --> 00:34:04.879 Michael Schnuerle (OMF): Where is it? Hold on, I gotta find my…

202 00:34:06.310 --> 00:34:08.480 Michael Schnuerle (OMF): Where my slides are, but

203 00:34:09.320 --> 00:34:16.429 Michael Schnuerle (OMF): Yeah, I want to go to look at the open issues that you've also opened, and you mentioned a few of them.

204 00:34:16.590 --> 00:34:18.210 Michael Schnuerle (OMF): potentially

205 00:34:18.489 --> 00:34:31.809 Michael Schnuerle (OMF): and see how they… what you're wanting to do overlaps with what you presented, and with what is in CDS now, and what you want it to be. So, here are the four issues that you had opened.

206 00:34:31.949 --> 00:34:48.870 Michael Schnuerle (OMF): Let's… we'll just go through them one at a time. Today, I'd say what I'd like to do today is just give a high-level, less than 5 minutes for each one, so people are familiar with it. And then everyone who's watching, you can go down here and leave your own comments.

207 00:34:48.989 --> 00:34:57.319 Michael Schnuerle (OMF): If you make a free GitHub account and leave your thoughts. So, Rick, for this one, start off by saying, like.

208 00:34:57.730 --> 00:35:02.299 Michael Schnuerle (OMF): What is the problem, and what is your suggested solution?

209 00:35:03.100 --> 00:35:16.840 Rick Neubauer (Umojo): Yep, no worries. So for us, the areas exist today, and you can have any number of areas, and they can overlap, and… but they aren't interconnected. And so what we ran into was, this was in San Jose, where they were saying, look, I've got

210 00:35:16.870 --> 00:35:36.100 Rick Neubauer (Umojo): 3 different… they were gonna do some, changing of pricing for their meters, but they wanted to look at some of the data and aggregate the data across 3 different areas separately, but then also have it to be able to be rolled up into a… another area that would show all of the aggregated data of the sub-areas

211 00:35:36.120 --> 00:35:50.760 Rick Neubauer (Umojo): Van Wilson, in that parent area. Right? So that's the whole was the main driver for this. And so that's why we said, Okay, maybe we can come up with a way to have areas that have parents. And then we can aggregate the data together. And so that was really the the driver behind this one.

212 00:35:51.380 --> 00:35:59.380 Michael Schnuerle (OMF): Yeah, and it seems like your solution is two options, or two potential changes. One is.

213 00:35:59.380 --> 00:36:13.130 Michael Schnuerle (OMF): make the inclusion of zone IDs conditionally required, because if you have a parent area, it won't have any zone IDs. Only the lowest area might. And then.

214 00:36:13.930 --> 00:36:18.200 Michael Schnuerle (OMF): Yeah, maybe make… allow multi-polygon in addition to polygon, so you can

215 00:36:18.340 --> 00:36:29.949 Michael Schnuerle (OMF): put things together. And then, do you have a… oh, this is new, I guess, child area IDs and parent area IDs, right? Yeah, new, new, new.

216 00:36:30.880 --> 00:36:34.430 Michael Schnuerle (OMF): And then this real quick, this Curb objects one.

217 00:36:34.650 --> 00:36:38.880 Michael Schnuerle (OMF): Are you thinking these are objects that are not in any zone, or…

218 00:36:38.880 --> 00:36:42.050 Rick Neubauer (Umojo): Yeah, these are just the regular curb objects, remember? Like, so, like.

219 00:36:42.050 --> 00:36:42.370 Michael Schnuerle (OMF): Yeah.

220 00:36:42.430 --> 00:36:51.890 Rick Neubauer (Umojo): If you do, like, a bus stop, or a parking meter, or a… I mean, we're starting to do a lot of stuff that are outside just regular old

221 00:36:51.920 --> 00:37:05.409 Rick Neubauer (Umojo): space, you know, zone, space, you know, meter, and so if they… if you want to be able to create an area that has that in there, keep it in a CDS approach, but use device, you know, whatever. Let's use.

222 00:37:05.410 --> 00:37:05.960 Michael Schnuerle (OMF): There we go.

223 00:37:05.960 --> 00:37:15.150 Rick Neubauer (Umojo): bike racks or an Amazon, you know, locker that's on the side of the road, you could still do that and show it in an area and use it this way.

224 00:37:15.150 --> 00:37:29.490 Michael Schnuerle (OMF): Yeah, so you want to show some things that have typically been set as connected to a curb zone or a curb space as required. You want to be able to show them at a higher level where they're not really associated with any particular zone, right?

225 00:37:29.710 --> 00:37:30.660 Rick Neubauer (Umojo): Yep, exactly.

226 00:37:30.660 --> 00:37:42.820 Michael Schnuerle (OMF): Yeah. Okay. Well, I think there's a lot going on here. There's, it's hard for me to tell if this would be breaking or not, but I think we're open to breaking changes going into the new year.

227 00:37:42.820 --> 00:37:45.489 Rick Neubauer (Umojo): I think it talks… it explains that at the top, though, too.

228 00:37:45.490 --> 00:37:46.220 Michael Schnuerle (OMF): Yeah.

229 00:37:46.890 --> 00:37:49.789 Michael Schnuerle (OMF): So, that's fine if,

230 00:37:49.790 --> 00:37:52.370 Rick Neubauer (Umojo): It's very tough. Additive, non-breaking, there you go.

231 00:37:52.560 --> 00:37:59.590 Michael Schnuerle (OMF): Yeah, I think it actually… some of this would probably be breaking, in a way, because If you…

232 00:38:00.120 --> 00:38:03.950 Michael Schnuerle (OMF): Hmm. If you, like, I don't know, like, the fact that, like,

233 00:38:05.020 --> 00:38:08.160 Michael Schnuerle (OMF): An object ID doesn't have to be part of a zone.

234 00:38:08.650 --> 00:38:25.760 Michael Schnuerle (OMF): might be breaking, maybe. But anyway, we could talk about it, and I think it's okay, though, if it's breaking, because we're looking at doing a lot of new things with MDS and CDS in the new year, so we could have breaking changes. We could have a 2.0 CDS or something bigger happening.

235 00:38:26.340 --> 00:38:30.060 Michael Schnuerle (OMF): So, if anyone has thoughts on this, leave feedback.

236 00:38:31.920 --> 00:38:35.090 Michael Schnuerle (OMF): That's an interesting one. Let's go to the next one.

237 00:38:35.790 --> 00:38:36.630 Michael Schnuerle (OMF): Right.

238 00:38:38.360 --> 00:38:42.509 Michael Schnuerle (OMF): Okay, Rick, talk about this one.

239 00:38:42.890 --> 00:38:55.240 Rick Neubauer (Umojo): Yeah, this is the one for… for… so, okay, if you look at zones, the zones, the way they're set up today, the definition of num spaces is… is demarcated spaces in the zone.

240 00:38:55.290 --> 00:39:13.080 Rick Neubauer (Umojo): And where this kind of popped up is, remember, we're not only tracking parking areas with cameras, but we're also tracking non-parking areas, no-stopping areas, bus zones, you know, loading zones, what have you. And a lot of them, especially where cities are shifting to a zone approach.

241 00:39:13.190 --> 00:39:27.520 Rick Neubauer (Umojo): aren't marking spaces at all, and so we didn't really have a way to say, okay, if there's no… if, first of all, a zone is demarcated spaces, it says right there under the problem, so we've got to get rid of that. And then also, we've got to still come up with a

242 00:39:27.690 --> 00:39:45.140 Rick Neubauer (Umojo): method that we use to… to calculate how many spaces are in that zone based on its length, is what we think, right? So if you take… obviously everything in CDS is in meters, but if you shifted 24 meters to 79 feet, then you've got to be able to understand how many vehicles can fit in there.

243 00:39:45.280 --> 00:39:47.989 Rick Neubauer (Umojo): Then you've got to come up with a…

244 00:39:48.240 --> 00:40:04.480 Rick Neubauer (Umojo): approach that I think is standardized across all the cities. Now, at first, I thought this was gonna be a super easy one to solve, and then the more I got involved in it, it just started getting more complicated and more complicated, and it's funny because I was like, well, you know, if Buffalo says the average

245 00:40:04.480 --> 00:40:19.670 Rick Neubauer (Umojo): stalls or car size is 18 feet, another city says it's 15 feet, then maybe we should probably store those as, you know, as variables or as data in a configuration database, or I'm sorry, configuration table inside of

246 00:40:19.670 --> 00:40:32.889 Rick Neubauer (Umojo): CDS so that, and when I went to a city and they said, Hey, our cars are 549 or 549 centimeters, our vans are 700 trucks or 823, then I could still use that to calculate.

247 00:40:32.890 --> 00:40:39.769 Rick Neubauer (Umojo): classes at Zones when… when I was, you know, doing it out, from a third-party, CDS link, right?

248 00:40:39.780 --> 00:40:44.069 Rick Neubauer (Umojo): But then that requires, like, okay, then if we're doing that, do we…

249 00:40:44.540 --> 00:41:00.179 Rick Neubauer (Umojo): There's estimated capacity was a way to do it. So there's a few different options that we put in there. One of them is a little, it's very simple that we don't have anything stored in CDS. And one I think is a little bit more complete, but would also require some changing of the way the schema is today.

250 00:41:00.660 --> 00:41:01.390 Michael Schnuerle (OMF): Okay.

251 00:41:01.870 --> 00:41:08.940 Michael Schnuerle (OMF): Yeah, this is an interesting one. I know it's come up before. Let's just take a peek real fast at…

252 00:41:09.780 --> 00:41:13.610 Michael Schnuerle (OMF): The, curb… Zone.

253 00:41:13.780 --> 00:41:17.390 Michael Schnuerle (OMF): object here… Where we have…

254 00:41:17.390 --> 00:41:18.500 Rick Neubauer (Umojo): Some spaces.

255 00:41:18.500 --> 00:41:19.720 Michael Schnuerle (OMF): Yeah.

256 00:41:20.680 --> 00:41:27.360 Michael Schnuerle (OMF): So we have… what's… so I think, like, there's num spaces, and it's integer, a number of spaces, and it's hard to know.

257 00:41:27.470 --> 00:41:33.019 Michael Schnuerle (OMF): And then… Why, that's the width of the curve.

258 00:41:34.120 --> 00:41:34.790 Michael Schnuerle (OMF): This is a…

259 00:41:34.790 --> 00:41:35.400 Jacob Malleau (CurbIQ): wonder.

260 00:41:35.400 --> 00:41:39.440 Michael Schnuerle (OMF): And then, real quick, why not use this,

261 00:41:40.250 --> 00:41:45.359 Michael Schnuerle (OMF): Available space lengths, where you get an array of all, like, you could have

262 00:41:45.900 --> 00:41:48.309 Michael Schnuerle (OMF): If you had 7 car spaces, you would just.

263 00:41:48.310 --> 00:41:48.710 Jacob Malleau (CurbIQ): sense.

264 00:41:48.710 --> 00:41:58.839 Michael Schnuerle (OMF): enumerate those seven places. But you're saying you wouldn't really do that because you might have a large truck taking up a piece of a zone and then a car in another zone, another.

265 00:41:58.840 --> 00:42:08.879 Rick Neubauer (Umojo): Yeah, yeah, exactly. So some of the things that we're doing now, like, for example, let's just say there's 5 car spaces, but a big truck comes and parks there, doesn't mean there's 4 spaces, then there's only 3.

266 00:42:09.090 --> 00:42:21.940 Rick Neubauer (Umojo): Right? So, because some of the models we're using now are doing a size estimation on the vehicle, and then showing available spaces versus, you know, just number of spaces minus one vehicle, two vehicle, three vehicle, right?

267 00:42:22.280 --> 00:42:25.199 Michael Schnuerle (OMF): Yep. And did I hear Jacob wanting to say something?

268 00:42:25.710 --> 00:42:27.649 Jacob Malleau (CurbIQ): Yeah, I was just gonna say…

269 00:42:27.790 --> 00:42:34.920 Jacob Malleau (CurbIQ): What we've dealt with with cities is every city does have, like, as Rick was saying, a different assumption for what they want for.

270 00:42:35.130 --> 00:42:39.830 Jacob Malleau (CurbIQ): the length of a space when we do our calculation, so even with option B.

271 00:42:40.070 --> 00:42:42.990 Jacob Malleau (CurbIQ): Even just being able to say in the metadata.

272 00:42:43.160 --> 00:42:52.779 Jacob Malleau (CurbIQ): This is the… assumed length of a space, unless… unless specifically demarcated. Yeah, yeah. That would be enough, too.

273 00:42:54.010 --> 00:43:07.660 Rick Neubauer (Umojo): @thecurtiseaton: something that would pass right, Jacob, where, like, if I hit your Cds, you would have put some kind of in there to be like, Hey, by the way, our standard space length is 18 feet or 17 feet, or whatever that. And and what's interesting is, we went to the cities and asked them, and

274 00:43:07.660 --> 00:43:16.890 Rick Neubauer (Umojo): And every city had a different length for their standard length, which is what was so… I thought… I thought they would all sit at the same distance, or the same amount, and it wasn't the same, so…

275 00:43:17.270 --> 00:43:17.820 Michael Schnuerle (OMF): Yep.

276 00:43:18.270 --> 00:43:19.210 Michael Schnuerle (OMF): Olivier?

277 00:43:20.250 --> 00:43:23.119 Olivier Audet: Yeah, and also the…

278 00:43:23.540 --> 00:43:32.020 Olivier Audet: Estimate length for space vary in some places. Sometimes we tighten it because of some restriction.

279 00:43:32.130 --> 00:43:35.720 Olivier Audet: So that may vary in the field.

280 00:43:35.870 --> 00:43:40.270 Olivier Audet: So I like the estimated capacity.

281 00:43:41.070 --> 00:43:43.480 Olivier Audet: This is really what it are. It is.

282 00:43:43.610 --> 00:43:49.059 Olivier Audet: So you have, like, length, and you estimate about how many vehicles can go there.

283 00:43:49.650 --> 00:44:02.810 Olivier Audet: I can see also my teams, we use, LPR to do some, parking studies, using that to having, the estimated capacity for, section.

284 00:44:03.370 --> 00:44:06.079 Olivier Audet: So that's 1 I think it's interesting, isn't it?

285 00:44:06.520 --> 00:44:08.579 Olivier Audet: It's just another field.

286 00:44:08.690 --> 00:44:10.259 Olivier Audet: This is interesting. Yeah.

287 00:44:11.940 --> 00:44:14.669 Olivier Audet: or that's a that's a or each something.

288 00:44:15.220 --> 00:44:30.770 Olivier Audet: In other words, if you just want with car, you can put just car. If you want to add other bus or truck or bus, you add it if you want. And you can do many calculation or estimation based on what the new purpose you want for the crew.

289 00:44:32.280 --> 00:44:49.390 Rick Neubauer (Umojo): Yeah, one other thing to note, we did include bus in here, because we also are tracking things like when bus zones… bus stops, excuse me, are getting blocked, or how long buses are spinning at those bus stops and things, and so it's got to be able to cover, you know, regular parking, non-parking, and

290 00:44:49.390 --> 00:44:52.859 Rick Neubauer (Umojo): Bus stops, commercial loading zones. It's got to cover all the classes of

291 00:44:52.860 --> 00:44:59.309 Rick Neubauer (Umojo): vehicles, I think that we're, you know, that we're doing. : I don't know if it needs to cover like mopeds and scooters and motorcycles. : I think we can probably.

292 00:44:59.310 --> 00:44:59.980 Olivier Audet: Maybe not.

293 00:44:59.980 --> 00:45:01.070 Rick Neubauer (Umojo): Yeah, yeah.

294 00:45:01.070 --> 00:45:01.400 Michael Schnuerle (OMF): really.

295 00:45:01.400 --> 00:45:05.599 Rick Neubauer (Umojo): I think we could come up with a standard length for that, but on other ones.

296 00:45:06.280 --> 00:45:09.009 Michael Schnuerle (OMF): Or standard width or something. Andrew.

297 00:45:09.660 --> 00:45:14.149 Andrew Kay: Yeah. I wonder in, instead of thinking about it in terms of.

298 00:45:14.300 --> 00:45:15.040 Michael Schnuerle (OMF): Okay.

299 00:45:15.040 --> 00:45:16.890 Andrew Kay: a pure, like.

300 00:45:17.000 --> 00:45:32.439 Andrew Kay: addition and subtraction problem, oftentimes in, like, travel models, but you… the way this gets handled, because, like, in the same way that a truck takes up more of a parking zone than a standard car does, right? There's the concept of.

301 00:45:32.750 --> 00:45:48.059 Andrew Kay: It takes up more of a travel lane too, right? You can't fit as you can't. The capacity per hour for traveling is different. Everything is reduced into a common normalized unit called a passenger car equivalent, and I wonder if that would help here.

302 00:45:48.060 --> 00:45:48.600 Rick Neubauer (Umojo): Yeah.

303 00:45:48.600 --> 00:45:59.060 Andrew Kay: So, instead of that, you just specify the user classes as being some passenger car equivalent, you know, where a passenger car is 1.0, and maybe a.

304 00:45:59.230 --> 00:46:03.539 Andrew Kay: you know, a 40-foot box truck is… is twice that, or something like that. Interesting.

305 00:46:03.540 --> 00:46:04.080 Rick Neubauer (Umojo): Right.

306 00:46:04.080 --> 00:46:14.820 Andrew Kay: And then instead, you just count… you maintain a normalized count of available spaces in that same PCE, passenger car equivalent, unit.

307 00:46:16.660 --> 00:46:29.230 Michael Schnuerle (OMF): I just wonder if that would work at an international level, especially, like, when you think about, you know, just having come back from Amsterdam, where the car… the passenger cars are maybe typically half the size of the

308 00:46:29.950 --> 00:46:40.939 Michael Schnuerle (OMF): what we have in America, I know East City would define that, but then if you really wanted to find, like, a van versus a passenger car, then it might be, like, what, like a 1.5 equivalent or something?

309 00:46:41.370 --> 00:46:42.019 Andrew Kay: Yeah, exactly.

310 00:46:42.020 --> 00:46:43.619 Michael Schnuerle (OMF): Is that… is that how it works?

311 00:46:43.620 --> 00:46:54.010 Andrew Kay: Exactly, and you would count… and you would localize the calculation of available spaces to reflect those kinds of… differences between the EU and the US, where they maybe have smaller cars over there.

312 00:46:54.550 --> 00:47:07.910 Rick Neubauer (Umojo): Denae, and that PCU, I'm sorry, PCE, I'm reading up on it, but it doesn't really talk about, like, it says, like, a car, or light goods vehicles, one PCU, but it doesn't really say what that length is. Any idea what that is?

313 00:47:08.680 --> 00:47:23.730 Andrew Kay: It varies, there's different, like, standards that are used to represent it in different situations, but it would… I'm imagining it would be sort of configurable in the same way that you have here, right? Where you say a car is one, you know, van.

314 00:47:23.730 --> 00:47:24.560 Rick Neubauer (Umojo): Yeah, yeah, yeah.

315 00:47:24.810 --> 00:47:27.120 Andrew Kay: And you could localize it that way, too.

316 00:47:27.920 --> 00:47:33.860 Rick Neubauer (Umojo): Interesting. Okay, I'll do some investigation on that, Michael. That's a good idea. It's definitely an alternate approach. I like it.

317 00:47:34.410 --> 00:47:37.689 Michael Schnuerle (OMF): Nice idea, Andrew. It's not too dissimilar to this.

318 00:47:38.150 --> 00:47:44.639 Michael Schnuerle (OMF): you know, in a way, these, like, units of estimated capacity, but coming from the perspective of a car.

319 00:47:44.640 --> 00:47:49.490 Olivier Audet: Give me a mix of this and the, vehicle Line Class.

320 00:47:49.940 --> 00:47:50.480 Michael Schnuerle (OMF): Yeah.

321 00:47:50.770 --> 00:47:57.149 Olivier Audet: But cache capacity is related to the line of car you put there. So it'll match your PC or something.

322 00:47:57.480 --> 00:48:01.180 Andrew Kay: Yeah, exactly. It just simplifies the counting problem. It would… it would…

323 00:48:01.180 --> 00:48:04.170 Olivier Audet: Yeah, uniform on all your data.

324 00:48:04.580 --> 00:48:07.340 Andrew Kay: Yeah, and it would potentially open up a…

325 00:48:07.720 --> 00:48:19.249 Andrew Kay: Possibly an issue, depending on how the spaces are allocated, in terms of, like, what do you do with something that maybe takes up one point, you know?

326 00:48:20.090 --> 00:48:26.709 Andrew Kay: 6-5 spaces, or something like that, but I think it's… I think it's solvable, and possibly cleaner. It's something to think about.

327 00:48:27.160 --> 00:48:44.759 Rick Neubauer (Umojo): Yeah, my only thing I was gonna say, too, is I'm gonna look and see on the… I know in our computer vision models, we don't even think about any concept of a PCE or PCU, but it'd be interesting to see if there's something out there for that, because we're converting the feet, basically, estimated feet on a calibrated camera.

328 00:48:44.760 --> 00:48:50.689 Rick Neubauer (Umojo): So alright. No, it's a it's definitely interesting. A good, awesome approach. I'll have to check that out. Thanks, Andrew.

329 00:48:51.040 --> 00:48:56.119 Michael Schnuerle (OMF): Yeah, thanks, Andrew. Everyone leave comments on that issue if you have thoughts or links to more info.

330 00:48:56.370 --> 00:49:06.540 Michael Schnuerle (OMF): Now we have two more issues. We're down to four minutes each to cover these. So this one's about fire hydrant clearance on blocks and curb zones, I think.

331 00:49:06.540 --> 00:49:11.289 Rick Neubauer (Umojo): That's an interesting one. So, you know, we've got a whole block, let's say that's no parking.

332 00:49:11.370 --> 00:49:31.120 Rick Neubauer (Umojo): and there's a fire hydrant in the middle. The difference is, is that if someone parks, you know, 20 feet from the fire hydrant, it's just a normal no-parking spot. If they park and block the fire hydrant, it's a completely different citation and a completely different ticket. It's blocking the fire hydrant. And so… and I mean, if we're gonna make it where things are

333 00:49:31.320 --> 00:49:46.089 Rick Neubauer (Umojo): you know, down to zones and policy and everything else, then you technically would have to create a separate zone with a different policy for the fire hydrant versus 15 feet from the fire hydrant, which got us into another interesting

334 00:49:46.090 --> 00:49:52.910 Rick Neubauer (Umojo): conversation because like I know Chicago, it's 50, it's 30 feet on center. So 15 feet each direction.

335 00:49:52.910 --> 00:50:02.490 Rick Neubauer (Umojo): I want to say in Buffalo, it's 12 feet in each direction of where the… so there's another variable there, similar to, like, a standard car length that they use for calculating spaces.

336 00:50:02.490 --> 00:50:13.930 Rick Neubauer (Umojo): Rory Bilocerkowycz, that they use for calculating how much space you have to give for a fire hydrant. And so, the whole idea here was that… is making a way that… I just thought it was an interesting way where

337 00:50:14.100 --> 00:50:20.020 Rick Neubauer (Umojo): there is no concept of defining it in CDS today, per se, the fire hydrant, but also.

338 00:50:20.090 --> 00:50:35.209 Rick Neubauer (Umojo): Kevin D'coming up with a method to where you have to take a fire… a no-parking area that was, say, 100 feet long, and say, okay, 30 feet of this now has to be for a fire hydrant, and then it's applied to a different policy, and then… and a method to split that zone up, right? Based on that.

339 00:50:35.210 --> 00:50:35.800 Michael Schnuerle (OMF): Yeah.

340 00:50:36.080 --> 00:50:41.609 Michael Schnuerle (OMF): Well, so, I… yeah, I think, obviously, you're saying this, but the way CDS is built.

341 00:50:42.020 --> 00:50:49.980 Michael Schnuerle (OMF): In that case, you would have 3 zones if the fire hydrant's in the middle of a block, you'd have two, and then a third one in the middle, and that's…

342 00:50:50.490 --> 00:51:05.099 Michael Schnuerle (OMF): is… so a question, is that not okay? And then, if you think about fire hydrants, you can think about a bunch of other stuff that maybe has citywide rules attached to it that are similar, like daylighting from intersections, and…

343 00:51:05.100 --> 00:51:12.730 Michael Schnuerle (OMF): Maybe ramp acts, space distance from ramps, maybe in the middle of a… Curb or something.

344 00:51:12.730 --> 00:51:17.860 Rick Neubauer (Umojo): I think the way that we do it, the way that the breaking the zone up into three zones, that's not the issue.

345 00:51:17.860 --> 00:51:18.320 Michael Schnuerle (OMF): Why is.

346 00:51:18.320 --> 00:51:21.149 Rick Neubauer (Umojo): is defining it, right? As we go back up just a hair.

347 00:51:21.830 --> 00:51:29.660 Rick Neubauer (Umojo): Again, you see, if you like, there's no link to how it's enforced. So we started including enforcement right as part of events now too.

348 00:51:29.660 --> 00:51:30.610 Michael Schnuerle (OMF): Okay, yeah.

349 00:51:30.610 --> 00:51:43.369 Rick Neubauer (Umojo): no way to be like, hey, this is a certain type of violation code or citation that was issued for that, for that, for that policy. And then secondly, there's really not a way to define a fire hydrant zone.

350 00:51:44.200 --> 00:51:47.000 Michael Schnuerle (OMF): Oh, okay. So you're… so you want…

351 00:51:48.280 --> 00:51:55.930 Michael Schnuerle (OMF): proposed changes, two fields, violation codes and restriction reasons. So this is inside of the rule…

352 00:51:56.600 --> 00:52:00.600 Michael Schnuerle (OMF): Or don't we have some enforcement actions, too?

353 00:52:02.400 --> 00:52:06.150 Michael Schnuerle (OMF): Maybe not. Or maybe not here.

354 00:52:08.860 --> 00:52:14.810 Michael Schnuerle (OMF): Yeah, so you're wanting, as a rule, a specific call-out for… A violation.

355 00:52:14.810 --> 00:52:15.270 Rick Neubauer (Umojo): the.

356 00:52:15.270 --> 00:52:15.590 Michael Schnuerle (OMF): should.

357 00:52:15.590 --> 00:52:16.280 Rick Neubauer (Umojo): Good.

358 00:52:16.280 --> 00:52:18.830 Michael Schnuerle (OMF): Yeah. Okay, well, that makes sense.

359 00:52:19.720 --> 00:52:21.420 Michael Schnuerle (OMF): That makes sense to think about how that's.

360 00:52:21.420 --> 00:52:35.929 Rick Neubauer (Umojo): If you're starting to paint in, or I'm saying paint in, but add in violations, right, for enforcement, then if there's certain areas where the violation code is different, like, if you didn't know, if you're staying there, you look at it physically, it looks like one big, gigantic.

361 00:52:35.930 --> 00:52:52.899 Rick Neubauer (Umojo): a no parking zone. It's not like it's gonna have a… they might have signage, let's say, that says no parking from here to here in certain cities, but other cities won't have any signage, but it's a known thing that they park in front of the fire hydrant. It's a different citation, right? That's all I think we're trying to do… to map out here.

362 00:52:53.170 --> 00:52:59.429 Michael Schnuerle (OMF): Yeah, you want to add it to the curbs area so that you know how to do the enforcement on the events area.

363 00:52:59.880 --> 00:53:01.000 Rick Neubauer (Umojo): Yep, yep, exactly.

364 00:53:01.000 --> 00:53:01.390 Michael Schnuerle (OMF): could.

365 00:53:01.390 --> 00:53:09.129 Olivier Audet: I have to do that on my crypto to attach like regulation to site regulation codes.

366 00:53:09.710 --> 00:53:11.070 Olivier Audet: or citation.

367 00:53:12.540 --> 00:53:17.429 Michael Schnuerle (OMF): Yes, you… I think you could do in the events, I guess, Rick, what Rick's saying is you want to…

368 00:53:17.430 --> 00:53:25.700 Olivier Audet: Not in advance. I need to have, like, the… what's the… it's the… usually what I put is the default citation I'll put for that regulation.

369 00:53:26.090 --> 00:53:26.710 Michael Schnuerle (OMF): Yeah.

370 00:53:26.710 --> 00:53:34.360 Olivier Audet: Afterward, if the agent in LPR want to change it, they can change it, but the default one for this particular regulation.

371 00:53:34.760 --> 00:53:36.510 Olivier Audet: At the building.

372 00:53:38.480 --> 00:53:45.449 Michael Schnuerle (OMF): Yeah, okay, so maybe this is maybe the easiest one to solve for, and maybe there's some possible workaround.

373 00:53:46.140 --> 00:53:53.540 Michael Schnuerle (OMF): And then let's hit this last one before we leave. Standardized priority bands for Curb policies. This is what you're talking about with Curb.

374 00:53:53.540 --> 00:53:54.490 Rick Neubauer (Umojo): Yeah, this is just one.

375 00:53:54.490 --> 00:53:55.620 Michael Schnuerle (OMF): Naming convention.

376 00:53:56.100 --> 00:54:20.619 Rick Neubauer (Umojo): But yeah, it's kind of like the naming convention. To me, it's like rules of the universe, so to speak, in CDS, right? Like, if I name my default route, like, if everybody… if there's no sign that you can park, then that's my default route is 99, and Olivier puts his at 50, then I don't even know that that's his default route, because we don't define it as the default… as the default policy, excuse me, not default route, I'm thinking of networking stuff, sorry. So my point is.

377 00:54:20.620 --> 00:54:36.240 Rick Neubauer (Umojo): Is that we just kind of came up with some bands that we use internally to be like, hey, these are travel restrictions, put them in around 15. If there are no stopping, start them at 20 to 29. If they're, you know, special events at the very top that have the highest priority.

378 00:54:36.290 --> 00:54:39.679 Rick Neubauer (Umojo): Like, that are temporary, to go back up to the top, Mike.

379 00:54:39.680 --> 00:54:40.430 Michael Schnuerle (OMF): Yeah.

380 00:54:40.430 --> 00:54:59.750 Rick Neubauer (Umojo): You know, then those are, like, special events, or route level, emergency routes, whatever, then those have the highest, you know, have a higher priority than other ones in the thing. And again, this is just a suggestion, it's just that when we… like, when we did the stuff with Curb IQ in Seattle and got the CDS permit, the way we mapped

381 00:54:59.870 --> 00:55:08.959 Rick Neubauer (Umojo): policy priorities was completely different, and we had to go, like, figure it out, and be like, okay, hey, they don't have any policies over 50, or I don't remember what it was.

382 00:55:09.140 --> 00:55:21.230 Rick Neubauer (Umojo): But so we knew that was their last policy that they used as their, you know, default fallback policy if there was no signage there. So that was just the idea is to come up with a…

383 00:55:22.310 --> 00:55:32.390 Rick Neubauer (Umojo): Krista Braaksma whatever you want to call it, guidelines on how to put policies out that… that everybody can start to agree on, so that when we know we get policy 99, then that's the…

384 00:55:32.550 --> 00:55:39.660 Rick Neubauer (Umojo): The standard default policy that people… or 90 here, for example, then that's usually default policy for those cities.

385 00:55:40.340 --> 00:55:51.979 Michael Schnuerle (OMF): Yeah, so this sounds interesting, like sort of a supplemental resource that's a recommendation for how to categorize priority, which makes it a little more uniform across vendors and jurisdictions.

386 00:55:52.150 --> 00:55:52.920 Michael Schnuerle (OMF): Yeah.

387 00:55:53.160 --> 00:55:54.420 Rick Neubauer (Umojo): Yep, exactly.

388 00:55:54.420 --> 00:55:55.080 Michael Schnuerle (OMF): Cool.

389 00:55:55.400 --> 00:55:56.130 Michael Schnuerle (OMF): Olivier?

390 00:55:56.270 --> 00:55:59.039 Olivier Audet: Question that Luke Weber or Ivan?

391 00:55:59.450 --> 00:56:02.380 Olivier Audet: Are the policy the same?

392 00:56:02.580 --> 00:56:04.830 Olivier Audet: Everywhere around the world.

393 00:56:05.490 --> 00:56:06.160 Michael Schnuerle (OMF): It's hard.

394 00:56:06.160 --> 00:56:06.840 Olivier Audet: 3…

395 00:56:06.840 --> 00:56:11.480 Michael Schnuerle (OMF): That would be a question, like, does this cover every city, country?

396 00:56:11.480 --> 00:56:18.200 Olivier Audet: Or are the same priority? Are travel like less for jurisdiction and higher for another one?

397 00:56:19.520 --> 00:56:21.160 Michael Schnuerle (OMF): Yeah, the hot…

398 00:56:21.160 --> 00:56:22.640 Olivier Audet: I didn't review it, but

399 00:56:23.070 --> 00:56:26.709 Michael Schnuerle (OMF): Yeah, like, the smaller the number, the higher the…

400 00:56:26.710 --> 00:56:27.560 Rick Neubauer (Umojo): Higher than priority.

401 00:56:27.560 --> 00:56:29.899 Michael Schnuerle (OMF): Takes precedence, yes, that's global.

402 00:56:30.940 --> 00:56:32.230 Olivier Audet: No, no, I mean, I mean…

403 00:56:32.340 --> 00:56:35.570 Olivier Audet: Are they ranking correctly for every jurisdiction?

404 00:56:35.570 --> 00:56:36.670 Michael Schnuerle (OMF): Oh, yeah, yeah, like…

405 00:56:36.670 --> 00:56:41.730 Olivier Audet: Do a travel go at the second, or do you need to be at the bottom of the top, or…

406 00:56:42.390 --> 00:56:45.580 Michael Schnuerle (OMF): Yeah, like, maybe in some country, this…

407 00:56:45.580 --> 00:56:47.480 Olivier Audet: Barry.

408 00:56:47.480 --> 00:56:47.820 Michael Schnuerle (OMF): take.

409 00:56:47.820 --> 00:56:48.250 Olivier Audet: pro.

410 00:56:48.250 --> 00:56:51.369 Michael Schnuerle (OMF): precedent over ballet. I don't know. Yeah.

411 00:56:52.250 --> 00:57:00.040 Michael Schnuerle (OMF): Yeah, it's a good question. So that's how to figure out, globally and in other jurisdictions, how this could work in a consistent way.

412 00:57:00.570 --> 00:57:08.929 Michael Schnuerle (OMF): But yeah, I think if we did this, we would sort of create a wiki page, I would say, that links over from the spec, and then that way we can keep it up to date, modify it.

413 00:57:08.930 --> 00:57:16.590 Olivier Audet: Yeah, or it can, like in other standard, it can be in the feed. You can have

414 00:57:17.530 --> 00:57:19.360 Olivier Audet: these, publish.

415 00:57:20.270 --> 00:57:22.570 Michael Schnuerle (OMF): Yeah. And,

416 00:57:22.570 --> 00:57:29.510 Olivier Audet: Everything's published, so you can suggest a default, but you can change it, and you publish it also. It's available.

417 00:57:29.510 --> 00:57:31.680 Michael Schnuerle (OMF): Maybe it could be part of the feed as well.

418 00:57:31.810 --> 00:57:40.800 Rick Neubauer (Umojo): You're saying almost part of like the, like a, a configuration object of like, Hey, here's our average size vehicles, here's our, our policy band.

419 00:57:40.800 --> 00:57:42.400 Olivier Audet: Paraphilia party.

420 00:57:42.400 --> 00:57:43.300 Rick Neubauer (Umojo): Whatever.

421 00:57:43.300 --> 00:57:45.359 Olivier Audet: That's our carbonara. Do it.

422 00:57:45.360 --> 00:57:45.860 Michael Schnuerle (OMF): the.

423 00:57:45.860 --> 00:57:47.159 Olivier Audet: you put it up.

424 00:57:47.160 --> 00:57:51.490 Rick Neubauer (Umojo): Yeah, that would be totally cool. Then everybody could drink whatever they wanted to, but then at least that.

425 00:57:51.490 --> 00:57:53.349 Olivier Audet: I can have a suggested one.

426 00:57:53.600 --> 00:58:11.900 Rick Neubauer (Umojo): Yeah, exactly. Because if you're not getting that data when you get to CDS, I mean, you just have no way to… how to… what's what until you go and spend a bunch of time. And unfortunately, it's very manual. I mean, you gotta look at all the different policies manually today and, you know, kind of cross-reference it. So I'm with you on that. That makes a lot of sense.

427 00:58:12.860 --> 00:58:24.029 Michael Schnuerle (OMF): Yeah. All right. Let's wrap up here. Thank you for that great discussion. The key here is that everyone needs to leave comments. I saw some comments coming in there.

428 00:58:24.240 --> 00:58:33.960 Michael Schnuerle (OMF): Our next meeting is November 3rd, so it'd be great to have some time, some comments in before that. So feel free to do that. Rick, did you have a final thought?

429 00:58:33.960 --> 00:58:40.980 Rick Neubauer (Umojo): Yeah, just one last thing, yeah, Jacob said he had, he has the one from Curb IQ, yeah, I mean, dude, I'd love for you to drop it in there and let's, let's, let's.

430 00:58:41.090 --> 00:59:01.029 Rick Neubauer (Umojo): merge them, or, like, compare to see where they're at. I'm just super curious to see where it lays out, but I think the sooner we… even if we don't figure out a way to where we store this inside a CDS somewhere, at least if there's some guidelines that we all kind of agree to, to say, hey, this is how we think is the best way to manage policy.

431 00:59:01.040 --> 00:59:02.290 Rick Neubauer (Umojo): Yeah, I think that's great.

432 00:59:03.510 --> 00:59:19.590 Michael Schnuerle (OMF): Yeah, great work. That's a lot of presenting and talking today, Rick. Thanks for that, and thanks for everyone for participating. Follow up on GitHub, and we'll send out the recording, meeting notes, and chat log soon. So thanks, everybody, and we'll see you next time.

433 00:59:20.770 --> 00:59:21.530 Brian Hamlin | Seattle DOT: Thanks all.

434 00:59:21.920 --> 00:59:22.590 Michael Schnuerle (OMF): Right.