Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Possible Substituion for the Shut Down of Googler Fusion Table API #10

Open
AkashNayak48 opened this issue Jun 5, 2020 · 2 comments
Open

Possible Substituion for the Shut Down of Googler Fusion Table API #10

AkashNayak48 opened this issue Jun 5, 2020 · 2 comments

Comments

@AkashNayak48
Copy link

HI guys,

Tried running your project for OBIA based stuff. Found out later that Google Fusion Table API has been shut down since #rd December, 2019. DO you have any substituion for that???AM trying ot execute the code, but cant cause of this.
@AkashNayak48 AkashNayak48 changed the title Possible Substituion fir the Shut Down of Googler Fusion Table API Possible Substituion for the Shut Down of Googler Fusion Table API Jun 5, 2020
@erin-ntnu
Copy link

Hi! I did this recently - my solution was to make a shapefile (I used ArcMap) and upload that as an asset. You need to include the fields as specified in the script 'landslide_id' (I changed it to 'LS_id' because of the 10 character header limit for shapefiles), 'latitude', 'longitude', and 'event_date'. It was also important that the event date was written in the Joda DateTime format - for example: 2019-07-30T00:00:00.000+0100'.

@pearsongs
Copy link

@erin-ntnu Excuse me. Could you share the shapefile you made with me? I really need this. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AkashNayak48 @erin-ntnu @pearsongs