<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Stuart,<br>
<br>
thanks for the insights, and we also appreciate contributions :) !<br>
<br>
Kind Regards,<br>
Peter<br>
<br>
On 02.05.2015 23:20, Stuart Adam wrote:<br>
</div>
<blockquote cite="mid:DUB119-W19DED605282046A2A7C680BAD40@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Hello All<br>
<br>
One approach might be using the gdal ogr2ogr tools to convert
the shapefile to a gml file. The readers I have been creating
in engaric/graphhoper for Ordnance Survey formats are basically
readers for gml 2.X and 3.X files so with minor modification
might handle custom shapefiles converted to gml. I am starting
to consider how to start prepping pull requests for some of the
work done but I am relatively new to git/github and suspect it
may be a case of you wouldn't start from here.<br>
<br>
Sincerely<br>
Stuart Adam<br>
<br>
<br>
<div>> Date: Tue, 21 Apr 2015 08:57:26 +0200<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:graphhopper@gmx.de">graphhopper@gmx.de</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:graphhopper@openstreetmap.org">graphhopper@openstreetmap.org</a><br>
> Subject: Re: [GraphHopper] Any ideas to convert shape
file to routable osm data?<br>
> <br>
> Hi there,<br>
> <br>
> we are interested in this as well for a custom shapefile
import. If<br>
> someone is willing to put this under an open source we
would love to<br>
> support this and integrate it etc :) !<br>
> <br>
> Kind Regards,<br>
> Peter<br>
> <br>
> On 21.04.2015 08:26, Sander van Tulden wrote:<br>
> > Hi,<br>
> ><br>
> > We have a similar use case, where we use our
shapefile network within <br>
> > Graphhopper. The way we solve this is by first
converting the shapefile <br>
> > network with JOSM and plugin "OpenData" to .osm
(xml). We then use <br>
> > Graphhopper with minimum settings (using chWeighting
= no and <br>
> > prepare.minNetworkSize=1) to parse the shapefile by
using a custom <br>
> > Graphhopper encoder class that uses the tags that
the shapefile segments <br>
> > contain. In our case we had no initial tags, so in
JOSM we just selected <br>
> > the whole network and gave it a custom tag to be
used in the Graphhopper <br>
> > encoder class. If you don't yet know how to make a
custom encoder, you <br>
> > could use the Bike/Foot one and just add your custom
tag for testing <br>
> > purposes. <br>
> ><br>
> > In our case this works pretty well. We don't have
very frequent changes to <br>
> > the network, so we just prepare the set again when
we need to change it. <br>
> > <br>
> > Good luck,<br>
> ><br>
> > <br>
> > Sander van Tulden<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Op 20-04-15 19:28 schreef Bulut Aras
<a class="moz-txt-link-rfc2396E" href="mailto:bulutaras@gmail.com"><bulutaras@gmail.com></a>:<br>
> ><br>
> >> Hi,<br>
> >> We have our own road data. We use Esri products
and want to abandon<br>
> >> network analyst tool. How can we export our data
(from un-routable<br>
> >> shapefile for example) to use with graphhopper,
manually or<br>
> >> programmatically? Out data changes frequently.<br>
> >><br>
> >> May networkx library work for us?<br>
> >><br>
> >><br>
> >> Thanks in advance.<br>
> >><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>