Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Clifford Snow]

On Sun, Feb 25, 2018 at 6:14 PM, Nick Hocking 
wrote:
>
>
> Given that the *vast* majority of these (with no name) are completely
> fictional, and even those that aren't, are so out of position and so
> wrongly connected as to render them worse than useless, I believe that
> deletion is the only sensible option.
>

No doubt that way too many highway=residential are fictional, but there are
a number of valid, just never touched ways. Of the ones that are valid they
often need alignment.


Working on a Maproulette Challenge[1] for Washington state here are my
findings so far:
 1. Most of the old logging roads were entered as highway=residential. Even
though I've gotten some pushback, I mostly delete them. If the road looks
like it's a main forest service road, I convert it to either unclassified
or service.

  2. These highway=residential connect to state highways and tertiary roads
that need significant alignment to imagery. Just delete the old data would
still leave hundred of valid roads mis-aligned.

  3. Next to old logging roads, are ways that should be driveways or
service ways. These are easy to fix.

  4. Occasionally there are valid short segments of these original ways.
For those I remove the review=no tag.

  5. Cleaning up Washington State is a long term process. So far about 3%
have been cleared.

One of the positive outcomes is I've learned how to run a geoserver to
serve open data [2] from the state to aid in the cleanup. Ian Dees has
offered to help me migrate off my home server to the US Chapter's account
on Mapbox. The state data far exceeds what's in TIGER. If you are working
in Washington, please do not rely on any TIGER overlays. Simply put, its
crap.

The cleanup effort is a lot of work. I'm always trying to encourage local
mappers to get involve. It is work that is needs to be done to improve the
quality of OSM in the States. I encourage you to work on your state.

Nick - if you do decide to just delete the ways, I would recommend first
communicating with the community on your plans. Your plans should include
how you plan to repair broken routes in a timely manner.


[1] http://maproulette.org/map/2871
[2]
http://tiles.snowandsnow.us/geoserver/gwc/service/tms/1.0.0/WashingtonRoads:all_wash_roads/{zoom}/{x}/{-y}.png

Clifford

-- 
@osm_seattle
osm_seattle.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Paul Johnson]

On Sun, Feb 25, 2018 at 8:14 PM, Nick Hocking 
wrote:

> Paul wrote  "Or maybe the unedited original TIGER that's still around
> dropped to
> highway=road.  "
>
>
> Given that the *vast* majority of these (with no name) are completely
> fictional, and even those that aren't, are so out of position and so
> wrongly connected as to render them worse than useless, I believe that
> deletion is the only sensible option.
>


I don't think it's actually fictional in a lot of cases, just *super* rural
and often hard to tell from aerial imagery, at least what I've seen in the
Oklahoma and Kansas area.

However, being able to tell the known-good stuff from a raw unknown in
pretty much any renderer at a glance would be handy.  For example, planning
routes through Death Valley or the Oregon Siskyous.  Both are known to be
low quality deathtraps in TIGER.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Mike N]

On 2/25/2018 9:14 PM, Nick Hocking wrote:
Paul wrote  "Or maybe the unedited original TIGER that's still around 
dropped to

highway=road.  "


Given that the *vast* majority of these (with no name) are completely 
fictional, and even those that aren't, are so out of position and so 
wrongly connected as to render them worse than useless, I believe that 
deletion is the only sensible option.


  Deletion is highly dependent on the quality of TIGER ways in each 
region: many TIGER roads near me were directly derived from government 
data, probably 0.1cm accuracy.   I haven't gone out to collect surface 
type, speed limits, lane configurations confirmed road name and 
therefore not touched them but they're very serviceable for automobile 
navigation.



___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Albert Pundt]

I concur that deleting unnamed and untouched TIGER ways is the way (no pun
intended) to go. From my experience editing, many rural driveways mapped in
TIGER were converted to highway=service with access=private (though rarely
with service=driveway), though there are many more that are still just
highway=residential. If these are all deleted, it's not like we can't just
go through and map more driveways. (Driveway mapping doesn't often seem to
be much of a focus for a lot of people anyway, though they should still get
mapped eventually.)

For many of these roads around Pennsylvania, I generally set what appear to
be unpaved roads that go and piddle out in someone's field to highway=track,
and roads connecting to houses and buildings to highway=service. Sometimes
I'll fix alignment, but most of the time these fixes are sidelined in favor
of my main editing goal. I don't often go and edit random TIGER roads;
instead, I focus on the numbered routes in my state.

On Sun, Feb 25, 2018 at 9:14 PM, Nick Hocking 
wrote:

> Paul wrote  "Or maybe the unedited original TIGER that's still around
> dropped to
> highway=road.  "
>
>
> Given that the *vast* majority of these (with no name) are completely
> fictional, and even those that aren't, are so out of position and so
> wrongly connected as to render them worse than useless, I believe that
> deletion is the only sensible option.
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>


-- 
—Albert
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Whole-US Garmin Map update - 2018-02-22

[Dave Hansen]

These are based off of Lambertus's work here:

http://garmin.openstreetmap.nl

If you have questions or comments about these maps, please feel
free to ask.  However, please do not send me private mail.  The
odds are, someone else will have the same questions, and by
asking on the talk-us@ list, others can benefit.

Downloads:

http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-02-22

Map to visualize what each file contains:


http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-02-22/kml/kml.html


FAQ



Why did you do this?

I wrote scripts to joined them myself to lessen the impact
of doing a large join on Lambertus's server.  I've also
cut them in large longitude swaths that should fit conveniently
on removable media.  

http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-02-22

Can or should I seed the torrents?

Yes!!  If you use the .torrent files, please seed.  That web
server is in the UK, and it helps to have some peers on this
side of the Atlantic.

Why is my map missing small rectangular areas?

There have been some missing tiles from Lambertus's map (the
red rectangles),  I don't see any at the moment, so you may
want to update if you had issues with the last set.

Why can I not copy the large files to my new SD card?

If you buy a new card (especially SDHC), some are FAT16 from
the factory.  I had to reformat it to let me create a >2GB
file.

Does your map cover Mexico/Canada?

Yes!!  I have, for the purposes of this map, annexed Ontario
in to the USA.  Some areas of North America that are close
to the US also just happen to get pulled in to these maps.
This might not happen forever, and if you would like your
non-US area to get included, let me know. 

-- Dave


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us