Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page, the default filter will display tickets relevant to you:

  • If logged in then all open tickets, it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences, then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged in and no name/email is defined in the preferences, then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right. Filters with either a text box or a pulldown menu of options can be added multiple times to perform an Or on the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

After you have edited your filters, click the Update button to refresh your results.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria , the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria, see Query Language.

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Using the [[TicketQuery]] Macro

The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

Example:

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language. This also displays the link and description of a single ticket:

[[TicketQuery(id=123)]]

This is displayed as:

No results

A more compact representation without the ticket summaries is:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Finally, if you wish to receive only the number of defects that match the query, use the count parameter:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field>. You can specify multiple fields and what order they are displayed in by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Full rows

In table format you can also have full rows by using rows=<field>:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 95)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#163 fixed BoundingBoxData xml parser fails during the rdirienzo
Description

During the parsing request, Zoo-kernel fails on "BoundingBoxData" In the example attached the XML

 <wps:Input>
            <ows:Identifier>SubsetBoundingBox</ows:Identifier>
            <wps:Data>
                <wps:BoundingBoxData ows:crs="urn:ogc:def:crs:EPSG:6.6:4326" ows:dimensions="2">
                    <ows:LowerCorner>12.513 41.87</ows:LowerCorner>
                    <ows:UpperCorner>14.996 43.333</ows:UpperCorner>
                </wps:BoundingBoxData>
            </wps:Data>
        </wps:Input>

Has been parsed:


MAP => [SubsetBoundingBox]
 * CONTENT [SubsetBoundingBox]
encoding: utf-8
value:



minOccurs: 1
maxOccurs: 1
CRS: urn:ogc:def:crs:EPSG:6.6:4326

POST XML:

