Adam, Thanks for adding Vermont. At some point I'd like to do like you did with surfaces. One of the problems I run into is that every agency seems to have a different list of surfaces. We'd should probably try to create a conversion chart to map different names into OSM surface types.
For example, USFS roads has the following surface types AC - ASPHALT AGG - CRUSHED AGGREGATE OR GRAVEL AGG - LIMESTONE AGG - SCORIA BST - BITUMINOUS SURFACE TREATMENT CSOIL - COMPACTED SOIL FSOIL - FROZEN SOIL IMP - IMPROVED NATIVE MATERIAL NATIVE MATERIAL NAT - NATIVE MATERIAL OTHER - OTHER PCC - PORTLAND CEMENT CONCRETE PIT - PIT RUN SHOT ROCK P - PAVED SOD - GRASS >From Okanogan county in Washington they have D d null (which has the highest count) P G The states metadata can help us build a conversion to OSM surface types; Clifford On Wed, Aug 8, 2018 at 7:49 AM Adam Franco <[email protected]> wrote: > I've added Vermont's center-line > <http://geodata.vermont.gov/datasets/VTrans::vt-road-centerline> info to > the spreadsheet. As someone who does a lot of filtering of OSM roads based > on surface, exposing surface info to a broader group of editors would be a > fabulous win. Thanks for heading in this direction! > > To do my own surface entry I've resorted to side-by side JOSM and QGIS > windows with the latter showing a color-coded road-centerline file. As can > be imagined, most people won't go to this effort and hence US road-surface > data in OSM is pretty patchy to say the least. > > > > > On Tue, Aug 7, 2018 at 11:32 PM, Elliott Plack <[email protected]> > wrote: > >> Maryland’s Transportation Basemap is already availability in iD and JOSM >> as an imagery source. We also have a slew of open datasets including >> centerline and speed limits. I’ll take a look at the doc and add some. >> http://data.imap.maryland.gov/datasets?q=transportation >> >> Kudos on getting this together! >> On Tue, Aug 7, 2018 at 23:27 Paul Johnson <[email protected]> wrote: >> >>> >>> >>> On Tue, Aug 7, 2018 at 9:00 PM, Clifford Snow <[email protected]> >>> wrote: >>> >>>> Ian, >>>> >>>> >>>> On Tue, Aug 7, 2018 at 9:30 AM Ian Dees <[email protected]> wrote: >>>> >>>>> Thanks for putting this together, Clifford! >>>>> >>>>> I was collecting street centerline data as part of OpenAddresses a >>>>> while ago here: https://github.com/openaddresses/centerlines >>>>> >>>>> I'm happy to add you to this repo if you want to use this repo or feel >>>>> free to pull from this repo into your spreadsheet. >>>>> >>>>> My goal with this was to pull all this data into a single, >>>>> country-wide layer to map in OSM with. I'm happy to help you down that >>>>> path, if that's what you're thinking. >>>>> >>>>> >>>> That is exactly my goal - get all of the states with open data into a >>>> background image that people could use to trace from, much like your TIGER >>>> 2017 and previous years. My initial attempt will be just centerlines with >>>> street names. Later we need to add surface and other details. >>>> >>> >>> >>> This could present a feedback loop in Oklahoma, since OklaDOT's portal >>> can use (and in some datasets, does use by default) OSM. >>> _______________________________________________ >>> Talk-us mailing list >>> [email protected] >>> https://lists.openstreetmap.org/listinfo/talk-us >>> >> -- >> Elliott Plack >> http://elliottplack.me >> >> _______________________________________________ >> Talk-us mailing list >> [email protected] >> https://lists.openstreetmap.org/listinfo/talk-us >> >> > _______________________________________________ > Talk-us mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-us > -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch
_______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
