[RouterGeocoder] The Key Comercial Players

[Dave McIlhagga]

Dave - I think you are absolutely on the right track ... the issue is  
finding the people with the energy to solicit the interest.

As for the interest in commercialization -- I can speak for DM in  
saying that our interest in the liberal licensing is for our  
flexibility, and our customers / partners flexibility. So if we're  
involved -- the license change will have had a lot to do with it.

In the meantime -- the more the merrier.

Dave

www.dmsolutions.ca


On 4-Dec-08, at 8:38 AM, Sampson, David wrote:

> Hey Folks,
> After reading Toru's e-mail (a while back),
> "Re: [RouterGeocoder] Re: [Pagc-devel] Comments re.  
> Requirementsoutlined on OSGeo"
> this solidified my thought that there might be some other key  
> players out there. Perhaps we should start gathering a list of  
> current, potential and future stakeholders… Then invite into the  
> discussion
>
> Keeping with the theory that open source approaches work best for  
> non-differentiating products one area to find some key partners are  
> web based services that already use geocoding. Maybe some web  
> services that are employing their own model for geocoding might be  
> valuable such as:
>
> * http://www.postlbs.org/en/project (not accessible last time I  
> tried it)
> * http://geocoder.ca/
> * http://www.batchgeocode.com/
> Some of these use pre-existing web based API's like Google and  
> yahoo.  And some are one offs.
> Would it be valuable to check out the interest level of this project  
> with commercial stakeholders
> * Google
> * Yahoo
> * Mapquest
> etc etc...
> I am thinking especially with Google, there may be components or  
> logic they would want to open source or parts that already exist in  
> projects like PAGC that they would like to include.
>
> These stakeholders may help to hash out the requirements. After all  
> with the PAGC having moved to modify its licence for commercial  
> stakeholders it would only make sense to actually invite the people  
> that could develop and use the product based on the lic we modified  
> to. Unless that was all hot air...
>
> If these people are already on the list (silently) then feel free to  
> intro yourselves.
> Just some thoughts.
> Cheers
> > -----Original Message-----
> > From: routergeocoder-bounces at lists.osgeo.org
> > [mailto:routergeocoder-bounces at lists.osgeo.org] On Behalf Of
> > (Orkney)Toru Mori
> > Sent: Thursday, November 27, 2008 23:20
> > To: routergeocoder at lists.osgeo.org
> > Cc: pagc-devel at lists.sourceforge.net
> > Subject: Re: [RouterGeocoder] Re: [Pagc-devel] Comments re.
> > Requirementsoutlined on OSGeo
> >
> > Dan,
> >
> > Thank you very much for referring Japanese postal address system.
> > As project owner of Japanese geocoder (geocoder.ja is part of  
> PostLBS
> > http://www.postlbs.org/ ), I want to make my comments on your post.
> >
> > Yes, you are partially right. The reality gets much complicated. We
> > have 3 types of address systems and we use 3 types (at least) of
> > Characters sets in writing postal address. We do not use street
> > network in geocoding at all.
> > They are totally separated.
> >
> > There are proprietary/opensource geocoding software and web services
> > in Japan. They consist of two processes, text normalization and
> > matching with address point data (over 30 millions points). Since
> > inputted address text may use different characters set and/or way of
> > abbreviation, all the address data will be normalized first. This
> > process plays say over 60% of total process. Then matching process
> > starts. This can be even done by usual database software.
> >
> > My purpose in this post to everybody is not to describe how Japanese
> > address system is complicated, but want to tell everybody lives in
> > "non- Asian entity" that even a smart software cannot always handle
> > geocoding and routing at a time. We should not forget that almost  
> 60%
> > of world population is in Asia.
> >
> > Mori
> >
> >
> > > > Once you move to Asian countries, things get complicated. We  
> know
> > > > that in Japan house numbers along a street are assigned
> > > > chronologically rather than spatially, as a result the standard
> > > > algorithms for locating an address along a blockface
> > breakdown. What
> > > > is in PAGC (starting with
> > > > v0.1.4) that could be the basis for a geocoder in Japan
> > (and perhaps
> > > > other Asian countries) is the parcel geocoder that is now part  
> of
> > > > PAGC.
> > > > However, whether this would work as a solution is largely
> > > > speculation on my part, and could well be wrong.
> > _______________________________________________
> > Routergeocoder mailing list
> > Routergeocoder at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/routergeocoder
> >
>
> _______________________________________________
> Routergeocoder mailing list
> Routergeocoder at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/routergeocoder

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/routergeocoder/attachments/20081204/f899097b/attachment.html