Does anyone (you know who you are) know exactly what is disappearing when Autodesk deprecates the /v1 equivalent of the ModelDerivative API?
I've taken care of everything that was in the blog post here:
https://forge.autodesk.com/cloud_and_mobile/2016/09/autodesk-forge-apis-migrating-from-v1-to-v2.html
But I also have some calls such as:
/viewingservice/v1/:URN/status
and:
/viewingservice/v1/items/:dbpath object_ids.json.gz
That were not specifically mentioned. Will these also need to be modified?
These endpoints will no longer be valid. The status of a translation can be obtained by using the GET :urn/manifest endpoint.
We have official SDK's for multiple programming languages that will make it easier to handle the REST calls.
To download the derivatives of a model, the SDK's do not expose direct methods so you actually have to issue the calls "directly". Take a look at the extract.io sample that expose the full download workflow, more specifically there.
Hope that helps
Related
I've been following this tutorial to successfully upload Revit & AutoCad files to Bim360 Docs using 2-legged tokens. I am also using the 'x-user-id' header.
The problem I'm having is after the model is published to Bim360 docs, it’s not viewable in the browser and derivatives are empty (see below). It appears that the model translation job never occurs. Isn’t this supposed to happen automatically for Bim360 Docs files? Could the 2-legged token be hindering this process? Is there another step I'm missing?
I've even tried to manually kick off a translation job after uploading the file by calling this API with NO success.
This image is the result of calling the manifest API.
empty derivatives
Thank you for reporting it to us. Our engineering team is investigating the problem. But you should see the progress status 100% now, please haveing a try, thanks!
I want to have a full dump of a rest API. Now I have to query on everything but I just want to have everything of the API in one file (csv or json).
How can I do this?
Thanks!
There's no one size fits all answer for this. Every API works differently, and some might have a specific feature for this.
If the service you are using is truly RESTful (as in: uses hyperlinks for everything), you might be able to just use a mirror/spider tool to get all the data, but very few services that advertise themselves as REST really are.
"full dump of a rest API" do you mean you want to have file specification of API? If so, you can a have a look at this tool (http://editor.swagger.io/#/) for describing rest api interfaces.
I have been looking all day at the Google Drive SDK for Android,
but I am a bit confused.
I need to make the list of folders and files in the user Google Drive account.
I thought that was a simple, basic standard feature, but maybe not...
Please can you help me?
You have two possible ways to go:
use RESTful API, or
use Google Drive Android Api (GDAA)
I would say the former would be easier to start with.
If you decide to go with the REST, you may use the GitHub demo here, that has both the REST and the GDAA 'CRUD' implementations (you just comment out the one you don't need). It also has some code to deal with the authentication / authorization which you need to do anything on Google Drive. See SO 28439129.
In case you decide to use GDAA, (you still have to get the authorization done), the 'official' to get you started demos are here and here.
You will definitely run into a lot of roadblocks and the solutions are mostly found here under the tag 'google-drive-android-api'.
Good Luck.
I went through method documentations both patch and update and it looks they both doing the same.
And i also note that the patch doesn't required the content of the patching comment even though its required to call the patch() method.
So, is the difference between comment.patch() and the comment.update() methods in Google Drive API?
PS : I'm using Google-Drive Java SDK for my implementation.
Thanks.
Patch is used to perform partial updates and save some bandwidth when, for instance, you only want to update a single field in a resource.
For more details about how patch work and for other performance tips, please check the Google Drive SDK documentation:
https://developers.google.com/drive/performance#patch
So, Google Places API allows me to receive JSON data through a Google Places API search using a simple:
"https://maps.googleapis.com/maps/api/place/search/json?location=-33.8670522,151.1957362&radius=50&client=clientId&sensor=true_or_false&signature=SIGNATURE"
(note, includes signature/key).
Why does SimpleGeo not allow this same feature? Is it possible? What is the purpose of all of this server side code that SimpleGeo uses?
Regards,
Ryan
SimpleGeo has recently announced a JavaScript SDK, which includes a JSONP API. This should allow you to do exactly what you're asking -- requesting read-only information from their Context and Places APIs purely from the client side with a simple key to authenticate the request.
I think there are still plenty of purposes for accessing SimpleGeo's data from a server-side application -- not all developers are writing purely JavaScript client-side applications -- but I agree that this new SDK will help a lot of developers.
Also, if you're looking for straightforward REST access to JSON resources without any client libraries, that's also present. See SimpleGeo's documentation on API endpoints.