[Talk-us] Whole-US Garmin Map update - 2013-03-28

2013-03-29 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@ l

Re: [Talk-us] Overpass API and T-mobile

2013-03-29 Thread Roland Olbricht
Dear all, thank you very much. Now it looks quite clearly like a T-mobile US related problem. I do see only very few T-mobile US addresses (all from 208.54.X.X, although T-mobile has mauch more IPv4 space) in the log files for today. And a lot of people have just confirmed that the problem exis

Re: [Talk-us] Overpass API and T-mobile

2013-03-29 Thread Philip Barnes
It may not help much, but it works fine on my t-mobile UK phone. Browser is firefox. As a matter of interest, does it work if you use your phones as access points and use the full computer browser? Phil (trigpoint) On Fri, 2013-03-29 at 13:28 -0700, Clifford Snow wrote: > I couldn't get it eith

Re: [Talk-us] Overpass API and T-mobile

2013-03-29 Thread Clifford Snow
I couldn't get it either on my t-mobile phone. Same 504 error code. Location Seattle, WA On Fri, Mar 29, 2013 at 12:55 PM, Roland Olbricht wrote: > Dear all, > > a user of the OSM readonly mirror Overpass API has complained about getting > always the HTTP error code 504 instead of a valid respo

Re: [Talk-us] Overpass API and T-mobile

2013-03-29 Thread Mike Thompson
Roland, I could not access it through my T-Mobile serviced device. Time 2:03pm US Mountain Daylight Time (UTC-06). Not sure of IP address. Mike On Fri, Mar 29, 2013 at 1:59 PM, Clay Smalley wrote: > Working fine on AT&T. > On Mar 29, 2013 2:57 PM, "Roland Olbricht" wrote: > >> Dear all, >>

Re: [Talk-us] Overpass API and T-mobile

2013-03-29 Thread Clay Smalley
Working fine on AT&T. On Mar 29, 2013 2:57 PM, "Roland Olbricht" wrote: > Dear all, > > a user of the OSM readonly mirror Overpass API has complained about getting > always the HTTP error code 504 instead of a valid response with HTTP 200. > After we have excluded all potential obvious problems o

[Talk-us] Overpass API and T-mobile

2013-03-29 Thread Roland Olbricht
Dear all, a user of the OSM readonly mirror Overpass API has complained about getting always the HTTP error code 504 instead of a valid response with HTTP 200. After we have excluded all potential obvious problems on both the client and the server, he still sees the 504 and his requests never a