Closed GoogleCodeExporter closed 8 years ago
At first this error was able to be bypassed but at now when the error shows up
you can only click OK and the map is lost. Looks like a problem with the API
key and possibly too many page views or maps drawn.
Original comment by kimballd...@gmail.com
on 2 Feb 2012 at 6:28
Attachments:
The problem is that there is no API key registered in the app. As such, it's
getting the bare-minimum of resources from the Maps API. I'm going to
permanently register a key with the application that should hopefully fix this
issue.
Original comment by bdfer...@google.com
on 7 Feb 2012 at 8:35
Original comment by bdfer...@google.com
on 7 Feb 2012 at 8:35
Reviewed at http://codereview.appspot.com/5643046/ and committed at r1648.
Original comment by bdfer...@google.com
on 7 Feb 2012 at 8:44
Hi
Thanks for the updates, it is not fixed yet.
I just checked, do i need to download a new schedule viewer or what?
Original comment by mazed...@gmail.com
on 7 Feb 2012 at 8:52
Sorry... I checked in a fix and it's fixed in the source code. You should be
able to run from source directly to get the update. If you need a Windows
binary, you will have to wait until I cut a new release of Schedule Viewer
later today.
Original comment by bdfer...@google.com
on 7 Feb 2012 at 8:54
Thanks a lot, that would be helpful too.
Sincerely,
Mazed
Original comment by mazed...@gmail.com
on 7 Feb 2012 at 8:59
Hi
I tried running using the source code from the server, but couldn't, where
as we ran successfully before.
*Here is our questions*
In file file: schedule_viewer.py, Line 532 options.key =
'AIzaSyAZTTRO6RC6LQyKCD3JODhxbClsZl95P9U', this key is registered against a
domian name, for our purposes do you think we need to register under the
domain where we are using this source code. Just looking at the key, it
looks like it is not Google Map API key.
Please give us further guidelines to resolve the issue
I appreciate your feedback
Original comment by mazed...@gmail.com
on 8 Feb 2012 at 6:06
Hi,
If possible, please send an URL, so that we can see the output of your
schedule viewer.
Like, www.m2gha.com:8090 (example)
Original comment by mazed...@gmail.com
on 8 Feb 2012 at 6:26
The key, as I understand it, shouldn't be tied to a domain like an old Google
Maps V2 API key would. Either way, the url for your scheduler viewer instance
is usually always http://localhost:8765/.
In the meantime, I've uploaded some test binaries for Windows:
http://code.google.com/p/googletransitdatafeed/downloads/detail?name=transitfeed
-windows-binary-trunk.zip
Give those a shot and let me know if they work for you.
Original comment by bdfer...@google.com
on 8 Feb 2012 at 5:05
HI,
Thanks for your assistance, the PC/Wiindows version work.
However, intially we used the source code on linax enviornment,
Transitfeed-1.2.10.tar.gz-----------transitfeed
python library and tools source distribution (version 1.2.10).
In version 1.2.10, we only chnaged the old source code as you indictaed in
your earlier e-mail, the option key.
However, it didn't work.
As i mentioned, we successfully ran (version 1.2.10) on a linax
enviornment, but after the api error issue reaised, we couldn't run
successfully, and even w/ your suggessted correction.
It would be real helpful, if you can update the (version 1.2.10), and post
on the download tab, or send me a link.
I appreciate your time and efforts.
Please let me know if you have any questions.
Original comment by mazed...@gmail.com
on 8 Feb 2012 at 6:56
Dear GTFS Guru,
We need your feedback.
Original comment by mazed...@gmail.com
on 10 Feb 2012 at 9:22
I'm still making some other changes before I cut a full release.
In the meantime, a question. When you had issue running from source, did you
get the source from the Download page? Or did you check it out from source
directly?
Original comment by bdfer...@google.com
on 10 Feb 2012 at 9:43
Hi,
Yes we got source from Download page.
Please let me know if you have any questions.
When we could expect your updated version, would be real helpful to know.
Original comment by mazed...@gmail.com
on 10 Feb 2012 at 9:58
Can you check out the latest source code directly?
http://code.google.com/p/googletransitdatafeed/source/checkout
That code has all the latest fixes and is the best thing to test with.
Original comment by bdfer...@google.com
on 10 Feb 2012 at 10:34
Hi GTFS Guru,
We tried w/ your new code, it ran, but when we open using
www.domainname.com:8090, we didn't view anything.
If you can help us providing more direction would be real helpful.
Original comment by mazed...@gmail.com
on 11 Feb 2012 at 6:18
Hi,
If you need the server access please let me know we can provide you the
access to test.
Original comment by mazed...@gmail.com
on 11 Feb 2012 at 6:47
[deleted comment]
Whoa whoa whoa. You really shouldn't be publishing login credentials to a
public forum on the internet! You should change your password RIGHT NOW.
Typically, when schedule viewer launches, it tells you the URL you can use to
access the tool and it's usually something like http://localhost:8765/ .
Schedule Viewer was really only designed to be used by someone locally to
verify that their schedule looks ok. I suppose it could be run as a public
service on the internet, but do you really need to?
Original comment by bdfer...@google.com
on 11 Feb 2012 at 9:42
Thanks for all of your feedback, it was really helpful.
We do really need to run as a public service on the internet, and we ran
successfully before, the address we used was www.nworegontransit.org:8090,
however, after the API key problem raised, and with recent code updates, we
ran successfully the Schedule Viewer using the source code in lynax
enviornment, but couldn't view as we viewed the schedule viewer
output before in www.nworegontransit.org:8090.
So, if you can tell us, is that something you have changed that causing us
not to view the Schedule Viewer output in www.nworegontransit.org:8090,
would be helpful. Or, if you can bring the old features that we had before
would be really helpful.
Please let me know if you have any questions.
Our development team is on online right now, if any case you would like to
chat w/ us in gtalk or in skype, we could provide our id.
Original comment by mazed...@gmail.com
on 11 Feb 2012 at 10:00
Dear GTFS Guru,
We need your feedback, i appreciate for your time and considertaion.
Original comment by mazed...@gmail.com
on 12 Feb 2012 at 10:49
Original issue reported on code.google.com by
mazed...@gmail.com
on 2 Feb 2012 at 6:01