I'm currently using the isoline api to create a coverage area around Seattle,WA based on time traveled.
https://isoline.route.api.here.com/routing/7.2/calculateisoline.json?app_id=<APP_ID>&app_code=<APP_CODE>&mode=fastest;car;traffic:disabled&rangetype=time&start=geo!47.6062,-122.3221&range=32400
However, I've noticed a few sections of map in Washington state that are never covered, even when the time distance is set to the max of 9 hours.
All of these places are reachable by car/bike/walking and Ocean Shores takes me less than 3 hours to drive to - and with 9 hours of driving I could easily make it into California or Montana.
So is this a Here-API bug/limitation or is there something wrong with the way that I am making the call?
Thank you and any help and all help is always appreciated
Related
For any given route e.g. Brooklyn, NY to Seattle, WA, I need to calculate amount of miles we drove via each state.
I have tested multiple routing APIs and non of them return anything I could use in calculation. (I testes MapQuest, google and TomTom)
I spoke to HERE.com sales rep and he told me HERE-apis return that info but after running test calls it does not look to me that this is the case.
Does anyone know how to format query on HERE-api to get info I am looking for or any other way?
HERE Routing API does not support a feature to calculate to calculate the sum of amount miles grouping by State level. But probably you can do post process for the calculation the sum of amount miles based on road network in State level.
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.
UPDATE: This occurs only when using the simulator in Xcode. For this reason this question can be considered resolved. I'm not going to delete it though in case someone else experiences the same issue.
When I try to calculate routes for long distances (for example from Vancouver BC to New York NY I get an error back, error 5.
Error 5 is defined in the API as:
NMARoutingErrorInvalidOperation
There was an error due to another request already being processed.
This is however the same call that is made for other calculations without issue, this only happens for long distances.
Do you have any insight into what could be causing this? I have tried using both fastest and balanced for the routing type. I am using
router.calculateRoute(withStops: [startWaypoint, destinationWaypoint], routingMode: routingMode)
Going South I can calculate a route from Vancouver to Seattle (195Km) but not Aberdeen (250Km). Going East I can calculate to Skagit Provincial Park (150Km) but not to Manning Park (190 Km)
(iOS Premium License)
This occurs only when using the simulator in Xcode. For this reason this question can be considered resolved. I'm not going to delete it though in case someone else experiences the same issue.
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 would like to know if it is possible to get the total miles traveled (via road/interstate) in each state instead of the total miles only.
For example: From Chicago, IL to Atlanta, GA the total miles traveled in each state would be:
IL=16 miles
IN=284 miles
KY=137 miles
TN=152 miles
GA=128 miles
From what I understand this is not possible in google maps api but I wanted to see if it is possible using anything else, Bing, YAhoo, Mapquest ???
Thanks for any help...
You might be able to use the MapQuest Directions Service to come up with very basic/general distances for each state, but I'm not sure if the distances will be exact enough to fit your needs. Basically, the directions service returns driving directions in terms of "maneuvers" and you can make a request to the directions service that tells it to include crossing state boundaries in the maneuvers it returns. You may be able to parse the data that is returned to calculate the route distances between the "crossing into (state name)" maneuvers, but again, it might not be exact enough.
It might be worth a look. I've never done this before, but it's my first thought. The MapQuest Developer Network has forums, so it might be worth it to post the question there, too.
You can keep track of miles driven in each state (Example: Travel from home in New Mexico to (any city)Texas. These programs will do this for you, Trulos.com, IFTA Plus, truckingoffice.com, ifta-calculator.com Some are free others usually give a 30 day free trial. I use programs like this when I'm filing mileage/fuel reports for commercial drivers. These drivers always have to report how many miles they travel in "each" state. All you have to enter is the location of your starting point and your final destination. The program will then calculate your miles traveled for each state and also will give you the "total" miles traveled.