-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calibrating the map #9
Comments
Not sure I follow the question. Are you asking if GPS points collected using an existing basemap? The matcher currently defaults to basemap tiles generated from OpenStreetMap data, however, basemap tiles can be generated from any map that contains topology info (intersections between segments need to be defined for routing). Also regarding calibration: the matcher can be used to collect places where GPS data fails to match against an existing basemap (described as "map dust" output files in the current matcher code). Those map failures can be used to drive QA processes to improve the underlying basemap. Let me know if the above doesn't answer your question -- happy to discuss further! |
I work for Ford. I saw an article on my intranet home page about the recent agreement between Ford, Uber and Lyft to share data through the sharedstreets/sharedstreets-matcher.
I am a civil engineer and have used digital mapping in previous jobs to develop site surveys using aerial Images calibrated back to a property traverse to generate a “corrected” image.
So my question stated another way is:
Are established GPS waypoints, physically imbedded into the cityscape, used to correct the underlying base map OR are you simply using high confidence best fit vehicle position data collected from ongoing vehicle paths? [Your response below seems to indicate not.]
A local grid of transmitters tied back to the GPS system [and by association a high confidence digital map of the included space] would provide a provide a higher level of confidence than a vehicle movement distribution when describing a “road” vs. a temporary detour.
It's not about where I have been, it’s about where am I going.
Pat Chouinard, P.E.
From: Kevin Webb <[email protected]>
Sent: Friday, September 28, 2018 1:25 AM
To: sharedstreets/sharedstreets-matcher <[email protected]>
Cc: go4itpc <[email protected]>; Author <[email protected]>
Subject: Re: [sharedstreets/sharedstreets-matcher] Calibrating the map (#9)
Not sure I follow the question. Are you asking if GPS points collected using an existing basemap? The matcher currently defaults to basemap tiles generated from OpenStreetMap data, however, basemap tiles can be generated from any map that contains topology info (intersections between segments need to be defined for routing).
Also regarding calibration: the matcher can be used to collect places where GPS data fails to match against an existing basemap (described as "map dust" output files in the current matcher code). Those map failures can be used to drive QA processes to improve the underlying basemap.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#9 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AposGVuAH0fv-u_aiMppBJY68l28Tk7bks5ufbKugaJpZM4W9nyD> . <https://github.com/notifications/beacon/AposGSckv0Xm2TMYpSheudbhgihsYQL4ks5ufbKugaJpZM4W9nyD.gif>
|
Are the virtual maps tied into physically embedded way-points located
throughout the Cityscape OR is everything driven off of the dynamic GIS mapping?
The text was updated successfully, but these errors were encountered: