OpenGeocoder 2009 SOC Ideas - Revision history

Wiki-Woodbri: /* PAGC Landmark Gecoder */

2009-03-26T18:38:16Z

PAGC Landmark Gecoder

Wiki-Woodbri: /* PAGC Code Refactoring */

2009-03-26T18:35:30Z

PAGC Code Refactoring

Wiki-Woodbri: New page: * Back to the main OSGeo Google Summer of Code 2009 wiki page. * Back to the main OSGeo Google Summer of Code 2009 Ideas wiki page. = OpenGeocoder 2009 SoC Ideas = Enter ideas f...

2009-03-26T04:33:43Z

New page: * Back to the main OSGeo Google Summer of Code 2009 wiki page. * Back to the main OSGeo Google Summer of Code 2009 Ideas wiki page. = OpenGeocoder 2009 SoC Ideas = Enter ideas f...

New page

* Back to the main OSGeo [[Google Summer of Code 2009]] wiki page.
* Back to the main OSGeo [[Google Summer of Code 2009 Ideas]] wiki page.

= OpenGeocoder 2009 SoC Ideas =

Enter ideas for development projects here. Note these are just suggestions - students are welcome to propose projects based on their own interests that relate to OpenGeocoder. Our current efforts are based on the PAGC code. This is a C language geocoder You can read more about it at:

[http://www.pagcgeo.org/ PAGC Home] that has links to download the code and to sign up for the email list.

== PAGC Code Refactoring ==

We currently have a project proposal rework the existing code to make it support SQL database(s) and to restructure it to be more modular. '''Need to link PDF proposal here.'''

== PAGC Landmark Gecoder ==

This is a project proposal that would standardize non-address type landmarks and handle geocoder requests for them. '''Need to link PDF proposal here.'''

== PAGC Build Address parsing and standardization tools for countries ==

We currently have an address standardizer that is partially data driven, based on a Lexicon and a Gazetteer for a given reference data set. We currently have support for US Tiger data and Canada Road Network File records. We will be building similar ones for Navteq North America data. It would be interesting to integrate something like OSM (OpenStreetMap) data or other country data sets as a reference data set for any given country and have Lexicons and Gazetteers to match.

== PAGC OpenLS compatible API ==

PAGC currently has web API that allows it to handle web requests and return XML documents. [http://www.opengeospatial.org/standards/ols OpenLS] is an OGC standard for Open Location Services. OpenLS has many features described as [http://www.opengeospatial.org/standards/ols OpenLS] but we would be interested in support those appropriate to PAGC.

= Mentor Candidates =

The following individuals are potentially willing to serve as OpenGeocoder/PAGC mentors or co-mentors.

* Stephen Woodbridge

[[Category:Google Summer of Code]]

@@ Line 17: / Line 17: @@
 == PAGC Landmark Gecoder ==
-This is a project proposal that would standardize non-address type landmarks and handle geocoder requests for them. '''Need to link PDF proposal here.'''
+This is a project proposal that would standardize non-address type landmarks and handle geocoder requests for them. [http://www.deadwrite.com/landmarks.pdf Project Proposal] (PDF).
 == PAGC Build Address parsing and standardization tools for countries ==

@@ Line 13: / Line 13: @@
 == PAGC Code Refactoring ==
-We currently have a project proposal rework the existing code to make it support SQL database(s) and to restructure it to be more modular. '''Need to link PDF proposal here.'''
+We currently have a project proposal rework the existing code to make it support SQL database(s) and to restructure it to be more modular. [http://www.deadwrite.com/pagc_restructure.pdf Project Proposal] (PDF).
 == PAGC Landmark Gecoder ==