[Talk-us] Whole-US Garmin Map update - 2014-12-30

2015-01-01 Thread 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@

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Natfoot
The inherent problem with ferry routes is that they have a schedule. Routers can't then tell their users how long it is going to take without that data. As far as I know we don't have schedule capability within OSM and it is something that the routers have not pulled not even the big G. The big G

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Harald Kliems
Graphhopper doesn't have the problem. It could be that other routers are using outdated data that did indeed have a tagging problem. https://graphhopper.com/maps/?point=47.811656%2C-122.379627point=47.809696%2C-122.528286layer=Lyrk Harald. On Thu Jan 01 2015 at 10:20:45 AM Clifford Snow

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Richard Welty
On 1/1/15 1:55 PM, Clifford Snow wrote: On Thu, Jan 1, 2015 at 10:23 AM, Natfoot natf...@gmail.com mailto:natf...@gmail.com wrote: The inherent problem with ferry routes is that they have a schedule. Routers can't then tell their users how long it is going to take without that

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Richard Welty
On 1/1/15 12:13 PM, Harald Kliems wrote: Graphhopper doesn't have the problem. It could be that other routers are using outdated data that did indeed have a tagging problem. https://graphhopper.com/maps/?point=47.811656%2C-122.379627point=47.809696%2C-122.528286layer=Lyrk in the long run, we

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Clifford Snow
On Thu, Jan 1, 2015 at 10:23 AM, Natfoot natf...@gmail.com wrote: The inherent problem with ferry routes is that they have a schedule. Routers can't then tell their users how long it is going to take without that data. As far as I know we don't have schedule capability within OSM and it is

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Clifford Snow
On Wed, Dec 31, 2014 at 11:18 PM, Natfoot natf...@gmail.com wrote: When talking to the Scout team this summer it was mentioned as an issue. Also Scout wont route across access roads and if there is an access road leading up to the dock/portal then no route. you will notice that it is listed

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Darrell Fuhriman
GTFS works fine for ferries already. Many do publish the data. d. On Jan 1, 2015, at 10:55, Clifford Snow cliff...@snowandsnow.us wrote: I agree. However, it would be nice to have it show the route. Somehow we can route via bus using GTFS. I wonder if ferry routes have a similar spec?

Re: [Talk-us] access road routing - two real world cases

2015-01-01 Thread stevea
i suppose OSM could use access=permissive for the preferred route, but that usage doesn't match well with the current language for permissive. Richard, I'm not sure this is a perfect solution, but it could work. What about using access=destination (Only when travelling to this element...) on

Re: [Talk-us] Routing on Ferries

2015-01-01 Thread Clifford Snow
On Thu, Jan 1, 2015 at 11:23 AM, Darrell Fuhriman darr...@garnix.org wrote: GTFS works fine for ferries already. Many do publish the data. I just checked, Washington State Ferries does use GTFS [1]. I originally posted this message because of a Scout note in OSM. My sense is the problem is

Re: [Talk-us] Rail westerly (Dave Mansfield)

2015-01-01 Thread Michael Patrick
What I'm not quite sure about are federal records such as FRA records (as I believe Oak Ridge data are). These would be covered under, say, a FOIA request, and so are quite similar to the same nexus argument as state records, only under federal law, not state law. Generally, I have had very

Re: [Talk-us] access road routing - two real world cases

2015-01-01 Thread Harald Kliems
I don't think that this is a tagging but a routing problem. It seems easy enough to me to program a router do not use roads with access=private unless they are the first or last segment of a route or something along those lines. RE: access=destination. Not sure what the convention is in the US,

Re: [Talk-us] access road routing - two real world cases

2015-01-01 Thread Richard Welty
On 1/1/15 6:00 PM, Harald Kliems wrote: I don't think that this is a tagging but a routing problem. It seems easy enough to me to program a router do not use roads with access=private unless they are the first or last segment of a route or something along those lines. well, it is an issue

Re: [Talk-us] access road routing - two real world cases

2015-01-01 Thread stevea
Harald Kliems kli...@gmail.com writes: I don't think that this is a tagging but a routing problem. It seems easy enough to me to program a router do not use roads with access=private unless they are the first or last segment of a route or something along those lines. RE: access=destination.

Re: [Talk-us] access road routing - two real world cases

2015-01-01 Thread jfeldredge.com
The equivalent sign in the USA states either No Thru Traffic or Local Traffic Only. While the standard written spelling is through, the shortened spelling Thru is standard on road signs. -- John F. Eldredge -- j...@jfeldredge.com Darkness cannot drive out darkness; only light can do that.