https://wiki.osgeo.org/w/api.php?action=feedcontributions&feedformat=atom&user=Wiki-Olt 2026-04-12T03:20:42Z User contributions MediaWiki 1.35.9 https://wiki.osgeo.org/w/index.php?title=MapProxy_Incubation_Application&diff=123873 2020-04-16T08:30:55Z

<p>Wiki-Olt: Update to 2020 state</p> <hr /> <div>= MapProxy Incubation Application =<br /> <br /> Mailing list discussion: http://lists.osgeo.org/pipermail/incubator/2012-January/001747.html<br /> <br /> Ticket: http://trac.osgeo.org/osgeo/ticket/851<br /> <br /> == Questionnaire ==<br /> <br /> === Please provide the name and email address of the principal Project Owner. ===<br /> <br /> Oliver Tonnhofer, olt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> <br /> === Please provide the names, emails and entity affiliation of all official committers ===<br /> <br /> * Oliver Tonnhofer, olt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> <br /> Right know we are building a PCS and adding more official committers.<br /> <br /> === Please describe your Project. ===<br /> <br /> MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.<br /> <br /> MapProxy is a tile cache solution, but also offers many new and innovative features like full support for WMS clients and a powerful authorization API.<br /> <br /> === Why is hosting at OSGeo good for your project? ===<br /> <br /> MapProxy fits in well in the OSGeo software stack. It can be used in combination with other software like MapServer, GeoServer, OpenLayers, QGIS, etc and this has been demonstrated on OSGeo Live.<br /> <br /> MapProxy was developed and maintained by Omniscale as a single-vendor open source project. Omniscale is now stepping down from any further development. MapProxy is used all around the world and there is interest from companies and individuals to continue to work on MapProxy. Right know we are building a PSC with users and developers. We think it is a good idea to hand the project to the OSGeo as an umbrella for this new developer community that is building right now. <br /> <br /> === Type of application does this project represent(client, server, standalone, library, etc.): ===<br /> <br /> Server/proxy application.<br /> <br /> === Please describe any relationships to other open source projects. ===<br /> <br /> MapProxy is written in Python and uses multiple open source libraries, from Python Image Library to GDAL, Proj4 and GEOS.<br /> <br /> === Please describe any relationships with commercial companies or products. ===<br /> <br /> Development was started by Omniscale. There are no commercial versions of MapProxy available (no dual-licensing, etc.).<br /> <br /> === Which open source license(s) will the source code be released under? ===<br /> <br /> The source code is released under the Apache License 2.0.<br /> <br /> === Is there already a beta or official release? ===<br /> <br /> The first official release was made in March 2010. There was at least one major releases per year in the past. We hope to increase this pace in the future. <br /> <br /> === What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? ===<br /> <br /> The project started as a commercial product by Omniscale and was open sourced in March 2010.<br /> <br /> === Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? ===<br /> <br /> It implements various open standards like WMS, WMTS, KML, and TMS.<br /> <br /> === Is the code free of patents, trademarks, and do you control the copyright? ===<br /> <br /> The code does not contain anything where we have patents on and we are not aware of any other existing patents. The Apache License also contains a patent clause.<br /> <br /> MapProxy is not a registered trademark.<br /> <br /> All rights are held by Omniscale, with the exception of a few modules that are included in MapProxy. These modules are under a BSD-ish licenses, included in separate files. Copyright is documented in COPYING.txt, see https://github.com/mapproxy/mapproxy/blob/master/COPYING.txt<br /> <br /> === How many people actively contribute (code, documentation, other?) to the project at this time? ===<br /> <br /> Most code was contributed by Omniscale, with only a few smaller patches from other people. <br /> Omniscale received monetary contributions from various companies and institutions in the last years to implement new features for MapProxy.<br /> Omniscale is stepping down from the development and other developers are already started to work on new features. <br /> <br /> But the codebase of MapProxy is also not very large, with around 20k lines of code and around 20k lines of tests.<br /> <br /> === How many people have commit access to the source code repository? ===<br /> <br /> We use a distributed version control system, so anybody can fork the project and provide code. We will increase the number of people with push-rights to GitHub in the PSC forming process.<br /> <br /> === How many users do you expect to download the project when it is released? ===<br /> === Approximately how many users are currently using this project? ===<br /> <br /> We have an active mailing list with 320 subscribers (as of April 2020) and around 2000 downloads/month according to https://pypistats.org/packages/mapproxy.<br /> <br /> We know from conferences, mailing lists and business contacts, that MapProxy is used by a lot of open source GIS companies all around the world. Especially in Germany, were we are active in the local chapter (FOSSGIS e.V.).<br /> <br /> === What type of users does your project attract (government, commercial, hobby, academic research, etc. )? ===<br /> <br /> Mostly government, but also commercial and academic users.<br /> <br /> === If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation? ===<br /> <br /> Our mailing list is already hosted by OSGeo as a OSGeo Lab project. We are using Git and the code is hosted on GitHub.<br /> <br /> The PSC might plan to move the mapproxy.org domain and hosting (static web page only) to the OSGeo infrastructure in the future.<br /> <br /> === Does the project include an automated build and test? ===<br /> <br /> We have an extensive test suite with over 1000 unit and system tests. We have a continuous integration server that runs all these tests automatically with different Python versions. (https://travis-ci.org/github/mapproxy/mapproxy)<br /> <br /> Documentation is build nightly and there are packages with the latest source code available.<br /> <br /> === What language(s) are used in this project? (C/Java/perl/etc) ===<br /> <br /> Python and it makes use of libraries written in C (Proj4, GDAL, ...)<br /> <br /> === What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? ===<br /> <br /> All source code, comments and documentation is written in English.<br /> <br /> === What is the (estimated) size of a full release of this project? ===<br /> <br /> Should fit on a floppy.</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=OSGeo_Advocate&diff=78586 2014-07-22T13:09:54Z