<wps:Execute version="1.0.0" service="WPS" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns="http://www.opengis.net/wps/1.0.0" 
    xmlns:wfs="http://www.opengis.net/wfs" 
    xmlns:wps="http://www.opengis.net/wps/1.0.0" 
    xmlns:ows="http://www.opengis.net/ows/1.1" 
    xmlns:gml="http://www.opengis.net/gml" 
    xmlns:ogc="http://www.opengis.net/ogc" 
    xmlns:wcs="http://www.opengis.net/wcs/1.1.1" 
    xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd">
    <ows:Identifier>geohazards_tep_dcs_rss_snap_s1_insar_snap_s1_ifg_overall_1_2</ows:Identifier>
    <wps:DataInputs>
        <wps:Input>
            <ows:Identifier>master</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[https://catalog.terradue.com/sentinel1/search?format=json&uid=S1A_IW_SLC__1SDV_20160821T051116_20160821T051143_012694_013F33_53E5]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>slave</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[https://catalog.terradue.com/sentinel1/search?format=json&uid=S1A_IW_SLC__1SDV_20160902T051117_20160902T051144_012869_014526_DFB4]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>polarisation</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[VV]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>orbittype</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[Sentinel Restituted (Auto Download)]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>cohWinAz</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[6]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>cohWinRg</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[20]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>demtype</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[SRTM 3Sec]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>performPhaseFiltering</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[true]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>nAzLooks</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[1]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>nRgLooks</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[4]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>performPhaseUnwrapping</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[true]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>SubsetBoundingBox</ows:Identifier>
            <wps:Data>
                <wps:BoundingBoxData ows:crs="urn:ogc:def:crs:EPSG:6.6:4326" ows:dimensions="2">
                    <ows:LowerCorner>12.513 41.87</ows:LowerCorner>
                    <ows:UpperCorner>14.996 43.333</ows:UpperCorner>
                </wps:BoundingBoxData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>pixelSpacingInMeter</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[15.0]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
        <wps:Input>
            <ows:Identifier>_T2Username</ows:Identifier>
            <wps:Data>
                <wps:LiteralData>
                    <![CDATA[eboissier]]>
                </wps:LiteralData>
            </wps:Data>
        </wps:Input>
    </wps:DataInputs>
    <wps:ResponseForm>
        <wps:ResponseDocument storeExecuteResponse="true" status="true">
            <wps:Output mimeType="application/opensearchdescription+xml">
                <ows:Identifier>result_osd</ows:Identifier>
            </wps:Output>
        </wps:ResponseDocument>
    </wps:ResponseForm>
</wps:Execute>

Zoo params map dump:

[rdirienzo@0cbcb8659202 zoo-bin]$ ./zoo_loader.cgi < /Projects/work/request.xml
MAP => [master]
 * CONTENT [master]
encoding: utf-8
value: https://catalog.terradue.com/sentinel1/search?format=json&uid=S1A_IW_SLC__1SDV_20160821T051116_20160821T051143_012694_013F33_53E5
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [master]
MAP => [slave]
 * CONTENT [slave]
encoding: utf-8
value: https://catalog.terradue.com/sentinel1/search?format=json&uid=S1A_IW_SLC__1SDV_20160902T051117_20160902T051144_012869_014526_DFB4
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [slave]
MAP => [polarisation]
 * CONTENT [polarisation]
encoding: utf-8
value: VV
minOccurs: 1
maxOccurs: 1
dataType: string
AllowedValues: VV,VH,HH,HV
inRequest: true
 * CHILD [polarisation]
MAP => [orbittype]
 * CONTENT [orbittype]
encoding: utf-8
value: Sentinel Restituted (Auto Download)
minOccurs: 1
maxOccurs: 1
dataType: string
AllowedValues: Sentinel Precise (Auto Download),Sentinel Restituted (Auto Download)
inRequest: true
 * CHILD [orbittype]
MAP => [cohWinAz]
 * CONTENT [cohWinAz]
encoding: utf-8
value: 6
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [cohWinAz]
MAP => [cohWinRg]
 * CONTENT [cohWinRg]
encoding: utf-8
value: 20
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [cohWinRg]
MAP => [demtype]
 * CONTENT [demtype]
encoding: utf-8
value: SRTM 3Sec
minOccurs: 1
maxOccurs: 1
dataType: string
AllowedValues: SRTM 3Sec
inRequest: true
 * CHILD [demtype]
MAP => [performPhaseFiltering]
 * CONTENT [performPhaseFiltering]
encoding: utf-8
value: true
minOccurs: 1
maxOccurs: 1
dataType: string
AllowedValues: true,false
inRequest: true
 * CHILD [performPhaseFiltering]
MAP => [nAzLooks]
 * CONTENT [nAzLooks]
encoding: utf-8
value: 1
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [nAzLooks]
MAP => [nRgLooks]
 * CONTENT [nRgLooks]
encoding: utf-8
value: 4
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [nRgLooks]
MAP => [performPhaseUnwrapping]
 * CONTENT [performPhaseUnwrapping]
encoding: utf-8
value: true
minOccurs: 1
maxOccurs: 1
dataType: string
AllowedValues: true,false
inRequest: true
 * CHILD [performPhaseUnwrapping]
MAP => [SubsetBoundingBox]
 * CONTENT [SubsetBoundingBox]
encoding: utf-8
value:



minOccurs: 1
maxOccurs: 1
CRS: urn:ogc:def:crs:EPSG:6.6:4326
inRequest: true
 * CHILD [SubsetBoundingBox]
MAP => [pixelSpacingInMeter]
 * CONTENT [pixelSpacingInMeter]
encoding: utf-8
value: 15.0
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [pixelSpacingInMeter]
MAP => [_T2Username]
 * CONTENT [_T2Username]
encoding: utf-8
value: eboissier
minOccurs: 1
maxOccurs: 1
dataType: string
inRequest: true
 * CHILD [_T2Username]
X-Powered-By: ZOO@ZOO-Project
Content-Type: text/xml; charset=UTF-8
Status: 200 OK

Zoo cfg file:

[geohazards_tep_dcs_rss_snap_s1_insar_snap_s1_ifg_overall_1_2]
	Title = SNAP Sentinel-1 IW SLC Interferogram and Displacements
	Abstract = This service provides the interferometric processor for the Sentinel-1 TOPSAR IW data performed through SNAP. SNAP is a common architecture for all Sentinel Toolboxes, which is ideal for Earth Observation processing and analysis. WARNING: the TIFF output products will be automatically deleted after 2 weeks; this does not apply to results published on Zenodo.
	processVersion = 1.2
	storeSupported = true
	statusSupported = true
	serviceType = C
	serviceProvider = geohazards_tep_dcs_rss_snap_s1_insar_snap_s1_ifg_overall_1_2.zo
<DataInputs>
	[master]
	Title = Master product reference
	Abstract = Define the master product reference to be processed with SNAP
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[slave]
	Title = Slave product reference
	Abstract = Define the slave product reference to be processed with SNAP
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[polarisation]
	Title = Product polarisation
	Abstract = Define the product polarisation
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		AllowedValues = VV,VH,HH,HV
		<Default>
			value = VV
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[orbittype]
	Title = Orbit type
	Abstract = Define the orbit source for the Orbit Correction. NOTE: Precise orbit is available after 20 days of the data acquisition time.
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		AllowedValues = Sentinel Precise (Auto Download),Sentinel Restituted (Auto Download)
		<Default>
			value = Sentinel Restituted (Auto Download)
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[cohWinAz]
	Title = Azimuth coherence window size
	Abstract = Define the coherence estimation azimuth window size for the Interferogram processing [integer number of pixels]
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
			value = 6
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[cohWinRg]
	Title = Range coherence window size
	Abstract = Define the coherence estimation range window size for the Interferogram processing [integer number of pixels]
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
			value = 20
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[demtype]
	Title = DEM type
	Abstract = Define the DEM source for the Back-Geocoding Coregistration, Topographic Phase Removal and Terrain Correction processing. NOTE: SRTM valid in the [-56 deg,+60 deg] range of latitudes.
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		AllowedValues = SRTM 3Sec
		<Default>
			value = SRTM 3Sec
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[performPhaseFiltering]
	Title = Perform phase filtering
	Abstract = Select if the Goldstein phase filtering has to be performed
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		AllowedValues = true,false
		<Default>
			value = true
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[nAzLooks]
	Title = Azimuth Multilook factor
	Abstract = Define the multilook factor applied for Azimuth direction in the Multilooking processing [integer]
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
			value = 1
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[nRgLooks]
	Title = Range Multilook factor
	Abstract = Define the multilook factor applied for Range direction in the Multilooking processing [integer]
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
			value = 4
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[performPhaseUnwrapping]
	Title = Perform phase unwrapping
	Abstract = Select if the phase unwrapping (through SNAPHU) has to be performed
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		AllowedValues = true,false
		<Default>
			value = false
		</Default>
	</LiteralData>
</DataInputs>
<DataInputs>
	[SubsetBoundingBox]
	Title = Subset Bounding Box for Unwrapping
	Abstract = xxxxxDefine the area of interest for the Phase Unwrapping processing [lon_min,lat_min,lon_max,lat_max]. NOTE: Area is limited to 0.25*0.25 degrees around the center.
	minOccurs = 1
	maxOccurs = 1
	<BoundingBoxData>
		<Default>
			CRS = urn:ogc:def:crs:EPSG:6.6:4326
		</Default>
		<Supported>
			CRS = urn:ogc:def:crs:EPSG:6.6:4326
		<Supported>
	</BoundingBoxData>
</DataInputs>
<DataInputs>
	[pixelSpacingInMeter]
	Title = Pixel spacing in meters
	Abstract = Define the pixel spacing for the Terrain-Correction processing [meters]
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
			value = 15.0
		</Default>
	</LiteralData>
</DataInputs>

<DataInputs>
	[_T2Username]
	Title = User name
	Abstract = Valid username
	minOccurs = 1
	maxOccurs = 1
	<LiteralData>
		dataType = string
		<Default>
		</Default>
	</LiteralData>
</DataInputs>

<DataOutputs>
	[result_osd]
	Title = OpenSearch Description to the Results
	Abstract = OpenSearch Description to the Results
<ComplexOutput>
	<Default>
                MimeType = application/opensearchdescription+xml
	</Default>
	<Supported>
			MimeType = application/opensearchdescription+xml
	</Supported>
</ComplexOutput>
</DataOutputs>
#160 fixed service.h: Windows compile errors of C89-style declarations jmckenna
Description

Using Visual Studio 2012, the following errors are thrown:

ulinet.c
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(58) : error C2143: syntax error : missing ';' before 'type'
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(59) : error C2065: 'theTime' : undeclared identifier
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(59) : warning C4133: 'function' : incompatible types - from 'int *' to '__timeb64 *'
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(60) : error C2065: 'theTime' : undeclared identifier
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(60) : error C2224: left of '.time' must have struct/union type
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(61) : error C2065: 'theTime' : undeclared identifier
d:\build\mapserver-buildkit-2012\zoo-project-svn-20170731\zoo-project\zoo-kernel\service.h(61) : error C2224: left of '.millitm' must have struct/union type

This is due to the C89-style requirement, where variables must be declared at beginning of scope.

#159 fixed request_parser.c error on Windows: cannot convert from 'const char *' to 'char *' jmckenna
Description

Using Visual Studio 2012 compiler, the following errors are thrown:

request_parser.c(1743) : error C2440: 'initializing' : cannot convert from 'const char *' to 'char *'
        Conversion loses qualifiers
request_parser.c(1792) : error C2440: 'initializing' : cannot convert from 'const char *' to 'char *'
        Conversion loses qualifiers
request_parser.c(1795) : error C2440: 'initializing' : cannot convert from 'const char *' to 'char *'
        Conversion loses qualifiers
request_parser.c(1807) : error C2440: '=' : cannot convert from 'const char *' to 'char *'
        Conversion loses qualifiers
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2'
Stop.

more about this error: https://msdn.microsoft.com/en-us/library/sy5tsf8z.aspx

I am attaching a possible fix for this (please review if it is valid).

1 2 3 4 5 6 7 8 9 10 11

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter consists of the ticket field name, an operator and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide

Search

Context Navigation

ZOO Sponsors

http://www.zoo-project.org/trac/chrome/site/img/geolabs-logo.pnghttp://www.zoo-project.org/trac/chrome/site/img/neogeo-logo.png http://www.zoo-project.org/trac/chrome/site/img/apptech-logo.png http://www.zoo-project.org/trac/chrome/site/img/3liz-logo.png http://www.zoo-project.org/trac/chrome/site/img/gateway-logo.png

Become a sponsor !

Knowledge partners

http://www.zoo-project.org/trac/chrome/site/img/ocu-logo.png http://www.zoo-project.org/trac/chrome/site/img/gucas-logo.png http://www.zoo-project.org/trac/chrome/site/img/polimi-logo.png http://www.zoo-project.org/trac/chrome/site/img/fem-logo.png http://www.zoo-project.org/trac/chrome/site/img/supsi-logo.png http://www.zoo-project.org/trac/chrome/site/img/cumtb-logo.png

Become a knowledge partner

Related links

http://zoo-project.org/img/ogclogo.png http://zoo-project.org/img/osgeologo.png