[OSGeo-Discuss] semi-OT... Using Google Drive as a file repository for a mapping app

[Andy Anderson]

One suggestion if you don’t want to / can’t use your own server, perhaps Github would work for you. I know places like the City of Cambridge, Massachusetts, GIS department have used it to distribute data files:

	https://github.com/cambridgegis

— Andy

> On Oct 18, 2024 08:46 AM, at 8:46 AM, Andy Anderson <aanderson at amherst.edu> wrote:
> 
> Hi, Andrea,
> 
> The problem is that the link that Google Drive provides is to a “preview” program that turns it into a web page, even for well-known file types like “.txt” and “.png”. It is not a link to the “raw” file.
> 
> The only way around that I’ve seen is for Sheets documents, which, when sharing, can be “Published to web” in standard formats such as “.csv”.
> 
> — Andy
> 
>> On Oct 18, 2024 04:38 AM, at 4:38 AM, Andrea Giacomelli via Discuss <discuss at lists.osgeo.org <mailto:discuss at lists.osgeo.org>> wrote:
>> 
>> Hello to all,
>> 
>> a) This is a question I tried to pose initially on Google Drive discussions as it is a generic issue on the Google Drive side.
>> In absence of feedback for the moment I am relaying it also here...maybe somebody has tried this.
>> 
>> I would like to understand if there is a way to use a Google Drive folder as a repository for GPX or Geojson files to be displayed via web map applications that allow online data sources.
>> 
>> b) As a test, I took a generic geojson file and uploaded it via FPT to a folder on my web site, and I am able to use that file as a layer by indicating its URL....works fine.
>> 
>> If I upload the same file to Google Drive, share it to "Anyone with the link", and then use the deriving URL as a data source, the layer is not displayed....
>> 
>> example:
>> https://drive.google.com/file/d/1Iao_JWwGgOqrFTGNdjxvuTSaq1whnXz9/view?usp=sharing <https://drive.google.com/file/d/1Iao_JWwGgOqrFTGNdjxvuTSaq1whnXz9/view?usp=sharing>
>> 
>> c) I am wondering if there are other ways to refer to the shared file, so that it may be read appropriately by the mapping app.
>> 
>> I noted that Drive uses different URL for the file depending on the function (e.g.  https://drive.usercontent.google.com/u/0/uc?id=1Iao_JWwGgOqrFTGNdjxvuTSaq1whnXz9&export=download <https://drive.usercontent.google.com/u/0/uc?id=1Iao_JWwGgOqrFTGNdjxvuTSaq1whnXz9&export=download> )...but I cannot find a documentation about this...
>> 
>> TIA for any feedback, and best regards
>> 
>> Andrea Giacomelli
>> http://www.pibinko.org <http://www.pibinko.org/> Cultura, ambiente, innovazione libera...
>> http://www.jugbandcm.it <http://www.jugbandcm.it/> ...e musica
>> +39 3791680739 - voce
>> +39 3317539228 - whatsapp
>> PIVA 01582480537
>> 
>> 
>> p.s. I am evaluating the Google Drive approach since I have some data providers who are comfortable using Drive to upload their files, but are less conversant with FTP or other tools.
>> 
>> 
>> Andrea Giacomelli
>> http://www.pibinko.org <http://www.pibinko.org/> Cultura, ambiente, innovazione libera...
>> http://www.jugbandcm.it <http://www.jugbandcm.it/> ...e musica
>> +39 3791680739 - voce
>> +39 3317539228 - whatsapp
>> PIVA 01582480537
>> 
>>  <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>	Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <x-msg://2/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________
>> Discuss mailing list
>> Discuss at lists.osgeo.org <mailto:Discuss at lists.osgeo.org>
>> https://lists.osgeo.org/mailman/listinfo/discuss
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/discuss/attachments/20241018/b252a7e3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 529 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.osgeo.org/pipermail/discuss/attachments/20241018/b252a7e3/attachment.sig>