<p>Wiki-Olt: /* Europe:Germany */ add olt; sort alphabetical</p> <hr /> <div>__FORCETOC__<br /> <br /> = Introduction =<br /> <br /> OSGeo Advocates are authoritative OSGeo personalities who have volunteered to talk on behalf of the [http://osgeo.org OSGeo foundation]. Advocates should be able to speak well, even better if they are entertaining.<br /> <br /> There are hundreds, if not thousands of conferences around the world which have an interest in seeing presentations from authoritative speakers, with deep insights into topics related to Open Source Geospatial Software. Luckily, OSGeo is fortunate to draw extensive membership from around the world, and has access to such authoritative figures within most countries.<br /> <br /> = Process for becoming an OSGeo Advocate =<br /> <br /> Anyone fitting one of the [[OSGeo_Advocate#Understanding_OSGeo_roles|OSGeo Advocate categories]], may put themselves forward as an OSGeo Advocate. To do so, you will need to:<br /> * Create an OSGeo wiki account, to edit this wiki (See &quot;login&quot; link in top right of this page).<br /> * Add a portrait photo of yourself using the [http://wiki.osgeo.org/wiki/Special:Upload Upload file] link in left margin in each page.<br /> * Create a new wiki page http://wiki.osgeo.org/wiki/User:YourOSGeoWikiUserName, and populate as per [[User:Template]], (copy and paste from the [http://wiki.osgeo.org/index.php?title=User:Template&amp;action=edit source] so that you see comments in the template).<br /> * You can then add your profile on [[OSGeo_Advocate#OSGeo_Advocates|this wiki page]], under your Region:Country, names ordered alphabetically by First name, using the following:<br /> {{User:&lt;YourOSGeoWikiUserName&gt;}}<br /> <br /> = Annual Refresh of Advocate list =<br /> * The list of OSGeo Advocates will be refreshed annually, after the annual voting of OSGeo Charter Members. This will be achieved by removing lapsed Advocates, then moving all Current Advocates into the Past Advocate section. All Advocates will be invited to update their profile, and move their profile back into the current Advocates section.<br /> <br /> = Advocates =<br /> <br /> == Advocate Map ==<br /> <br /> &lt;!-- {{#umAllUserMap: width|height|zoom|centerat|baselayer|navbar}} --&gt;<br /> {{#umAllUserMap:}}<br /> <br /> == Africa:Ghana ==<br /> {{User:Eyedol}}<br /> <br /> == Africa:South Africa ==<br /> === Gavin Fleming ===<br /> {{User:Gfleming}}<br /> {{User:Sokolic}}<br /> {{User:Timlinux}}<br /> <br /> == Asia:India ==<br /> {{User:ravivundavalli}}<br /> <br /> == Asia:Japan ==<br /> {{User:Yoichi}}<br /> {{User:danielkastl}}<br /> <br /> ===[http://cse.niaes.affrc.go.jp/niwasaki/ Nobusuke Iwasaki]===<br /> <br /> [[File:Iwasaki.jpg|thumb|right|100px|Nobusuke Iwasaki]]<br /> <br /> Senior Researcher, [http://www.niaes.affrc.go.jp/index_e.html National Institute for Agro-Environmental Sciences]<br /> <br /> Location: Tsukuba, Japan<br /> <br /> Nobusuke Iwasaki is researcher of land use change and rural planning and extensively using FOSS4G. Also, he is one of the main organizers of FOSS4G-Japan event and proactively commits promotion and dissemination of FOSS4G, especially academic sector. He strongly contributes [http://www.osgeo.jp/foss4g-mext/ some academic project which aims utilization of satellite image and FOSS4G for beginners and non-specialist user]. <br /> The major his product is [http://habs.dc.affrc.go.jp Historical Agro-Environmental Browsing System (HABS)], which is commended [http://psgsv2.gsi.go.jp/koukyou/G-award/list_award1.html the first Cyber Japan Award].<br /> <br /> ;OSGeo Experience [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]:<br /> :* [http://www.osgeo.jp/ OSGeo Japan Chapter] Board member since 2008<br /> :* member of [http://www.gisa-japan.org/ GIS Assosiation of JAPAN] <br /> :* member of [https://sites.google.com/site/foss4gsig/ FOSS4G special interest group] in GIS Assosiation of JAPAN<br /> <br /> ;Contact:<br /> : Email: wata909 AT gmail DOT com<br /> : Skype: wata909<br /> <br /> ;Profile last updated<br /> :2013-07-11<br /> <br /> == Asia:Korea ==<br /> {{User:Sanghee}}<br /> <br /> ==Asia:Philippines==<br /> {{User:Maning}}<br /> <br /> == Asia:Malaysia ==<br /> {{User:Thuygeo}}<br /> <br /> == Australia ==<br /> {{User:camerons}}<br /> {{User:NathanW}}<br /> {{User:jive}}<br /> <br /> == Canada ==<br /> {{User:Dmorissette}}<br /> {{User:Aross}}<br /> {{User:Gzeiss}}<br /> {{User:Mdavis}}<br /> {{User:Pwramsey3}}<br /> <br /> == Europe:Belgium ==<br /> {{User:Johanvdw}}<br /> <br /> == Europe:Czech Republic ==<br /> {{User:Jachym}}<br /> {{User:KarelCharvat}}<br /> <br /> == Europe:France ==<br /> {{User:Djay}}<br /> {{User:JRM}}<br /> {{User:grizonnetm}}<br /> {{User:NBozon}}<br /> {{User:volaya}}<br /> <br /> === [[User:Djay|Gérald Fenoy]] ===<br /> [[Image:Gérald Fenoy.jpg|thumb|right|100px]]<br /> <br /> Founder and CEO of [http://www.geolabs.fr GeoLabs SARL].<br /> <br /> Location: Lattes, France.<br /> <br /> ;OSGeo Experience [[File:OSGeo_board.png|link=OSGeo_Advocate#OSGeo Board Members]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]] [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br /> <br /> * [http://www.zoo-project.org ZOO-Project] Developper and PSC Chair,<br /> * Creator of the original [http://www.postgis.fr french web site for PostGIS], <br /> * Provide training, use and develop (WEB-)GIS applications based on OSGeo Libraries / Applications,<br /> * Active in the [http://wiki.osgeo.org/wiki/Senegalease OSGeo Senegal Local chapter],<br /> * Provide Gentoo packaging and patches for proj, geos, postgis, pgRouting, mapserver and gpsbabel,<br /> * Active at all FOSS4G international events since 2006.<br /> <br /> ;Contacts<br /> &lt;!-- {{#umSetParam: 3.921261|43.585592|Lattes, France|Djay|Gérald Fenoy}}<br /> {{#umUserMap: Djay|400px|250px|6|2|y}} --&gt;<br /> : Phone: +33670082539<br /> : Skype: gfenoy<br /> : Mail: gerald DOT fenoy AT geolabs DOT fr<br /> : IRC: djay<br /> <br /> [[Category:OSGeo Charter Member]]<br /> [[Category:OSGeo Member]]<br /> <br /> === Nicolas Bozon ===<br /> [[Image:nicolas_bozon.png|thumb|right|100px|Nick at Abikocho station]]<br /> Principle, [http://www.cartogenic.com Cartogenic].<br /> <br /> Nicolas Bozon is an open source enthusiast and specializes in designing user interfaces and experiences for mapping and web applications. Nicolas runs [http://www.cartogenic.com Cartogenic], a geospatial consutling company located in Lyon, France. He is also a researcher in geomatics and environmental sciences, and currently pursues a post-doctoral fellowship in Osaka, Japan.<br /> <br /> ;OSGeo Experience [[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]] [[File:OSGeo_committee.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]]<br /> <br /> * Co-founder and PSC member of [http://zoo-project.org ZOO-Project], the Open WPS platform<br /> * [http://www.osgeo.org/charter_members Charter Member] of OSGeo<br /> * Member of the [http://wiki.osgeo.org/wiki/Marketing_Committee Marketing Committee] of OSGeo<br /> <br /> ;Academics<br /> * Post-doc fellowship (JP, 2011/2013)<br /> * PhD Maths/GIS (FR, 2006/2009)<br /> * Master GIS (FR, 2005)<br /> * Undergraduate Env Sc (QC, 2002/2004)<br /> * Undergraduate Geo (FR, 2000/2002)<br /> <br /> ;Contact<br /> :Email: nicolas dot bozon at gmail dot com<br /> :[http://www.linkedin.com/in/nbozon Linkedin profile ]<br /> :Skype: nicboz1<br /> :IRC: nbozon<br /> <br /> {{#umSetParam: 4.856216|45.770527|Lyon, France|Nbozon|Nicolas Bozon}}<br /> &lt;!-- {{#umUserMap: Nbozon|600px|300px|6|2|y}} --&gt;<br /> [[Category:OSGeo Member]]<br /> [[Category:OSGeo Charter Member]]<br /> <br /> == Europe:Germany ==<br /> {{User:Aghisla}}<br /> {{User:Arnulf Christl}}<br /> {{User:Astrid_Emde}}<br /> {{User:misev}}<br /> {{User:olt}}<br /> {{User:Pebau}}<br /> {{User:Stefan_A._Tzeggai}}<br /> {{User:Thomas_Baschetti}}<br /> <br /> == Europe:Greece ==<br /> {{User:Kalxas}}<br /> {{User:ArArgyridis}}<br /> {{User:kotzino}}<br /> {{User:Nikos}}<br /> <br /> == Europe:Italy ==<br /> {{User:Madi}}<br /> {{User:Lucadelu}}<br /> {{User:Aaime}}<br /> {{User:Maxi71}}<br /> {{User:epifanio}}<br /> {{User:Moovida}}<br /> {{Talk:Markus_Neteler}}<br /> <br /> == Europe:The Netherlands ==<br /> {{User:Ticheler}}<br /> {{User:BarendKobben}}<br /> {{User:Just}}<br /> {{User:bartvde}}<br /> {{User:Milovanderlinden}}<br /> {{User:Genuchten}}<br /> <br /> == Europe:Portugal==<br /> {{User:Lutra}}<br /> <br /> == Europe:Romania ==<br /> {{User:Vasile}}<br /> <br /> == Europe:Spain ==<br /> {{User:Lluís}}<br /> {{User:vehrka}}<br /> {{User:Michogar}}<br /> {{User:Delawen}}<br /> {{User:Adiez}}<br /> {{User:Jsanz}}<br /> <br /> <br /> == Europe:Switzerland ==<br /> {{User:Maxi71}}<br /> {{User:Mbernasocchi}}<br /> <br /> == Europe:United Kingdom ==<br /> {{User:Ian}}<br /> {{User:JoCook}}<br /> {{User:Ianturton}}<br /> {{User:Stevenfeldman}}<br /> {{User:Sanand}}<br /> <br /> == Latin America:Argentina ==<br /> {{User:Maurimiranda}}<br /> <br /> == Latin America:Brazil ==<br /> {{User:Fsc7}}<br /> <br /> == Latin America:Chile ==<br /> {{User:Perriger}}<br /> <br /> == Latin America:Ecuador ==<br /> {{User:Eamado}}<br /> <br /> == Latin America:Mexico ==<br /> {{User:Aborrell}}<br /> <br /> == United States ==<br /> {{User:EliL}}<br /> {{User:Alex Mandel}}<br /> {{User:Brian Hamlin}}<br /> {{User:Dnewcomb}}<br /> {{User:Amyonthemap}}<br /> {{User:warmerda}}<br /> {{User:Helena}}<br /> {{User:Surveyor}}<br /> {{User:Mark Lucas}}<br /> {{User:msmitherdc}}<br /> {{User:mpg}}<br /> {{User:pmbatty}}<br /> {{User:Rburhum}}<br /> {{User:Sdlime}}<br /> {{User:Woodbri}}<br /> <br /> <br /> === [http://www.redefinedhorizons.com/printingpress/landon-blakes-bio/ Landon Blake] (AKA - The Sunburned Surveyor) ===<br /> <br /> [[File:landon_blake_portrait.jpg|100px|thumb|right|Landon Blake]]<br /> <br /> Owner, [http://www.redefinedhorizons.com Redefined Horizons]<br /> <br /> Location: Stockton, California, United States of America<br /> <br /> Landon Blake is a land surveyor and GIS programmer with a focus on OpenJUMP and CAD customization. <br /> <br /> * Web Page: [http://www.redefinedhorizons.com]<br /> * Blog: [http://www.redefinedhorizonsblog.com]<br /> * Twitter: [https://twitter.com/mapit4u]<br /> * LinkedIn: [http://www.linkedin.com/in/landonblake]<br /> <br /> ;OSGeo Experience<br /> * Volunteer Editor of the OSGeo Journal<br /> * Board Representative for the OSGeo California Chapter<br /> <br /> ;Contact:<br /> : Email: sunburned dot surveyor at gmail dot com<br /> : Phone (Home): 209-464-2612<br /> : Phone (Cell): 209-298-7521<br /> : Skype: <br /> <br /> ;Profile last updated: 07 14 2013<br /> <br /> = Past OSGeo Advocates =<br /> This section lists prior listed Advocates who have not recently updated their profiles.<br /> <br /> = Understanding OSGeo roles =<br /> <br /> Below is an explanation of roles which Advocates might have been involved in as part of OSGeo:<br /> <br /> ====[[File:OSGeo_board.png]] [[File:OSGeo_exboard.png]] OSGeo Board Members====<br /> : We only have 9 active OSGeo board members in the world, which have been peer selected based upon their outstanding leadership in the greater OSGeo community.<br /> <br /> ====[[File:OSGeo_charter.png]] OSGeo Charter Members====<br /> : Charter membership is obtained through a strongly contested selection process. Members tend to be developers and leaders in one or more OSGeo projects, and/or OSGeo business leaders, and have a deep understanding in many of the OSGeo projects and principles of Open Source.<br /> <br /> ==== [[File:SolKatz.png]] Sol Katz Award ====<br /> : Every year, OSGeo presents the prestigious [http://www.osgeo.org/solkatz Sol Katz Award] to one individual who has demonstrated leadership and contributed significantly to advance open source ideals in the geospatial realm.<br /> <br /> ====[[File:OSGeo_chair.png]] [[File:OSGeo_psc.png]] Voted position in an OSGeo community====<br /> : These people hold a position of responsibility within one of the OSGeo sub-communities. This may be a chair of an OSGeo committee or board member of a Regional Chapter, or a member of a project's Project Steering Committee (PSC).<br /> <br /> ====[[File:OSGeo_coder.png]] [[File:OSGeo_committee.png]] Developers and Committee Members====<br /> : This is where the real work gets done developing and coordinating development of OSGeo Software.<br /> <br /> ====[[File:OSGeo_user.png]] OSGeo Community Members====<br /> : These people are actively involved in one or more OSGeo communities, acting as practitioners, users, promoters or supporters of OSGeo software. These people tend to have a practical understanding about how OSGeo software works.<br /> <br /> ====[[File:OSGeo_translate.png]] OSGeo Translators====<br /> : These people have translated documentation for OSGeo-Live, and/or OSGeo projects. They usually have an established understanding of OSGeo topics and can present them in local languages.<br /> <br /> = Expenses =<br /> <br /> This OSGeo Advocate list has been designed to help event organisors find local authoritative speakers. Events wishing to import keynote speakers should anticipate covering expenses of these speakers. Note that OSGeo is a volunteer driven organisation without paid positions of authority and OSGeo doesn't budget to cover travel expenses. Note also that unlike proprietary companies, a company promoting Open Source software don't earn license fees when a delegate is convinced to start using the free software.<br /> <br /> When budgeting for keynote speakers expect to cover the following expenses:<br /> * Travel, typically including:<br /> ** airfare<br /> ** visa<br /> ** travel insurance (including overseas medical, trip disruption, lost luggage, etc)<br /> ** meals during travel<br /> ** transit costs to local and host airports<br /> * Accommodation<br /> ** standard 3 or 4 star hotel within walking distance of the event<br /> ** high speed internet<br /> * Per diem costs<br /> ** 3 meals a day<br /> * Speakers fee<br /> ** typically $US 1000 per day. (Note that OSGeo volunteer speakers usually have a full time job and will be loosing wages for the duration of the event)<br /> <br /> For a rough guide of travel costs refer to the [http://aoprals.state.gov/web920/per_diem.asp US Department of State costs]<br /> <br /> Individual speakers may waive any of these costs if attracted to the event for other reasons, and final costs are to be negotiated with the selected speaker.<br /> <br /> = Other Resources =<br /> Links to other organizations running a similar process. <br /> * http://www.ogcnetwork.net/node/1585</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=User:Olt&diff=78585 2014-07-22T12:55:58Z

<p>Wiki-Olt: </p> <hr /> <div>===Oliver Tonnhofer===<br /> <br /> [[File:oliver_tonnhofer.jpeg|thumb|right|100px|Oliver Tonnhofer]]<br /> <br /> Software Engineer, [http://omniscale.de Omniscale]<br /> <br /> Location: Oldenburg, Germany<br /> <br /> Oliver Tonnhofer is a software engineer at Omniscale. He is the core-developer of [http://mapproxy.org MapProxy] and [http://imposm.org Imposm], user and contributor of various OSGeo projects.<br /> <br /> ;OSGeo Experience<br /> <br /> [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]<br /> [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br /> <br /> :* Speaker at FOSS4G, FOSSGIS and FOSS4GE conferences<br /> :* Maintainer of MapProxy on the OSGeo LiveDVD<br /> :* User, advocate and contributor of/to (geospatial) open source software<br /> <br /> <br /> ;Contact:<br /> : Email: olt ÅT bogosoft DØT com<br /> <br /> ;Spoken Language(s): English, German<br /> <br /> ;Profile last updated: 22 July 2014</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=User:Olt&diff=78584 2014-07-22T12:55:18Z

<p>Wiki-Olt: </p> <hr /> <div>===Oliver Tonnhofer===<br /> <br /> [[File:oliver_tonnhofer.jpeg|thumb|right|100px|Oliver Tonnhofer]]<br /> <br /> Software Engineer, [http://omniscale.de Omniscale]<br /> <br /> Location: Oldenburg, Germany<br /> <br /> Oliver Tonnhofer is a software engineer at Omniscale. He is the core-developer of [http://mapproxy.org MapProxy] and [http://imposm.org Imposm], user and contributor of various OSGeo projects.<br /> <br /> ;OSGeo Experience<br /> <br /> [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]<br /> [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br /> <br /> :* Speaker at FOSS4G, FOSSGIS and FOSS4GE conferences<br /> :* Maintainer of MapProxy on the OSGeo LiveDVD<br /> :* User, advocate and contributor of (geospatial) open source software<br /> <br /> <br /> ;Contact:<br /> : Email: olt ÅT bogosoft DØT com<br /> <br /> ;Spoken Language(s): English, German<br /> <br /> ;Profile last updated: 22 July 2014</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=File:Oliver_tonnhofer.jpeg&diff=78582 2014-07-22T12:49:10Z

<p>Wiki-Olt: </p> <hr /> <div></div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=User:Olt&diff=78581 2014-07-22T12:44:16Z

<p>Wiki-Olt: </p> <hr /> <div>===Oliver Tonnhofer===<br /> <br /> [[File:OSGeo_compass300.png|thumb|right|100px|Your Name]]<br /> <br /> Software Engineer, [http://omniscale.de Omniscale]<br /> <br /> Location: Oldenburg, Germany<br /> <br /> Oliver Tonnhofer is a software engineer at Omniscale. He is the core-developer of [http://mapproxy.org MapProxy] and [http://imposm.org Imposm], user and contributor of various OSGeo projects.<br /> <br /> ;OSGeo Experience<br /> <br /> [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]<br /> [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br /> <br /> :* Speaker at FOSS4G, FOSSGIS and FOSS4GE conferences<br /> :* Maintainer of MapProxy on the OSGeo LiveDVD<br /> :* User, advocate and contributor of (geospatial) open source software<br /> <br /> <br /> ;Contact:<br /> : Email: olt ÅT bogosoft DØT com<br /> <br /> ;Spoken Language(s): English, German<br /> <br /> ;Profile last updated: 22 July 2014</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=MapProxy&diff=74335 2013-10-01T15:36:44Z

<p>Wiki-Olt: add links to documentation</p> <hr /> <div>== Basic Project Data ==<br /> *'''Project Name:''' MapProxy<br /> *'''Project Status Condition:''' Stable<br /> *'''Project Web Site:''' http://mapproxy.org<br /> *'''Project Documentation:''' http://mapproxy.org/documentation.html<br /> *'''Project Contact:''' Oliver Tonnhofer &lt;olt at omniscale.de&gt;<br /> *'''Short Project Description:''' MapProxy is a tile cache and WMS proxy.<br /> <br /> == Project Infrastructure ==<br /> *'''Project Source Code:''' https://github.com/mapproxy/mapproxy<br /> *'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/mapproxy<br /> *'''Project Version Control Repository:''' git://github.com/mapproxy/mapproxy.git<br /> *'''Project Developer Documentation:''' http://mapproxy.org/docs/nightly/deployment.html<br /> *'''Project Bug Tracker:''' https://github.com/mapproxy/mapproxy/issues<br /> *'''Project Feature Request Tracker:''' ditto<br /> <br /> == Project Governance ==<br /> *'''Source Code License:''' [http://www.apache.org/licenses/LICENSE-2.0.html Apache License 2.0]<br /> *'''Documentation License:''' ditto<br /> *'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the Apache License 2.0 without explicit assignment (see [http://www.apache.org/licenses/LICENSE-2.0.html license])<br /> *'''Decision Making Procedure:''' [http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life BDFL], at least for now.<br /> *'''Coding Standards:''' [http://www.python.org/dev/peps/pep-0008/ PEP8]<br /> *'''Release Procedure:''' Major/minor releases. Beta and release candidates as necessary.<br /> <br /> == Project Deliverables ==<br /> *'''Latest Project Release:''' http://pypi.python.org/pypi/MapProxy<br /> <br /> [[Category: OSGeo Labs]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Geoservices_REST_API&diff=71113 2013-05-13T11:20:17Z

<p>Wiki-Olt: /* Signed */</p> <hr /> <div>This wiki page aims to collate community concerns related to the adoption of the &quot;Geoservices REST API&quot; document as a standard of the [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)]. The page is being collaboratively edited, targeting completion by Wednesday 15 May 2013, after which it will be delivered by the board of the [http://osgeo.org OSGeo Foundation (OSGeo)] to the OGC and OGC voting members.<br /> <br /> = Cover Letter from the OSGeo Board =<br /> ''Please don't edit this &quot;Cover Letter&quot; statement, which has been approved by the OSGeo Board.'' <br /> <br /> The board of the [http://osgeo.org Open Source Geospatial Foundation] (OSGeo) is presenting this letter to the OGC. It highlights concerns about the &quot;GeoServices REST API&quot; from many people within the OSGeo community. As always, if there is anything the OSGeo board can do to help, then please let us know.<br /> <br /> Signed: Jeff McKenna (OSGeo president), <br /> Peter Batty,<br /> Jáchym Čepický,<br /> Michael Gerlek,<br /> Anne Ghisla,<br /> Mark Lucas,<br /> Daniel Morissette,<br /> Cameron Shorter,<br /> Frank Warmerdam<br /> <br /> = Open Letter to OGC and voting members =<br /> <br /> ''Please don't edit this &quot;Open Letter&quot; statement, comments and discussion should go in the &quot;Further Concerns&quot; section below.'' <br /> <br /> May 2013<br /> <br /> We, the undersigned, have concerns that approving the &quot;Geoservices REST API&quot; as an OGC standard, would have detrimental impacts on interoperability within the spatial industry.<br /> <br /> We strongly urge that the proposed &quot;Geoservices REST API&quot;, as it stands in May 2013, be rejected as an OGC standard.<br /> <br /> People have listed different reasons for concern. They are described below.<br /> <br /> == Signed ==<br /> ''Please add your name here if you agree with the above statement. Include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. (Link to OSGeo profile if appropriate). You may sign as a group, such as the Project Steering Committee of XXX project if you wish, or as Your Name on behalf of YYY company.''<br /> <br /> # [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor &amp; coordinator of [http://live.osgeo.org OSGeo-Live], OSGeo Board member<br /> # [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Principal Scientist for RadiantBlue Technologies Inc.<br /> # [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]<br /> # [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]<br /> # Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]<br /> # [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member<br /> # [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]<br /> # [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]<br /> # [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]<br /> # [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]<br /> # [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.<br /> # [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.<br /> # [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.<br /> # [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.<br /> # Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client<br /> # [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.<br /> # [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.<br /> # [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter<br /> # [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, Post-doctoral researcher at the European Commission, JRC, Italy<br /> # [[Jorge Sanz]], GIS Consultant at [http://www.prodevelop.es Prodevelop], OSGeo Charter Member, OSGeo Spanish Local Chapter Member, Spain<br /> # [[Pablo Sanxiao]], CTO and co-founder at [http://www.icarto.es iCarto], OSGeo Spanish Local Chapter Member, Spain<br /> # [[User:Fsteggink|Frank Steggink]], GIS software developer at [http://www.vicrea.nl Vicrea], The Netherlands, member of the Dutch Local Chapter<br /> # [[User:Olivier.courtin|Olivier Courtin]], [http://www.oslandia.com Oslandia] co-founder, core contributor or/and PSC member of [http://mapserver.org Mapserver] and [http://www.postgis.org/ PostGIS]. OGC TC member.<br /> # [[User:Bolosig|Wladimir Szczerban]], OSGeo Spanish Local Chapter Member, Spain<br /> # [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member.<br /> # [[User:Vmische|Volker Mische]], geospatial software engineer, creator of GeoCouch<br /> # [[User:Ivansanchez|Iván Sánchez]], OSGeo Spanish Local Chapter Member, head of [http://www.openstreetmap.es OpenStreetMap Spain], [http://osmfoundation.org OpenStreetMap Foundation] member, [http://hot.openstreetmap.org/ Humanitarian OpenStreetMap Team] member, [http://www.idee.es/ Spanish SDI working group] member<br /> # [[User:Gabi|Gabriel Carrión]], Strategy Manager at [http://www.gvsig.com gvSIG association]<br /> # [http://strk.keybit.net Sandro Santilli], OSGeo Charter Member, [http://postgis.net PostGIS] and [http://trac.osgeo.org/geos GEOS] PSC member and core hacker.<br /> # [[User:Javiarch|Javier Diaz]], member of Geoinquietos Bs As [http://wiki.osgeo.org/wiki/Category:Geoinquietos_Buenos_Aires], member of the Organizing Committee FOSS4G Bs As 2013 [http://www.foss4g-ba.org/]<br /> # [[User: JoCook|Jo Cook]], Consultant at [http://isharemaps.com| Astun Technology], former Director of OSGeo, Charter Member, founder of UK Local Chapter, Deputy Chair of [http://2013.foss4g.org| FOSS4G 2013]<br /> # [[User: Fpenarru | Francisco José Peñarrubia]], CTO and co-founder at [http://www.scolab.es SCOLAB]. Members of [http://www.gvsig.com gvSIG Association]<br /> # [[User: Ganesh|Shanmugam Ganeshkumar]], Director of [http://www.geoicon.com GeoICON], member OSGeo Malaysia Chapter<br /> # [[User:Barryrowlingson|Barry Rowlingson]], Senior Researcher, Lancaster University and Software Sustainability Institute Fellow<br /> # [[User: Sfkeller|Stefan Keller]], University of Applied Sciences, Rapperswil (Switzerland), Member of Swiss OSM (SOSM) and QGIS association and of organizing committees of pgConf.DE and FOSSGIS 2013, and member of eCH (e-government standards of Switzerland)<br /> # [[User: AndyBMapMan|Andrew Bailey]], OSGeo member, Astun Technology<br /> # [[User: Sanand|Suchith Anand]], OSGeo Charter member, OSGeo Education member, FOSS4G 2013 LOC member<br /> # [[User: krefftc|Carlos Krefft]], GIS software developer at [http://www.cstars.miami.edu CSTARS - University of Miami], OGC and OSGeo Member.<br /> # [[User:Steko|Stefano Costa]], OSGeo member, GFOSS.it member and former board member, Ministero per i Beni e le Attività Culturali (Italy)<br /> # [[User:pebau|Peter Baumann]], [http://www.jacobs-university.de/lsis Jacobs University], OGC member, WCS.SWG chair, editor of 10+ specs (disclaimer: this is an expression of my personal opinion and not in any way endorsed by OGC)<br /> # [[User:pmbatty|Peter Batty]], CTO of Geospatial Division at [http://www.ubisense.net Ubisense], OSGeo board member, former CTO of [http://intergraph.com Intergraph] and [http://www.gedigitalenergy.com/gis.htm GE Smallworld], Technical Committee member of OGC in its formative years c 1995-97<br /> # [[User: BarendKobben | Barend K&amp;ouml;bben]], OSGEO Chartered Member, OSGeo.nl Dutch chapter treasurer, Senior Lecturer at [http://www.itc.nl ITC-University of Twente]<br /> # [[User: pcav | Paolo Cavallini]], [http://www.faunalia.it Faunalia], OSGeo member, GFOSS.it member and former president, QGIS-PSC<br /> # [[User: fthamura| FRans Thamura]], [http://www.osgeo.or.id Indonesia], OSGeo Indonesia, organizer]<br /> # [[User: Endofcap| Sanghee Shin]], Founder and CEO of [http://www.gaia3d.com Gaia3D], OSGeo Charter Member, Representative of [http://www.osgeo.kr OSGeo Korean Chapter], Chairman of Open Source GIS Alliance Korea<br /> # [[User: rentairo| Benni Purwonegoro]],Indonesia, IT-Spatial Engineer @ Geospatial Information Agency .<br /> # [[User: jachym| Jachym Cepicky]], Czech Republic, member of OSGeo Board of Directors<br /> # [[User: cappelaere| Pat Cappelaere]], Vightel Corporation<br /> # [[User: JuergenFischer|Jürgen Fischer]], norBIT GmbH, QGIS core developer<br /> # [[User: Maria|Maria Antonia Brovelli]], OSGeo Charter member, OSGeo Education member, GIS Professor and Vice Rector for the Como Campus at [http://www.polimi.it/en Politecnico di Milano], Italy<br /> # [[User:Nachouve |Nacho Varela]], GIS Consultant, OSGeo Spanish Local Chapter Member, Spain<br /> # [[User:vasile |Vasile Craciunescu]], OSGeo Charter member, OSGeo Romania Local Chapter Leader, Researcher at Romanian National Meteorological Administration, Romania<br /> # [[User:badaveil |Abbas Abdul Wahab]], Asst. Director, Federal Department of Town &amp; Country Planning, Peninsular Malaysia<br /> # [[User:rbraam | Roy Braam]], Software Engineer @ [http://www.b3partners.nl | B3Partners]<br /> # [[User:peteris | Peteris Bruns]], Latvia, GIS Consultant &amp; Software Engineer @ [http://www.sungis.lv | SunGIS]<br /> # [[User:Lutra | Giovanni Manghi]], Portugal, [http://www.faunalia.pt Faunalia], OSGeo member, OSGeo-Portugal<br /> # [[User:Hfpmartins | Hugo Martins]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], WebGIS Developer, OSGeo-Portugal Member<br /> # [[User:Sabb | Saber Razmjooei]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder<br /> # [[User:Wellsp | Peter Wells]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder<br /> # [[User:SGijzen | Sidney Gijzen]], The Netherlands, Researcher GIS @ [http://www.wageningenur.nl/en/Expertise-Services/Research-Institutes/alterra.htm Alterra, Wageningen UR]<br /> # [[User:mfidelman | Miles Fidelman]], US, Principal, Protocol Technologies Group, LLC<br /> # [[User:punkish | Puneet Kishor]], OSGeo Charter Member; [http://www.geology.wisc.edu Geology, Univ. of Wisconsin-Madison]; [http://creativecommons.org/staff#puneetkishor Creative Commons]<br /> # [[User:Toze | António José Silva]], Portugal, GIS Consultant, OSGeo-Portugal Member<br /> # [[User:AndreMano | AndreMano]], Portugal, Natural History Society - GIS Department, OSGeo-Portugal Member<br /> # [[User:maurimiranda|Mauricio Miranda]], Argentina, OSGeo Charter Member, OSGeo Spanish Local Chapter Board Member<br /> # [[User:pmachado|Paulo Machado]], Portugal, Software Engineer @ PT Inovação<br /> # [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]<br /> # [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain<br /> # [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].<br /> # [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor<br /> # [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center<br /> # [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens<br /> # [[User:Kimaidou|Michaël Douchin]], France, GIS consultant &amp; software engineer at [http://3liz.com/ 3liz]<br /> # [[User:PedroVenancio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel<br /> # [[User:Jgrocha|Jorge Gustavo Rocha]], Portugal, GIS Professor at Universidade do Minho<br /> # [[User:Danielkastl| Daniel Kastl]], Japan, [http://georepublic.info Georepublic], Founder<br /> # [[Diodata|John Callahan]], US, Research Scientist and GIS/Remote Sensing Specialist, University of Delaware<br /> # [[User:kjkalyan|Kalyan Janakiraman]], Senior Systems Analyst, Business Development Services, NSW Land and Property Information, Sydney, Australia<br /> # [[User:goliadranger|Phillip Davis]], Director, National Geospatial Technology Center of Excellence, Texas, USA<br /> # [[User:simonp|Simon Pigot]], contributor to and PSC member of [http://geonetwork-opensource.org GeoNetwork opensource] (speaking for myself, not an official view of my employer)<br /> # [[User:jbryant|John Bryant]], Consultant, Mammoth Mapping, Dawson City, Canada and GIS/DB Admin, Jupiter Mines, Perth, Australia<br /> # [[ChIossif|Christos Iossifides]], Remote Sensing Instructor, Laboratory Teaching Staff, Remote Sensing Instructor and Researcher, National Technical University of Athens<br /> # [[User:tbowden|Tim Bowden]], Spatial Consultant, Perth, Australia<br /> # [[User:Lucadelu|Luca Delucchi]], GIS Technician, Trento, Italy<br /> # [[User:bartvde|Bart van den Eijnden]], GIS software developer, Utrecht, Netherlands<br /> # [[User:eyedol|Henry Addo]], Software Developer at Ushahidi [http://ushahidi.com], contributor of [http://live.osgeo.org OSGeo-Live]<br /> # [[User:iacovellas|Stefano Iacovella]], GIS consultant &amp; software engineer, Rome, Italy<br /> # [[User:Mtoonen| Meine Toonen]], Software Engineer @ [http://www.b3partners.nl B3Partners], The Netherlands<br /> # [[User:arneke| Arne Kepp]], Software Engineer, Oslo, Norway<br /> # [[User:Pirmin_Kalberer| Pirmin Kalberer]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Contributor of [http://gdal.org GDAL/OGR], [http://qgis.org QGIS], [http://mapfish.org/ Mapfish], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], [http://live.osgeo.org OSGeo-Live], Switzerland<br /> # [[User:hdus| Dr. Horst Düster]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Treasurer QGIS Project [http://qgis.org QGIS], Zürich, Switzerland<br /> # [[User:rduivenvoorde| Richard Duivenvoorde]], Managing director &amp; software developer [http://www.webmapper.net/ Webmapper], QGIS community member<br /> # [[User:stevenfeldman|Steven Feldman]], Principal at [http://knowwhereconslting.co.uk KnowWhere Consulting] and Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]<br /> # [[User:Edward_Mac_Gillavry| Edward Mac Gillavry]], Managing director &amp; software developer [http://www.webmapper.net/ Webmapper]<br /> # [[User:maximdubinin| Maxim Dubinin]], CEO at [http://www.nextgis.org/ NextGIS], head of [http://gis-lab.info GIS-Lab.info]<br /> # [[User:flavour| Fran Boon]], PMC Chair at [http://sahanafoundation.org/ Sahana Foundation], CTO of [http://aidiq.com AidIQ]<br /> # [[User:Ian| Ian Edwards]], Chair [http://www.osgeo.org/uk OSGeo:UK]<br /> # [[User:Bishop|Dmitriy Baryshnikov]] Developer at [http://www.nextgis.org/ NextGIS], [http://gdal.org GDAL/OGR] committer, [http://wxgis.googlecode.com wxGIS] developer, [http://gis-lab.info GIS-Lab.info] community member<br /> # [[User:cvanlith| Chris van Lith]], Director [http://www.b3partners.nl B3Partners], member of [http://www.opengeogroep.nl OpenGeoGroep]<br /> # [[User:VincentP| Vincent Picavet]], co-founder of [http://www.oslandia.com Oslandia], founding member and treasurer of OSGeo-FR<br /> # [[User:Stefan_A._Tzeggai| Stefan A. Tzeggai]], creator of [http://www.geopublishing.org/AtlasStyler AtlasStyler SLD editor], founder of [http://www.empirica-systeme.de empirica systeme gmbh]<br /> # [[User:Rdewit| Roald de Wit]], Geospatial Software Engineer, Melbourne, Australia<br /> # [[User:grizonnetm| Manuel Grizonnet]], working at the [http://www.cnes.fr/ French Space Agency], [http://www.orfeo-toolbox.org/otb/ ORFEO ToolBox library] developer<br /> # [[User:RdeMoritoru| Toru Mori]], President &amp; CEO, [http://www.orkney.co.jp Orkney, Inc.], Yokohama, Japan, Representative of OSGeo Japan Chapter, OSGeo Charter Member<br /> # [[User:MarkusSchneider2|Markus Schneider]], TMC chair of the [http://www.deegree.org deegree project], CEO of [http://www.occamlabs.de Occam Labs]<br /> # [[User:elena|Elena Mezzini]], Remote Sensing and GIS Technician, GFOSS.it member, Bologna, Italy<br /> # [[User:Alexbruy|Alexander Bruy]], [http://nextgis.org NextGIS], QGIS core developer<br /> # [[User:Dfurtado | Danilo Furtado]], Portugal, OSGeo member, OSGeo-Portugal<br /> # [[User:Stranger | Andreas Schmitz]], Germany, deegree core developer and TMC member, CTO of [http://www.occamlabs.de Occam Labs]<br /> # [[User:Olt | Oliver Tonnhofer]], Germany, [http://mapproxy.org MapProxy] core developer, founder &amp; CTO of [http://www.omniscale.com Omniscale]<br /> <br /> = Summary =<br /> <br /> ''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''<br /> <br /> The document titled &quot;GeoServices REST API&quot; is currently, in May 2013, being considered to be included as one of the Open Geospatial Consortium (OGC) standards. The vote to accept the document as a standard is unusually contentious; the controversy is the cause of this page.<br /> <br /> The document was previously released for public comment and can be found [http://www.opengeospatial.org/standards/requests/89 on the request for public comment page] (though public comment has been closed for now).<br /> <br /> The document attempts to standardize a suite of web services such as a service which provides map images, a service which provides geospatial feature data, and a service which performs geospatial processing. The standard focuses on interactions via a defined hierarchy of URLs and using predominantly a particular set of JSON schemas for the exchange of geospatial data.<br /> <br /> == Criticism and Response ==<br /> <br /> The adoption of the document as an OGC Standard is contentious for a wide variety of reasons including:<br /> <br /> * the process through which the document was developed which is thought to lack sufficient flexibility to respond to input from various stakeholders, <br /> * the focus of the document on 'REST' and 'API' which is seen as not matching the ideas others have for these concepts,<br /> * the names of the standard and of the services which are seen as potentially confusing, <br /> * the functionality of the new services which are considered to duplicate that of existing services already standardized by the OGC such as WMS, WFS, WCS, and WPS,<br /> * the addition of a new set of services based on new URL patterns and new JSON exchange formats which is seen as duplicating the efforts of other working groups bringing similar ideas to the updates of existing OGC services,<br /> * the re-introduction in the new services of previously resolved interoperability issues which is seen as failing to build on the existing knowledge and experience,<br /> * the use of the particular JSON schemas which are seen as having little industry acceptance and are incompatible with other widely used schemas, and <br /> * the lack of implementation diversity which is thought to give the vendor of the one complete implementation an unusual commercial advantage on top of the vendor's already dominant position in the domain. <br /> <br /> These issues have potential impacts on the use of 'Open Standards' by governments and companies, on the interoperability of software interacting with standards compliant OGC services, on the costs to developers and users of standards compliant software, on the understanding of 'Open Standards' by the public at large, and, possibly, on the reputation of the OGC as a champion of interoperability.<br /> <br /> In particular there are concerns by some that adoption of the standard will likely result in a combination of the following:<br /> # The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.<br /> # Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.<br /> # Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.<br /> # This will result in a diminished importance of OGC, as the &quot;OGC standards&quot; stamp of approval will not equate interoperability.<br /> # After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.<br /> # One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation.<br /> <br /> In response to these issues, the authors of the Geoservices REST API document have stated that:<br /> <br /> * the process of the OGC has been followed completely,<br /> * the specification actually is RESTful and does define an API,<br /> * the name, due to the controversy, may be open for modification<br /> * the OGC does not forbid duplication of service functionality, already has duplication between the W*S and the S*S (sensor) family of standards, should not block progress in the name of 'one true way', and harmonization between the services can be considered in the future,<br /> * the JSON format exists and functions, and<br /> * there are alternative implementations for some of these services.<br /> <br /> The authors also stress that the existence of a large user base shows the service is useful, and that the standardization of the services at the OGC may encourage new implementations.<br /> <br /> = Positions on the vote =<br /> ''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''<br /> <br /> The discussion raises a number of issues, many based upon complex technical concepts and implications. This makes it difficult for voting OGC members considering whether to support &quot;Geoservices REST API&quot; as a standard. The following provides one analysis of the positions on the vote, aimed to simplify and summarize key points. However, it does not necessarily represent the opinions held by all signatories above.<br /> <br /> ; The pros for accepting the &quot;Geoservices REST API&quot; document as an OGC standard:<br /> <br /> :* The OGC should be in the business of developing good standards, not in choosing which standards should be implemented.<br /> :* The proposers of the document want to make a standard and have followed all the rules of the OGC. The work of any such group of members deserves serious, good faith consideration.<br /> :* The need for an integrated suite of services using simple data, which is addressed (partially) by the document, is real. The proposed document is pushing the OGC on this issue.<br /> :* The proposed document could be useful to a number of people.<br /> :* The proposed document is not significantly more broken than the existing standards of the OGC. As one author of standards [http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html notes]: <br /> :''&quot;I know how totally impossible it is to write a good standard, so the weaknesses in the existing document seem more acceptable.&quot;''<br /> <br /> ; The cons:<br /> <br /> :* The OGC actually is, whether it should be or not, in the position of recommending interoperable standards for geospatial services. The proposed document is not good enough, not widely enough implemented, and not publicly supported enough, to be considered at the same level as existing standards.<br /> :* Adopting a standard implies a desire to maintain the standard, but OGC's desire to support this approach has been questioned by some. In particular, the lack of collaboration and willingness to accept recommendations from the community on this version of the &quot;Geoservices REST API&quot; document bodes ill for the future.<br /> :* The overlap in functionality between the proposed services and the existing services, notably with the ongoing work to modularize the existing services, is almost 100 percent. However, compatibility is low.<br /> :* There is already a published document: http://www.esri.com/library/whitepapers/pdfs/geoservices-rest-spec.pdf so there is no need for the document to be adopted as an OGC Standard merely for interoperability with the ESRI implementation.<br /> :* The document, as a new, separate effort, repeats mistakes which were made and since solved by the other services.<br /> :* The document focuses on the past (notably with backwards compatibility and use of only GET/POST) not on the future.<br /> :* The document needs a comprehensive editorial review and substantial rewriting for clarity.<br /> <br /> ; A conclusion:<br /> <br /> Both simple answers are bad.<br /> <br /> A simple acceptance of the standard would introduce a new set of 'OGC approved' open services. The OGC approval might enable governments to buy a XXXX-new-name-here-XXXX solution instead of a W*S or a S*S solution. The path forwards towards harmonizing the services is unclear. Fixing this document in addition to fixing the W*S services will be a pain.<br /> <br /> Simply rejecting the solution would be bad for the OGC. It would place the OGC in the position of picking winners and losers in the standards business. It would mean that the OGC is stuck on the project of fixing the W*S standards to meet some nebulous future functionality without having any path to get there. It would discourage innovation and progress.<br /> <br /> Is there any third way?<br /> <br /> Well, actually, there is a different way of thinking of the issue. Overall, there appears to be a shared desire for an integrated suite of geospatial services, originally focused on a simple data model, built on the exchange of well defined resources in simple formats including JSON, accessible and usable using the core HTTP verbs, and discoverable through following HTML links and patterns of URL paths. The hope is that such a suite can be designed based on the best expertise of the OGC, can be widely supported by the community, and can be implemented and tested by multiple groups. Neither the proposed document, nor the current services meet this vision. So the work, ultimately, is on improving all the services at the OGC, first to modularize them, then to enable simple implementations, and finally to link those implementations into a functional suite. Since this is the work that is already happening, perhaps the vote is an unfortunate distraction and the productive way forward is merely to redouble the efforts to create the next versions of the standards.<br /> <br /> = Issues with the document =<br /> <br /> ''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''<br /> <br /> Beyond the controversy described above, there are issues with the Geoservices REST API document itself. Even if the standard deserves support, these issues could be considered blockers to the adoption of the current, May 2013, document.<br /> <br /> The critique is incomplete because it quickly falls into a full editorial review of the text, something which takes a lot of time and effort and is beyond the scope and intent of this Open Letter.<br /> <br /> The critique can be found at: http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique.<br /> <br /> Note that some of these critiques hold the document to OGC's current, standards writing guidelines. The OGC has been striving to develop better standards so new standards must meet higher requirements than past standards. The lack of clarity in the proposed document is not substantially worse than many published standards but ought to be resolved in new standards.<br /> <br /> = Further Concerns =<br /> --- DRAFT ____<br /> <br /> ''Please add concerns not addressed above as bullet points below. Where appropriate, link to external web pages (such as email achieves). Try to be concise, and try not to repeat concepts which have been covered above, (less words get read by more people). Points you have previously added, which are now covered above should be removed. Words that have been struck out will be removed by Tuesday 14 May.''<br /> <br /> == Political Concerns ==<br /> <br /> * &lt;strike&gt;Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.&lt;/strike&gt;<br /> * &lt;strike&gt;It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a newcomer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?&lt;/strike&gt;<br /> <br /> == Commercial Concerns ==<br /> <br /> * &lt;strike&gt;Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.&lt;/strike&gt;<br /> * &lt;strike&gt;Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.&lt;/strike&gt;<br /> * &lt;strike&gt;Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.&lt;/strike&gt;<br /> * &lt;strike&gt;Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.&lt;/strike&gt;<br /> <br /> == Technical Concerns ==<br /> <br /> * &lt;strike&gt;The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.&lt;/strike&gt;<br /> * The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.<br /> * &lt;strike&gt;The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.&lt;/strike&gt;<br /> * see [http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique#The_Technical_Approach this discussion] for detailed arguments why OGC WCS is superior to the &quot;GeoServices REST API&quot; Part 6. It concludes: ''In summary, the ESRI &quot;Geoservice REST API&quot; Imaging part is at a technological level where WCS departed from some 5 years ago. Inconciseness of the specification at large will make it difficult for third parties to come up with interoperable implementations. The components making up the ESRI &quot;Geoservice REST API&quot; provide natural blocks assignable to the matching SWGs. As for Part 6 of the ESRI &quot;Geoservice REST API&quot;, if to become a standard it needs to be discussed in the WCS.SWG for harmonization, clarification, and improvement.''<br /> <br /> == Methodological Concerns ==<br /> <br /> # Ten months after submitting, no public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.<br /> # The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.<br /> # OGC standards normally require interoperability experiments and a richer process to ratify a standard such as this one. No explanation has been forthcoming as to why a simplified process is appropriate in this case.<br /> <br /> A response (from Adrian Custer):<br /> <br /> # The OGC is working to release those documents to the public as of 9 May 2013.<br /> # Work on the next version of the document can take any perspective acceptable to those working on the document. (The OGC has no method in place in case two groups want to evolve the document in two different directions.)<br /> # That is not true, the OGC does not require interoperability experiments or some &quot;richer process&quot; for the adoption of a standard; that may be desirable but is not required.<br /> <br /> = Further Reading =<br /> ''Please add links to referenced documents, related news stories or blog posts here.''<br /> * Call for comments on GeoServices REST API: http://www.opengeospatial.org/standards/requests/89<br /> * Email archive of OSGeo discussions about GeoServices REST API: http://lists.osgeo.org/pipermail/discuss/2013-May/thread.html<br /> * Adrian Custer's summary of technical issues (and original source of some content in this letter): http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html<br /> * &quot;Is OGC Loosing its way?&quot;, letter to OGC Voters, from OGC Interoperability Movement Team Leaders, http://lists.osgeo.org/pipermail/discuss/2013-May/011632.html<br /> <br /> [[Category: OGC]]<br /> [[Category: Standards]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=MapProxy&diff=67892 2012-12-09T15:26:48Z

<p>Wiki-Olt: </p> <hr /> <div>== Basic Project Data ==<br /> *'''Project Name:''' MapProxy<br /> *'''Project Status Condition:''' Stable<br /> *'''Project Web Site:''' http://mapproxy.org<br /> *'''Project Contact:''' Oliver Tonnhofer &lt;olt at omniscale.de&gt;<br /> *'''Short Project Description:''' MapProxy is a tile cache and WMS proxy.<br /> <br /> == Project Infrastructure ==<br /> *'''Project Source Code:''' https://github.com/mapproxy/mapproxy<br /> *'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/mapproxy<br /> *'''Project Version Control Repository:''' git://github.com/mapproxy/mapproxy.git<br /> *'''Project Bug Tracker:''' https://github.com/mapproxy/mapproxy/issues<br /> *'''Project Feature Request Tracker:''' ditto<br /> <br /> == Project Governance ==<br /> *'''Source Code License:''' [http://www.apache.org/licenses/LICENSE-2.0.html Apache License 2.0]<br /> *'''Documentation License:''' ditto<br /> *'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the Apache License 2.0 without explicit assignment (see [http://www.apache.org/licenses/LICENSE-2.0.html license])<br /> *'''Decision Making Procedure:''' [http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life BDFL], at least for now.<br /> *'''Coding Standards:''' [http://www.python.org/dev/peps/pep-0008/ PEP8]<br /> *'''Release Procedure:''' Major/minor releases. Beta and release candidates as necessary.<br /> <br /> == Project Deliverables ==<br /> *'''Latest Project Release:''' http://pypi.python.org/pypi/MapProxy<br /> <br /> [[Category: OSGeo Labs]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Bolsena_Code_Sprint_2012&diff=62201 2012-04-23T08:55:19Z

<p>Wiki-Olt: /* Network links */</p> <hr /> <div>== OSGeo Hacking event in a monastery near Bolsena (10-16 June 2012) ==<br /> ; [[Event Owner]]: [[User:ticheler | Jeroen Ticheler]]<br /> ; When: [http://www.osgeo.org/node/1221 10-16 June 2012] (Note: Date change!)<br /> ; Where: [http://tinyurl.com/2t6zby Bolsena - Italy]<br /> ; Agenda: [[Agenda 2012]]<br /> ; Previous years: [[OSGeo Hacking event|2008]], [[Bolsena Code Sprint 2009|2009]], [[Bolsena Code Sprint 2010|2010]] and [[Bolsena Code Sprint 2011|2011]]<br /> <br /> <br /> After four successful years, we'll continue the OSGeo &quot;hacking&quot; event in Bolsena in an [http://www.conventobolsena.org/ Italian monastery] ([http://tinyurl.com/2t6zby see map location], and videos: [http://www.youtube.com/watch?v=9wrZrK64UIw 2008-video], [http://www.youtube.com/watch?v=Mxox3AsjH6Q 2009-video] and [http://www.youtube.com/watch?v=8Vjx06Rlols 2010-video]. The monastery is overlooking Lago Bolsena and offers space to about 25 people in small bedrooms :-) . It is one of the coolest places for such an event. Quiet, isolated, simple and serene. There's a good wireless and wired internet connection, further improved this year. It should be perfect for SVN, IRC and mail. Have a look yourself, including looking at the photo gallery.<br /> For what the food concerns, we will have a cook who will take care of us :-) . There's a large dining space, but we will eat outside overlooking the lake if weather permits (very likely in June).<br /> <br /> The all inclusive cost will be 550 Euro (Excl VAT) per person for the full week. You can stay all seven days and food (breakfast, lunch and dinner) is included in the price. As in previous years, we will go out for a city visit and a dinner on one of the evenings (also included).<br /> <br /> The event will take place during the whole week (7 days), although the emphasis will probably be Monday to Friday for most participants.<br /> Please contact me if you have questions about this event ([[User:ticheler |Jeroen Ticheler]])<br /> <br /> == Network links ==<br /> <br /> IRC channel: #bolsena at freenode<br /> <br /> <br /> === Registered Attendees ===<br /> <br /> Those participating, you will need to make the payment of 550 Euro (Excl VAT) in advance to GeoCat bv to guarantee your place. Please contact me by email so I can send you the invoice and bank details. I've no problems if you later need to change as long as you make sure there's someone taking your place :-)<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; class=&quot;wikitable sortable&quot;<br /> !width=&quot;30&quot;|No<br /> !width=&quot;250&quot;|Name<br /> !width=&quot;250&quot;|Projects<br /> !width=&quot;150&quot;|single/double room?<br /> !width=&quot;150&quot;|Confirmed/tentative?<br /> !width=&quot;150&quot;|Advance paid?<br /> !width=&quot;250&quot;|Leaving at:<br /> |-<br /> | 1 ||[[User:ticheler|Jeroen Ticheler]] || [[GeoNetwork]] &amp; [[Marketing]] || double || confirmed || x ||<br /> |-<br /> | 2 ||[[User:alfonx|Stefan Tzeggai]] || Geopublisher &amp; AtlasStyler || single || confirmed || ||<br /> |-<br /> | 3 ||[[User:stranger|Andreas Schmitz]] || deegree || single || confirmed || ||<br /> |-<br /> | 4 ||[[User:genuchten|Paul van Genuchten]] || GeoNetwork &amp; Inspire || single || confirmed || ||<br /> |-<br /> | 5 ||[[User:jeichar|Jesse EIchar]]|| GeoNetwork || single || confirmed || ||<br /> |-<br /> | 6 ||[[User:Just|Just van den Broecke]]||Heron MC and NLExtract || single || confirmed || ||<br /> |-<br /> | 7 ||[[User:MarkusSchneider|Markus Schneider]] || deegree || single || confirmed || ||<br /> |-<br /> | 8 ||Francois Prunayre || GeoNetwork || single || confirmed || ||<br /> |-<br /> | 9 ||Jose Garcia || GeoNetwork || single || confirmed || ||<br /> |-<br /> | 10 ||[[User:vmische|Volker Mische]] || GeoCouch, MapQuery, Couchbase, CouchDB || single || confirmed || ||<br /> |-<br /> | 11 ||Oliver Tonnhofer|| MapProxy, Imposm || single || confirmed || ||<br /> |-<br /> | 12 ||Christian Wygoda|| Mapbender, MapQuery || single || confirmed || ||<br /> |-<br /> | 13 ||[[User:Uli | Uli Rothstein]]|| Mapbender || single || confirmed || ||<br /> |-<br /> | 14 ||Matthijs Laan||Flamingo-mc, B3P GisSuite, Kaartenbalie, OpenLayers || single || confirmed|| ||<br /> |-<br /> | 15 ||[[User:Mtoonen | Meine Toonen ]]||Flamingo-mc, B3P GisSuite, Kaartenbalie,OpenLayers || single || confirmed|| ||<br /> |-<br /> | 16 ||[[User:Rbraam | Roy Braam ]]||Flamingo-mc, B3P GisSuite, Kaartenbalie,OpenLayers || single || confirmed|| ||<br /> |-<br /> | 16 ||Hue Dang ||Geocat Bridge || single || confirmed|| ||<br /> |-<br /> | N ||''copy and paste this to add yourself''|| || single/double || confirmed/tentative || ||<br /> |-<br /> |}<br /> <br /> : [1] there are options to do outdoor activities like tracking. A guide can be organized and the cost is very reasonable.<br /> <br /> === Sponsoring ===<br /> We are always welcoming sponsors!<br /> <br /> === How to arrive to the Monastery ===<br /> <br /> The closest airports are the Roma airports (Ciampino and Fiumincino).<br /> <br /> From Rome to the monastery there is 135 km aproximately.<br /> <br /> There is no railway to Bolsena.<br /> <br /> From Fiumicino to Rome you can take the train [http://www.adr.it/content.asp?Subc=1363&amp;L=1&amp;idMen=731 METROPOLITANO FR1].<br /> <br /> From Rome you can take a bus (cotral http://www.cotralspa.it/ENG/capolinea.asp) to Viterbo and other bus from viterbo to Bolsena (9am &amp; 7.30pm).<br /> <br /> Alternatively you can take a train from Rome to Orvieto and take a taxi from Orvieto to Bolsena. Orvieto Taxi info: <br /> 1) Paolo of 'Gulliver Taxi' gullirent@alice.it tel 0763 302969 or mobile 330 477399. <br /> 2) Luigi gigitaxi@libero.it tel 338 9790846. Luigi speaks limited English<br /> 3) OrvietoTaxi : http://www.orvietotaxi.it simone@orvietotaxi.it is a good option (by Just)<br /> <br /> Monday to Friday there is a bus each hour but Sunday there are very few buses.<br /> <br /> From Bolsena main street to the Monastery is aproximately 1 km.<br /> <br /> It could be interesting to rent a private bus or several cars to move from Rome to the Monastery and from the Monastery to Rome.<br /> <br /> If you are interested in share vehicle please add your name to the following table and the columns you need for new ideas.<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; class=&quot;wikitable&quot;<br /> !width=&quot;250&quot;|Name<br /> !width=&quot;150&quot;|I prefer to rent a bus<br /> !width=&quot;150&quot;|I prefer to share rented car<br /> !width=&quot;150&quot;|I prefer to get a ride if you have a car<br /> !width=&quot;150&quot;|I'll go with my car and I have free seats<br /> !width=&quot;150&quot;|I'll go by train<br /> |-<br /> |''Stefan Tzeggai''|| || X || || || |<br /> |-<br /> |''Roy Braam, Matthijs Laan, Meine Toonen''|| || x || || || |<br /> |-<br /> |''Paul van Genuchten, Hue Dang''|| || x (ciampino, su 16.30) || || || |<br /> |-<br /> |''Volker, Oliver''|| || || || || x (Fiumicino, Su ~12:30) ||<br /> |-<br /> |''copy and paste this to add yourself''|| || || || || |<br /> |}<br /> <br /> === How to get back home ===<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; class=&quot;wikitable&quot;<br /> !width=&quot;250&quot;|Name<br /> !width=&quot;150&quot;|I prefer to rent a bus<br /> !width=&quot;150&quot;|I prefer to share rented car<br /> !width=&quot;150&quot;|I prefer to get a ride if you have a car<br /> !width=&quot;150&quot;|I'll go with my car and I have free seats<br /> !width=&quot;150&quot;|I'll go by train<br /> |-<br /> |''Roy Braam, Matthijs Laan, Meine Toonen''|| || x || || || |<br /> |-<br /> |''Paul van Genuchten, Hue Dang''|| || x (ciampino, sa 13.50) || || || |<br /> |-<br /> |''Volker, Oliver''|| || || || || x (Fiumicino, Sa ~15:00) ||<br /> |-<br /> |''copy and paste this to add yourself''|| || || || || |<br /> |}<br /> <br /> === Resources ===<br /> <br /> === Photo's ===<br /> <br /> [[Category:Events]]<br /> [[Category:Code Sprints]]<br /> [[Category:Bolsena]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Bolsena_Code_Sprint_2012&diff=61277 2012-03-14T10:54:11Z

<p>Wiki-Olt: </p> <hr /> <div>== OSGeo Hacking event in a monastery near Bolsena (10-16 June 2012) ==<br /> ; [[Event Owner]]: [[User:ticheler | Jeroen Ticheler]]<br /> ; When: [http://www.osgeo.org/node/1221 10-16 June 2012] (Note: Date change!)<br /> ; Where: [http://tinyurl.com/2t6zby Bolsena - Italy]<br /> ; Agenda: [[Agenda 2012]]<br /> ; Previous years: [[OSGeo Hacking event|2008]], [[Bolsena Code Sprint 2009|2009]], [[Bolsena Code Sprint 2010|2010]] and [[Bolsena Code Sprint 2011|2011]]<br /> <br /> <br /> After four successful years, we'll continue the OSGeo &quot;hacking&quot; event in Bolsena in an [http://www.conventobolsena.org/ Italian monastery] ([http://tinyurl.com/2t6zby see map location], and videos: [http://www.youtube.com/watch?v=9wrZrK64UIw 2008-video], [http://www.youtube.com/watch?v=Mxox3AsjH6Q 2009-video] and [http://www.youtube.com/watch?v=8Vjx06Rlols 2010-video]. The monastery is overlooking Lago Bolsena and offers space to about 25 people in small bedrooms :-) . It is one of the coolest places for such an event. Quiet, isolated, simple and serene. There's a good wireless and wired internet connection, further improved this year. It should be perfect for SVN, IRC and mail. Have a look yourself, including looking at the photo gallery.<br /> For what the food concerns, we will have a cook who will take care of us :-) . There's a large dining space, but we will eat outside overlooking the lake if weather permits (very likely in June).<br /> <br /> The all inclusive cost will be 550 Euro (Excl VAT) per person for the full week. You can stay all seven days and food (breakfast, lunch and dinner) is included in the price. As in previous years, we will go out for a city visit and a dinner on one of the evenings (also included).<br /> <br /> The event will take place during the whole week (7 days), although the emphasis will probably be Monday to Friday for most participants.<br /> Please contact me if you have questions about this event ([[User:ticheler |Jeroen Ticheler]])<br /> <br /> == Network links ==<br /> <br /> IRC channel: #bolsena at freenode<br /> <br /> <br /> === Registered Attendees ===<br /> <br /> Those participating, you will need to make the payment of 550 Euro (Excl VAT) in advance to GeoCat bv to guarantee your place. Please contact me by email so I can send you the invoice and bank details. I've no problems if you later need to change as long as you make sure there's someone taking your place :-)<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; class=&quot;wikitable sortable&quot;<br /> !width=&quot;30&quot;|No<br /> !width=&quot;250&quot;|Name<br /> !width=&quot;250&quot;|Projects<br /> !width=&quot;150&quot;|single/double room?<br /> !width=&quot;150&quot;|Confirmed/tentative?<br /> !width=&quot;150&quot;|Advance paid?<br /> !width=&quot;250&quot;|Leaving at:<br /> |-<br /> | 1 ||[[User:ticheler|Jeroen Ticheler]] || [[GeoNetwork]] &amp; [[Marketing]] || double || confirmed || x ||<br /> |-<br /> | 2 ||[[User:alfonx|Stefan Tzeggai]] || Geopublisher &amp; AtlasStyler || single || confirmed || ||<br /> |-<br /> | 3 ||[[User:stranger|Andreas Schmitz]] || deegree || single || confirmed || ||<br /> |-<br /> | 4 ||[[User:genuchten|Paul van Genuchten]] || GeoNetwork &amp; Inspire || single || confirmed || ||<br /> |-<br /> | 5 ||[[User:jeichar|Jesse EIchar]]|| GeoNetwork || single || confirmed || ||<br /> |-<br /> | 6 ||[[User:Just|Just van den Broecke]]||Heron MC and NLExtract || single || confirmed || ||<br /> |-<br /> | 7 ||[[User:MarkusSchneider|Markus Schneider]] || deegree || single || confirmed || ||<br /> |-<br /> | 8 ||Francois Prunayre || GeoNetwork || single || confirmed || ||<br /> |-<br /> | 9 ||Jose Garcia || GeoNetwork || single || confirmed || ||<br /> |-<br /> | 10 ||[[User:vmische|Volker Mische]] || GeoCouch, MapQuery, Couchbase, CouchDB || single || confirmed || ||<br /> |-<br /> | 11 ||Oliver Tonnhofer|| MapProxy, Imposm || single || confirmed || ||<br /> |-<br /> | N ||''copy and paste this to add yourself''|| || single/double || confirmed/tentative || ||<br /> |-<br /> |}<br /> <br /> : [1] there are options to do outdoor activities like tracking. A guide can be organized and the cost is very reasonable.<br /> <br /> === Sponsoring ===<br /> We are always welcoming sponsors!<br /> <br /> === How to arrive to the Monastery ===<br /> <br /> The closest airports are the Roma airports (Ciampino and Fiumincino).<br /> <br /> From Rome to the monastery there is 135 km aproximately.<br /> <br /> There is no railway to Bolsena.<br /> <br /> From Fiumicino to Rome you can take the train [http://www.adr.it/content.asp?Subc=1363&amp;L=1&amp;idMen=731 METROPOLITANO FR1].<br /> <br /> From Rome you can take a bus (cotral http://www.cotralspa.it/ENG/capolinea.asp) to Viterbo and other bus from viterbo to Bolsena (9am &amp; 7.30pm).<br /> <br /> Alternatively you can take a train from Rome to Orvieto and take a taxi from Orvieto to Bolsena. Orvieto Taxi info: <br /> 1) Paolo of 'Gulliver Taxi' gullirent@alice.it tel 0763 302969 or mobile 330 477399. <br /> 2) Luigi gigitaxi@libero.it tel 338 9790846. Luigi speaks limited English<br /> 3) OrvietoTaxi : http://www.orvietotaxi.it simone@orvietotaxi.it is a good option (by Just)<br /> <br /> Monday to Friday there is a bus each hour but Sunday there are very few buses.<br /> <br /> From Bolsena main street to the Monastery is aproximately 1 km.<br /> <br /> It could be interesting to rent a private bus or several cars to move from Rome to the Monastery and from the Monastery to Rome.<br /> <br /> If you are interested in share vehicle please add your name to the following table and the columns you need for new ideas.<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; class=&quot;wikitable&quot;<br /> !width=&quot;250&quot;|Name<br /> !width=&quot;150&quot;|I prefer to rent a bus<br /> !width=&quot;150&quot;|I prefer to share rented car<br /> !width=&quot;150&quot;|I prefer to get a ride if you have a car<br /> !width=&quot;150&quot;|I'll go with my car and I have free seats<br /> |-<br /> |''Stefan Tzeggai''|| || X || || |<br /> |-<br /> |''copy and paste this to add yourself''|| || || || |<br /> |}<br /> <br /> === How to get back home ===<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; class=&quot;wikitable&quot;<br /> !width=&quot;250&quot;|Name<br /> !width=&quot;150&quot;|I prefer to rent a bus<br /> !width=&quot;150&quot;|I prefer to share rented car<br /> !width=&quot;150&quot;|I prefer to get a ride if you have a car<br /> !width=&quot;150&quot;|I'll go with my car and I have free seats<br /> |-<br /> |''copy and paste this to add yourself''|| || || || |<br /> |}<br /> <br /> === Resources ===<br /> <br /> === Photo's ===<br /> <br /> [[Category:Events]]<br /> [[Category:Code Sprints]]<br /> [[Category:Bolsena]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=MapProxy_Incubation_Application&diff=60300 2012-01-30T12:45:25Z

<p>Wiki-Olt: /* MapProxy Incubation Application */</p> <hr /> <div>= MapProxy Incubation Application =<br /> <br /> Mailing list discussion: http://lists.osgeo.org/pipermail/incubator/2012-January/001747.html<br /> <br /> Ticket: http://trac.osgeo.org/osgeo/ticket/851<br /> <br /> == Questionnaire ==<br /> <br /> === Please provide the name and email address of the principal Project Owner. ===<br /> <br /> Oliver Tonnhofer, olt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> <br /> === Please provide the names, emails and entity affiliation of all official committers ===<br /> <br /> * Oliver Tonnhofer, olt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> * Dominik Helle, helle&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> * Marcel Radischat, radischadt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> <br /> === Please describe your Project. ===<br /> <br /> MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.<br /> <br /> MapProxy is a tile cache solution, but also offers many new and innovative features like full support for WMS clients and a powerful authorization API.<br /> <br /> === Why is hosting at OSGeo good for your project? ===<br /> <br /> We believe that OSGeo is a powerful brand in the geo-spatial software world and that the MapProxy project would benefit from this brand. We hope that this will convince even more people that MapProxy is an open and sustainable project.<br /> <br /> On the other hand, MapProxy fits in well in the OSGeo software stack. It can be used in combination with other software like MapServer, GeoServer, OpenLayers, QGIS, etc and this has been demonstrated on the last OSGeo LiveDVD.<br /> <br /> === Type of application does this project represent(client, server, standalone, library, etc.): ===<br /> <br /> Server/proxy application.<br /> <br /> === Please describe any relationships to other open source projects. ===<br /> <br /> MapProxy is written in Python and uses multiple open source libraries, from Python Image Library to GDAL, Proj4 and GEOS.<br /> <br /> === Please describe any relationships with commercial companies or products. ===<br /> <br /> Development was started by Omniscale and most development is still done by Omniscale today. There are no commercial versions of MapProxy available (no dual-licensing, etc.).<br /> <br /> === Which open source license(s) will the source code be released under? ===<br /> <br /> The source code is already released under the Apache License 2.0.<br /> <br /> === Is there already a beta or official release? ===<br /> <br /> The first official release was made in March 2010 and there were 18 official releases in the last 20 month. Six of them were releases with new (major) features. We offer backwards compatibility between releases since the release of version 1.0.0.<br /> <br /> === What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? ===<br /> <br /> The project started as a commercial product by Omniscale and was open sourced in March 2010.<br /> <br /> === Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? ===<br /> <br /> It implements various open standards like WMS, WMTS, KML, and TMS.<br /> <br /> === Is the code free of patents, trademarks, and do you control the copyright? ===<br /> <br /> The code does not contain anything where we have patents on and we are not aware of any other existing patents. The Apache License also contains a patent clause.<br /> <br /> MapProxy is not a registered trademark.<br /> <br /> All rights are held by Omniscale, with the exception of a few modules that are included in MapProxy. These modules are under a BSD-ish licenses, included in separate files. Copyright is documented in COPYING.txt, see https://bitbucket.org/olt/mapproxy/raw/default/COPYING.txt<br /> <br /> === How many people actively contribute (code, documentation, other?) to the project at this time? ===<br /> <br /> Most code is contributed by Omniscale, with only a few smaller patches from other people. <br /> We received monetary contributions from various companies in the last two years to implement new features for MapProxy. A few of these companies are also active contributors in other OSGeo projects.<br /> <br /> But the codebase of MapProxy is also not very large, with only 11k lines of code (23k in total with 10k lines of tests and 2k for external modules distributed with MapProxy).<br /> <br /> === How many people have commit access to the source code repository? ===<br /> <br /> We use a distributed version control system, so anybody can fork the project and provide code. <br /> <br /> === How many users do you expect to download the project when it is released? ===<br /> === Approximately how many users are currently using this project? ===<br /> <br /> We have an active mailing list with 140 subscribers (as of January 2012) and the past releases where downloaded nearly 10000 times.<br /> <br /> We know from conferences, mailing lists and business contacts, that MapProxy is used by a lot of open source GIS companies. Especially in Germany, were we are active in the local chapter (FOSSGIS e.V.).<br /> <br /> === What type of users does your project attract (government, commercial, hobby, academic research, etc. )? ===<br /> <br /> Mostly government, but also commercial and academic users.<br /> <br /> === If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation? ===<br /> <br /> Our mailing list is already hosted by OSGeo as a OSGeo Lab project. We do not use SVN and we do not intend to switch to it. We are using Mercurial for our source code repositories and we might switch to Git in the future.<br /> <br /> === Does the project include an automated build and test? ===<br /> <br /> We have an extensive test suite with over 1000 unit and system tests. We have a continuous integration server that runs all these tests automatically with different Python versions. (http://ci.mapproxy.org/)<br /> <br /> Documentation is build nightly and there are packages with the latest source code available.<br /> <br /> === What language(s) are used in this project? (C/Java/perl/etc) ===<br /> <br /> Python and it makes use of libraries written in C (Proj4, GDAL, ...)<br /> <br /> === What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? ===<br /> <br /> All source code, comments and documentation is written in English.<br /> <br /> === What is the (estimated) size of a full release of this project? ===<br /> <br /> Should fit on a floppy.</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=MapProxy_Incubation_Application&diff=60274 2012-01-30T08:53:25Z

<p>Wiki-Olt: Created page with &quot;= MapProxy Incubation Application = == Questionnaire == === Please provide the name and email address of the principal Project Owner. === Oliver Tonnhofer, olt&lt;ät&gt;omniscale.d...&quot;</p> <hr /> <div>= MapProxy Incubation Application =<br /> <br /> == Questionnaire ==<br /> <br /> === Please provide the name and email address of the principal Project Owner. ===<br /> <br /> Oliver Tonnhofer, olt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> <br /> === Please provide the names, emails and entity affiliation of all official committers ===<br /> <br /> * Oliver Tonnhofer, olt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> * Dominik Helle, helle&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> * Marcel Radischat, radischadt&lt;ät&gt;omniscale.de, Omniscale GmbH &amp; Co. KG<br /> <br /> === Please describe your Project. ===<br /> <br /> MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.<br /> <br /> MapProxy is a tile cache solution, but also offers many new and innovative features like full support for WMS clients and a powerful authorization API.<br /> <br /> === Why is hosting at OSGeo good for your project? ===<br /> <br /> We believe that OSGeo is a powerful brand in the geo-spatial software world and that the MapProxy project would benefit from this brand. We hope that this will convince even more people that MapProxy is an open and sustainable project.<br /> <br /> On the other hand, MapProxy fits in well in the OSGeo software stack. It can be used in combination with other software like MapServer, GeoServer, OpenLayers, QGIS, etc and this has been demonstrated on the last OSGeo LiveDVD.<br /> <br /> === Type of application does this project represent(client, server, standalone, library, etc.): ===<br /> <br /> Server/proxy application.<br /> <br /> === Please describe any relationships to other open source projects. ===<br /> <br /> MapProxy is written in Python and uses multiple open source libraries, from Python Image Library to GDAL, Proj4 and GEOS.<br /> <br /> === Please describe any relationships with commercial companies or products. ===<br /> <br /> Development was started by Omniscale and most development is still done by Omniscale today. There are no commercial versions of MapProxy available (no dual-licensing, etc.).<br /> <br /> === Which open source license(s) will the source code be released under? ===<br /> <br /> The source code is already released under the Apache License 2.0.<br /> <br /> === Is there already a beta or official release? ===<br /> <br /> The first official release was made in March 2010 and there were 18 official releases in the last 20 month. Six of them were releases with new (major) features. We offer backwards compatibility between releases since the release of version 1.0.0.<br /> <br /> === What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? ===<br /> <br /> The project started as a commercial product by Omniscale and was open sourced in March 2010.<br /> <br /> === Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? ===<br /> <br /> It implements various open standards like WMS, WMTS, KML, and TMS.<br /> <br /> === Is the code free of patents, trademarks, and do you control the copyright? ===<br /> <br /> The code does not contain anything where we have patents on and we are not aware of any other existing patents. The Apache License also contains a patent clause.<br /> <br /> MapProxy is not a registered trademark.<br /> <br /> All rights are held by Omniscale, with the exception of a few modules that are included in MapProxy. These modules are under a BSD-ish licenses, included in separate files. Copyright is documented in COPYING.txt, see https://bitbucket.org/olt/mapproxy/raw/default/COPYING.txt<br /> <br /> === How many people actively contribute (code, documentation, other?) to the project at this time? ===<br /> <br /> Most code is contributed by Omniscale, with only a few smaller patches from other people. <br /> We received monetary contributions from various companies in the last two years to implement new features for MapProxy. A few of these companies are also active contributors in other OSGeo projects.<br /> <br /> But the codebase of MapProxy is also not very large, with only 11k lines of code (23k in total with 10k lines of tests and 2k for external modules distributed with MapProxy).<br /> <br /> === How many people have commit access to the source code repository? ===<br /> <br /> We use a distributed version control system, so anybody can fork the project and provide code. <br /> <br /> === How many users do you expect to download the project when it is released? ===<br /> === Approximately how many users are currently using this project? ===<br /> <br /> We have an active mailing list with 140 subscribers (as of January 2012) and the past releases where downloaded nearly 10000 times.<br /> <br /> We know from conferences, mailing lists and business contacts, that MapProxy is used by a lot of open source GIS companies. Especially in Germany, were we are active in the local chapter (FOSSGIS e.V.).<br /> <br /> === What type of users does your project attract (government, commercial, hobby, academic research, etc. )? ===<br /> <br /> Mostly government, but also commercial and academic users.<br /> <br /> === If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation? ===<br /> <br /> Our mailing list is already hosted by OSGeo as a OSGeo Lab project. We do not use SVN and we do not intend to switch to it. We are using Mercurial for our source code repositories and we might switch to Git in the future.<br /> <br /> === Does the project include an automated build and test? ===<br /> <br /> We have an extensive test suite with over 1000 unit and system tests. We have a continuous integration server that runs all these tests automatically with different Python versions. (http://ci.mapproxy.org/)<br /> <br /> Documentation is build nightly and there are packages with the latest source code available.<br /> <br /> === What language(s) are used in this project? (C/Java/perl/etc) ===<br /> <br /> Python and it makes use of libraries written in C (Proj4, GDAL, ...)<br /> <br /> === What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? ===<br /> <br /> All source code, comments and documentation is written in English.<br /> <br /> === What is the (estimated) size of a full release of this project? ===<br /> <br /> Should fit on a floppy.</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=56887 2011-08-31T15:06:10Z

<p>Wiki-Olt: /* Importing */ mention --optimize/autovacuum</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> pip install imposm<br /> <br /> To install the &quot;trunk&quot; version change the last line from above with:<br /> <br /> pip install https://bitbucket.org/olt/imposm/get/default.tar.gz<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache --proj epsg:3857<br /> <br /> <br /> The ''--optimize'' option calls ''VACUUM ANALYZE'' on all tables. Autovacuum can be disabled in PostgreSQL (and is).<br /> <br /> And that's it:<br /> <br /> [[File:Imposm-db-denver.png]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Breakout_Sessions&diff=56764 2011-08-25T07:19:35Z

<p>Wiki-Olt: /* Proposed Topics */</p> <hr /> <div>= Introduction =<br /> During the [http://2011.foss4g.org/ FOSS4G2011 conference] in Denver, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).<br /> <br /> Breakout Sessions are unstructured timeslots where people can self-organize themselves to discuss topics of interest.<br /> <br /> '''Room allocation to be determined'''<br /> <br /> == Organising Contact ==<br /> <br /> == Timeslots Available ==<br /> <br /> Wednesday 5:30pm to 6:30pm and 7:00pm to 8:00pm<br /> <br /> = Room Assignments =<br /> <br /> == Rooms Available ==<br /> <br /> = Proposed Topics =<br /> <br /> *'''Tiling''' <br /> **Proposed Topics <br /> ***standardised sqlite schema for tile caches <br /> ***TMS/WMTS evolutions: <br /> ****Tile merging (i.e. equivalent of WMS LAYERS=baselayer,overlaylayer) <br /> ****TMS multiple grids per tileset <br /> ****WMTS multiple url endpoints (eg tile1.domain.tld, tile2.domain.tld...): is this still needed now that browsers allow many more connections per server? <br /> ***add yours... <br /> **Attending: <br /> ***[[User:Tbonfort]] <br /> ***[[User:Olt|Oliver Tonnhofer (Omniscale, MapProxy)]]<br /> ***[[User:stvn|Steven M. Ottens]]<br /> <br /> *'''GeoNode''' <br /> **Proposed topics: <br /> ***Brief overview <br /> ***Get involved with the community! <br /> ***Meet developers and institutional partners <br /> ****Opportunities for work around the world, especially in South America and Indonesia <br /> ****Positions available at the World Bank and OpenGeo <br /> **Attending: <br /> ***Rolando Peñate (OpenGeo) <br /> ***David Winslow (OpenGeo) <br /> ***Robert Soden (World Bank) <br /> ***Ariel Nuñez (World Bank) <br /> ***Seb Benthall (UC Berkeley) <br /> ***Matt Bertrand (Harvard University) <br /> ***Sachindra Singh (SOPAC) <br /> ***[[User:Ortelius|Jeffrey Johnson (OpenGeo)]] <br /> ***Jubal Harpster (SpatialDev)<br /> ***[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]<br /> ***[[User:Wildintellect|Alex Mandel (UC Davis)]]<br /> <br /> *'''Python''' <br /> **Proposed topics: <br /> ***High fives <br /> ***Extension modules, Pyrex, Cython, ctypes <br /> ***Python 3 <br /> ***PyPy <br /> ***Packaging and distributions <br /> **Attending: <br /> ***Sean Gillies (NYU, Shapely and friends) <br /> ***[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]] <br /> ***Michael Weisman (Urban Mapping) <br /> ***Derek Hohls (CSIR, South Africa)<br /> ***[[User:Dandye|Dan Dye (WeoGeo)]] <br /> ***[[User:Davidfawcett|David Fawcett (MPCA)]]<br /> ***[[User:Wildintellect|Alex Mandel (UC Davis)]]<br /> ***[[User:hobu|Howard Butler (Hobu, Inc.)]]<br /> ***[[User:olt|Oliver Tonnhofer (Omniscale)]] MapProxy, Imposm, Shapely, etc. I'm in conflict with the tiling BOF, try to come for the high five at least.<br /> <br /> <br /> *Add yours below...<br /> <br /> [[Category:FOSS4G]] [[Category:FOSS4G2011]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Live_GIS_Add_Project&diff=56725 2011-08-23T06:30:05Z

<p>Wiki-Olt: /* Port numbers */</p> <hr /> <div>== What gets into OSGeoLive? ==<br /> <br /> We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.<br /> <br /> Priority for selecting OSGeoLive projects to package is:<br /> # OSGeo Projects<br /> # OSGeo Projects in incubation<br /> # Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G<br /> # Other Stable GeoSpatial Open Source Software with established project communities and a wide user base<br /> # It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&amp;hl=en_GB schedule]<br /> <br /> == Application Questions ==<br /> <br /> Projects need to provide:<br /> * Project Champion<br /> : Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.<br /> * A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.<br /> * [[#Documentation]] in line with OSGeoLive templates<br /> * Someone who will run and verify the applications works in development releases<br /> * [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB Project Status] to be maintained.<br /> <br /> If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.<br /> <br /> == Which version to use? ==<br /> <br /> * Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.<br /> <br /> == Install Script ==<br /> Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.<br /> <br /> All install scripts for building the LiveGIS disc shall be licensed as LGPL.<br /> <br /> When finished, ask the OSGeoLive team to reference your script from ''main.sh''.<br /> <br /> Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/<br /> <br /> The script may be as simple as:<br /> [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just <br /> apt-get install mapserver<br /> <br /> Projects that haven't been packaged for Ubuntu yet are slightly more complicated:<br /> <br /> The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]<br /> <br /> * 3rd Party Repositories: Create an &lt;app&gt;.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like<br /> cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/<br /> <br /> don't forget to add the repository key like so<br /> apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF<br /> <br /> == Packaging conventions ==<br /> <br /> * '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.<br /> : This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.<br /> : Preferred method is to put the &lt;tt&gt;USER_NAME&lt;/tt&gt; and &lt;tt&gt;USER_HOME&lt;/tt&gt; variables at the top, so these can be easily changed in all scripts if needed.<br /> USER_NAME=&quot;user&quot;<br /> USER_HOME=&quot;/home/$USER_NAME&quot;<br /> cp package_readme.txt &quot;$USER_HOME&quot;<br /> <br /> * '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).<br /> : Make sure that nothing is corrupted if the script runs a second time.<br /> <br /> * '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.<br /> <br /> * '''/tmp''': Copy all downloads into /tmp/build_&lt;package&gt;/<br /> : Don't delete the /tmp/build_&lt;package&gt; directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the &quot;BUILD_DIR&quot; environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.<br /> <br /> * '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called &lt;packagename&gt;.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.<br /> : Install &lt;packagename&gt;.png icon files to the /usr/share/icons/ directory.<br /> : see &lt;tt&gt;install_qgis.sh&lt;/tt&gt; for an example<br /> <br /> * '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.<br /> : (Todo: How do we do this?)<br /> <br /> * '''wget''': When downloading large files using wget, use the &quot;-c&quot; continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:<br /> wget -c package.tar.gz<br /> : Do not use -c if there is a chance the file of that name will change on the server. Add &quot;&lt;tt&gt;--progress=dot:mega&lt;/tt&gt;&quot; to the wget command line if the file is at all large.<br /> : Tiny files should use wget's -nv (non-verbose) flag.<br /> : In a similar manner, use &quot;&lt;tt&gt;--quiet&lt;/tt&gt;&quot; when calling '''qsql'''.<br /> <br /> * '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.<br /> mkdir -p &lt;dir&gt;<br /> <br /> * '''Binary files''': Do not put large (&gt;5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.<br /> <br /> = Packaging considerations =<br /> <br /> The criteria used to select applications for the LiveGIS follow.<br /> <br /> == Technical limitations ==<br /> === Space considerations ===<br /> * DVD: approx 4.2gb compressed<br /> * USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)<br /> * Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed<br /> <br /> So smaller apps (&lt;30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.<br /> <br /> === Memory considerations ===<br /> Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.<br /> <br /> The following principles should be followed. <br /> * Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).<br /> * Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.<br /> * Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.<br /> <br /> File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.<br /> <br /> To install a writable data directory or files, change its group to &quot;users&quot; and set the file(s) as group-writable:<br /> <br /> adduser $USER_NAME users<br /> chmod -R g+w /usr/local/share/&lt;packagename&gt;/data/<br /> chown -R root.users /usr/local/share/&lt;packagename&gt;/data/<br /> <br /> and symlink into the user's home directory if necessary.<br /> <br /> Setting files to have universal write permission is strongly discouraged. '''Do not use &quot;''chmod 777 -R''&quot;.'''<br /> <br /> === Shared resources ===<br /> <br /> The disc is a busy place, so we must all play nice and take care not step on each others toes.<br /> <br /> ==== Changes to the base system ====<br /> <br /> Please don't customize any system level infrastructure which other projects may be relying on.<br /> Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!<br /> <br /> ==== Port numbers ====<br /> <br /> To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. &quot;grep -R 8042 doc bin&quot;) and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.<br /> <br /> = Directory Structure =<br /> <br /> # '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.<br /> # '''/usr/lib''' application are usually installed into /usr/lib<br /> # '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin<br /> # '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d<br /> # '''/usr/local/share''' sample data and documentation goes into /usr/local/share<br /> # '''/etc''' config files are stored in /etc<br /> # '''/home/user''' user specific config files or working directories can go into &lt;tt&gt;/home/user/&lt;/tt&gt;. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.<br /> <br /> * ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''<br /> <br /> == .deb Packaging ==<br /> While many packages are installed from a bash script, ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). Next would be packaged into .debs from your own Ubuntu repository. An official Debian package could be used, but we'd have to rebuild it from source (this takes time but is fairly easy; usually these are already sucked in Ubuntu automatically so it isn't an issue).<br /> <br /> If you must build from source, building a .deb package and installing that is preferred to &quot;make install&quot;. If you do need to &quot;make install&quot;, please set the path prefix to /usr/local/ and ''ensure that your package does not introduce namespace conflicts''.<br /> <br /> In practice a number of scripts employ a hybrid approach, with as much as possible installed via official packages, and the occasional plugin compiled from source.<br /> <br /> A base set of build-tools are already included, but if you install a bunch of -dev packages to build your app, make sure that you clean them all up after you are done.<br /> <br /> Using &quot;&lt;tt&gt;gdebi&lt;/tt&gt;&quot; instead of &quot;&lt;tt&gt;dpkg -i&lt;/tt&gt;&quot; can be useful for installing .deb packages manually, as it ensures that all dependencies are also installed.<br /> <br /> == Example Datasets ==<br /> In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script. <br /> <br /> All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).<br /> <br /> There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).<br /> <br /> Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).<br /> <br /> === Natural Earth ===<br /> The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.<br /> <br /> * [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.<br /> ** admin_0_countries<br /> ** admin_1_states_provinces<br /> ** geography_marine_polys<br /> ** geography_regions_elevated_points<br /> ** geography_regions_polys<br /> ** lakes<br /> ** land<br /> ** ocean<br /> ** populated_places_simple<br /> ** rivers_lake_centerlines<br /> ** urban_areas<br /> <br /> * Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*<br /> <br /> === OpenStreetMap ===<br /> OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm<br /> <br /> === North Carolina === <br /> The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.<br /> <br /> The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)<br /> <br /> === Others ===<br /> If you need another type of data for your examples, please discuss this with us.<br /> <br /> == Documentation ==<br /> OSGeo-Live documentation is published at:<br /> ;On OSGeo-Live: http://localhost/ which is stored in /var/www/<br /> ;Stable release: http://live.osgeo.org<br /> ;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html<br /> <br /> === Application Overview ===<br /> <br /> The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/overview/overview.html<br /> <br /> The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/&lt;application&gt;_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst<br /> <br /> The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).<br /> <br /> Overviews also require:<br /> * an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]].<br /> * A project logo as per [[#Logo]]<br /> <br /> Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)<br /> <br /> Once finished, note your project's overview status=&quot;draft&quot; in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to &quot;complete&quot; and is ready for translation.<br /> <br /> === Application Quick Start ===<br /> The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.<br /> <br /> Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.<br /> <br /> Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/&lt;application&gt;_quickstart.rst<br /> <br /> The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:<br /> https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/udig_quickstart.rst<br /> and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html<br /> <br /> In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.<br /> <br /> Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].<br /> <br /> Once finished, note your project's quickstart status=&quot;draft&quot; in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to &quot;complete&quot; and is ready for translation.<br /> <br /> === Logo ===<br /> The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.<br /> <br /> ;Header logo:<br /> :* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos<br /> :* Filename should be &quot;logo-&lt;projectname&gt;.png&quot;<br /> :* Should have a transparent background (not white)<br /> :* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)<br /> :* Should preferably be in PNG format<br /> :* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.<br /> :* Preferably also available as SVG, stored as &quot;logo-&lt;projectname&gt;.svg&quot;<br /> <br /> ;Desktop logo:<br /> :We are still to define the requirements for creating a desktop logo. They will likely include:<br /> :* A 32x32-pixel XPM icon for use by the Debian menus<br /> :* A 48x48-pixel PNG icon for use by freedesktop.org menus<br /> <br /> === Screen Shot ===<br /> Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.<br /> * Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).<br /> * Screen shots should be taken from a 1024x768 display, and stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768<br /> * For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the &quot;Edit&quot; tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.<br /> * Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.<br /> * For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.<br /> <br /> === Extra Documentation ===<br /> Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:<br /> http://localhost/&lt;application&gt;/... or http://live.osgeo.org/&lt;application&gt;/...<br /> <br /> This should typically be achieved by creating a symbolic link from /var/www/&lt;application&gt; to /usr/local/share/doc/&lt;application&gt;<br /> <br /> == Publishing Documentation ==<br /> <br /> The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/<br /> <br /> For a more comprehensive test, set up the reST processor, sphinx:<br /> : (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' &lt;tt&gt;python-sphinx&lt;/tt&gt; ''Debian package'')<br /> <br /> sudo apt-get install python-sphinx<br /> <br /> cd osgeo/livedvd/gisvm/trunk/doc/<br /> make html<br /> <br /> You can then view the results in:<br /> osgeo/livedvd/gisvm/trunk/doc/_build/*.html<br /> <br /> == Testing procedure ==<br /> <br /> Provide test steps for your application as per the [[Live GIS Disc Testing]] wiki page.<br /> <br /> Once the application has been included into a release candidate, ensure the test steps are executed and work on the release candidate. Write up the results as per the [[Live GIS Disc Testing]] wiki page.<br /> <br /> = Translations =<br /> For details on how to translate, refer to [[Live GIS Translate]]<br /> <br /> [[Category: Live-demo]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Live_GIS_Add_Project&diff=56724 2011-08-23T06:29:17Z

<p>Wiki-Olt: /* Port numbers */</p> <hr /> <div>== What gets into OSGeoLive? ==<br /> <br /> We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.<br /> <br /> Priority for selecting OSGeoLive projects to package is:<br /> # OSGeo Projects<br /> # OSGeo Projects in incubation<br /> # Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G<br /> # Other Stable GeoSpatial Open Source Software with established project communities and a wide user base<br /> # It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&amp;hl=en_GB schedule]<br /> <br /> == Application Questions ==<br /> <br /> Projects need to provide:<br /> * Project Champion<br /> : Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.<br /> * A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.<br /> * [[#Documentation]] in line with OSGeoLive templates<br /> * Someone who will run and verify the applications works in development releases<br /> * [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB Project Status] to be maintained.<br /> <br /> If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.<br /> <br /> == Which version to use? ==<br /> <br /> * Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.<br /> <br /> == Install Script ==<br /> Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.<br /> <br /> All install scripts for building the LiveGIS disc shall be licensed as LGPL.<br /> <br /> When finished, ask the OSGeoLive team to reference your script from ''main.sh''.<br /> <br /> Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/<br /> <br /> The script may be as simple as:<br /> [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just <br /> apt-get install mapserver<br /> <br /> Projects that haven't been packaged for Ubuntu yet are slightly more complicated:<br /> <br /> The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]<br /> <br /> * 3rd Party Repositories: Create an &lt;app&gt;.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like<br /> cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/<br /> <br /> don't forget to add the repository key like so<br /> apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF<br /> <br /> == Packaging conventions ==<br /> <br /> * '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.<br /> : This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.<br /> : Preferred method is to put the &lt;tt&gt;USER_NAME&lt;/tt&gt; and &lt;tt&gt;USER_HOME&lt;/tt&gt; variables at the top, so these can be easily changed in all scripts if needed.<br /> USER_NAME=&quot;user&quot;<br /> USER_HOME=&quot;/home/$USER_NAME&quot;<br /> cp package_readme.txt &quot;$USER_HOME&quot;<br /> <br /> * '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).<br /> : Make sure that nothing is corrupted if the script runs a second time.<br /> <br /> * '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.<br /> <br /> * '''/tmp''': Copy all downloads into /tmp/build_&lt;package&gt;/<br /> : Don't delete the /tmp/build_&lt;package&gt; directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the &quot;BUILD_DIR&quot; environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.<br /> <br /> * '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called &lt;packagename&gt;.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.<br /> : Install &lt;packagename&gt;.png icon files to the /usr/share/icons/ directory.<br /> : see &lt;tt&gt;install_qgis.sh&lt;/tt&gt; for an example<br /> <br /> * '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.<br /> : (Todo: How do we do this?)<br /> <br /> * '''wget''': When downloading large files using wget, use the &quot;-c&quot; continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:<br /> wget -c package.tar.gz<br /> : Do not use -c if there is a chance the file of that name will change on the server. Add &quot;&lt;tt&gt;--progress=dot:mega&lt;/tt&gt;&quot; to the wget command line if the file is at all large.<br /> : Tiny files should use wget's -nv (non-verbose) flag.<br /> : In a similar manner, use &quot;&lt;tt&gt;--quiet&lt;/tt&gt;&quot; when calling '''qsql'''.<br /> <br /> * '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.<br /> mkdir -p &lt;dir&gt;<br /> <br /> * '''Binary files''': Do not put large (&gt;5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.<br /> <br /> = Packaging considerations =<br /> <br /> The criteria used to select applications for the LiveGIS follow.<br /> <br /> == Technical limitations ==<br /> === Space considerations ===<br /> * DVD: approx 4.2gb compressed<br /> * USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)<br /> * Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed<br /> <br /> So smaller apps (&lt;30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.<br /> <br /> === Memory considerations ===<br /> Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.<br /> <br /> The following principles should be followed. <br /> * Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).<br /> * Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.<br /> * Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.<br /> <br /> File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.<br /> <br /> To install a writable data directory or files, change its group to &quot;users&quot; and set the file(s) as group-writable:<br /> <br /> adduser $USER_NAME users<br /> chmod -R g+w /usr/local/share/&lt;packagename&gt;/data/<br /> chown -R root.users /usr/local/share/&lt;packagename&gt;/data/<br /> <br /> and symlink into the user's home directory if necessary.<br /> <br /> Setting files to have universal write permission is strongly discouraged. '''Do not use &quot;''chmod 777 -R''&quot;.'''<br /> <br /> === Shared resources ===<br /> <br /> The disc is a busy place, so we must all play nice and take care not step on each others toes.<br /> <br /> ==== Changes to the base system ====<br /> <br /> Please don't customize any system level infrastructure which other projects may be relying on.<br /> Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!<br /> <br /> ==== Port numbers ====<br /> <br /> To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation (i.e. &quot;grep -R 8042 doc bin&quot;) for this port number and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.<br /> <br /> = Directory Structure =<br /> <br /> # '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.<br /> # '''/usr/lib''' application are usually installed into /usr/lib<br /> # '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin<br /> # '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d<br /> # '''/usr/local/share''' sample data and documentation goes into /usr/local/share<br /> # '''/etc''' config files are stored in /etc<br /> # '''/home/user''' user specific config files or working directories can go into &lt;tt&gt;/home/user/&lt;/tt&gt;. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.<br /> <br /> * ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''<br /> <br /> == .deb Packaging ==<br /> While many packages are installed from a bash script, ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). Next would be packaged into .debs from your own Ubuntu repository. An official Debian package could be used, but we'd have to rebuild it from source (this takes time but is fairly easy; usually these are already sucked in Ubuntu automatically so it isn't an issue).<br /> <br /> If you must build from source, building a .deb package and installing that is preferred to &quot;make install&quot;. If you do need to &quot;make install&quot;, please set the path prefix to /usr/local/ and ''ensure that your package does not introduce namespace conflicts''.<br /> <br /> In practice a number of scripts employ a hybrid approach, with as much as possible installed via official packages, and the occasional plugin compiled from source.<br /> <br /> A base set of build-tools are already included, but if you install a bunch of -dev packages to build your app, make sure that you clean them all up after you are done.<br /> <br /> Using &quot;&lt;tt&gt;gdebi&lt;/tt&gt;&quot; instead of &quot;&lt;tt&gt;dpkg -i&lt;/tt&gt;&quot; can be useful for installing .deb packages manually, as it ensures that all dependencies are also installed.<br /> <br /> == Example Datasets ==<br /> In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script. <br /> <br /> All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).<br /> <br /> There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).<br /> <br /> Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).<br /> <br /> === Natural Earth ===<br /> The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.<br /> <br /> * [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.<br /> ** admin_0_countries<br /> ** admin_1_states_provinces<br /> ** geography_marine_polys<br /> ** geography_regions_elevated_points<br /> ** geography_regions_polys<br /> ** lakes<br /> ** land<br /> ** ocean<br /> ** populated_places_simple<br /> ** rivers_lake_centerlines<br /> ** urban_areas<br /> <br /> * Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*<br /> <br /> === OpenStreetMap ===<br /> OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm<br /> <br /> === North Carolina === <br /> The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.<br /> <br /> The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)<br /> <br /> === Others ===<br /> If you need another type of data for your examples, please discuss this with us.<br /> <br /> == Documentation ==<br /> OSGeo-Live documentation is published at:<br /> ;On OSGeo-Live: http://localhost/ which is stored in /var/www/<br /> ;Stable release: http://live.osgeo.org<br /> ;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html<br /> <br /> === Application Overview ===<br /> <br /> The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/overview/overview.html<br /> <br /> The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/&lt;application&gt;_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst<br /> <br /> The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).<br /> <br /> Overviews also require:<br /> * an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]].<br /> * A project logo as per [[#Logo]]<br /> <br /> Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)<br /> <br /> Once finished, note your project's overview status=&quot;draft&quot; in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to &quot;complete&quot; and is ready for translation.<br /> <br /> === Application Quick Start ===<br /> The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.<br /> <br /> Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.<br /> <br /> Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/&lt;application&gt;_quickstart.rst<br /> <br /> The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:<br /> https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/udig_quickstart.rst<br /> and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html<br /> <br /> In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.<br /> <br /> Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].<br /> <br /> Once finished, note your project's quickstart status=&quot;draft&quot; in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to &quot;complete&quot; and is ready for translation.<br /> <br /> === Logo ===<br /> The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.<br /> <br /> ;Header logo:<br /> :* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos<br /> :* Filename should be &quot;logo-&lt;projectname&gt;.png&quot;<br /> :* Should have a transparent background (not white)<br /> :* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)<br /> :* Should preferably be in PNG format<br /> :* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.<br /> :* Preferably also available as SVG, stored as &quot;logo-&lt;projectname&gt;.svg&quot;<br /> <br /> ;Desktop logo:<br /> :We are still to define the requirements for creating a desktop logo. They will likely include:<br /> :* A 32x32-pixel XPM icon for use by the Debian menus<br /> :* A 48x48-pixel PNG icon for use by freedesktop.org menus<br /> <br /> === Screen Shot ===<br /> Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.<br /> * Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).<br /> * Screen shots should be taken from a 1024x768 display, and stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768<br /> * For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the &quot;Edit&quot; tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.<br /> * Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.<br /> * For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.<br /> <br /> === Extra Documentation ===<br /> Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:<br /> http://localhost/&lt;application&gt;/... or http://live.osgeo.org/&lt;application&gt;/...<br /> <br /> This should typically be achieved by creating a symbolic link from /var/www/&lt;application&gt; to /usr/local/share/doc/&lt;application&gt;<br /> <br /> == Publishing Documentation ==<br /> <br /> The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/<br /> <br /> For a more comprehensive test, set up the reST processor, sphinx:<br /> : (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' &lt;tt&gt;python-sphinx&lt;/tt&gt; ''Debian package'')<br /> <br /> sudo apt-get install python-sphinx<br /> <br /> cd osgeo/livedvd/gisvm/trunk/doc/<br /> make html<br /> <br /> You can then view the results in:<br /> osgeo/livedvd/gisvm/trunk/doc/_build/*.html<br /> <br /> == Testing procedure ==<br /> <br /> Provide test steps for your application as per the [[Live GIS Disc Testing]] wiki page.<br /> <br /> Once the application has been included into a release candidate, ensure the test steps are executed and work on the release candidate. Write up the results as per the [[Live GIS Disc Testing]] wiki page.<br /> <br /> = Translations =<br /> For details on how to translate, refer to [[Live GIS Translate]]<br /> <br /> [[Category: Live-demo]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Live_GIS_Add_Project&diff=56723 2011-08-23T06:23:40Z

<p>Wiki-Olt: /* Port numbers */</p> <hr /> <div>== What gets into OSGeoLive? ==<br /> <br /> We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.<br /> <br /> Priority for selecting OSGeoLive projects to package is:<br /> # OSGeo Projects<br /> # OSGeo Projects in incubation<br /> # Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G<br /> # Other Stable GeoSpatial Open Source Software with established project communities and a wide user base<br /> # It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&amp;hl=en_GB schedule]<br /> <br /> == Application Questions ==<br /> <br /> Projects need to provide:<br /> * Project Champion<br /> : Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.<br /> * A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.<br /> * [[#Documentation]] in line with OSGeoLive templates<br /> * Someone who will run and verify the applications works in development releases<br /> * [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB Project Status] to be maintained.<br /> <br /> If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.<br /> <br /> == Which version to use? ==<br /> <br /> * Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.<br /> <br /> == Install Script ==<br /> Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.<br /> <br /> All install scripts for building the LiveGIS disc shall be licensed as LGPL.<br /> <br /> When finished, ask the OSGeoLive team to reference your script from ''main.sh''.<br /> <br /> Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/<br /> <br /> The script may be as simple as:<br /> [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just <br /> apt-get install mapserver<br /> <br /> Projects that haven't been packaged for Ubuntu yet are slightly more complicated:<br /> <br /> The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]<br /> <br /> * 3rd Party Repositories: Create an &lt;app&gt;.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like<br /> cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/<br /> <br /> don't forget to add the repository key like so<br /> apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF<br /> <br /> == Packaging conventions ==<br /> <br /> * '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.<br /> : This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.<br /> : Preferred method is to put the &lt;tt&gt;USER_NAME&lt;/tt&gt; and &lt;tt&gt;USER_HOME&lt;/tt&gt; variables at the top, so these can be easily changed in all scripts if needed.<br /> USER_NAME=&quot;user&quot;<br /> USER_HOME=&quot;/home/$USER_NAME&quot;<br /> cp package_readme.txt &quot;$USER_HOME&quot;<br /> <br /> * '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).<br /> : Make sure that nothing is corrupted if the script runs a second time.<br /> <br /> * '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.<br /> <br /> * '''/tmp''': Copy all downloads into /tmp/build_&lt;package&gt;/<br /> : Don't delete the /tmp/build_&lt;package&gt; directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the &quot;BUILD_DIR&quot; environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.<br /> <br /> * '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called &lt;packagename&gt;.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.<br /> : Install &lt;packagename&gt;.png icon files to the /usr/share/icons/ directory.<br /> : see &lt;tt&gt;install_qgis.sh&lt;/tt&gt; for an example<br /> <br /> * '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.<br /> : (Todo: How do we do this?)<br /> <br /> * '''wget''': When downloading large files using wget, use the &quot;-c&quot; continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:<br /> wget -c package.tar.gz<br /> : Do not use -c if there is a chance the file of that name will change on the server. Add &quot;&lt;tt&gt;--progress=dot:mega&lt;/tt&gt;&quot; to the wget command line if the file is at all large.<br /> : Tiny files should use wget's -nv (non-verbose) flag.<br /> : In a similar manner, use &quot;&lt;tt&gt;--quiet&lt;/tt&gt;&quot; when calling '''qsql'''.<br /> <br /> * '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.<br /> mkdir -p &lt;dir&gt;<br /> <br /> * '''Binary files''': Do not put large (&gt;5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.<br /> <br /> = Packaging considerations =<br /> <br /> The criteria used to select applications for the LiveGIS follow.<br /> <br /> == Technical limitations ==<br /> === Space considerations ===<br /> * DVD: approx 4.2gb compressed<br /> * USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)<br /> * Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed<br /> <br /> So smaller apps (&lt;30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.<br /> <br /> === Memory considerations ===<br /> Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.<br /> <br /> The following principles should be followed. <br /> * Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).<br /> * Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.<br /> * Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.<br /> <br /> File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.<br /> <br /> To install a writable data directory or files, change its group to &quot;users&quot; and set the file(s) as group-writable:<br /> <br /> adduser $USER_NAME users<br /> chmod -R g+w /usr/local/share/&lt;packagename&gt;/data/<br /> chown -R root.users /usr/local/share/&lt;packagename&gt;/data/<br /> <br /> and symlink into the user's home directory if necessary.<br /> <br /> Setting files to have universal write permission is strongly discouraged. '''Do not use &quot;''chmod 777 -R''&quot;.'''<br /> <br /> === Shared resources ===<br /> <br /> The disc is a busy place, so we must all play nice and take care not step on each others toes.<br /> <br /> ==== Changes to the base system ====<br /> <br /> Please don't customize any system level infrastructure which other projects may be relying on.<br /> Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!<br /> <br /> ==== Port numbers ====<br /> <br /> To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others fill find it.<br /> <br /> = Directory Structure =<br /> <br /> # '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.<br /> # '''/usr/lib''' application are usually installed into /usr/lib<br /> # '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin<br /> # '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d<br /> # '''/usr/local/share''' sample data and documentation goes into /usr/local/share<br /> # '''/etc''' config files are stored in /etc<br /> # '''/home/user''' user specific config files or working directories can go into &lt;tt&gt;/home/user/&lt;/tt&gt;. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.<br /> <br /> * ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''<br /> <br /> == .deb Packaging ==<br /> While many packages are installed from a bash script, ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). Next would be packaged into .debs from your own Ubuntu repository. An official Debian package could be used, but we'd have to rebuild it from source (this takes time but is fairly easy; usually these are already sucked in Ubuntu automatically so it isn't an issue).<br /> <br /> If you must build from source, building a .deb package and installing that is preferred to &quot;make install&quot;. If you do need to &quot;make install&quot;, please set the path prefix to /usr/local/ and ''ensure that your package does not introduce namespace conflicts''.<br /> <br /> In practice a number of scripts employ a hybrid approach, with as much as possible installed via official packages, and the occasional plugin compiled from source.<br /> <br /> A base set of build-tools are already included, but if you install a bunch of -dev packages to build your app, make sure that you clean them all up after you are done.<br /> <br /> Using &quot;&lt;tt&gt;gdebi&lt;/tt&gt;&quot; instead of &quot;&lt;tt&gt;dpkg -i&lt;/tt&gt;&quot; can be useful for installing .deb packages manually, as it ensures that all dependencies are also installed.<br /> <br /> == Example Datasets ==<br /> In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script. <br /> <br /> All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).<br /> <br /> There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).<br /> <br /> Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).<br /> <br /> === Natural Earth ===<br /> The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.<br /> <br /> * [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.<br /> ** admin_0_countries<br /> ** admin_1_states_provinces<br /> ** geography_marine_polys<br /> ** geography_regions_elevated_points<br /> ** geography_regions_polys<br /> ** lakes<br /> ** land<br /> ** ocean<br /> ** populated_places_simple<br /> ** rivers_lake_centerlines<br /> ** urban_areas<br /> <br /> * Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*<br /> <br /> === OpenStreetMap ===<br /> OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm<br /> <br /> === North Carolina === <br /> The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.<br /> <br /> The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)<br /> <br /> === Others ===<br /> If you need another type of data for your examples, please discuss this with us.<br /> <br /> == Documentation ==<br /> OSGeo-Live documentation is published at:<br /> ;On OSGeo-Live: http://localhost/ which is stored in /var/www/<br /> ;Stable release: http://live.osgeo.org<br /> ;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html<br /> <br /> === Application Overview ===<br /> <br /> The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/overview/overview.html<br /> <br /> The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/&lt;application&gt;_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst<br /> <br /> The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).<br /> <br /> Overviews also require:<br /> * an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]].<br /> * A project logo as per [[#Logo]]<br /> <br /> Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)<br /> <br /> Once finished, note your project's overview status=&quot;draft&quot; in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to &quot;complete&quot; and is ready for translation.<br /> <br /> === Application Quick Start ===<br /> The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.<br /> <br /> Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.<br /> <br /> Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/&lt;application&gt;_quickstart.rst<br /> <br /> The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:<br /> https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/udig_quickstart.rst<br /> and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html<br /> <br /> In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.<br /> <br /> Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].<br /> <br /> Once finished, note your project's quickstart status=&quot;draft&quot; in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&amp;hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to &quot;complete&quot; and is ready for translation.<br /> <br /> === Logo ===<br /> The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.<br /> <br /> ;Header logo:<br /> :* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos<br /> :* Filename should be &quot;logo-&lt;projectname&gt;.png&quot;<br /> :* Should have a transparent background (not white)<br /> :* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)<br /> :* Should preferably be in PNG format<br /> :* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.<br /> :* Preferably also available as SVG, stored as &quot;logo-&lt;projectname&gt;.svg&quot;<br /> <br /> ;Desktop logo:<br /> :We are still to define the requirements for creating a desktop logo. They will likely include:<br /> :* A 32x32-pixel XPM icon for use by the Debian menus<br /> :* A 48x48-pixel PNG icon for use by freedesktop.org menus<br /> <br /> === Screen Shot ===<br /> Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.<br /> * Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).<br /> * Screen shots should be taken from a 1024x768 display, and stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768<br /> * For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the &quot;Edit&quot; tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.<br /> * Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.<br /> * For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.<br /> <br /> === Extra Documentation ===<br /> Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:<br /> http://localhost/&lt;application&gt;/... or http://live.osgeo.org/&lt;application&gt;/...<br /> <br /> This should typically be achieved by creating a symbolic link from /var/www/&lt;application&gt; to /usr/local/share/doc/&lt;application&gt;<br /> <br /> == Publishing Documentation ==<br /> <br /> The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/<br /> <br /> For a more comprehensive test, set up the reST processor, sphinx:<br /> : (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' &lt;tt&gt;python-sphinx&lt;/tt&gt; ''Debian package'')<br /> <br /> sudo apt-get install python-sphinx<br /> <br /> cd osgeo/livedvd/gisvm/trunk/doc/<br /> make html<br /> <br /> You can then view the results in:<br /> osgeo/livedvd/gisvm/trunk/doc/_build/*.html<br /> <br /> == Testing procedure ==<br /> <br /> Provide test steps for your application as per the [[Live GIS Disc Testing]] wiki page.<br /> <br /> Once the application has been included into a release candidate, ensure the test steps are executed and work on the release candidate. Write up the results as per the [[Live GIS Disc Testing]] wiki page.<br /> <br /> = Translations =<br /> For details on how to translate, refer to [[Live GIS Translate]]<br /> <br /> [[Category: Live-demo]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Breakout_Sessions&diff=56587 2011-08-18T12:00:58Z

<p>Wiki-Olt: /* Proposed Topics */</p> <hr /> <div>= Introduction =<br /> During the [http://2011.foss4g.org/ FOSS4G2011 conference] in Denver, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).<br /> <br /> Breakout Sessions are unstructured timeslots where people can self-organize themselves to discuss topics of interest.<br /> <br /> '''Room allocation to be determined'''<br /> <br /> == Organising Contact ==<br /> <br /> == Timeslots Available ==<br /> <br /> Wednesday 5:30pm to 6:30pm and 7:00pm to 8:00pm<br /> <br /> = Room Assignments =<br /> <br /> == Rooms Available ==<br /> <br /> = Proposed Topics =<br /> <br /> * Tiling<br /> ** Proposed Topics<br /> *** standardised sqlite schema for tile caches<br /> *** TMS/WMTS evolutions:<br /> **** Tile merging (i.e. equivalent of WMS LAYERS=baselayer,overlaylayer)<br /> **** TMS multiple grids per tileset<br /> **** WMTS multiple url endpoints (eg tile1.domain.tld, tile2.domain.tld...): is this still needed now that browsers allow many more connections per server?<br /> *** add yours...<br /> ** Attending<br /> *** [[User:Tbonfort]]<br /> *** [[User:Olt|Oliver Tonnhofer]]<br /> <br /> * Add yours below...<br /> <br /> [[Category:FOSS4G]]<br /> [[Category:FOSS4G2011]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=User:Olt&diff=56547 2011-08-16T16:57:56Z

<p>Wiki-Olt: </p> <hr /> <div>Hi, I'm Oliver Tonnhofer (olt on freednode/bitbucket/etc, or [http://twitter.com/oltonn @oltonn]) and I'm working for [http://omniscale.de Omniscale].<br /> <br /> I'm the author of [http://mapproxy.org MapProxy] and [http://imposm.org Imposm] and contributor to some other opens source projects like [http://trac.gispython.org/lab/wiki/Shapely Shapely].<br /> <br /> You can contact me on freenode (olt) or via mail (oltÄTbogosoftDØTcom).</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Code_Sprint&diff=56546 2011-08-16T16:55:54Z

<p>Wiki-Olt: /* Additional Interested People */</p> <hr /> <div>== Code Sprint - what's that? ==<br /> <br /> [[Image:Code-sprint-foss4g2010.jpg|thumb|400px|FOSS4G 2010 code sprint, in Barcelona]]<br /> A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise.<br /> <br /> With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great :)<br /> <br /> == Venue ==<br /> <br /> *Date: '''Saturday September 17th, 2011''' (the day after the conference). <br /> *Time: '''9am-5pm'''&amp;nbsp; ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&amp;month=9&amp;day=17&amp;hour=15&amp;min=0&amp;sec=0 timeandate])&amp;nbsp; <br /> *'''Where:''' [http://www.tivoli.org/tivoli/ Tivoli Student Union building] (a former brewery), Auraria Campus<br /> [[Image:Tivoli-logo.jpg|150px]]<br /> <br /> Tivoli Student Union<br /> 900 Auraria Parkway<br /> Denver, CO<br /> '''[http://www.openstreetmap.org/?lat=39.745249&amp;lon=-105.005806&amp;zoom=18&amp;layers=M OSM map]'''<br /> <br /> *'''Rooms: (each room has a 60-70 person capacity)''' <br /> ** room 440/540 (bilevel)<br /> ** room 640<br /> <br /> == What to Bring ==<br /> <br /> * power bars (only outlets for 30 computers exist)<br /> <br /> == How to get there from the Sheraton ==<br /> <br /> The easiest way to get there from the Sheraton is to catch the free shuttle bus along 16th Street to Larimer, then it's about a half mile walk from there (7-10 minutes) - just take a left on Larimer and keep going straight into the campus. More detail to come shortly on how to get to the exact rooms etc.<br /> <br /> == Sponsor ==<br /> <br /> Please! contact organizers: Rafael Moreno, or [[Jeff McKenna]]<br /> <br /> == Questions/Comments/Ideas ==<br /> <br /> * ask on the foss4g2011 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2011 subscribe])<br /> <br /> == Additional Interested People ==<br /> <br /> The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup. <br /> <br /> * name:project<br /> <br /> * [[Daniel Kastl]]<br /> * Haruyuki Seki<br /> * [[Mike Adair]]<br /> * [[User:Olt|Oliver Tonnhofer]] I like to work on tiling stuff (MapProxy) or Python geo APIs (Shapely, imposm).<br /> <br /> = Workgroups =<br /> <br /> To participate, copy a project skeleton and start a section below for your project. <br /> <br /> == Project-name ==<br /> <br /> '''Attending:''' <br /> <br /> * user<br /> * user<br /> <br /> '''Goals:''' <br /> <br /> * your goals<br /> <br /> <br /> == GeoExt ==<br /> <br /> '''Attending:''' <br /> <br /> * [[User:Rdewit| Roald de Wit]]<br /> * [[User:mpriour| Matt Priour]]<br /> * ...<br /> <br /> '''Goals:''' <br /> <br /> * Getting GeoExt to work with ExtJS4<br /> <br /> == MapQuery ==<br /> <br /> '''Attending:''' <br /> <br /> * [[User:Vmische|Volker Mische]]<br /> * [[User:stvn|Steven M. Ottens]]<br /> * [[User:h0st1le|Justin Penka]]<br /> <br /> '''Goals:''' <br /> <br /> * Making MapQUery more awesome<br /> * Talk to OpenLayers 3 people about the future<br /> <br /> == PostGIS ==<br /> <br /> '''Attending:''' <br /> <br /> * Paul Ramsey<br /> * Pierre Racine<br /> * David Bitner<br /> * Brian Hamlin<br /> * Bborie Park<br /> * you?<br /> <br /> '''Goals:''' <br /> <br /> * Close bugs and triage for 2.0 release<br /> <br /> == Opticks ==<br /> <br /> '''Attending:''' <br /> <br /> * Kip Streithorst<br /> * Trevor Clarke<br /> * Michael Considine<br /> <br /> '''Goals:''' <br /> <br /> * TBD<br /> <br /> '''Possible:'''<br /> * Work with OSSIM developers to apply OSSIM patches developed by the Opticks developers.<br /> * Co-registration/image-to-image registration tool to replace Data Fusion<br /> * Open source the Opticks unit tests<br /> * Misc small enhancements and bug fixes<br /> * Add georectification and orthorectification<br /> * Prototype an OpenGL 2.1 based rendering pipeline<br /> * Fix AEB installation to support auto-elevation, no need to start-up app with admin privs<br /> * automatically restart Opticks to complete installation and uninstallation<br /> * replace band math with raster math<br /> * Prototype a multithreaded raster algorithm library<br /> * Prototype am OpenCL/CUDA raster algorithm library<br /> <br /> '''Collaborate:'''<br /> * OSSIM<br /> <br /> == Mapnik ==<br /> <br /> I ([[User:springmeyer|Dane Springmeyer]]) can't make the code sprint (leaving the night of the 16th),<br /> so catch me during the conference to chat Mapnik coding.<br /> <br /> == OSGeo edu ==<br /> <br /> '''Attending:''' <br /> <br /> * Ari Jolma<br /> <br /> '''Goals:'''<br /> <br /> Possible things to do:<br /> <br /> * Set up a repository for joint development of edu materials and kick-start a few projects<br /> * Gather/organize materials for Desktop GIS or Web GIS workbooks<br /> <br /> == MapServer ==<br /> <br /> '''Attending:''' <br /> <br /> * Michael Smith<br /> * [[Jeff McKenna]]<br /> * [[Thomas Bonfort]]<br /> * [[User:Schpidi|Stephan Meissl]]<br /> * [[User:fschindler|Fabian Schindler]]<br /> * [[User:Dmorissette|Daniel Morissette]]<br /> <br /> == libLAS / PDAL ==<br /> <br /> '''Attending:''' <br /> <br /> * Michael Smith<br /> <br /> == GeoMOOSE ==<br /> <br /> '''Attending:''' <br /> <br /> * Brian Fischer<br /> * Bob Basques<br /> * Jim Klassen<br /> * Eli Adam<br /> * Dan &quot;Ducky&quot; Little<br /> * you?<br /> <br /> '''Goals:''' <br /> <br /> * Testing and bug fixes for 2.6 release<br /> * Documentation<br /> <br /> == ZOO-Project ==<br /> <br /> '''Attending:''' <br /> <br /> * Nicolas Bozon<br /> * [[User:djay|Gérald Fenoy]]<br /> <br /> <br /> == uDig ==<br /> <br /> '''Attending:''' <br /> <br /> * [[User:Jive|Jody Garnett]]<br /> * [[User:Kengu|Kenneth Gulbrandsøy]] (IRC)<br /> <br /> '''Goals:''' <br /> <br /> * TBD<br /> <br /> '''Possible:'''<br /> <br /> * roll out CDO and a bit of QA on EMF goodness<br /> * migrate user guide to help plugin (since Eclipse has a Wiki Editor that supports textile)<br /> * refactor to *eu.udig* and make a verison release<br /> * GeoTools as OSGi (no more net.refractions.udig.libs) - see GeoTools below as this would require collaborative effort<br /> <br /> == GeoTools ==<br /> <br /> '''Attending:''' <br /> <br /> * [[User:Jive|Jody Garnett]]<br /> <br /> '''Goals:''' <br /> <br /> * TBD<br /> <br /> '''Possible:'''<br /> <br /> * Implement Query/Join for more than just JDBC-NG code<br /> * Get OSGi bundle information sorted (collaborate with downstream applications )<br /> * Set up new developers<br /> * Major Bug stomp <br /> * Technical Debt (FunctioName details; Remove old Filter code from test cases etc...)<br /> <br /> '''Collaboration:'''<br /> <br /> * uDig: Collaborate on OSGi rollout (ie Equinox testing)<br /> * GeoServer: Collaborate on OSGi rollout (ie Spring testing)<br /> * Zoo-Project: collaborate on WPS Client testing?<br /> <br /> [[Category:FOSS4G2011]]<br /> [[Category:FOSS4G]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=56234 2011-08-01T15:43:05Z

<p>Wiki-Olt: /* Tables */ add SRID</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> The geometries are stored in spherical (web)mercator projection (SRID/EPSG:3857).<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> * landusages_gen0<br /> * waterareas_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> * landusages_gen1<br /> * waterareas_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Usage Tips ==<br /> <br /> For rendering roads with the right ordering (highways above minorroads, bridges above tunnels, etc.) you should use the &lt;tt&gt;roads&lt;/tt&gt; views and order it by &lt;tt&gt;z_order&lt;/tt&gt;.<br /> <br /> For example:<br /> <br /> (select * from osm_roads where tunnel = 1 order by z_order) as roads<br /> (select * from osm_roads where tunnel = 0 and bridge = 0 order by z_order) as roads<br /> (select * from osm_roads where bridge = 1 order by z_order) as roads<br /> <br /> For lower resolutions, the &lt;tt&gt;roads_genX&lt;/tt&gt; views can be used. The geometries have lower spatial resolution and the views do not contain minor roads.<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> area real,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=56233 2011-08-01T15:41:47Z

<p>Wiki-Olt: /* Schema Dump */ 900913 -&gt; 3857</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> * landusages_gen0<br /> * waterareas_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> * landusages_gen1<br /> * waterareas_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Usage Tips ==<br /> <br /> For rendering roads with the right ordering (highways above minorroads, bridges above tunnels, etc.) you should use the &lt;tt&gt;roads&lt;/tt&gt; views and order it by &lt;tt&gt;z_order&lt;/tt&gt;.<br /> <br /> For example:<br /> <br /> (select * from osm_roads where tunnel = 1 order by z_order) as roads<br /> (select * from osm_roads where tunnel = 0 and bridge = 0 order by z_order) as roads<br /> (select * from osm_roads where bridge = 1 order by z_order) as roads<br /> <br /> For lower resolutions, the &lt;tt&gt;roads_genX&lt;/tt&gt; views can be used. The geometries have lower spatial resolution and the views do not contain minor roads.<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> area real,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 3857))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=56232 2011-08-01T15:40:41Z

<p>Wiki-Olt: /* Importing */ add --proj option</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> pip install imposm<br /> <br /> To install the &quot;trunk&quot; version change the last line from above with:<br /> <br /> pip install https://bitbucket.org/olt/imposm/get/default.tar.gz<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache --proj epsg:3857<br /> <br /> <br /> Done:<br /> <br /> [[File:Imposm-db-denver.png]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=55921 2011-07-06T14:28:52Z

<p>Wiki-Olt: /* Schema Dump */</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> * landusages_gen0<br /> * waterareas_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> * landusages_gen1<br /> * waterareas_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Usage Tips ==<br /> <br /> For rendering roads with the right ordering (highways above minorroads, bridges above tunnels, etc.) you should use the &lt;tt&gt;roads&lt;/tt&gt; views and order it by &lt;tt&gt;z_order&lt;/tt&gt;.<br /> <br /> For example:<br /> <br /> (select * from osm_roads where tunnel = 1 order by z_order) as roads<br /> (select * from osm_roads where tunnel = 0 and bridge = 0 order by z_order) as roads<br /> (select * from osm_roads where bridge = 1 order by z_order) as roads<br /> <br /> For lower resolutions, the &lt;tt&gt;roads_genX&lt;/tt&gt; views can be used. The geometries have lower spatial resolution and the views do not contain minor roads.<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> area real,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=55920 2011-07-06T14:27:21Z

<p>Wiki-Olt: /* Generalized tables */</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> * landusages_gen0<br /> * waterareas_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> * landusages_gen1<br /> * waterareas_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Usage Tips ==<br /> <br /> For rendering roads with the right ordering (highways above minorroads, bridges above tunnels, etc.) you should use the &lt;tt&gt;roads&lt;/tt&gt; views and order it by &lt;tt&gt;z_order&lt;/tt&gt;.<br /> <br /> For example:<br /> <br /> (select * from osm_roads where tunnel = 1 order by z_order) as roads<br /> (select * from osm_roads where tunnel = 0 and bridge = 0 order by z_order) as roads<br /> (select * from osm_roads where bridge = 1 order by z_order) as roads<br /> <br /> For lower resolutions, the &lt;tt&gt;roads_genX&lt;/tt&gt; views can be used. The geometries have lower spatial resolution and the views do not contain minor roads.<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55855 2011-07-01T06:49:01Z

<p>Wiki-Olt: /* Installation steps */ installation from trunk</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> pip install imposm<br /> <br /> To install the &quot;trunk&quot; version change the last line from above with:<br /> <br /> pip install https://bitbucket.org/olt/imposm/get/default.tar.gz<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache<br /> <br /> <br /> Done:<br /> <br /> [[File:Imposm-db-denver.png]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55854 2011-07-01T06:47:27Z

<p>Wiki-Olt: /* Importing */</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> pip install imposm<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache<br /> <br /> <br /> Done:<br /> <br /> [[File:Imposm-db-denver.png]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55853 2011-07-01T06:46:52Z

<p>Wiki-Olt: /* Installation steps */</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> pip install imposm<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm/src<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache<br /> <br /> <br /> Done:<br /> <br /> [[File:Imposm-db-denver.png]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55375 2011-05-30T12:45:39Z

<p>Wiki-Olt: /* Importing */ add image</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> bin/pip install imposm<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm/src<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache<br /> <br /> <br /> Done:<br /> <br /> [[File:Imposm-db-denver.png]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=File:Imposm-db-denver.png&diff=55374 2011-05-30T12:44:49Z

<p>Wiki-Olt: </p> <hr /> <div></div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55373 2011-05-30T12:38:59Z

<p>Wiki-Olt: /* Importing */</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> bin/pip install imposm<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm/src<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write --optimize --deploy-production-tables -d osm --user postgres --overwrite-cache</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55372 2011-05-30T12:37:03Z

<p>Wiki-Olt: /* Importing */ create db and import data</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> bin/pip install imposm<br /> <br /> == Importing ==<br /> <br /> Creating the database:<br /> <br /> sudo su postgres<br /> createdb -E UTF8 osm<br /> createlang plpgsql osm<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/postgis.sql<br /> psql -d osm -f /usr/share/pgsql/contrib/postgis-1.5/spatial_ref_sys.sql<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm/src<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write -d osm --user postgres --overwrite-cache</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55342 2011-05-25T15:22:42Z

<p>Wiki-Olt: </p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> bin/pip install imposm<br /> <br /> == Importing ==<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm/src<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write -d osm -n</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/Imposm&diff=55340 2011-05-25T15:21:42Z

<p>Wiki-Olt: add installation notes</p> <hr /> <div>== Installation ==<br /> <br /> Installation of imposm with all dependencies on the linux_db_bm host. <br /> <br /> === Installation steps ===<br /> <br /> Install everything inside `/opt/imposm`: <br /> <br /> cd /opt/<br /> mkdir imposm<br /> sudo mkdir imposm<br /> sudo chown myusername:wms imposm<br /> <br /> Install a recent &amp;gt;2.4 Python version: <br /> <br /> cd /opt/imposm/<br /> mkdir src<br /> cd /opt/imposm/src<br /> wget http://python.org/ftp/python/2.7.1/Python-2.7.1.tgz<br /> tar xf Python-2.7.1.tgz <br /> cd Python-2.7.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install google-protobuf for PBF format: <br /> <br /> cd /opt/imposm/src<br /> wget http://protobuf.googlecode.com/files/protobuf-2.4.1.tar.bz2<br /> tar xf protobuf-2.4.1.tar.bz2 <br /> cd protobuf-2.4.1<br /> ./configure --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install tokyocabinet for internal import cache: <br /> <br /> cd /opt/imposm/src<br /> sudo yum install bzip2-devel<br /> wget http://fallabs.com/tokyocabinet/tokyocabinet-1.4.47.tar.gz<br /> tar xf tokyocabinet-1.4.47.tar.gz <br /> cd tokyocabinet-1.4.47<br /> ./configure --enable-off64 --prefix /opt/imposm<br /> make -j2<br /> make install<br /> <br /> Install distribute/pip to install Python packages: <br /> <br /> cd /opt/imposm/src<br /> wget http://python-distribute.org/distribute_setup.py<br /> ../bin/python distribute_setup.py<br /> ../bin/easy_install pip<br /> <br /> Install Imposm: <br /> <br /> cd /opt/imposm/src<br /> export CFLAGS=-I/opt/imposm/include<br /> export LDFLAGS=-L/opt/imposm/lib<br /> export PATH=/opt/imposm/bin:$PATH<br /> bin/pip install imposm<br /> <br /> == Importing ==<br /> <br /> Download OSM extract: <br /> <br /> cd /opt/imposm/src<br /> mkdir osm_data<br /> cd osm_data<br /> wget http://download.geofabrik.de/osm/north-america/us/colorado.osm.pbf<br /> <br /> Run Imposm: <br /> <br /> export LD_LIBRARY_PATH=/opt/imposm/lib<br /> imposm --read colorado.osm.pbf --write -d osm -n</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011&diff=55339 2011-05-25T15:17:25Z

<p>Wiki-Olt: /* Datasets */ make list</p> <hr /> <div>== Basic Premise ==<br /> <br /> Following up on [[Benchmarking 2010|last year's exercise]], the performance shoot-out presentation at [[FOSS4G2011]] will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers. <br /> <br /> == Communication ==<br /> <br /> Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking <br /> <br /> Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use [http://webchat.freenode.net/ webchat] to connect in browser)<br /> <br /> === Next IRC Meeting ===<br /> <br /> <br /> * Wed April 20th, 2011 @ [http://timeanddate.com/worldclock/fixedtime.html?year=2011&amp;month=04&amp;day=20&amp;hour=14&amp;min=0&amp;sec=0 14:00:00 UTC]<br /> ** Provisional Agenda:<br /> *** Create plan for vector (OSM) and raster (DEM) data processing<br /> *** Discuss testing methodology<br /> <br /> === Previous IRC Meetings ===<br /> <br /> * [[Benchmarking_2011/MeetingLog | Meeting Log]]<br /> <br /> == Potential Participants ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> | '''Mapping Server''' <br /> | '''Development Team Leader'''<br /> | '''Contacted'''<br /> | '''Confirmed'''<br /> | '''Comment'''<br /> |-<br /> | Cadcorp GeognoSIS <br /> | [[User:Mpd|Martin Daly]]<br /> | Dec 9th, 2010<br /> | Yes<br /> |<br /> |-<br /> | Constellation-SDI <br /> | [[User:Acuster|Adrian Custer]], [[User:Cedricbr|Cédric Briançon]]<br /> | <br /> | <br /> |<br /> |-<br /> | Erdas Apollo <br /> | [mailto:dimitri.monie@erdas.com Dimitri Monie]<br /> | <br /> | <br /> | <br /> |-<br /> | ESRI ArcServer<br /> | Satish Sankaran<br /> | <br /> | <br /> | discussing internally<br /> |-<br /> | GeoServer <br /> | Andrea Aime, [[User:groldan|Gabriel Roldan]]<br /> | <br /> | Yes<br /> |<br /> |-<br /> | MapGuide Open Source<br /> | TBD (contacted mapguide-internals)<br /> | Jan 12th, 2011<br /> | <br /> | Response from Jason Birch: Unable to participate<br /> |-<br /> | Mapnik <br /> | [[User:Springmeyer|Dane Springmeyer]]<br /> | Dec 8th, 2010<br /> | Yes<br /> |<br /> |-<br /> | MapServer <br /> | [[User:Jmckenna|Jeff McKenna]], [[User:msmitherdc|Michael Smith]]<br /> | Dec 8th, 2010<br /> | Yes<br /> |<br /> |-<br /> | Oracle MapViewer <br /> | [[User:LJQian|LJ Qian]]<br /> | <br /> | Yes<br /> |<br /> |-<br /> | QGIS Server<br /> | [[User:Pirmin_Kalberer|Pirmin Kalberer]], Marco Hugentobler<br /> | <br /> | Yes<br /> |<br /> |-<br /> | SPOT imagery<br /> | [[User:Jeffaudi|Jean-Francois (Jeff) Faudi]]<br /> | Dec 12th, 2010<br /> | <br /> |<br /> |-<br /> | [http://www.interactive-instruments.de/index.php?id=107&amp;L=1 XtraServer]<br /> | <br /> | <br /> | <br /> |<br /> |}<br /> <br /> == Timeline ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> | January 1st, 2011<br /> | begin contacting all mapping servers<br /> |-<br /> | March 1st, 2011 <br /> | commitment due by all interested mapping servers<br /> |-<br /> | March 2nd, 2011<br /> | exercise begins (and weekly meetings)<br /> |-<br /> | June 1st, 2011 <br /> | final testing begins (no more changes to data/styles/hardware, but changes to software is allowed)<br /> |-<br /> | September 1st, 2011 <br /> | no further testing<br /> |-<br /> | September 2nd, 2011 <br /> | final results due from all teams<br /> |-<br /> | September 12-16, 2011<br /> | present results at FOSS4G2011<br /> |}<br /> <br /> == Rules of Engagement (DRAFT) ==<br /> <br /> # All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.<br /> # Comparisons will be made of the best available version of the software, be it a formal release or a development version. <br /> # One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.<br /> # Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.). If a team does not document the steps on this wiki then that team's test results will not be used. <br /> # WMS output formats to be used will be png8 and png24 where possible<br /> <br /> == Documenting Server Details and Differences ==<br /> <br /> It is the responsibility of each team to document their setup with regard to data. <br /> <br /> Please keep your notes either on a wiki subpage or in svn (or both).<br /> <br /> Generally teams keep notes on setup on the wiki while they put stylesheets and scripts in svn.<br /> <br /> A good organization for wiki pages is to create a subpage like: http://wiki.osgeo.org/wiki/Benchmarking_2011/Mapnik_notes<br /> <br /> And create a directory in svn named {servername}/{year} like: http://svn.osgeo.org/osgeo/foss4g/benchmarking/mapnik/2011<br /> <br /> == Datasets ==<br /> * [[Benchmarking_2011/DB_Schema]]<br /> * [[Benchmarking_2011/Imposm]]<br /> <br /> == SVN ==<br /> <br /> The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/).<br /> <br /> == Hardware ==<br /> <br /> windows_wms_bm (windows server)<br /> * System Type: Dell PowerEdge R410<br /> * Ship Date: 7/7/2010<br /> * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem<br /> * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized<br /> * 2TB 7.2K RPM SATA<br /> * OS: Windows Server 64bit <br /> <br /> linux_wms_bm (linux server)<br /> * System Type: Dell PowerEdge R410<br /> * Ship Date: 7/7/2010<br /> * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem<br /> * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized<br /> * 2TB 7.2K RPM SATA<br /> * OS: Centos 5.5 x86-64<br /> <br /> == External Related Links ==<br /> <br /> * [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout-2010 FOSS4G2010 Benchmarking Presentation]<br /> * [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout FOSS4G2009 Benchmarking Presentation]<br /> * [[FOSS4G Benchmark|FOSS4G WMS Benchmark]] <br /> * [http://sourceforge.net/projects/wmstester/ WMSTester - tool for testing not from OSGeo]<br /> <br /> ----<br /> <br /> [[Category:FOSS4G2011]] [[Category:FOSS4G]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011&diff=55338 2011-05-25T15:17:02Z

<p>Wiki-Olt: /* Datasets */ add link to imposm page</p> <hr /> <div>== Basic Premise ==<br /> <br /> Following up on [[Benchmarking 2010|last year's exercise]], the performance shoot-out presentation at [[FOSS4G2011]] will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers. <br /> <br /> == Communication ==<br /> <br /> Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking <br /> <br /> Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use [http://webchat.freenode.net/ webchat] to connect in browser)<br /> <br /> === Next IRC Meeting ===<br /> <br /> <br /> * Wed April 20th, 2011 @ [http://timeanddate.com/worldclock/fixedtime.html?year=2011&amp;month=04&amp;day=20&amp;hour=14&amp;min=0&amp;sec=0 14:00:00 UTC]<br /> ** Provisional Agenda:<br /> *** Create plan for vector (OSM) and raster (DEM) data processing<br /> *** Discuss testing methodology<br /> <br /> === Previous IRC Meetings ===<br /> <br /> * [[Benchmarking_2011/MeetingLog | Meeting Log]]<br /> <br /> == Potential Participants ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> | '''Mapping Server''' <br /> | '''Development Team Leader'''<br /> | '''Contacted'''<br /> | '''Confirmed'''<br /> | '''Comment'''<br /> |-<br /> | Cadcorp GeognoSIS <br /> | [[User:Mpd|Martin Daly]]<br /> | Dec 9th, 2010<br /> | Yes<br /> |<br /> |-<br /> | Constellation-SDI <br /> | [[User:Acuster|Adrian Custer]], [[User:Cedricbr|Cédric Briançon]]<br /> | <br /> | <br /> |<br /> |-<br /> | Erdas Apollo <br /> | [mailto:dimitri.monie@erdas.com Dimitri Monie]<br /> | <br /> | <br /> | <br /> |-<br /> | ESRI ArcServer<br /> | Satish Sankaran<br /> | <br /> | <br /> | discussing internally<br /> |-<br /> | GeoServer <br /> | Andrea Aime, [[User:groldan|Gabriel Roldan]]<br /> | <br /> | Yes<br /> |<br /> |-<br /> | MapGuide Open Source<br /> | TBD (contacted mapguide-internals)<br /> | Jan 12th, 2011<br /> | <br /> | Response from Jason Birch: Unable to participate<br /> |-<br /> | Mapnik <br /> | [[User:Springmeyer|Dane Springmeyer]]<br /> | Dec 8th, 2010<br /> | Yes<br /> |<br /> |-<br /> | MapServer <br /> | [[User:Jmckenna|Jeff McKenna]], [[User:msmitherdc|Michael Smith]]<br /> | Dec 8th, 2010<br /> | Yes<br /> |<br /> |-<br /> | Oracle MapViewer <br /> | [[User:LJQian|LJ Qian]]<br /> | <br /> | Yes<br /> |<br /> |-<br /> | QGIS Server<br /> | [[User:Pirmin_Kalberer|Pirmin Kalberer]], Marco Hugentobler<br /> | <br /> | Yes<br /> |<br /> |-<br /> | SPOT imagery<br /> | [[User:Jeffaudi|Jean-Francois (Jeff) Faudi]]<br /> | Dec 12th, 2010<br /> | <br /> |<br /> |-<br /> | [http://www.interactive-instruments.de/index.php?id=107&amp;L=1 XtraServer]<br /> | <br /> | <br /> | <br /> |<br /> |}<br /> <br /> == Timeline ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> | January 1st, 2011<br /> | begin contacting all mapping servers<br /> |-<br /> | March 1st, 2011 <br /> | commitment due by all interested mapping servers<br /> |-<br /> | March 2nd, 2011<br /> | exercise begins (and weekly meetings)<br /> |-<br /> | June 1st, 2011 <br /> | final testing begins (no more changes to data/styles/hardware, but changes to software is allowed)<br /> |-<br /> | September 1st, 2011 <br /> | no further testing<br /> |-<br /> | September 2nd, 2011 <br /> | final results due from all teams<br /> |-<br /> | September 12-16, 2011<br /> | present results at FOSS4G2011<br /> |}<br /> <br /> == Rules of Engagement (DRAFT) ==<br /> <br /> # All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.<br /> # Comparisons will be made of the best available version of the software, be it a formal release or a development version. <br /> # One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.<br /> # Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.). If a team does not document the steps on this wiki then that team's test results will not be used. <br /> # WMS output formats to be used will be png8 and png24 where possible<br /> <br /> == Documenting Server Details and Differences ==<br /> <br /> It is the responsibility of each team to document their setup with regard to data. <br /> <br /> Please keep your notes either on a wiki subpage or in svn (or both).<br /> <br /> Generally teams keep notes on setup on the wiki while they put stylesheets and scripts in svn.<br /> <br /> A good organization for wiki pages is to create a subpage like: http://wiki.osgeo.org/wiki/Benchmarking_2011/Mapnik_notes<br /> <br /> And create a directory in svn named {servername}/{year} like: http://svn.osgeo.org/osgeo/foss4g/benchmarking/mapnik/2011<br /> <br /> == Datasets ==<br /> [[Benchmarking_2011/DB_Schema]]<br /> [[Benchmarking_2011/Imposm]]<br /> <br /> == SVN ==<br /> <br /> The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/).<br /> <br /> == Hardware ==<br /> <br /> windows_wms_bm (windows server)<br /> * System Type: Dell PowerEdge R410<br /> * Ship Date: 7/7/2010<br /> * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem<br /> * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized<br /> * 2TB 7.2K RPM SATA<br /> * OS: Windows Server 64bit <br /> <br /> linux_wms_bm (linux server)<br /> * System Type: Dell PowerEdge R410<br /> * Ship Date: 7/7/2010<br /> * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem<br /> * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized<br /> * 2TB 7.2K RPM SATA<br /> * OS: Centos 5.5 x86-64<br /> <br /> == External Related Links ==<br /> <br /> * [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout-2010 FOSS4G2010 Benchmarking Presentation]<br /> * [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout FOSS4G2009 Benchmarking Presentation]<br /> * [[FOSS4G Benchmark|FOSS4G WMS Benchmark]] <br /> * [http://sourceforge.net/projects/wmstester/ WMSTester - tool for testing not from OSGeo]<br /> <br /> ----<br /> <br /> [[Category:FOSS4G2011]] [[Category:FOSS4G]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=User:Olt&diff=55213 2011-05-17T09:29:36Z

<p>Wiki-Olt: Created page with 'Hi, I'm Oliver Tonnhofer (olt on freednode/bitbucket/etc, or [http://twitter.com/oltonn @oltonn]) and I'm working for [http://omniscale.de Omniscale]. I'm the author of [http://…'</p> <hr /> <div>Hi, I'm Oliver Tonnhofer (olt on freednode/bitbucket/etc, or [http://twitter.com/oltonn @oltonn]) and I'm working for [http://omniscale.de Omniscale].<br /> <br /> I'm the author of [http://mapproxy.org MapProxy] and [http://imposm.org Imposm] and contributor to some other opens source projects like [http://trac.gispython.org/lab/wiki/Shapely Shapely].</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=55212 2011-05-17T07:43:23Z

<p>Wiki-Olt: formatting</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Usage Tips ==<br /> <br /> For rendering roads with the right ordering (highways above minorroads, bridges above tunnels, etc.) you should use the &lt;tt&gt;roads&lt;/tt&gt; views and order it by &lt;tt&gt;z_order&lt;/tt&gt;.<br /> <br /> For example:<br /> <br /> (select * from osm_roads where tunnel = 1 order by z_order) as roads<br /> (select * from osm_roads where tunnel = 0 and bridge = 0 order by z_order) as roads<br /> (select * from osm_roads where bridge = 1 order by z_order) as roads<br /> <br /> For lower resolutions, the &lt;tt&gt;roads_genX&lt;/tt&gt; views can be used. The geometries have lower spatial resolution and the views do not contain minor roads.<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=55211 2011-05-17T07:42:16Z

<p>Wiki-Olt: usage tips</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Usage Tips ==<br /> <br /> For rendering roads with the right ordering (highways above minorroads, bridges above tunnels, etc.) you should use the *roads* views and order it by *z_order*.<br /> <br /> For example:<br /> <br /> (select * from osm_roads where tunnel = 1 order by z_order) as roads<br /> (select * from osm_roads where tunnel = 0 and bridge = 0 order by z_order) as roads<br /> (select * from osm_roads where bridge = 1 order by z_order) as roads<br /> <br /> For lower resolutions, the *roads_genX* views can be used. The geometries have lower spatial resolution and the views do not contain minor roads.<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=55210 2011-05-17T07:30:25Z

<p>Wiki-Olt: add link title</p> <hr /> <div>[http://imposm.org Imposm] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011&diff=55209 2011-05-17T07:29:15Z

<p>Wiki-Olt: /* Datasets */</p> <hr /> <div>== Basic Premise ==<br /> <br /> Following up on [[Benchmarking 2010|last year's exercise]], the performance shoot-out presentation at [[FOSS4G2011]] will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers. <br /> <br /> == Communication ==<br /> <br /> Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking <br /> <br /> Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use [http://webchat.freenode.net/ webchat] to connect in browser)<br /> <br /> === Next IRC Meeting ===<br /> <br /> <br /> * Wed April 20th, 2011 @ [http://timeanddate.com/worldclock/fixedtime.html?year=2011&amp;month=04&amp;day=20&amp;hour=14&amp;min=0&amp;sec=0 14:00:00 UTC]<br /> ** Provisional Agenda:<br /> *** Create plan for vector (OSM) and raster (DEM) data processing<br /> *** Discuss testing methodology<br /> <br /> === Previous IRC Meetings ===<br /> <br /> * [[Benchmarking_2011/MeetingLog | Meeting Log]]<br /> <br /> == Potential Participants ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> | '''Mapping Server''' <br /> | '''Development Team Leader'''<br /> | '''Contacted'''<br /> | '''Confirmed'''<br /> | '''Comment'''<br /> |-<br /> | Cadcorp GeognoSIS <br /> | [[User:Mpd|Martin Daly]]<br /> | Dec 9th, 2010<br /> | Yes<br /> |<br /> |-<br /> | Constellation-SDI <br /> | [[User:Acuster|Adrian Custer]], [[User:Cedricbr|Cédric Briançon]]<br /> | <br /> | <br /> |<br /> |-<br /> | Erdas Apollo <br /> | [mailto:dimitri.monie@erdas.com Dimitri Monie]<br /> | <br /> | <br /> | <br /> |-<br /> | ESRI ArcServer<br /> | Satish Sankaran<br /> | <br /> | <br /> | discussing internally<br /> |-<br /> | GeoServer <br /> | Andrea Aime, [[User:groldan|Gabriel Roldan]]<br /> | <br /> | Yes<br /> |<br /> |-<br /> | MapGuide Open Source<br /> | TBD (contacted mapguide-internals)<br /> | Jan 12th, 2011<br /> | <br /> | Response from Jason Birch: Unable to participate<br /> |-<br /> | Mapnik <br /> | [[User:Springmeyer|Dane Springmeyer]]<br /> | Dec 8th, 2010<br /> | Yes<br /> |<br /> |-<br /> | MapServer <br /> | [[User:Jmckenna|Jeff McKenna]], [[User:msmitherdc|Michael Smith]]<br /> | Dec 8th, 2010<br /> | Yes<br /> |<br /> |-<br /> | Oracle MapViewer <br /> | [[User:LJQian|LJ Qian]]<br /> | <br /> | Yes<br /> |<br /> |-<br /> | QGIS Server<br /> | [[User:Pirmin_Kalberer|Pirmin Kalberer]], Marco Hugentobler<br /> | <br /> | Yes<br /> |<br /> |-<br /> | SPOT imagery<br /> | [[User:Jeffaudi|Jean-Francois (Jeff) Faudi]]<br /> | Dec 12th, 2010<br /> | <br /> |<br /> |-<br /> | [http://www.interactive-instruments.de/index.php?id=107&amp;L=1 XtraServer]<br /> | <br /> | <br /> | <br /> |<br /> |}<br /> <br /> == Timeline ==<br /> <br /> {| border=&quot;1&quot;<br /> |-<br /> | January 1st, 2011<br /> | begin contacting all mapping servers<br /> |-<br /> | March 1st, 2011 <br /> | commitment due by all interested mapping servers<br /> |-<br /> | March 2nd, 2011<br /> | exercise begins (and weekly meetings)<br /> |-<br /> | June 1st, 2011 <br /> | final testing begins (no more changes to data/styles/hardware, but changes to software is allowed)<br /> |-<br /> | September 1st, 2011 <br /> | no further testing<br /> |-<br /> | September 2nd, 2011 <br /> | final results due from all teams<br /> |-<br /> | September 12-16, 2011<br /> | present results at FOSS4G2011<br /> |}<br /> <br /> == Rules of Engagement (DRAFT) ==<br /> <br /> # All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.<br /> # Comparisons will be made of the best available version of the software, be it a formal release or a development version. <br /> # One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.<br /> # Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.). If a team does not document the steps on this wiki then that team's test results will not be used. <br /> # WMS output formats to be used will be png8 and png24 where possible<br /> <br /> == Documenting Server Details and Differences ==<br /> <br /> It is the responsibility of each team to document their setup with regard to data. <br /> <br /> Please keep your notes either on a wiki subpage or in svn (or both).<br /> <br /> Generally teams keep notes on setup on the wiki while they put stylesheets and scripts in svn.<br /> <br /> A good organization for wiki pages is to create a subpage like: http://wiki.osgeo.org/wiki/Benchmarking_2011/Mapnik_notes<br /> <br /> And create a directory in svn named {servername}/{year} like: http://svn.osgeo.org/osgeo/foss4g/benchmarking/mapnik/2011<br /> <br /> == Datasets ==<br /> [[Benchmarking_2011/DB_Schema]]<br /> <br /> == SVN ==<br /> <br /> The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/).<br /> <br /> == Hardware ==<br /> <br /> windows_wms_bm (windows server)<br /> * System Type: Dell PowerEdge R410<br /> * Ship Date: 7/7/2010<br /> * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem<br /> * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized<br /> * 2TB 7.2K RPM SATA<br /> * OS: Windows Server 64bit <br /> <br /> linux_wms_bm (linux server)<br /> * System Type: Dell PowerEdge R410<br /> * Ship Date: 7/7/2010<br /> * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem<br /> * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized<br /> * 2TB 7.2K RPM SATA<br /> * OS: Centos 5.5 x86-64<br /> <br /> == External Related Links ==<br /> <br /> * [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout-2010 FOSS4G2010 Benchmarking Presentation]<br /> * [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout FOSS4G2009 Benchmarking Presentation]<br /> * [[FOSS4G Benchmark|FOSS4G WMS Benchmark]] <br /> * [http://sourceforge.net/projects/wmstester/ WMSTester - tool for testing not from OSGeo]<br /> <br /> ----<br /> <br /> [[Category:FOSS4G2011]] [[Category:FOSS4G]]</div>

Wiki-Olt https://wiki.osgeo.org/w/index.php?title=Benchmarking_2011/DB_Schema&diff=55208 2011-05-17T07:28:50Z

<p>Wiki-Olt: Created page with '[http://imposm.org] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema. == Tables == Here is a list of tables that…'</p> <hr /> <div>[http://imposm.org] is used for importing the OSM data extracts into the PostGIS database. Imposm has a configurable database schema.<br /> <br /> == Tables ==<br /> <br /> Here is a list of tables that are included by default. The imposm mapping file is here: [https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py]<br /> <br /> === Point tables ===<br /> * amenities<br /> * places<br /> * transport_points<br /> <br /> === Polygon tables ===<br /> * admin<br /> * buildings<br /> * landusages<br /> * aeroways<br /> * waterareas<br /> <br /> === Linestring tables ===<br /> * minorroads<br /> * mainroads<br /> * motorways<br /> * railways<br /> * waterways<br /> <br /> === Generalized tables ===<br /> Tables like above but with simplified geometries (tolerance 200m):<br /> <br /> * motorways_gen0<br /> * mainroads_gen0<br /> * railways_gen0<br /> <br /> Tables like above but with simplified geometries (tolerance 50m):<br /> * motorways_gen1<br /> * mainroads_gen1<br /> * railways_gen1<br /> <br /> === Views ===<br /> <br /> These views combine minorroads, mainroads, motorway and railways:<br /> <br /> * roads<br /> * roads_gen0<br /> * roads_gen1<br /> <br /> == Schema Dump ==<br /> &lt;pre&gt;<br /> --<br /> -- Name: osm_admin; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_admin (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> admin_level smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_aeroways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_aeroways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_amenities; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_amenities (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_buildings; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_buildings (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_landusages; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_landusages (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_mainroads_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_mainroads_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_minorroads; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_minorroads (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_motorways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_motorways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> oneway smallint,<br /> ref character varying(255),<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_places; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_places (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> z_order smallint,<br /> population integer,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen0; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen0 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_railways_gen1; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_railways_gen1 (<br /> osm_id integer,<br /> name character varying(255),<br /> type character varying(255),<br /> tunnel smallint,<br /> bridge smallint,<br /> z_order smallint,<br /> geometry geometry<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_roads; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads AS<br /> ((SELECT osm_motorways.osm_id, osm_motorways.name, osm_motorways.type, osm_motorways.geometry, osm_motorways.bridge, osm_motorways.ref, osm_motorways.tunnel, osm_motorways.oneway, osm_motorways.z_order, 'motorways' AS class FROM osm_motorways UNION ALL SELECT osm_mainroads.osm_id, osm_mainroads.name, osm_mainroads.type, osm_mainroads.geometry, osm_mainroads.bridge, osm_mainroads.ref, osm_mainroads.tunnel, osm_mainroads.oneway, osm_mainroads.z_order, 'mainroads' AS class FROM osm_mainroads) UNION ALL SELECT osm_minorroads.osm_id, osm_minorroads.name, osm_minorroads.type, osm_minorroads.geometry, osm_minorroads.bridge, osm_minorroads.ref, osm_minorroads.tunnel, osm_minorroads.oneway, osm_minorroads.z_order, 'minorroads' AS class FROM osm_minorroads) UNION ALL SELECT osm_railways.osm_id, osm_railways.name, osm_railways.type, osm_railways.geometry, osm_railways.bridge, NULL::unknown AS ref, osm_railways.tunnel, 0 AS oneway, osm_railways.z_order, 'railways' AS class FROM osm_railways;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen0; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen0 AS<br /> (SELECT osm_railways_gen0.osm_id, osm_railways_gen0.name, osm_railways_gen0.type, osm_railways_gen0.geometry, osm_railways_gen0.bridge, NULL::unknown AS ref, osm_railways_gen0.tunnel, 0 AS oneway, osm_railways_gen0.z_order, 'railways_gen1' AS class FROM osm_railways_gen0 UNION ALL SELECT osm_mainroads_gen0.osm_id, osm_mainroads_gen0.name, osm_mainroads_gen0.type, osm_mainroads_gen0.geometry, osm_mainroads_gen0.bridge, osm_mainroads_gen0.ref, osm_mainroads_gen0.tunnel, osm_mainroads_gen0.oneway, osm_mainroads_gen0.z_order, 'mainroads_gen1' AS class FROM osm_mainroads_gen0) UNION ALL SELECT osm_motorways_gen0.osm_id, osm_motorways_gen0.name, osm_motorways_gen0.type, osm_motorways_gen0.geometry, osm_motorways_gen0.bridge, osm_motorways_gen0.ref, osm_motorways_gen0.tunnel, osm_motorways_gen0.oneway, osm_motorways_gen0.z_order, 'motorways_gen1' AS class FROM osm_motorways_gen0;<br /> <br /> <br /> --<br /> -- Name: osm_roads_gen1; Type: VIEW; Schema: public; Owner: osm<br /> --<br /> <br /> CREATE VIEW osm_roads_gen1 AS<br /> (SELECT osm_railways_gen1.osm_id, osm_railways_gen1.name, osm_railways_gen1.type, osm_railways_gen1.geometry, osm_railways_gen1.bridge, NULL::unknown AS ref, osm_railways_gen1.tunnel, 0 AS oneway, osm_railways_gen1.z_order, 'railways' AS class FROM osm_railways_gen1 UNION ALL SELECT osm_mainroads_gen1.osm_id, osm_mainroads_gen1.name, osm_mainroads_gen1.type, osm_mainroads_gen1.geometry, osm_mainroads_gen1.bridge, osm_mainroads_gen1.ref, osm_mainroads_gen1.tunnel, osm_mainroads_gen1.oneway, osm_mainroads_gen1.z_order, 'mainroads' AS class FROM osm_mainroads_gen1) UNION ALL SELECT osm_motorways_gen1.osm_id, osm_motorways_gen1.name, osm_motorways_gen1.type, osm_motorways_gen1.geometry, osm_motorways_gen1.bridge, osm_motorways_gen1.ref, osm_motorways_gen1.tunnel, osm_motorways_gen1.oneway, osm_motorways_gen1.z_order, 'motorways' AS class FROM osm_motorways_gen1;<br /> <br /> <br /> --<br /> -- Name: osm_transport_areas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_areas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_transport_points; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_transport_points (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> ref character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'POINT'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterareas; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterareas (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> <br /> <br /> --<br /> -- Name: osm_waterways; Type: TABLE; Schema: public; Owner: osm; Tablespace: <br /> --<br /> <br /> CREATE TABLE osm_waterways (<br /> osm_id integer NOT NULL,<br /> name character varying(255),<br /> type character varying(255),<br /> geometry geometry,<br /> CONSTRAINT enforce_dims_geometry CHECK ((ndims(geometry) = 2)),<br /> CONSTRAINT enforce_geotype_geometry CHECK (((geometrytype(geometry) = 'LINESTRING'::text) OR (geometry IS NULL))),<br /> CONSTRAINT enforce_srid_geometry CHECK ((srid(geometry) = 900913))<br /> );<br /> &lt;/pre&gt;</div>

Wiki-Olt