I want to create POIs that need to be reviewed by someone authorized before
who is not authorized users can see the POI. Also when updating
or delete a point.
I do not know if it can be done natively or there is some strategy that is being followed in these cases.
Any advice or suggestion is welcome.
Regards.
Our recommendation is to use the FIWARE context Broker to deal with POIs. An NGSI Data Model for POIs is available at
http://fiware-datamodels.readthedocs.io/en/latest/PointOfInterest/PointOfInterest/doc/spec/index.html
I hope this helps
Related
I've had a major spike in my Google API usage. Because many of my sites share the same key, I was hoping to see a sorted list of where the API calls are coming from. I haven't managed to find how to do that in the Google API Console. I know that you can restrict the keys to specific domains, but that's not realistic with hundreds of domains.
In the mean time I've regenerated the keys and deployed them in case they've been co-opted by someone else. If anyone has any insight, I'd really appreciate it. Thanks.
You can do this for all future requests but not for past ones. Google recently implemented a channel parameter in requests. You can add a different channel (from 0 to 999) to your requests from different URLs and then filter your billing reports on that channel to see exactly what you are looking for in your billing report moving forward.
https://developers.google.com/maps/reporting/gmp-reporting#usage-tracking-per-channel
Is it possible to see what domains are using a Google API Key?
No its not.
If you want to know where the calls are coming from i would make project for each domain and then create a key. This will mean monitoring 100 google projects and creating billing accounts for each. I dont really see any other way around it though.
We are providing websites/CMS solutions for more than 2500 customers. Almost all websites have google-map module. So since google changed its map usage policy, from one day to another all those webs had an error on their map modules. We need to come up with some quick (and dirty) solution. We decided to use multiple api-keys, and devide domains between them - alphabetic. And we registered all those 2500+ domains under these keys - manually. One by one.
The solution worked until last week. Now we somehow reached some kind of limit, as we cannot register any new domains/referrers under one of those api-keys. The actual count of domains/referrer of this given api-key: 1537. The saving process yields an error with tracking code (which is every time I try different).
Is there really some kind of limit? Does anyone experienced the same problems. Does some time-economic solution exists?
Thanks for any help or suggestions. Peace!
There is indeed a limit of (at time of writing) about 1,000 referer restrictions per API key. You can create about 100 keys per project, so you can authenticate 100,000 domains with a single project. To proceed further, you can create multiple projects (note that multiple projects can be combined under the same billing account, so you would still receive a single bill).
As a short term fix, you can temporarily remove all restrictions on the key, so that apps relying on that key are functional again. Then you can take the time to release a new key sharding pattern that follows these guidelines.
I just created a feature request so that the situation can be improved, for this use case ("star" it, to be notified of updates).
Google has recently released an alpha version of API that allows manage API keys programmatically.
The best way to handle thousands of authorized domains is to use an API to programmatically manage your API Keys and their restrictions, and we have recently launched a new service that allows you to do this.
This API is still in Alpha. If you are interested in becoming a Trusted Tester for this service, you can use the following form to sign up, please read the instructions carefully:
https://forms.gle/qx2SMcarWCAsbWVp7
Please note that this API is not part of the Google Maps Platform. After you fill out the form, you will be contacted by the API Keys API team with instructions on how to get started, and how to receive support.
API Keys API is currently free of charge. However, please note that use of Cloud Endpoints may be subject to charges at high traffic volume. You can check the pricing sheet here:
https://cloud.google.com/endpoints/pricing-and-quotas
source: https://issuetracker.google.com/issues/35829646#comment12
Hope this helps!
Do any features exist in Socrata whereby my cloud-based app can receive a REST notification when new data is added to a (specific) dataset?
I could of course poll Socrata - via a REST request - to check this, but it would be much more efficient if there was a hook that I could, say, register a listener with to be notified when new data arrived in a dataset.
If this does not exist within Socrata, I could simulate this by creating a service that would poll Socrata and notify my app accordingly. Perhaps such a service exists?
Any suggestions are welcome.
Thanks
Colin Goldberg
What you're talking about sounds like a Webhook, and unfortunately its not something we support in our platform (yet). It's on our roadmap, and I'd love to have it myself, but unfortunately its not far enough along for me to have an availability date I can give you.
I have used omnipay before in a laravel project to process payments but i want be able to manage paypal subscriptions. can omnipay do this? If not can someone point me in the right direction.
thanks a lot!
Yes. It is not documented very well but the omnipay rest gateway exposes the subscription methods (even when it's own documentation says it doesn't).
Omnipay does not support it in a standard structure (see this thread) but it is encouraging people to implement them within gateways in the hope of being able to see the common structure and standardise it eventually.
If you look carefully you will find a few drivers support subscriptions (braintree, paypal and stripe all spring to mind) but they are all custom.
No. As per the readme.
Omnipay does not cover recurring payments or billing agreements, and so those features are not included in this package. Extensions to this gateway are always welcome.
A collegue recently asked what is the point of the nonce on WP JSON API
https://wordpress.org/plugins/json-api/
Since you can generate one without authentication, why bother with the extra step of having them at all?
I didn't know, and assumed maybe the authentication could be tightened later, but thought I would ask here in case someone knew.
Thanks in advance