[Geocoding] Help : How to import our own data into nominatim instead osm data sets

[Sarah Hoffmann]

Hi,
	
On Fri, May 22, 2015 at 01:11:32PM +0530, Neel Manoj wrote:
> Thanks for the response.
> 
> We have source data in mid/mif and shape format. Can we convert into
> OpenStreetMap data and import it into Nominatim ?

That would be an option, yes. There are a few shape file to osm converters
out there. You'll find some of the tags that are relevant for address
computation for Nominatim here:
http://wiki.openstreetmap.org/wiki/Nominatim/Development_overview#Tags_processed

The main issue are probably administrative boundaries. Nominatim
expects that the data contains admin boundaries as polygons somewhere.
These are the bases to compute the address of each object. So
you have to add those, too, from your source. You could also just add your
data to that of OSM but you should be aware that the way Nominatim mangles
the input data, the result would be then subject to ODbL.

Cheers

Sarah

> 
> Kindly suggest.
> 
> Regards
> Neel
> 
> On Tue, May 19, 2015 at 1:36 AM, Sarah Hoffmann <lonvia at denofr.de> wrote:
> 
> > Hi Neel,
> >
> > On Mon, May 18, 2015 at 03:35:03PM +0530, Neel Manoj wrote:
> > > I have set up the nominatim server in our local network cluster on cloud
> > > and working fine osm data sets. Now we want to replace the dataset that
> > we
> > > have.
> > >
> > > Need help how to import our own data in Nominatim and what all layers
> > data
> > > needed in Nominatim custom data creation.
> >
> > Nominatim is specifically made for importing and processing OpenStreetMap
> > data.
> > It is not designed to be used with other sources. There are other
> > opensource
> > geocoders which are better suited for use with data from multiple sources.
> > Have a look at pelias[1] for example.
> >
> > Regards
> >
> > Sarah
> >
> > [1] https://mapzen.com/blog/pelias-setup-tutorial
> >