- From: Sebastian Felix Zappe <sebastian@sozialhelden.de>
- Date: Mon, 5 Oct 2020 12:37:05 +0200
- To: Peter Shikli <pshikli@bizware.com>
- Cc: public-lda@w3.org
- Message-Id: <95A459C7-9E67-4CA5-8300-A5EB115145DA@sozialhelden.de>
Hi Peter, Examples how indoor accessibility is currently represented in data: - The biggest open data set for information like this is OpenStreetMap. It supports tagging for indoor navigation, for example with its ’Simple Indoor Tagging’ scheme [1]. So UCLA could tag its data using OSM and try out tech like OpenPlanner [2] or others [3]. - For public transit, indoor mapping can be done using the GTFS Pathways extension [4]. For end users, GTFS pathways data is supported in Google Maps, while Apple has IMDF, its own proprietary indoor mapping format [5]. Both have rudimentary support for accessibility-relevant features. - as community group, we strive towards a community-built standard to describe accessibility-relevant features of physical objects in detail. This data could then be mixed into other datasets, e.g. for routing engines [5]. We built A11yJSON for this [6], but there is no similar Linked Data vocabulary yet. Feel free to participate, e.g. in this GitHub issue! [7] - Have a look around for similar projects - some of the people behind them are also on this list :) [8] I hope this helps you to get started! Cheers, Sebastian Felix [1] https://wiki.openstreetmap.org/wiki/Simple_Indoor_Tagging [2] https://openplanner.team [3] https://wiki.openstreetmap.org/wiki/Routing [4] https://github.com/google/transit/issues/108 [5] https://register.apple.com/resources/imdf/ [6] https://a11yjson.org [7] https://github.com/schemaorg/schemaorg/issues/254 [8] https://accessiblemaps.de/?page_id=121&lang=en -- Sebastian Felix Zappe Tech Lead SOZIALHELDEN e.V., Andreasstr. 10, 10243 Berlin, Germany
Received on Monday, 5 October 2020 10:37:22 UTC