Paper: http://hw.oeaw.ac.at/0xc1aa500e%200x00324afb.pdf
Abstract: Navigation instructions in pre- and on-trip routing services are usually based on street names and types, distances, and turn directions. However, in digital street graphs it is common that street names for separately mapped pedestrian and cycle links are missing. This leads to unsatisfactory instructions containing “unknown road” records. Often, these unnamed links run parallel to a named road, and it would be beneficial to use this information to generate instructions similar to “follow the sidewalk along Street A”, whereby “Street A” has to be determined by an algorithm. This paper introduces the Unnamed Link Naming Problem (ULNP) and presents a new approach to automatically extract suitable names to describe separately mapped pedestrian and cycle links. The approach has been tested using OpenStreetMap data and manually generated ground truth data for the second district of the city of Vienna, Austria. Results show that our best method achieves 90.7% correct matches in this challenging setting.
Botany krishna series 2nd semester Only Mcq type questions
Improving Navigation: Automated Name Extraction for Separately Mapped Pedestrian and Cycle Links - #GIForum2015
1. Improving Navigation
Automated Name Extraction for Separately Mapped Pedestrian and
Cycle Links
Anita Graser, Markus Straub
This work is partially funded by the Austrian BMVIT programme “Mobilität der Zukunft” under grant 844434 “PERRON” as
well as the Vienna Business Agency call “From Science To Products 2013” under the grant for project “sproute”.
16. Hausdorff distance matching
𝜹 = 𝟐𝟎 correct name no match wrong name sum
already named
26
(100%)
26
should be matched
252
(66.7%)
67
(17.7%)
59
(15.6%)
378
should not be
matched
338
(84.5%)
62
(15.5%)
400
17
17. Hausdorff & Median matching
18
Hausdorff distance
matching
Median distance
matching
18. Median distance matching
19
𝜹 = 𝟐𝟎 correct name no match wrong name sum
already named
26
(100%)
26
should be matched
284
(75.1%)
2
(0.5%)
92
(24.3%)
378
should not be
matched
308
(77.0%)
92
(23.0%)
400
19. Median & Composite matching
20
Median distance
matching
Composite
matching
20. Composite matching
21
𝜹 = 𝟐𝟎, 𝛗 = 𝟏𝟓 correct name no match wrong name sum
already named
26
(100%)
26
should be matched
350
(92.6%)
20
(5.3%)
8
(2.1%)
378
should not be
matched
353
(88.3%)
47
(11.8%)
400
24. Conclusion
Solving the ULNP
Composite matching succeeded in matching 90.7% of test links
better performance expected for rectangular street networks
at roundabouts, a local relaxation of the angular tolerance might lead to better results.
Potential 2nd application: street graph generalization
enrich the generalized link with attributes from all matching links
automatic inference of street cross-section characteristics
25. Future work
address shortcomings of Composite matching
identify situations where links have to be split to be able to compute
appropriate matches
Test transferability to other cities