Graphhopper geocode not initialized by osm.pbf - geocode

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.

Related

Extending Leaflet Routing Machine to work with Here Maps

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.

How to AutoComplete an Address and get Lat/Long of that address in #flutter?

How to AutoComplete an Address and get Lat/Long of that address in #flutter?
This is nothing you can do directly with flutter. You need to call an API for that service. In a recent project I used HERE Autocomplete and HERE Geocoder for such a service, which worked quite well.
In Flutter you just need to work with the responses of those APIs. In my case the FutureBuilder was the perfect solution (there is even an example in the docs which is a good starting point).
You have to make HTTP Networking Requests in Flutter to the Place Autocomplete service that is part of the Places API Web Service.

Bing Maps v8, Rest Service URL for V8

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

Self hosting GraphHopper Directions API

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.

MapQuest Driving Directions API

Could anyone explain me what is "leg" and "maneuver" in a route and how to show the route highlight with this new API? Earlier with MapQuest 5.x we used to do it with LinePrimitive Class in MQClientInterface.
What exactly are you trying to do? Are you using the JavaScript Maps API (for instance) to show the route on a map? If so, the JavaScript Maps API (and Flash Maps API) have convenience functions for showing a route on the map and they handle most of the heavy lifting for you, so you don't have to call the Directions API directly if you want to show the route on a map generated by the JavaScript Maps API or Flash Maps API.
A "leg" is essentially a stop along a route -- for instance if you want to route yourself from Lancaster, PA to Harrisburg, PA to York, PA -- Lancaster to Harrisburg is one leg, while Harrisburg to York is another.
A "maneuver" is almost like each turn you would have to make, so the turn-by-turn directions included with each leg.
Hope this helps!