The Google Maps API states that the KML(or KMZ) file can be hosted on a publicly accessible web server. This does infer that the document should be available via HTTP(S), but the protocol is not actually stated. Can you please confirm whether the protocol must be HTTP / HTTPS, or could FTP be used as an interim option during the prototype.
Cant confirm but if they say that your KMZ can be hosted on a publicly accessible web server then it mean HTTP(S) and not FTP. Can you setup your FTP location to also be accessed via a URL?
If you enter a ftp url into the maps search box
We could not understand the location ftp://test...
suggests they dont understand ftp urls. If it understood the url, it would be a 'cant read file at ... '
Google Maps and the API use the same system for KML rendering.
Related
Hi i'm trying to make my own cloud web service that uses python google drive API.
what i'm trying to make is basically cloud service but can also interact with Google Drive.
To do that, my web service users have to have their own 'storage.json' file in their server's virtual directory (which really stores in server).
when I somehow get my own 'storage.json' file, (I followd: https://developers.google.com/drive/api/v3/manage-uploads)
and upload 'storage.json' file to my directory like User1, upload and download with Google drive works just fine.
but my final goal is when my user doesn't have 'storage.json' file in their directory like User2, I want browser to pops up in User2's computer and User2 can follow the google's authentication flow and finally download 'storage.json' file into server's ~/User2/ directory.
Do you think this is possible? or if there are better ways, can you notice me? thank you
Google chrome has just announced that V3 extensions is the disallowing of remotely hosted code. What does this means ? are they disallowing iframe? I am unable to find any details on this?
As wOxxOm noted, it means all of your code must be in the packaged you upload to the Chrome Web Store, you cannot include code from remote servers.
From the Overview of Manifest V3 docs on developer.chrome.com:
A key security improvement in MV3 is that extensions can't load remote code like JavaScript or Wasm files. This lets us more reliably and efficiently review the safe behavior of extensions when they're submitted to the Chrome Web Store. Specifically, all logic must be included in the extension's package.
I'm just having a site and I don't want to store the user uploaded Files in my server . I want to store it in a cloud server or storage like gdrive or dropbox. Is this possible todo?
You can simply use the Google Drive API for achieving this. Google Drive API is using OAuth 2.0 Authentication. You can find API Endpoints and Authentication methods from below link.
https://developers.google.com/drive/api/v3/manage-uploads
Suppose I want to write a tool which allows the user to copy a file from Dropbox to Google Drive but I don't want to download the file first to my server and then upload it to the drive. Is there a way where I can insert a file to drive by just providing a URL? I couldn't find anything in the documentation.
No.
Having said that, it isn't necessary to create a file on your server. You can buffer the content in memory.
I suppose you could send the access token to the client via a POST request. You'd have to encrypt it, of course, preferably SSL. Then the client could use the Drive SDK to upload the file directly from itself, completely bypassing your server.
I'm attempting to install the DrEdit sample app for python onto GAE. The app runs, but saving or opening a file results in an HTTP 403 "Access Not Configured Error".
client.json has client_id and client_secret set per the API Access>Client ID for Drive SDK values. I have also attempted to use the values for API Access>Client ID for web applications.
The Google Drive SDK> OAuth Client ID has also been set variously to the Drive SDK and web app Client IDs.
What am I doing wrong?
In the services section of the Google API console there are two services relating to drive development, SDK and API. When you create a new Drive SDK entry, Drive API service is not automatically enabled (which doesn't make sense, I don't see when you'd create a drive enabled application without using the drive API). Switch the Drive API service on for the project and try again.
#lurking_googlers I think a lot of people will fall for this, doesn't it make sense to enable the API when the SDK is enabled?
And your must also identify in your code the following
DriveService.Scope.DriveFile, DriveService.Scope.Drive
good luck