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

USA – Detroit – Road geometry #3

Closed
manuelab-telenav opened this Issue Apr 7, 2017 · 9 comments

Comments

7 participants
@manuelab-telenav
Contributor

manuelab-telenav commented Apr 7, 2017

Description

In this project we will map road geometry in Detroit, Michigan area and we will focus on adding missing roads as well as improving the existing data in OSM.
missing

How to map

We will follow the mapping scheme that is already used in the United States as it is described on this page:

For adding roundabouts we will follow this guideline :

Sources

  • Satellite imagery: Bing, Mapbox, NAIP
  • Government data: TIGER Roads
  • Improve OSM - Missing Roads
  • Street-level imagery: OpenStreetCam, Mapillary

See also

@mvexel

This comment has been minimized.

Show comment
Hide comment
@mvexel

mvexel Apr 7, 2017

Contributor

Which version of TIGER will we be using?

Contributor

mvexel commented Apr 7, 2017

Which version of TIGER will we be using?

@manuelab-telenav

This comment has been minimized.

Show comment
Hide comment
@manuelab-telenav

manuelab-telenav Apr 10, 2017

Contributor

We'll be using the latest version, released in 2016: https://www.census.gov/geo/maps-data/data/tiger.html

Contributor

manuelab-telenav commented Apr 10, 2017

We'll be using the latest version, released in 2016: https://www.census.gov/geo/maps-data/data/tiger.html

@mvexel

This comment has been minimized.

Show comment
Hide comment
@mvexel

mvexel Apr 10, 2017

Contributor

(Just FYI new TIGER data versions are released annually around the end of the summer)

Contributor

mvexel commented Apr 10, 2017

(Just FYI new TIGER data versions are released annually around the end of the summer)

@jmcbroom

This comment has been minimized.

Show comment
Hide comment
@jmcbroom

jmcbroom Apr 11, 2017

For road geometry, might also want to consider the Michigan Geographic Framework: http://gis-michigan.opendata.arcgis.com/datasets/5fddb53b929b4b729b8d4282b4d23ade_20

I think that's v15 (for 2015) - not sure on the release schedule for v16. Actually, that links to v16.

jmcbroom commented Apr 11, 2017

For road geometry, might also want to consider the Michigan Geographic Framework: http://gis-michigan.opendata.arcgis.com/datasets/5fddb53b929b4b729b8d4282b4d23ade_20

I think that's v15 (for 2015) - not sure on the release schedule for v16. Actually, that links to v16.

@manuelab-telenav

This comment has been minimized.

Show comment
Hide comment
@manuelab-telenav

manuelab-telenav Apr 11, 2017

Contributor

Great tip! Thanks, we'll be using these for sure.

Contributor

manuelab-telenav commented Apr 11, 2017

Great tip! Thanks, we'll be using these for sure.

@markscalf

This comment has been minimized.

Show comment
Hide comment
@markscalf

markscalf Apr 11, 2017

Please keep in mind that there has been a significant amount of construction in the area (and will continue to be), especially along freeways which may not be reflected in the latest Bing imagery (i.e. I 75 near bridge to Canada, I 275 between I96 & I 696, new 10 yr project along I75 between square lake road and downtown Detroit, new project along M59 between Romeo Plank and ~ Hayes). All road alignment changes should be confirmed with either probe traces and/or open source imagery traces from Mapillary and/or OpenStreetCam.

markscalf commented Apr 11, 2017

Please keep in mind that there has been a significant amount of construction in the area (and will continue to be), especially along freeways which may not be reflected in the latest Bing imagery (i.e. I 75 near bridge to Canada, I 275 between I96 & I 696, new 10 yr project along I75 between square lake road and downtown Detroit, new project along M59 between Romeo Plank and ~ Hayes). All road alignment changes should be confirmed with either probe traces and/or open source imagery traces from Mapillary and/or OpenStreetCam.

@markscalf

This comment has been minimized.

Show comment
Hide comment
@markscalf

markscalf Apr 11, 2017

Another thing to point out is that there are a significant number of duplicate nodes (i.e. highway node shared with admin boundary). I believe this issue goes back to initial import and is common throughout the entire metro area. Recommend that these be corrected if seen while adjusting road geometry.

markscalf commented Apr 11, 2017

Another thing to point out is that there are a significant number of duplicate nodes (i.e. highway node shared with admin boundary). I believe this issue goes back to initial import and is common throughout the entire metro area. Recommend that these be corrected if seen while adjusting road geometry.

@simonap-telenav

This comment has been minimized.

Show comment
Hide comment
@simonap-telenav

simonap-telenav Apr 13, 2017

Thanks, that's very helpful. We've found a few cases of duplicated nodes and we corrected them. We'll keep in mind your recommendations when we're editing.

simonap-telenav commented Apr 13, 2017

Thanks, that's very helpful. We've found a few cases of duplicated nodes and we corrected them. We'll keep in mind your recommendations when we're editing.

@hoream-telenav

This comment has been minimized.

Show comment
Hide comment
@hoream-telenav
Member

hoream-telenav commented Aug 22, 2018

This issue was moved to TelenavMapping/US_mapping_projects#22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment