Timeline for Match a path to a roadmap
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 24, 2018 at 15:25 | history | bounty ended | CommunityBot | ||
| S Apr 24, 2018 at 15:25 | history | notice removed | CommunityBot | ||
| Apr 21, 2018 at 20:00 | comment | added | Jim | Just some other initial thought: teach a neural net to do it. | |
| Apr 21, 2018 at 17:12 | comment | added | Gregg H | ¿Does the map contain distance data between nodes? And ¿what about angles between edges? If so, there could be a searching protocol that could be used to reduce the number of areas in the map that need to be searched. | |
| Apr 21, 2018 at 10:24 | comment | added | hans glick | Since the map could be very large I'm kinda perplexed but thanks for your thougths, interesting | |
| Apr 20, 2018 at 9:27 | comment | added | nlml | My initial thought is, since there's no real 'gradient' here, you probably need to brute force all possible rotations/positions. Perhaps you could quantise/downsample the map and path and brute force over that to find a shortlist of potential matches, then check each of these at higher resolution? | |
| S Apr 16, 2018 at 14:16 | history | bounty started | hans glick | ||
| S Apr 16, 2018 at 14:16 | history | notice added | hans glick | Draw attention | |
| Apr 14, 2018 at 2:38 | history | asked | hans glick | CC BY-SA 3.0 |