one of my client they using here map and api, for the bellow lat lon they get this
23.759769,90.411991
South 75m,Ideal Trade Centre,Madhubag, Dhaka Bangladesh
but when i am using
https://places.demo.api.here.com/places/v1/discover/around?at=23.7598%2C90.412&show_content=&Geolocation=geo%3A23.7598%2C90.412&X-Mobility-Mode=drive&Accept-Language=en-GB&app_id=5B88sPuZ1iyF3RjMLnqK&app_code=jcz5u1RQZ4HiY7FJLD0bvA
this give me
{ Siddik School } 21
{ Mamataz Bakery } 39
{ Ahad Bakery House } 45
etc
I need a help to understand how they getting bellow result from here API for that lat/lon
75m,Ideal Trade Centre,Madhubag, Dhaka Bangladesh
if some one can hellp me to understand what i am missing i would be really greatfull
It could be that your client is using the Reverse Geocode API, while you're trying to look for places at that same location, using the Places API. Note that the Reverse Geocode has more modes available than retrieveAddresses.
However, there are several ways your client could get to such result. For example, /discover/around filtered on business-services category returns Ideal Trade Centre among other places: example
Your best bet is to ask your client how exactly they are using the API.
Related
I would like to analyse the locations of electric vehicle charging stations for Germany, Italy and France. Those three countries, because they differ quite a lot in regard to their respective incentive programmes for public charging station infrastructure.
What I have so far are .csv exports from both OpenChargeMap and OpenStreetMap containing the location data (latitude and longitude) of all charging stations in those three countries along with a few other information that I can process in R.
What I would like to do now is some sort of reverse geocoding on those latitude and longitude coordinates to retrieve additional information on the surroundings. Especially, whether the respective charging station is located in a residential area in a city for example or at a rest stop on the highway. By knowing at what kind of locations the charging stations are placed in those three countries I am hoping to be able to draw conclusions regarding the incentive programmes. I'm not looking for specific addresses in this case, but rather an API or another way to process thousands of coordinates and retrieve information regarding for example population density or any other piece of data from which I could derive conclusions.
I have tried to get OpenStreetMap exports to work, but unfortunately I cannot seem to be able to query for the 'landuse' attribute through the Overpass Turbo API. This is my basic query that I'm using in this specific API, but as soon as I query for ["landuse" = "residential"] instead of ["landuse" = ""] I get prompted empty fields as result.
I found an API from Google which would offer lookup for various address components/types. Unfortunately, registering an API key at Google is not quite realistic for the scope of my work. Does somebody know of a (preferably FOSS) API that is able to do something like this? Or even how to make a 'landuse' query work in the Overpass Turbo API linked above?
Thank you in advance for your time.
Your Overpass API query is looking for elements that are tagged as amenity=charging_station and landuse. This is rather uncommon since charging stations and landuse are mapped as distinct objects. Instead you need to look around charging stations for landuse elements.
So instead of
area["ISO3166-1"="DE"]->.a;
nwr(area.a)["amenity"="charging_station"]["landuse"=""];
you will need a query like
area["ISO3166-1"="DE"]->.a;
nwr(area.a)["amenity"="charging_station"];
way(around:200)["landuse"];
This searches for ways with a landuse tag located within 200 meters of charging stations.
Note that this is a rather heavy query. You should probably use your own Overpass API server for it.
For routes that start and end in the US, HERE fails to suggest a route that goes through Canada even when I choose 'mode=fastest', and via Canada would clearly be the fastest route (traffic disabled).
e.g. Detroit to Buffalo
HERE We Go
HERE Routing API gives the same as HERE We Go. I use traffic disabled, hence a route through Canada is definitely the fastest: https://route.api.here.com/routing/7.2/calculateroute.json?waypoint0=42.33239,-83.04887&waypoint1=42.95594,-78.90584&mode=fastest;car;traffic:disabled&app_id=______&app_code=____
These places are just inside the US border. If I edit one co-ordinate to fall just inside the Canadian border, a route through Canada is recommended.
I can't find any restrictions that seem to be applied that would prevent routes going through Canada. I've tried examples in other countries which seem to be fine (e.g. a route starting and ending in Sweden was chosen to pass through Norway). What is going on here?
Can you please use fleet telematics with advance mapping options. Also if waypoint doesn't work, you can pass link ID or street to get the accurate result. please refer below documentation for more reference.
https://developer.here.com/documentation/fleet-telematics/api-reference.html
Also report the map team if the route is still incorrect using feedback API :
developer.here.com/documentation/map-feedback/dev_guide/topics/quick-start-submit-feedback.html
Im trying our different flight api's from sabre, I understand from reading the data Im getting back is limited in development but Im not sure if it really can be THAT limited or its me doing something wrong.
1: InstaFlights Search
First I use the citypairs lookup to show city pairs, then use them for the instasearch,
The problem is unlike I use NY or London (there were 2 other cities working fine), for almost ALL other cities, Im getting no response.
I know data is limited but since the citypairs api already returns VERY limited data, but is it really THAT limited? Feeling like I must be doing something wrong because I cannot image, that api to work (in dev) only for 3 cities on 3 different dates :-/
destination api
here I use first the supported cities api, then use results to use the multi airports api, then use that for destination api.
Again, same here, only 2/3 cities actually work. Since in the destination api, UNLIKE the instaflights api, the changes of 'matches' are higher as any destination could be shown for the picked origin. HERE AGAIN almost no results, BUT for about 3 cities.
If anyone who has some experience with sabre, could help out it would be great- just trying to figure out if its me whos using it wrong or no. Thanks!
Can you please provide the city pairs that seem to be failing for you? I just did a test of both APIs (InstaFlights and DestinationFinder) and was able to obtain results with the city pairs provided there. I changed the point of sale to FR and obtained PAR-ATH, and that worked. Also worked with ABE-MCO which is the first city pair I obtain when using POS US.
The testing environment for this API but you should be not limited to just three cities.
I am building an app for a federal government client using the Bargain Finder Max SOAP API. They need to adhere to the Fly America Act: any flight that leaves the US or arrives in the US must use a US flagged carrier.
I have tried to use the IncludeVendorPref and included all US carriers; however, on flights such as ALGIERS (ALG) to New York (JFK) I cannot find a solution because the route may go from ALG to London via British Airways and then London to JFK via American. Because not all flights are American (because of the IncludeVendorPref filter I have on), it does not find this solution even though it is valid because you are taking an American carrier back from a foreign country (it is okay that you are going from a foreign country to another foreign country - i.e. Algeria to London on a foreign carrier).
Does anyone have any advice on how to handle this? Is there an easy way to adhere to the Fly America Act?
There is no specific request that will meet what you want, at least as far as I know.
There are 2 ways in which I can think you can accomplish this:
1. By requesting 200 flights, in order to have more diversity, including the IncludeVendorPref qualifier for all US carriers with PreferredLevel="Preferred". The bad part is that you would have to end up doing the filtering on your side. I think this would be the best way, as it would give you the most heterogeneity without loosing too many itineraries.
2. By calling the service twice, once for the US connection and once for the trip outside. This has several disadvantages, for example it would make it really difficult to create itineraries based on the 2 responses, and it would require to create separate tickets, as those would be 2 separate itineraries.
If neither option suits your needs, I recommend you to contact the help desk to see if there would be another option that I didn't consider.
I am trying to get a list of nearby airports, given a certain location.
You can do this through the google places api and using types=airport.
The problem is that Google Places is self-policing so any tom, dick and harry can call themselves an airport.
Is there any way to determine whether an airport is real - through google maps?
I know I could double check against an airports database but then I'd be best just using an external database and only use google maps to plot their locations!!
thanks
Geonames will give you airports eg. a search centred on Central Park New York with a radius of 25 kms.
http://api.geonames.org/findNearby?lat=40.776902&lng=-73.968887&fcode=AIRP&radius=25&maxRows=100&username=xxxxx`.
You will need to open a (free) Geonames account to make it work.
Such a search would be in your "external database" category but as far as I know, the entries are not self-certified, so are possibly more reliable than Google's from what you say.
To verify Google results against Geonames results would need to develop and code your own comparison algorithm.