Hi Nick, all the points you 'add' will add no further information when I correctly understand.
You can avoid the minor reduction at the following two places: 1. while import: set this in the config osmreader.wayPointMaxDistance=0 or use hopper.setWayPointMaxDistance(0) to disable simplification while import 2. while querying: set the request hint simplifyRequest=false Regards, Peter. On 08.11.2014 05:13, Nick Bauer wrote: > Peter, > Thanks for the reply. Can you point reference material regarding the > index? > > I want to increase the density to satisfy another SDK's requirements. > I believe its a work around to get the other SDK to do what we want it > to do :) > We will implement our own density improvement since it does not appear > to be very configurable via graphhopper and OSM. > > Regards, > Nick > > On Fri, Nov 7, 2014 at 3:00 AM, Peter <[email protected] > <mailto:[email protected]>> wrote: > > Hi Nick, > > the index resolution has nothing to do with the GPX resolution. > Why would you want to increase the density? What problem you have? > There are options to slightly increase this but you cannot get > more than "OpenStreetMap" density. > > Regards, > Peter. > > On 07.11.2014 05:10, Nick Bauer wrote: >> Hi- >> >> I tried to adjust the resolution or density of the GPX points >> that can be exported from a route. Using v0.3. I modified >> config.properites to change index.highResolution=500 to 50, >> restarted graphhopper, but no change in GPX output. In the >> comments of the config file, it mentions that 500 is the lowest >> (resolution in meters). Can this be updated / improved to allow >> fine-grained resolutions / higher densities? >>
_______________________________________________ GraphHopper mailing list [email protected] https://lists.openstreetmap.org/listinfo/graphhopper
