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

2018-02-19 Thread Dave Mansfield
I agree. To me having paved and unpaved show on the osm.org default render 
would be the biggest improvement to OSM I can think of.

Dave

-Original Message-
From: Rihards [mailto:ric...@nakts.net] 
Sent: Monday, February 19, 2018 9:47 AM
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

On 2018.02.19. 15:28, Richard Fairhurst wrote:
...
> Having good paved/unpaved information will be a massive boost for OSM 
> in comparison to other map providers. We're already partway there. As 
> an

definitely. if somebody with the skills reads this, having that reflected on 
the osm.org default render would be a huge help.
i'd map more surface status if it was more obvious.

> example, try asking Google Maps for bike directions from SF to NYC. It 
> sends you down some really, really unsuitable tracks and I'm not 
> entirely convinced you'd survive the journey. By contrast, 
> cycle.travel (using OSM
> data) gets it pretty much right: occasionally it takes a gravel road 
> unnecessarily but it's pretty much always rideable.
> 
> It would be great if we could become the best map of the rural US just 
> as we are for much of the rest of the world.
> 
> cheers
> Richard--
 Rihards

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


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


Re: [Talk-us] I-69 east west vs north south

2017-09-21 Thread Dave Mansfield
Tod,

 

This section of I-69 is an exception to the odd numbers being north and south. 
The official highway direction of the section of I-69 I’m talking about is east 
and west. All signs for it are also east and west.

 

I understand what you are saying about the official direction is not always the 
same as the actual direction. There is a place on I-75 near me where northbound 
is going southwest for a short distance and southbound is going northeast but 
that is not the case with I-69

 

Dave

 

From: Tod Fitch [mailto:t...@fitchdesign.com] 
Sent: Thursday, September 21, 2017 11:49 PM
To: Dave Mansfield <mansfie...@chartermi.net>
Cc: talk-us@openstreetmap.org
Subject: Re: [Talk-us] I-69 east west vs north south

 

I don’t have direct knowledge of I-69 but the numbering on the Interstate 
system has odd numbers for north-south routes, so having all of I-69 in north 
and south relations seems correct to me.

 

I have seen area where due to topography long stretches of north-south road 
actually go east-west. I’ve also seem areas were US numbered highways end up 
with an opposite compass bearing (i.e. the north bound direction on the highway 
is actually going south). Just because a section of the route is going in a 
different direction than the overall route is not a reason to separate it out 
of the route relation. That is, the route relation should match the official 
highway direction.

 

Cheers,

Tod

 

 

On Sep 21, 2017, at 7:26 PM, Dave Mansfield <mansfie...@chartermi.net 
<mailto:mansfie...@chartermi.net> > wrote:

 

Hello,

 

I-69 in Michigan is east / west from where it splits from I-96 near Lansing  
<http://www.openstreetmap.org/#map=13/42.7761/-84.6325> 
http://www.openstreetmap.org/#map=13/42.7761/-84.6325 to where it ends in Port 
Huron. It is part Relations that are north and south. 

 

I would like to fix it but I don’t have a lot of experience with relations so I 
thought I should ask first. Would it be correct to remove the section that is 
east and west from the north and south relations and create new relations for 
east and west?

 

Thank You 

Dave 

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

 

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


[Talk-us] I-69 east west vs north south

2017-09-21 Thread Dave Mansfield
Hello,

 

I-69 in Michigan is east / west from where it splits from I-96 near Lansing
http://www.openstreetmap.org/#map=13/42.7761/-84.6325 to where it ends in
Port Huron. It is part Relations that are north and south. 

 

I would like to fix it but I don't have a lot of experience with relations
so I thought I should ask first. Would it be correct to remove the section
that is east and west from the north and south relations and create new
relations for east and west?

 

Thank You 

Dave 

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


Re: [Talk-us] State highway refs (was Re: New I.D Feature)

2014-11-29 Thread Dave Mansfield
From the Wiki  

http://wiki.openstreetmap.org/wiki/United_States_roads_tagging

“The two letter abbreviation for the state per the United States Postal 
Service's  https://www.usps.com/send/official-abbreviations.htm state 
abbreviation list, another abbreviation used by the state (such as SR for State 
Road), or no prefix. Different states may have different standards for which to 
use, and there is no current inter-state standard.”

