Searching for a specific food type doesn't work anymore (e.g. https://browse.search.hereapi.com/v1/browse?apiKey=xxx&at=51.500415,7.458788&limit=100&categories=101-000). (101-000 -> american)
Does anyone know where the problem is?
Related
I am looking for some help with finding a list of categories recognized by Google Vision API either by Object Localizer API or by Product Search API.
I searched the issue and found an old post here https://groups.google.com/g/cloud-vision-discuss/c/Gpo2h-Rw7gA/m/uSHH-r8lAgAJ and linked StackOverflow questions.
However, after a thorough examination of Open Images V6 and Google Knowledge Graph, I still do not see a clear connection between Open Images category tree and Vision API Product Search.
Product Search API has 5 main productCategories: homegoods, apparel, toys, packedgoods, general. (link: https://cloud.google.com/vision/product-search/docs/product-categories)
However, Open Images does not have any of these categories https://storage.googleapis.com/openimages/2018_04/bbox_labels_600_hierarchy_visualizer/circle.html.
Can anyone help me with a list of detailed categories returned by a detector in Product Search and corresponding top-category (homegoods, apparel, toys, packedgoods, general)?
I would like what categories can be detected in each of the top-category, so for example: "Apparel": ["Pants", "Skirt", "Shoes", ...].
Thanks in advance.
I am trying to use Geocoding and Search API v7, Where I can search using category that are mentioned in
https://developer.here.com/documentation/geocoding-search-api/dev_guide/topics-places/places-category-system-full.html
My question is, can we get the category list. At TomTom they provide the list as JSON file, can I get it from HERE in the same way.
You can use Place API to search the POIs based on category. The format is
https://places.sit.ls.hereapi.com/places/v1/categories/places?app_id=xx&app_code=xx&at=52.50449,13.39091&pretty
For more details refer : https://developer.here.com/documentation/places/dev_guide/topics_api/resource-place-categories.html
I am working on a project that involves integrating the PUBG API. From my site, the player can lookup stats using their player name, platform and season. One issue I am facing is that the player name have to be exact and is case sensitive. Now I assumed it to be the case at the beginning. However, after searching for the name in this site I found that they don't need the name to be case sensitive. Also, referring to this post from the PUBG Dev community here I saw that it confirmed my initial assumption. So my question is if PUBG API requires the names to be case sensitive then, how is the site (linked) can search for the player even if the name provided is not in exact, matching case? For example,:
I looked up the player name MyCholula. From the PUBG API page for player lookup, it returns the proper value. When I tried mycholula, it doesn't and sends a 404. From the linked site above, both combination seems to work. Now if spaces or other separators were involved in the name then, it would be easy to convert it assuming that separated words are all capitalized (somewhat naive assumption though). For this name, I don't see any way of converting mycholula to MyCholula. I also tried many other combination in the linked site above (also different user names I got from my friends) to confirm that the linked site is actually returning the data as expected for any combination of user names. I also tried it on other sites like this and it didn't work just like it doesn't work from the PUBG DEV API page or from my page.
I am really confused as to how they are doing it. The only possible explanation I can come up with is that they have the player records stored in their database from where, they can perform advanced regexp based search to get the actual name. However, this sounds far fetched since, there are millions of players and it would require them to know all the player names and associated IDs. Also, as far as I know, it is not possible to use regex or other string manipulation to convert to the actual name because there can be many combinations (not an expert on regex so can't be definitive on this).
Any help or suggestions will be greatly appreciated. Thanks.
I am trying to figure out the right parameters for ItemSearch such that the API call will return the same result as on the website. Currently I am using these params it is not consistent with the website.
url_params = dict(
Service='AWSECommerceService',
Operation='ItemSearch',
AssociateTag=AMAZON_ASSOCIATETAG,
SearchIndex='All',
AWSAccessKeyId=AWS_ACCESS_KEY_ID,
Keywords=keywords,
ResponseGroup='Small,OfferSummary,Images'
)
For example if 'iphone%205s' is put in keywords, the API returns a list of iPhone protectors, while searching on the website gives iPhones as top results.
I am also trying to figure out why this is for book searches. One possible answer I found online was that the websites search feature might use more elaborate queries than just one simple API call. For example, it may take into account other factors into the search (not sure what that might be but it may).
I tried looking for an example of getting around this but had no luck. Hopefully someone can point me in the right direction!
I have a Verity Collection. The description field of a record has a title, such as "Flowers & Candy Scented Candle"
When I type "Flowers & Candy" into a search, it returns no results.
If I type in just the word Flowers or Candy alone, it will find a result.
I am re-factoring some old code that did this through a fun and interesting sql query without use of the Verity Search engine.
Is there a quick way to get around this issue or get the Verity search to behave?
I considered enclosing the terms automatically in a quote but that might limit results.
cflib.org is your friend.
http://www.cflib.org/udf/verityClean