[OSM-dev] Suggestion about how to setup a local osm development

Chien Nguyen Khac threesearch at yahoo.com
Wed Aug 8 03:57:50 BST 2007


Tom wrote:
<<<
Ah, so you're talking about using the data rather than working on
the site itself. In which case most of your steps are irrelevant as
there is no need to load all the data into a clone of the live
database just to work with it.

In fact it probably generally makes more sense to parse the planet
dump yourself and load it into some sort of database that is designed
for whatever task it is you want to do with it.
>>>

My intention to load the whole data to local database is to develop a routing
application that query osm database as a whole.


<<<
You know there is already an live CD image for OSM that you can
boot in VMWare I take it? You can find it at:

http://artem.dev.openstreetmap.org/files/osm-linux.iso
>>>

Thanks for you infomation, I will try the live CD. However live CD is read only, I can not update the osm database in that live CD. So I still prefer having dev server in VMWare image that give me total control of the server.

<<<
I think the real question here is, are you talking about developing
OSM itself, or just developing applications that happen to use our
data...
>>>

I am talking about both: developing OSM itself and using OSM

For developing OSM itself:
There is the routing library for postgis database some where on the internet, so I want to do the same for MySQL database.

This is a my long term plan and may need your help because it requires a lot of work and time.

If I can setup a local osm dev server, I will do the following things with osm database:

1. write SQL statements to drop segments table and convert segments data into nodes and ways tables.

I hope osm foundation will consider implementation of dropping segments tables soon.
If we delay it and some US developers start to import a huge Tiger data into osm database then we will have more trouble with nodes/segments/ways later on.

2. design table structure for routing tables (graph, nodes...). These routing tables will provide a graph network for routing application

3. write SQL statements to popular graph network tables with nodes and ways data from nodes and ways tables.

4. write SQL statements to build routing library for shotest path algorithms (other web interface can call these library to find the shortest path without the need of knowning graph network and A* algorithms)


For using OSM:
1. write SQL statements to clip and convert osm data to other map format directly (by pass planet.osm because planet.osm format is too huge).

For example: London city contains 410,566 nodes, 433,332 segments, 409,978 ways

If I use planet.osm format, London data file is 139MB.
If I use polish format, London data file is only 21MB.

Richard wrote:
<<<
I really suggest you start reading up on OSM before firing off mails 
like the ones you've sent to the list over the last few days. Believe 
it or not, we're not all idiots, and some of the decisions we've made 
over the last two years actually have reasons behind them.
>>>

Of course, I believe all of you are talent people. However, you should consider this point: 
Believe it or not, when talent people try to design or solve some thing they tend to think about complicated solution while in the real life the real soultion is actually very simple.

I read this article:
OSM and the public - what barriers need to be crossed? - Muki Haklay
http://www.slideshare.net/mukih/usability-engineering-for-osm-sotm-2007/

May be talent people forgot to put themselves in user's shoes? And now they start to realize this issue?


<<<
and some of the decisions we've made 
over the last two years actually have reasons behind them
>>>

Are you taking about keeping segments in current design (nodes/segemnts/ways)?

If you can provide a valid point to keep segments then I will agree on that.

If you can not provide any valid point to keep segments then why we still keep it?

If the decisions actually have reasons behind them, then why dont you share it again instead of be rude to me?

Attually, when I read your email, I want to unsubscribe from dev mailling list.

I dont know why I still spend my time to write and send such a long email to this list again. :-)

May be I just want to make osm project become more easy to use for both developers and users?


Robert wrote:
<<<
> Your VMWare solution would be _more_ difficult for some of us. Not 
> everyone is developing on an x86 machine.

So because something only helps 95% of users, we shouldn't do it?
>>>

Attually, WMWare can run on Mac, Windows and Linux. If you dont use x86 machine
you still can use osm WMWare image.

I copy the idea of having all osm components pre-install in one machine from here:
http://www.wmware.com/appliances/

You see, people install everthing: browser, weblogic server, mysql server...
and publish the image so that new developers can immediate use the image to start the development instead of spend time to learn how to setup the dev enviroment.

<<<
Why can't people on this list say something like:

People have talked about this, but no one has done it yet. If you are
familiar with VMWare, start with debian (as that's what the real server
runs) and follow the instructions here:
http://wiki.openstreetmap.org/index.php/The_Rails_Port

When you have an image, we can put it on an FTP server somewhere.
>>>

I am not familiar with ruby and rails. So I am not sure whether or not I can setup an osm dev server follow the instructions at:
http://wiki.openstreetmap.org/index.php/The_Rails_Port


Regards,


      ____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 





More information about the dev mailing list