[GraphHopper] Distances are 2x wrong?

[Peter K]

Hi Jaak,

thanks for your detailed response!
I was in the hope that nutiteq somehow provides/sells the height
information (beyond OSM).

Regards,
Peter.

> Hi,
>
> Regarding 3D buildings you can easily have "shoebox" 3D models, which
> are actually 2D polygons with height. See code sample from
>  https://github.com/nutiteq/hellomap3d/wiki/Online-OSM-3D-buildings .
> Height value is taken from OSM tags (height and floors), and if it is
> missing (well, this means about 99.9% cases) just a fixed average value.
>
>  Having real buildings with textures is more complex task. There is
> another wiki page with code
> instructions: https://github.com/nutiteq/hellomap3d/wiki/Nml-3d-models-map-layer .
> I added now also a sample of it as Offline3DActivity to the
> HelloMap/AdvancedMap samples, and a link to wiki to download set of
> Barcelona buildings which are taken from the 
>
> Anyway, there are the steps needed:
>
> 1) get the data. We don't have our own 3D city datasets (yet), you
> should be able to license it from TomTom or Navteq, or from other
> providers. If you can suggest one for us, please do. Or you can use
> free 3D models from Google Trimble 3D Warehouse. My understanding is
> that you are actually free to use these models in your apps, but I
> don't have official confirmation from Google or Trimble about it. You
> can always create your own dataset.
>
> 2) convert it to a suitable format for Nutiteq SDK. We have a tool
> which reads KMZ/collada files and creates nmldb file which is heavily
> mobile-optimized special 3D format. This data can be used as offline
> package (nmldb file), or put to a server and be used as online
> service. This converter is licensed separately as add-on. We do test
> conversions with your data for free. 
>
> 3) Add a 3d model layer to your map, see the wiki page above
>
> Jaak
>
> On 07.04.2013, at 16:16, Peter K wrote:
>
>> Hi Jaak,
>>
>> I tried the example and it worked out of the box - very nice :) ! (to
>> enable 3D view I had to change setTilt(45))
>>
>> How can I enable seeing buildings like in your screenshot:
>> https://dl.dropboxusercontent.com/u/3573333/mapxt_3d_tallinn_device-2012-07-25-124845.png
>>
>> or is this only possible with your custom file storage?
>>
>> Regards,
>> Peter.
>>
>>> Hi,
>>>  regarding 1) . Maybe I used somehow older version of lib. Now I
>>> tried with Maven dependencies and it seems to get correct results,
>>> like
>>> in https://dl.dropbox.com/u/3573333/public_web/graphhopper_sample1.png
>>>
>>>  ps. I uploaded the graphhopper-1.0-SNAPSHOT to my Maven repo
>>> (https://repository-nutiteq.forge.cloudbees.com/release/), is there
>>> better place to fetch it from?
>>>
>>> Jaak
>>>
>>> On 04.04.2013, at 19:06, Peter K wrote:
>>>
>>>> Hi Jaak,
>>>>
>>>> cool, this is really great news! As I already wanted to look into
>>>> this, but hadn't the time so far.
>>>>
>>>> Regarding 1) The returned value is as expected (normal) meters.
>>>> Hopefully I can digg into the code next week.
>>>>
>>>> Regarding 2) ghz is a zipped folder and can be opened via the
>>>> Helper.unzip
>>>>
>>>> > mapsforge library
>>>>
>>>> Oh, so the mapsforge data can be opened? Nice!
>>>>
>>>> Regarding 3) This will be solved in issue-17. It is the problem of
>>>> mapping from "real world gps coordinates" to graph node ids.
>>>> You can partially work around this by increasing the precision of
>>>> Location2IDQuadtree index
>>>> or checkout the master (not really recommended yet, as incompatible
>>>> file layout and probably other minor issues)
>>>>
>>>> Regards,
>>>> Peter.
>>>>
>>>>
>>>>> Hello,
>>>>>
>>>>>  I just pushed a sample with Graphhopper routing to Nutiteq 3D SDK
>>>>> AdvancedMap3D samples: https://github.com/nutiteq/hellomap3d/,
>>>>> see GraphhopperRouteActivity.java . Nutiteq SDK is quite similar
>>>>> to Mapsforge, just with 2.5D perspective and rotation
>>>>> capabilities. And with a lot of different data source Layer
>>>>> implementations, from geotiff and shapefiles to mapsforge library.
>>>>>
>>>>>  Issues with grasshopper:
>>>>>
>>>>> 1) major problem - all the routes in my area (Estonia) are a bit
>>>>> more than 2x too short. Instead of 100 km I have 45 or so. Could
>>>>> it be that it is so much north and calculations of distances
>>>>> become wrong? If the "meter" is really "mercator meter" then the
>>>>> value could be even right, but calculation of mercator meters to
>>>>> real meters, when the route is from south to north, is not trivial
>>>>> (or not possible at all). I created test dataset for Baltics 3
>>>>> countries: https://dl.dropbox.com/u/3573333/baltics.ghz , where it
>>>>> is observable. 
>>>>>
>>>>> 2) some minor issues. I did not figure out how to open properly
>>>>> .ghz file with the API. So the sample asks now for .map file
>>>>> inside <map>_gh folder, so the files must be uncompressed in
>>>>> SDCARD. But it would be nicer to enable just to open ghz file, and
>>>>> GH would uncompress it automatically.
>>>>>
>>>>> 3) start and endpoints are sometimes not optimal, quite far from
>>>>> clicked location, and there seem to be much closer nodes to given
>>>>> points. I added lines from clicked location to first and from last
>>>>> location to make it nicer. Maybe some tolerance in graph
>>>>> generation, or in routing?
>>>>>
>>>>>
>>>>> Your pull requests with fixes to the demo app are very welcome,
>>>>> quite possibly I just did something wrong
>>>>>
>>>>> Jaak
>>>>> Nutiteq.com <http://Nutiteq.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20130408/f5719567/attachment.html>