I take the “Different states may have different standards for which to use” to 
mean that not all states use the two letter abbreviation and in states that 
don’t we should use that states standard for example Michigan uses M. The 
highway behind my house is M-15 and singed that way so I would think it should 
be tagged that way. Am I reading the Wiki wrong?

Thanks

Dave

 

 

 

From: Paul Johnson [mailto:ba...@ursamundi.org] 
Sent: Saturday, November 29, 2014 10:04 PM
To: Shawn K. Quinn
Cc: OpenStreetMap talk-us list
Subject: Re: [Talk-us] State highway refs (was Re: New I.D Feature)

 

On Sun, Nov 9, 2014 at 3:10 AM, Shawn K. Quinn skqu...@rushpost.com 
mailto:skqu...@rushpost.com  wrote:

So, a couple of questions:

1. What, exactly, is fair game to change to a state abbreviation
reference?

 

Fair game nationwide, two letter state abbreviations should be used for the 
primary state highway network.

 

2. Which states spell out the name in the ref?
I know Kansas uses K-123, and Michigan uses M-123. Are there any others
to be careful of?

 

Kansas should be KS 123, Michigan should be MI 123.

 

Ultimately, though, both should be part of route relations that describe the 
route so we can quit adding ref=* to the incorrect entity (it's not the way's 
ref, it's the route's!).

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


Re: [Talk-us] State highway refs (was Re: New I.D Feature)

2014-11-29 Thread Dave Mansfield
Please forgive me I’m not trying to stir things up. I’m new to OSM and trying 
to learn and I don’t have any idea what the NE2 you refer to is.

 

I understand that a lot of things are tagged different then what I would think 
do to standards. I understand that and I’m doing everything I can to learn the 
correct way to tag. I’m always looking at the Wiki and also how others are 
tagging. I’ve also sent emails asking for help on tagging. I understand that we 
normally don’t abbreviate but that states are the exception and we use the 2 
letter abbreviation. So I’m only trying to learn but in this case a ref tag 
seems like a name tag for the name of the route to me and I’m having a hard 
time understanding why we would tag a name something other then what it is.

 

Is there someplace I can go to read why it’s this way?

 

Thanks

Dave

From: Paul Johnson [mailto:ba...@ursamundi.org] 
Sent: Saturday, November 29, 2014 10:40 PM
To: Dave Mansfield
Cc: Shawn K. Quinn; OpenStreetMap talk-us list
Subject: Re: [Talk-us] State highway refs (was Re: New I.D Feature)

 

I'm going to say that the wiki is presently wrong compared to consensus 
previously arrived at on the tagging list regarding this issue the last 
971151183 times that this has come up, largely as a result of previous efforts 
by NE2 to game the renderer...

 

On Sat, Nov 29, 2014 at 9:31 PM, Dave Mansfield mansfie...@chartermi.net 
mailto:mansfie...@chartermi.net  wrote:

From the Wiki  

http://wiki.openstreetmap.org/wiki/United_States_roads_tagging

“The two letter abbreviation for the state per the United States Postal 
Service's  https://www.usps.com/send/official-abbreviations.htm state 
abbreviation list, another abbreviation used by the state (such as SR for State 
Road), or no prefix. Different states may have different standards for which to 
use, and there is no current inter-state standard.”

I take the “Different states may have different standards for which to use” to 
mean that not all states use the two letter abbreviation and in states that 
don’t we should use that states standard for example Michigan uses M. The 
highway behind my house is M-15 and singed that way so I would think it should 
be tagged that way. Am I reading the Wiki wrong?

Thanks

Dave

 

 

 

From: Paul Johnson [mailto:ba...@ursamundi.org mailto:ba...@ursamundi.org ] 
Sent: Saturday, November 29, 2014 10:04 PM
To: Shawn K. Quinn
Cc: OpenStreetMap talk-us list
Subject: Re: [Talk-us] State highway refs (was Re: New I.D Feature)

 

On Sun, Nov 9, 2014 at 3:10 AM, Shawn K. Quinn skqu...@rushpost.com 
mailto:skqu...@rushpost.com  wrote:

So, a couple of questions:

