[OSM-dev] Submitting proposal for GSoC 2017
Hriday N Sanghvi
hriday_nilesh at srmuniv.edu.in
Sat Feb 18 05:26:32 UTC 2017
Thank you for guiding me through the first steps in developing an
implementation plan for the project titled “Improve Postcode Handling”.
I have gone through http://wiki.openstreetmap.org/wiki/Elements to better
understand the OSM data model. I now have a fair idea of what nodes, ways,
relations, tags are and how they are related to each other. I also went
through http://wiki.openstreetmap.org/wiki/Key:addr and
understand how postcodes are either mapped to an address or to an area
within a geo fence. I also built and ran a few addr:postcode and
boundary:postal_code queries using the Overpass Turbo Wizard (
https://overpass-turbo.eu/ )for examples of the data output on the map.
I went through https://en.wikipedia.org/wiki/Postal_code to get a general
idea about postcode systems. The characters used in postal codes are the
Arabic numerals "0" to "9", letters of the ISO basic Latin alphabet, spaces
and hyphens. India has a 6 character numeric postcode, but many countries
have alphanumeric postcodes with varying number of characters.
I have experience in installing Wordpress, WooCommerce and other Ecommerce
softwares on AWS. Hence, I plan to install Nominatim on AWS Server - free
tier (https://aws.amazon.com/free/ ). However, from what I’ve read, it
looks like 1 GB of RAM provided under free tier may not be sufficient. I
would appreciate if you could suggest alternative low cost/free servers. In
, I will also refer to the following installation guides:
, https://andrewwhitby.com/2014/12/18/nominatim-on-ec2/ ,
On Fri, Feb 17, 2017 at 2:23 AM, Sarah Hoffmann <lonvia at denofr.de> wrote:
> Hi Hriday,
> thank you for your interest in the OSM GSoC.
> There are a couple of things you can do to prepare for the postcode
> First of all you should familiarize yourself a bit with the OSM data
> model in general (nodes, ways, relations, tags) and then find out
> how postcode tagging works in particular. There are essetially two
> ways how postcodes are mapped: as part of an address for a particular
> house (see http://wiki.openstreetmap.org/wiki/Key:addr) or as an
> area (see http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dpostal_code).
> You can use Overpass (or Overpass Turbo) to find examples of the data.
> Nominatim actually uses complete OSM data dumps and processes them
> into a search database. So improving the search means improving the
> import process. So, next you should try and set up your own instance
> of Nominatim using the current development version from
> https://github.com/twain47/Nominatim (installation documentation
> can be found in the doc/ directory) and a data extract from
> http://download.geofabrik.de/. I recommend something from Europe
> as there is already a fair coverage with postcodes.
> Finally, it will also be helpful if you do a little bit of research
> about postcodes in general to find out what different systems are
> in use and where.
> Hope that helps to get you started.
> Kind regards
> On Thu, Feb 16, 2017 at 07:13:31PM +0530, Hriday N Sanghvi wrote:
> > Hello Lonvia,
> > I’m a student of Computer Science Engineering at SRM University, India (
> > http://www.srmuniv.ac.in/). I am interested in submitting my proposal
> > GSOC 2017 for either one of the Open Street Map projects 1. Improve
> > Postcode handling or 2. OpenAddresses for Nominatim.
> > I have extensive experience working with PHP and MySQL databases on
> > web based projects. I have undergone a PostgreSQL course on
> > https://www.lynda.com/PHP-5-tutorials/PostgreSQL-9-with-
> > and http://www.tutorialspoint.com/postgresql/ and I’m quite comfortable
> > working with Github. I have some experience with Google Maps API while
> > working on a location based Click-and-Collect grocery shopping app. I
> > to continue with coding for OSM even after the GSOC project and also plan
> > to base my six months project in the eighth and final semester of my
> > on OSM.
> > I understand that the list of accepted mentoring organizations will be
> > published on February 27 and potential student participants will discuss
> > application ideas with mentoring organizations from February 27 to March
> > and that student application period is open from March 20 to April 3,
> but I
> > wish to start early.
> > I have downloaded JOSM to edit my local area on the map, but I found ID
> > editor to be an easier option.
> > With regard to extraction of postcode data and exporting data to the
> > Nominatim database related to the project titled “Improve Postcode
> > Handling”, I have looked at API v 0.6 (
> > http://wiki.openstreetmap.org/wiki/API_v0.6 ), including the endpoints
> > capabilities (http://api06.dev.openstreetmap.org/api/capabilities ),
> > permissions (http://api06.dev.openstreetmap.org/api/0.6/permissions ),
> > change sets (http://api06.dev.openstreetmap.org/api/0.6/changesets ),
> > (http://api06.dev.openstreetmap.org/api/0.6/node/12345 ), and trace
> > metadata (http://api06.dev.openstreetmap.org/api/0.6/gpx/12345/details
> ) in
> > which I was asked for Authentication.
> > I also went through the Overpass API (
> > http://wiki.openstreetmap.org/wiki/Overpass_API ), Overpass Turbo
> remote (
> > http://overpass-turbo.eu/ ) and Overpass Turbo Query form (
> > http://www.overpass-api.de/query_form.html ).
> > Though I was able to download limited data using the “Download Map data
> > from OSM server” tool in JOSM, I am not sure about the endpoint and query
> > to get post codes using API v 0.6 or Overpass API. I would really
> > appreciate any help on this. <http://overpass-api.de/api/>
> > I’m confident of producing productive work during the GSOC period.
> Before I
> > start working on the proposal for GSOC 2017, I would appreciate any
> > guidance you could provide.
> > Thank you.
> > Regards,
> > Hriday N Sanghvi
> > _______________________________________________
> > dev mailing list
> > dev at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev