Since yesterday, I am unable to create a new map by importing a .kml
file. The process fails with the usual "We could not finish uploading
your file." error message. However, the file being uploaded is known
to be 'good'. In fact, I tried uploading a file created by using the
output=kml parameter against a working map. Even more curiously the
same file will open perfectly in Google Earth.
It was all working perfectly a couple of days ago. I have tried it on
two different machines, with three different accounts, all with the
same result.
I don't know what steps you are following, so let's start by making sure you are doing them correctly.
First, host your KML file in a location that has unblocked internet access. Then, paste the URL hosting your file into the search box of Google Maps and click "Search Maps".
I just tried it with the KML file of a map that has over 300 items, and it worked fine.
On Tue, May 13, 2008 at 9:38 AM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote:
> Since yesterday, I am unable to create a new map by importing a .kml > file. The process fails with the usual "We could not finish uploading > your file." error message. However, the file being uploaded is known > to be 'good'. In fact, I tried uploading a file created by using the > output=kml parameter against a working map. Even more curiously the > same file will open perfectly in Google Earth.
> It was all working perfectly a couple of days ago. I have tried it on > two different machines, with three different accounts, all with the > same result.
> I don't know what steps you are following, so let's start by making
> sure you are doing them correctly.
> First, host your KML file in a location that has unblocked internet
> access. Then, paste the URL hosting your file into the search box of
> Google Maps and click "Search Maps".
> I just tried it with the KML file of a map that has over 300 items,
> and it worked fine.
I am using excatly the same steps I have used with success for the
last three months or so. Very simple stuff. Plain vanilla Google maps
browser interface approach. From My maps, click 'Create new map'.
Click 'Import'. Click 'Browse'. Select .kml file from local machine.
Click 'Upload from file'.
Now that might not be your 'correct' method, but it has always worked
for me before.
Interestingly I am now suddenly getting :
"Uploading file...
Please wait — this may take a few minutes depending on the speed of
your internet connection. "
Then waiting, and waiting, and ...
BTWm a similar map I created this way weeks ago is displaying
perfectly via a link. The problem is only with creating a new map.
If you click on the Help link inside Google Maps and search for "KML", you are directed to a Help page entitled "Can Google Maps read the KML files I've made for Google Earth?" Inside we are given the exact directions that I provided here.
So, sounds like your method is the root of your problem. Instead, use Google's published method. I have used it many times and I have never had any problems.
On Tue, May 13, 2008 at 10:30 AM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote:
> On 13 May, 18:02, NWT <nwt...@gmail.com> wrote: > > I don't know what steps you are following, so let's start by making > > sure you are doing them correctly.
> > First, host your KML file in a location that has unblocked internet > > access. Then, paste the URL hosting your file into the search box of > > Google Maps and click "Search Maps".
> > I just tried it with the KML file of a map that has over 300 items, > > and it worked fine.
> I am using excatly the same steps I have used with success for the > last three months or so. Very simple stuff. Plain vanilla Google maps > browser interface approach. From My maps, click 'Create new map'. > Click 'Import'. Click 'Browse'. Select .kml file from local machine. > Click 'Upload from file'.
> Now that might not be your 'correct' method, but it has always worked > for me before.
> Interestingly I am now suddenly getting : > "Uploading file... > Please wait — this may take a few minutes depending on the speed of > your internet connection. "
> Then waiting, and waiting, and ...
> BTWm a similar map I created this way weeks ago is displaying > perfectly via a link. The problem is only with creating a new map.
> If you click on the Help link inside Google Maps and search for "KML",
> you are directed to a Help page entitled "Can Google Maps read the KML
> files I've made for Google Earth?" Inside we are given the exact
> directions that I provided here.
> So, sounds like your method is the root of your problem. Instead, use
> Google's published method. I have used it many times and I have never
> had any problems.
I must clarify. The kml file I am attemping to upload was not created
in, or for, Google Earth, it was created programmatically and has been
formatted specifically for use in Google Maps. The same strategy has
worked many times in the past few months. A backup copy of exactly the
same file that was used a few days ago also fails. The same file is
being opened correctly (from a local file) in GE.
I now find that if I do exactly as before (rather than the method you
suggest) but import into Google Maps from a URL (the same file stored
by FTP on a server) rather than from a local file it works. The new
map is added perfectly to 'My Maps' . That will do as a work around,
but I still don't see why what worked a few days ago no longer behaves
as it did.
On Tue, May 13, 2008 at 11:33 AM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote: > I must clarify. The kml file I am attemping to upload was not created > in, or for, Google Earth, it was created programmatically and has been > formatted specifically for use in Google Maps.
That's fine. Any KML file that was correctly made will work regardless of where it was created. If your KML file still doesn't work, I would double and triple check the code.
But if everything worked before and you are absolutely certain that you haven't changed _anything_ _anywhere_, it may be that Google changed their requirement. I don't know if this is the case, though.
But I do know that it works exactly as the Help page describes.
> On Tue, May 13, 2008 at 11:33 AM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote:
> > I must clarify. The kml file I am attemping to upload was not created
> > in, or for, Google Earth, it was created programmatically and has been
> > formatted specifically for use in Google Maps.
> That's fine. Any KML file that was correctly made will work
> regardless of where it was created. If your KML file still doesn't
> work, I would double and triple check the code.
As I said, exactly the same file imports perfectly in to Google maps
from a URL, so *must* be valid. It only fails if imported from my
local machine, and yet GE can open it locally.
On Tue, May 13, 2008 at 12:30 PM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote:
> On 13 May, 20:13, NWT <nwt...@gmail.com> wrote: > > On Tue, May 13, 2008 at 11:33 AM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote: > > > I must clarify. The kml file I am attemping to upload was not created > > > in, or for, Google Earth, it was created programmatically and has been > > > formatted specifically for use in Google Maps.
> > That's fine. Any KML file that was correctly made will work > > regardless of where it was created. If your KML file still doesn't > > work, I would double and triple check the code.
> As I said, exactly the same file imports perfectly in to Google maps > from a URL, so *must* be valid. It only fails if imported from my > local machine, and yet GE can open it locally.
> Then that must mean your problem is isolated to that machine. Look it
> over with a fine-toothed comb.
Must it?
A quote from my original posting:
"It was all working perfectly a couple of days ago. I have tried it
on
*two different machines*, with three different accounts, all with the
same result."
The machines were even connected to the internet via utterly different
means from entirely separate locations.
Just tried it on a third (same internet connection via LAN and router
as machine number 2 though to be fair) - guess the result.
On Tue, May 13, 2008 at 1:21 PM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote:
> On 13 May, 20:36, NWT <nwt...@gmail.com> wrote: > > Then that must mean your problem is isolated to that machine. Look it > > over with a fine-toothed comb.
> Must it?
> A quote from my original posting:
> "It was all working perfectly a couple of days ago. I have tried it > on > *two different machines*, with three different accounts, all with the > same result."
I'm going by your last post that says "It only fails if imported from my local machine". Singular. Singular means one, right? Sorry I can't remember what you wrote 4 hours and 4 posts ago - not to mention all the details that I have been dealing with the some 30 threads that I am participating in today alone.
Since you didn't include your original post in your reply, and instead said that it isn't working on one singular machine, I came to that conclusion. If mixups aren't acceptable to you, don't leave any room for them to happen. Include ALL accurate necessary details in your message.
I am not here to argue with you. If you wish to ask for help on public forum, great. Be willing to accept public advice. If you don't want to accept it, that's fine too. But doing so does not encourage anyone else to help you.
> On Tue, May 13, 2008 at 1:21 PM, 72degrees <pe...@ps-fisher.demon.co.uk> wrote:
> > On 13 May, 20:36, NWT <nwt...@gmail.com> wrote:
> > > Then that must mean your problem is isolated to that machine. Look it
> > > over with a fine-toothed comb.
> > Must it?
> > A quote from my original posting:
> > "It was all working perfectly a couple of days ago. I have tried it
> > on
> > *two different machines*, with three different accounts, all with the
> > same result."
> I'm going by your last post that says "It only fails if imported from my
> local machine". Singular. Singular means one, right? Sorry I can't
> remember what you wrote 4 hours and 4 posts ago - not to mention all
> the details that I have been dealing with the some 30 threads that I
> am participating in today alone.
> Since you didn't include your original post in your reply, and instead
> said that it isn't working on one singular machine, I came to that
> conclusion. If mixups aren't acceptable to you, don't leave any room
> for them to happen. Include ALL accurate necessary details in your
> message.
> I am not here to argue with you. If you wish to ask for help on
> public forum, great. Be willing to accept public advice. If you
> don't want to accept it, that's fine too. But doing so does not
> encourage anyone else to help you.
> > The machines were even connected to the internet via utterly different
> > means from entirely separate locations.
> > Just tried it on a third (same internet connection via LAN and router
> > as machine number 2 though to be fair) - guess the result.- Hide quoted text -
You must forgive me for snipping posts to avoid them becoming longer
and ever longer. I date back to the usenet days when bandwidth was an
issue and one was expected to follow a thread.
I'm dismayed that you see my further clarification of the nature of
the problem as "arguing with you". I should of course said "any" local
machine in that posting.
In fact your comment about an alternative method for importing a kml
file pointed me in the direction of a (hopefully) temporary solution,
for which I thank you.
Should I discover what is actually causing the problem I will be sure
to report back my findings.
