That's a great point. I agree, and it relates to big questions for OSM in general regarding quality assurance and OSM's relationship to authoritative data sources.
Parking restrictions have law enforcement implications so a city government or other agency has to maintain its own authoritative data for these things... otherwise it would be easy for me to avoid a parking ticket by just editing OSM. Same goes for something like road closures - a public agency can't risk using OSM for all its needs, otherwise a vandal could close a bridge into Manhattan, with massive implications for traffic. That's another reason for curbspace regulations to live in a separate, standalone format with metadata - having a curbspace feed like CurbLR provides a way for a government agency to publish data they consider to be official, and "sign off" on it. Data consumers can then determine which feeds they trust and want to consume, and which ones they want to investigate or handle with care. This raises the question, "Why do this in OSM at all?" If there can be a separate place for official data, why should people bother to map it (or import it) into OSM? The biggest reason to me is because OSM provides a place for people to map their own communities or areas of interest, especially if a government can't or won't produce/maintain/share their data. This seems like one of the core reasons why OSM came about. For curbspace specifically, OSM gives mappers a place crowdsource information, take advantage of common tools that may emerge, analyze the data in order to understand how their public space is allocated, and potentially advocate for changes to be made. They could also conduct their own inventory and compare it to "official" sources as a means of verification and QA/QC that benefits everyone - just because a dataset is "official", doesn't mean it's correct. So OSM means that people aren't reliant on government, and can hold their local agencies accountable for both their mapping and their use of public space. I find that pretty compelling. I don't have a good answer to how OSM can conduct quality control for this data any differently than it does for other types of data... but I do think it's important for OSM to offer a place for those who do want to map the curbside, and I think the idea of a GTFS-like feed with metadata about where the data came from will provide a path for both "authoritative" and crowdsourced data to coexist. On Fri, Jun 21, 2019 at 12:39 PM Peter Elderson <pelder...@gmail.com> wrote: > I am impressed by the high quality of this project. I think it could > surely be done in or with OSM. One question though: it seems to me it only > works if permanent quality control and quality assurance is in place. OSM > is not known for its reliability in that respect, you simply cannot > guarantee that there is data and that the data is complete, correct and > verifiable at any given time. > > How will you go about that? > > Fr gr Peter Elderson > > > Op vr 21 jun. 2019 om 04:43 schreef Emily Eros <emily.e...@gmail.com>: > >> Hi mailing list, >> >> Kerb/curb management has become a hot topic for city governments and >> companies, but there's not really a way to map parking and other >> restrictions in OSM. There's been some discussion of the importance and >> applications, but not a proposal. >> >> In my day job at SharedStreets, I've been working with city governments >> and companies who are interested in having a data standard to communicate >> about the kerb/curb, sort of like what GTFS does for transit. So I did some >> digging into OSM to see what this currently looks like and how OSM could >> also be able to store this regulatory data, if that's something that people >> want to map. Since this is really long, I've put it up as a blog post here: >> https://medium.com/sharedstreets/openstreetmap-and-curb-regulations-7812ee582a33 >> >> I'd love to hear from people about what they think about this as a >> general approach. >> >> If there's a group that's interested in getting together to have a >> conversation about this in real-time, then we could also put a working >> group together, formally or informally. >> >> Best, >> Emily >> >> >> >> _______________________________________________ >> Tagging mailing list >> Tagging@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/tagging >> > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