1. What, exactly, is fair game to change to a state abbreviation
reference?

 

Fair game nationwide, two letter state abbreviations should be used for the 
primary state highway network.

 

2. Which states spell out the name in the ref?
I know Kansas uses K-123, and Michigan uses M-123. Are there any others
to be careful of?

 

Kansas should be KS 123, Michigan should be MI 123.

 

Ultimately, though, both should be part of route relations that describe the 
route so we can quit adding ref=* to the incorrect entity (it's not the way's 
ref, it's the route's!).

 

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


Re: [Talk-us] State highway refs (was Re: New I.D Feature)

2014-11-29 Thread Dave Mansfield
Thanks!

 

It makes sense the way you explain it. I was looking at it as a name of the 
route and thinking it should me the same as signs etc. But not the fact that 
routing engines and renderers will know it’s a state highway based on the state 
abbreviation.

 

Dave

 

From: Paul Johnson [mailto:ba...@ursamundi.org] 
Sent: Sunday, November 30, 2014 12:11 AM
To: Dave Mansfield
Cc: Shawn K. Quinn; OpenStreetMap talk-us list
Subject: Re: [Talk-us] State highway refs (was Re: New I.D Feature)

 

On Sat, Nov 29, 2014 at 10:50 PM, Dave Mansfield mansfie...@chartermi.net 
mailto:mansfie...@chartermi.net  wrote:

Please forgive me I’m not trying to stir things up. I’m new to OSM and trying 
to learn and I don’t have any idea what the NE2 you refer to is.

 

Glossing past this since it's extensively in the archives at this point.

 

I understand that a lot of things are tagged different then what I would think 
do to standards. I understand that and I’m doing everything I can to learn the 
correct way to tag. I’m always looking at the Wiki and also how others are 
tagging. I’ve also sent emails asking for help on tagging. I understand that we 
normally don’t abbreviate but that states are the exception and we use the 2 
letter abbreviation. So I’m only trying to learn but in this case a ref tag 
seems like a name tag for the name of the route to me and I’m having a hard 
time understanding why we would tag a name something other then what it is.

 

Don't take it too hard.  People game the wiki regularly, which makes it 
confusing for humans.  We've arrived at using the state name for the primary 
(and often only) state highway networks as this provides for a consistent, 
unambiguous and geographically context-free (ie, you don't need to know what 
state you're in to get it by context) way for routing engines and renderers to 
understand that it's a state highway, and from which state.  This system breaks 
down in ways route relations don't mostly because of the way the network tag 
works for state highways (ie, US:TX, US:TX:NASA, US:OK:Turnpike etc) for states 
that have multiple highway systems and that the ref tag on a way is still a 
legacy from when this whole system was an experiment on some guy's home server 
in London and didn't think it was really going to take off.  ;o)

 

Is there someplace I can go to read why it’s this way?

 

#osm-us on OFTC seems to be the best place to get a quickish answer, though in 
this case, sounds like you got it (even if it didn't sound great...) 

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


Re: [Talk-us] Rand McNally is using OSM

2014-11-22 Thread Dave Mansfield
It’s OSM. Looking at edits I made I found an error on the map. I then went to 
OSM and the error was there so I fixed it. I then reloaded Rand McNally and it 
was fixed.

 

Dave Mansfield

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


Re: [Talk-us] Whole-US Garmin Map update - 2014-10-01

2014-10-04 Thread Dave Mansfield
Hello Dave,

I have tried downloading  your maps. I put the .img file in the Garmin 
directory on a USB drive like I do other maps. When I start BaseCamp in the 
left window it looks like it's reading the map in but then it goes away. If I 
close and restart BaseCamp it will try to read it in again with the same 
results. I have tried renaming them and get the same results. Any idea what I'm 
doing wrong?

Thanks
Dave

-Original Message-
From: Dave Hansen [mailto:d...@sr71.net] 
Sent: Friday, October 3, 2014 4:44 AM
To: d...@sr71.net; talk-us@openstreetmap.org
Subject: [Talk-us] Whole-US Garmin Map update - 2014-10-01

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/2014-10-01

Map to visualize what each file contains:


http://daveh.dev.openstreetmap.org/garmin/Lambertus/2014-10-01/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/2014-10-01

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


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