We are looking for an offline routing and reverse geocoding service.
GraphHopper advertises that its Directions API can be self-hosted:
GraphHopper Directions API Self-Hosting / On-Premises
The Directions API comes as a cloud service where you pay on-demand. The API is also
available as on-premises solution (self-hosted), which gives you
maximum performance, customization possibilities, independence; all in
your hands!
After installing GraphHopper on my local instance as per these instructions, I am able to perform routing queries successfully through the localhost HTTP API.
How do I get reverse geocoding working? I cannot find any documentation on this and the code on GitHub doesn't seem to hint towards anything.
The GraphHopper Directions API is a different product than the open source GraphHopper routing engine. The GraphHopper Directions API currently consists of
the Routing API (based on the GraphHopper routing engine),
the Matrix API,
the Geocoding API and
the Route Optimization API.
Currently they are no longer available for self-hosting. Note: I'm one of the authors.
GraphHopper is a routing service, not a geocoder.
According to this issue the Geocoder is separate from GraphHopper and only available in the Directions API for business.
If you are looking for a free OSM-based geocoding service then take a look at search engines in the OSM wiki.
I don't think the geocoding comes with the current version. Only the route api seems to be available.
Related
Leaflet Routing Machine provides an easy way to integrate directions capabilities in Leaflet. Out of the box it used to work with MapBox but it is a while since it has been updated and I find thaat it does not quite work anymore. In any case I want to use Leaflet + LRM with my chosen provider - HERE maps. The HERE Maps directions URL bears the form
https://route.ls.hereapi.com/routing/7.2/calculateroute.json?apiKey=<API_KEY>&waypoint0=geo!lat0,lng0
9&waypoint1=geo!lat1,lng1&mode=fastest;car;traffic:disabled
How can I modify Leaflet Routing machine to access and then use the results provided by the Here Directions API?
There is a plugin for here's routing API: https://github.com/Daredzik/lrm-Here
Haven't used it myself, but looks good.
I am working on Bing Maps V8. Now i already have V6 implemented. i need to upgrade to v8.
Currently the Rest Service URL being used for version v6 is :
http://dev.virtualearth.net/REST/v1/Locations/query?key=BingMapsKey
I wanted to know for Bing Maps Version V8 is there any change/Different Rest Service URL or can i use the same ?
Any suggestions would be helpful.
Thanks in Advance
Regards,
Shyam
The Bing Maps REST service are their own API and independent of the web control versions. There is no change to the REST services. Note that Bing Maps V8 has two built in modules which you might consider using instead of the REST services;
Search Module - a JavaScript library that wraps the REST location
API.
https://www.bing.com/api/maps/sdkrelease/mapcontrol/isdk#searchByAddress+JS
https://msdn.microsoft.com/en-US/library/mt712846.aspx
Autosuggest
module - provides suggestions as you type.
https://www.bing.com/api/maps/sdkrelease/mapcontrol/isdk#autoSuggestUi+JS
https://msdn.microsoft.com/en-us/library/mt712650.aspx
https://cloud.google.com/ml-engine/docs/tutorials/python-guide says ml-engine library in present in Google Client API library. Since Google Cloud client library is tailor-made for cloud applications, it should have had it no?
The difference is that the client library is essentially autogenerated from REST API while the Google Cloud one is handwritten to follow idiomatic usage for each language. So, usually the client API has wider language coverage and is immediately available. The Cloud API for specific languages are created if there is sufficient need.
So, I guess what I am saying is that you should provide feedback to the cloudml team on which language you'd like Google Cloud API for ml-engine.
I have spent days looking for proper comprehensive documentation for the JavaScript client library for the Google Analytics API. The only bits I could find was this page: https://developers.google.com/analytics/devguides/reporting/core/v4/rest/ which has all of ~20 completely uninformative words on the page, and https://developers.google.com/analytics/devguides/reporting/core/v4/quickstart/web-js, which does have some actual JavaScript, but nothing like documentation. It just illustrates two or three functions using the client API.
Is there nowhere that they actually list the full API? How are we supposed to know what functionality is available?!
Then there are the pages in this section: https://developers.google.com/analytics/devguides/reporting/core/v4/basics#request_body which list a lot of query samples, but don't explain how to use any of this in a client library. Is there any practical information on how to get started with accessing the Analytics API anywhere?
Thanks
The Analytics API is language agnostic, the google js client library docs apply to all of Google's APIs. Every client libarary is built around the discovery service API which describes the entirety of whats is available.
V3 API discovery call
Analytics Reporting Discovery call
How to use a client library is centrally documented and applies to every Google API.
Analytics Specific
There are lots of languages and client libraries and the Analytics API team cannot support every language. Instead they make available comprehensive reference docs which describe what endpoints are available. Once you learn how to use a particular client library calling the individual API endpoints happen in the same why.
That being said every endpoint they have is documented in JS.
The Analytics Mangement API is well documented in JavaScript. the Open source Google deomos and tools is built with it.
The Analytics Reporting API Samples page has documentated examples in JavaScript. You even linked to a Quickstart guide which should help you understand how to use the client library.
Can you expound more on what you'd expect in terms of documentation?
Final tip
If you load the analytics client library
gapi.client.load('analytics', 'v3').then(...)
In the chrome console you can then just start playing with it dynamically:
gapi.client.analytics.managment.[hit tab]
will list all the management API methods available.
i have set up a graphhopper server, it work perfectly.
direction http api working well.
but geocode API not found anything.
i use a docker container : https://hub.docker.com/r/sogorkis/graphhopper/
initialized with an osm.pbf file.
that's sounds like it missing a config step...
could you help me?
Geocoding is supported by another external program (in the case of GraphHopper Maps it is the GraphHopper Geocoding API). GraphHopper only does routing, also the maps are not served from GraphHopper, just external services.