OSM can help Inventory and Manage the Curb
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 41 | |
| Autor | ||
| Lizenz | CC-Namensnennung 3.0 Unported: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen. | |
| Identifikatoren | 10.5446/58212 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
|
State of the Map US 202226 / 41
1
4
7
8
14
18
21
22
24
27
28
30
37
39
00:00
WhiteboardTransportproblemVorzeichen <Mathematik>GruppenoperationFokalpunktEDV-BeratungDifferenteDatenverwaltungMapping <Computergraphik>PunktBus <Informatik>HilfesystemFlächeninhaltMultiplikationsoperatorProzess <Informatik>ExpertensystemOrdnung <Mathematik>ClientDigitale PhotographieStandardabweichungFreewareÜberlagerung <Mathematik>KoordinatenBinärdatenGrundsätze ordnungsmäßiger DatenverarbeitungGüte der AnpassungDateiformatWellenpaketQuaderWorkstation <Musikinstrument>Regulärer GraphAutomatische HandlungsplanungRoutingZeitzoneAtomarität <Informatik>WendepunktMinkowski-MetrikTopologieInverser LimesTropfenE-MailRouterBitKurvenanpassungFormation <Mathematik>WhiteboardCoxeter-GruppeInformationQuick-SortBildverstehenPolygonMereologieProjektive Ebene
04:59
Meta-TagInformationSechsMinkowski-Metrikp-BlockBitTopologieBinärdatenZeitzoneComputeranimation
06:31
MIDI <Musikelektronik>Keilförmige AnordnungTropfenFreewareRegulärer GraphClientProjektive EbeneBildverstehenQuick-SortE-MailKurvenanpassungComputeranimation
08:15
W3C-StandardDatenverwaltungBus <Informatik>Inverser LimesRoutingStandardabweichungTransportproblemGrundsätze ordnungsmäßiger DatenverarbeitungKoordinatenGruppenoperationAutomatische HandlungsplanungVorzeichen <Mathematik>DateiformatZeitzoneComputeranimation
10:27
W3C-StandardComputeranimation
Transkript: Englisch(automatisch erzeugt)
00:05
Okay, hi, I'm Daniella Wolterstorfer. A lot of you know me as Danny. I'm here with OSM US Board. I'm a sitting member. I'm very happy to be one. And I also, aside from that, I have a day job with Cambridge Systematics.
00:22
I'm a GIS expert and transportation consultant. My background is in urban planning and transportation engineering, hence being in this group, this session. So today I'm going to talk about something that is very passionate to me and those who know me are probably aware of this and are probably tired because you've seen me talk about this many times and I've
00:46
posted on Slack many questions and it's the curb, but I'm actually not going to talk about mapping the KERB, which is like how it's labeled and tagged in OSM.
01:01
I'm gonna, so for the, well, I had animations. Wait, you don't see them, right? No, okay. It's not in order. Oh, I had a cool animation. Okay, whatever.
01:24
Anyway, for the purposes of KERB management, we're gonna treat the KERB as an asset that houses many other assets. If you are in the transportation industry, you probably heard about asset management in transportation and
01:40
a little secret about a lot of agencies, governmental agencies, municipalities, etc., is that their data can be really messy if you don't know. Or they could have various departments within their own agency where they're not working together. So there's no standard way of having an inventory of the assets.
02:03
You could have waste management easily. That's a department within a municipality that takes care of waste management, but they don't necessarily work together with sign management, even though they're sharing the same geography. Like within a quarter, you're gonna, they're gonna be using the same KERB for both purposes.
02:22
Alright, so back to many assets within the big asset that is the KERB. So again, waste management, what have you, those are what I want to focus on, like different kinds of management within the KERB. So that includes mapping. You have a bike lane over there.
02:42
Hmm, I have a bunch of photos popping up. Okay, well bus stops, bike lanes, trees, street parking, bike sharing? No, you don't see it. Nothing's popping up. There you go, okay. Bike sharing stations, dockless parking,
03:05
or, you know, like some areas in the US have this, but in Europe you see a lot of like the bike park, covered bike parking that are within parking slots on the street. So different uses of things on the street side of the KERB and then on the sidewalk side of the KERB. So for
03:26
asset management regarding the KERB, for certain clients that I've worked with, depending on the municipality, like I had one that wanted to solely focus on loading areas. So anything within the street side of the KERB, but then there are others that want to focus on both because you also need, okay,
03:45
so there's loading, but is there a lower curb ramp or something? Is it accessible? Like is it, if it's a TNC, Uber, Lyft, drop-off, pickup, is it actually accessible also for people with certain disabilities or someone with a stroller? So you ideally you would want to focus on both sides of the KERB.
04:04
So the good thing is that these are all things that we can map in OSM, and we know how to map in OSM. They're fairly easy. They're points of interest for the most part, unless you have a parking area and then you just do a polygon or whatnot. But this is all data that cities can definitely benefit with and from.
04:25
They can have a one-stop shop for this data rather than having PDFs of bus stops. I don't know if you've ever encountered that kind of data. It's not fun, and then you have to visualize it and then inventory it and somehow manage it and all you have is like hand-drawn bus stops on PDFs for a whole city.
04:44
So not quite ideal. So in this way you can help municipalities, MPOs, small transit agencies work together in a way that they are standardized, getting it from the same place.
05:00
So I wanted to pull an example from Tucson. Fortunately, it's not super well mapped, so I mapped a little bit for this. I chose this corridor since it had interesting points of interest. So this snippet has it's East Congress Street. You can see some of the assets. It has
05:24
bike parking, the tram stop, not tram, tram stop, some trees, but you can also map a lot more. Like there are certainly there are benches there and there's waste bins. There's a lot more that could definitely be mapped. There's parking and even, but with just even the information here, which is not a lot, a city could benefit
05:46
in noting, okay, so can you see my mouse? No, okay, so on the side where okay, so Congress Street and 6th Avenue where you see the trees map, you actually can see that there are no
06:03
there's no bike parking there. So perhaps the city could be like, hey, we actually on that corridor is pretty commercial. Why don't we designate a loading zone or why don't we designate a DNC Uber, Lyft, dropout pickup area? We have the space and we can just do the same that we did for the block adjacent,
06:20
but instead of bike parking, do it for something else. And also, you know, just to have the inventory to map, to properly manage those assets. This is, if you see my talk at MappingUSA, I show this example because I really like it. It's a commercial corridor in Glen Falls, New York and
06:43
I think it's quite impressive. It has a lot of POI's really well mapped. There are street lamps, trees, mail drop boxes, benches, wastebaskets, fire hydrants, bicycle parking, regular street parking, and then they all have the proper tax. So like if it's street parking, two-hour free parking,
07:02
but then it's residential parking at nighttime for free, like everything is really properly mapped. And this is, I'm not sure if Glen Falls, like again, I'm not talking about specific projects I've worked on. I'm not pulling up actual clients' examples. But it'd be interesting if Glen Falls is actually using this data to properly
07:22
manage the curve and manage that corridor and the assets that make up that corridor, that make up the curve. So ideally, the reason why I'm doing this, I'm sort of pushing this vision of having cities want to use OSM to manage the curve instead of hiring
07:45
certain companies that you know are going out there mapping everything and then they're selling that data and it's not open data. And if the city wants the fire hydrants mapped, they're going to charge like $5,000 extra, but it's
08:02
essentially something that everyone can do and then the cities could do it themselves. They could have a team that could do it. They could have existing data already and they're not even aware of it. So with all these assets mapped, cities
08:21
This is the wrong presentation. Okay. Yeah, so with all of these assets mapped, the cities could then be better informed to incorporate more bus lanes, bike parking, protective bike infrastructure or making the pedestrian experience safer in many ways and do better
08:44
management or also vehicular traffic. Because if you're managing the assets that make up the curve, you can actually lower the speed limit without putting signs all over. So just a little thing that I'm working on and pushing for
09:03
and I wanted to also open it up to see, I'm assuming since I'm in this lot that I have other fellow transportation planners or engineers here. And if so, if you are half worked in this realm of curb planning or freight management for loading zones and things like that,
09:23
if you think that this is something municipalities or MPOs could benefit from or if I'm going the wrong route. Essentially what moved me to doing this on OSN again is the lack of coordination and it's not the municipalities fault. It's this for
09:43
God knows how many years they've worked like that. They have different departments within one city and they're not working together and their formats of data are not the same. So it's a mess and then they want to implement something new and they realize oh my goodness, we have to work together. So think of like GTFS standardized something for public transit and it's great. We all use it and
10:06
if you're not in transportation, you probably don't know what I'm talking about, but I think it would be great to have something that you know, everyone could just use and all little departments can work together. So I
10:20
want to hear from you too. Yeah, it was short.