Skip to content
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

Mapping Exit Numbers and Destinations in 30 US Cities #178

Closed
poornibadrinath opened this issue May 2, 2016 · 5 comments
Closed

Mapping Exit Numbers and Destinations in 30 US Cities #178

poornibadrinath opened this issue May 2, 2016 · 5 comments
Assignees
Labels

Comments

@poornibadrinath
Copy link
Contributor

poornibadrinath commented May 2, 2016

Task Objective

Adding Exit numbers and Destinations for Top 30 US Cities.

c7610364-107c-11e6-88ed-5391d62bee3b

Team: @mapbox/india-office
Features to map: Exit Numbers and Destinations
Estimated features to map: Unknown
Estimated time to map: Unknown

Available Data Sources:

  • Mapbox Satellite
  • Bing
  • Mapillary
  • Wikipedia
  • DOT documents for each city

Tasks:

Spreadsheet: Two team members can pick one state together and update this spreadsheet with the status of exit and destinations mapped.

The Progress of this task is being updated here

Mapping Workflow:
The detailed workflow for Exit mapping and Destination mapping

Mark any highway as DONE if it has been completely mapped or mark it as NO if it is not mapped and state the reason: No resources/ No Mapillary coverage.

JOSM Workflow:
Filters to use:

  • Filter out non road features with boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:

  • Add inverse filter: highway=motorway | motorway_link | trunk| trunk_link | primary | secondary | tertiary

  • Layer:

    This layer can be used as guide to the city boundaries that a mapper is working on
    JOSM TMS: Navigation Mapping US 30 cities tms:https://api.mapbox.com/styles/v1/planemad/cijwpzx4m00ofcakw1m0f1ir1/tiles/{z}/{x}/{y}?access_token=pk.eyJ1IjoicGxhbmVtYWQiLCJhIjoiemdYSVVLRSJ9.g3lbg_eN0kztmsfIPxa9MQ

Changeset comment and source:

  • Comment ---> Adding missing exit and destination tags https://github.com/mapbox/mapping/issues/178
  • Source ---> Bing;Mapillary;Wikipedia

Resources

cc @mapbox/team-data

@abhisheksaikia
Copy link

In cases an exit is already tagged as noref=yes but there is good mapillary coverage in the the area, the exit should be double checked using mapillary images. Saw an instance in I-695 Washington, D.C where an exit was tagged as noref=yes but mapillary showed the exit ref as 1A.

cc @planemad @poornibadrinath @krishnanammala

@jothirnadh
Copy link

jothirnadh commented May 3, 2016

Most cities has a ring road circling the city and it might not fit inside priority mapping area.

screen shot 2016-05-03 at 11 28 03 am

In such cases add all the missing exit numbers and destinations within the ring and every motorways inside even it is outside our priority mapping area.

cc:/ @planemad @poornibadrinath @maning

@arunasank
Copy link

Stats for the week of 2nd May - 5th May.

There are some nodes in the features with destination, destination:ref and destination:street tags. I've left it in there in the event you want to identify and remove/modify those features. Let me know if that has to be removed!

Feature Count Geojson
destination 408 destination.geojson
destination:ref 255 destination_ref.geojson
destination:street 48 destination_street.geojson
ref 28 ref.geojson
noref=yes 22 noref_yes.geojson

@poornibadrinath
Copy link
Contributor Author

@poornibadrinath
Copy link
Contributor Author

Closing #178 here 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants