| 1 | | = Welcome to Trac 0.10.3.1 = |
| 2 | | |
| 3 | | Trac is a '''minimalistic''' approach to '''web-based''' management of |
| 4 | | '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress. |
| 5 | | |
| 6 | | All aspects of Trac have been designed with the single goal to |
| 7 | | '''help developers write great software''' while '''staying out of the way''' |
| 8 | | and imposing as little as possible on a team's established process and |
| 9 | | culture. |
| 10 | | |
| 11 | | As all Wiki pages, this page is editable, this means that you can |
| 12 | | modify the contents of this page simply by using your |
| 13 | | web-browser. Simply click on the "Edit this page" link at the bottom |
| 14 | | of the page. WikiFormatting will give you a detailed description of |
| 15 | | available Wiki formatting commands. |
| 16 | | |
| 17 | | "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created |
| 18 | | a new Trac environment, containing a default set of wiki pages and some sample |
| 19 | | data. This newly created environment also contains |
| 20 | | [wiki:TracGuide documentation] to help you get started with your project. |
| 21 | | |
| 22 | | You can use [wiki:TracAdmin trac-admin] to configure |
| 23 | | [http://trac.edgewall.org/ Trac] to better fit your project, especially in |
| 24 | | regard to ''components'', ''versions'' and ''milestones''. |
| 25 | | |
| 26 | | |
| 27 | | TracGuide is a good place to start. |
| 28 | | |
| 29 | | Enjoy! [[BR]] |
| 30 | | ''The Trac Team'' |
| 31 | | |
| 32 | | == Starting Points == |
| 33 | | |
| 34 | | * TracGuide -- Built-in Documentation |
| 35 | | * [http://trac.edgewall.org/ The Trac project] -- Trac Open Source Project |
| 36 | | * [http://trac.edgewall.org/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions |
| 37 | | * TracSupport -- Trac Support |
| 38 | | |
| 39 | | For a complete list of local wiki pages, see TitleIndex. |
| | 1 | == Background == |
| | 2 | |
| | 3 | MetaCRS is a project encompassing several projections, and coordinate system related technologies. Our plan is to treat a variety of coordinate system activities as one Project from an OSGeo point of view. This helps provide enough "project mass" to justify the full OSGeo project treatment. But more importantly it would give us a forum to cooperate. Sharing things like coordinate system dictionaries, test suites and mathematical formulations. |
| | 4 | |
| | 5 | == Project Steering Committee == |
| | 6 | |
| | 7 | The project steering committee consists of the following individuals and operates according to the [wiki:PSCGuidelines MetaCRS PSC] procedures. |
| | 8 | |
| | 9 | * Frank Warmerdam (chair) |
| | 10 | * Hugues Wisniewski |
| | 11 | * Norm Olson |
| | 12 | * Mike Adair |
| | 13 | * Howard Butler |
| | 14 | * Martin Davis |
| | 15 | |
| | 16 | == Sub-projects == |
| | 17 | |
| | 18 | The following are sub-projects of MetaCRS: |
| | 19 | |
| | 20 | * [http://trac.osgeo.org/proj PROJ.4] - lead - Frank Warmerdam |
| | 21 | * [http://trac.osgeo.org/proj4js Proj4js] - lead - Mike Adair |
| | 22 | * [http://trac.osgeo.org/csmap CS-Map] - lead - Hugues Wisiewski |
| | 23 | * [http://geotiff.osgeo.org/ GeoTIFF/libgeotiff] - lead - Frank Warmerdam |
| | 24 | * [http://spatialreference.org/ SpatialReference.org] - lead - Howard? Chris? |
| | 25 | * [http://trac.osgeo.org/proj4j/ Proj4J] - lead - Martin Davis |
| | 26 | |
| | 27 | == Commiters == |
| | 28 | |
| | 29 | Commiters are technically able to commit on any part of MetaCRS but traditionally they have sub-projects on which they focus, and they will avoid commits on other sub-projects without discussion with the project lead. New commiters may be [https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=metacrs added] after a vote of the PSC. |
| | 30 | |
| | 31 | * Howard Butler (hobu): libgeotiff, spatialreference.org |
| | 32 | * Hugues Wisiewski (hugueswski): CS-Map |
| | 33 | * Mike Adair (madair): Proj4js |
| | 34 | * Norm Olsen (normolsen): CS-Map |
| | 35 | * Paul Ramsey (pramsey): libgeotiff |
| | 36 | * Frank Warmerdam (warmerdam): PROJ.4, libgeotiff |
| | 37 | * Chris Schmidt (crschmidt): spatialreference.org |
| | 38 | * Richard Didier (drichard): PROJ.4 |
| | 39 | * Martin Davis (mdavis): Proj4J |
| | 40 | * Landon Blake (surveyor): Proj4J, testsuite |
| | 41 | * Martin Desruisseaux (desruisseaux): testsuite |
| | 42 | |
| | 43 | == Mailing list == |
| | 44 | |
| | 45 | In order to facilitate further discussion I have created a mailing list. Please join if you have an interest. |
| | 46 | |
| | 47 | http://lists.osgeo.org/mailman/listinfo/MetaCRS |
| | 48 | |
| | 49 | == Practical Questions == |
| | 50 | |
| | 51 | Answers are not authoritative - they are one opinion on possible answers. |
| | 52 | |
| | 53 | === Are we trying to merge the source into one super-library? === |
| | 54 | |
| | 55 | No, though there may be opportunities that arise for consolidation over time. |
| | 56 | |
| | 57 | === Is my library/component going to be subject to the whim of other contributors? === |
| | 58 | |
| | 59 | I imagine we will want to use the ''lieutenant model'' of development where particular components are essentially maintained by a chief maintainer. The project steering committee would establish broad policy (such as contributor rules) and facilitation for shared components (perhaps some dictionaries) while leaving technical direction of some components to their primary maintainer (ie. Norm for CS-Map). |
| | 60 | |
| | 61 | === So will all these packages live in a single subversion repository with a single Trac instance? === |
| | 62 | |
| | 63 | The current plan is to use a single SVN repository for MetaCRS projects (http://svn.osgeo.org/metacrs) with distinct subtrees for each project. But each project has the option of it's own distinct Trac instance - for example http://trac.osgeo.org/proj and http://trac.osgeo.org/proj4js. |
| | 64 | |
| | 65 | === What are Java developers doing on the mailing list? === |
| | 66 | |
| | 67 | The Java developers come from a range of projects; and are very interested in geeking out about correctness and accuracy issues. There are also a couple opportunities for collaboration (shared testing scripts and the like). |
| | 68 | |
| | 69 | We will seek close cooperation with a variety individuals and organizations interested in interchange of spatial reference system descriptions, and related standards including other open source projects, organizations like OGC, national mapping agencies, and proprietary software developers. |
| | 70 | |
| | 71 | == Non-Programming Collaboration == |
| | 72 | What opportunities are there for collaboration with projection libraries in languges that are not directly compatable with C programming language or C++ programming language libraries? (For example: GeoTools includes functional code for spatial reference systems in Java based on the ESPG database.) |
| | 73 | |
| | 74 | Suggestions: |
| | 75 | * Common Spatial Reference System or Coordinate Reference System Names and Descriptions |
| | 76 | * Coordinate System (and CRS related object) dictionaries. Stuff like the EPSG dictionary. |
| | 77 | * Datum shift lists (towgs84), and datum grid shift files (NTv1, etc). |
| | 78 | * Transformations, calculations, and algorithms written in pseudocode that can be edited in different languages. |
| | 79 | * Descriptions of spatial reference systems that can be used by developers in different programming languages. |
| | 80 | * Notes on transformation from different representations of a CRS (WKT, PROJ.4, GCTP, GML,...). |
| | 81 | * Test suites with test points in a variety of coordinate systems and their lat/long and WGS84 equivelents). |
| | 82 | * Articles on spatial reference systems and translations useful for programmers interested in spatial reference system implementations. For example: |
| | 83 | ** Understanding The Difference Between National Vertical Datum of 1929 and the North American Datum of 1988 |
| | 84 | |
| | 85 | == Standard MetaCRS Test Data Files == |
| | 86 | |
| | 87 | Work has begun on a set of standard test data files that can be used to verify the coordinate transformations/conversions performed by the various OSGeo projects that fall under the MetaCRS umbrella. You can learn more on the [wiki:TestSuite Standard MetaCRS Test Data Files] wiki page. |
