[Gfoss] [OSGeo-Discuss] pycsw 1.6.0 released

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Salve.
Nuovo rilascio di pycsw, reference implementation di ogc e valida alternativa al piu'
complesso GeoNetworks OS.
Feedback welcome.
Salluti.

- -------- Messaggio originale --------
Oggetto: [OSGeo-Discuss] pycsw 1.6.0 released
Data: Fri, 28 Jun 2013 21:26:03 +0300
Mittente: Angelos Tzotsos <gcpp.kalxas@gmail.com>
A: OSGeo Discussions <discuss@lists.osgeo.org>

The pycsw team announces the release of pycsw 1.6.0.

The 1.6.0 release brings numerous features, enhancements and fixes to the
codebase, including:

* Nabble community forum now available via OSGeo at
http://osgeo-org.1560.x6.nabble.com/pycsw-devel-f5055821.html
* fix broken connection in pycsw.admin.optimize_db
* native PostGIS geometry support
* new community section on website (http://pycsw.org/community.html)
* Web Accessible Folder (WAF) harvesting support
* added spatial ranking for spatial queries
* added lxml 3 support
* fixes for new OGC CITE tests
* added support for SOS 2.0.0 harvesting
* added support for SOS 1.0.0 harvesting
* added database specific unit tests
* added support for nested OGC Filter queries
* fixed ISO output/safeguarding extent elements
* fixed parameterization of OGC Filter queries
* fixed fulltext search to dump only XML element values
* added flexibility to pycsw.admin.setup_db to handle use cases from
calling applications, like specifying extra columns, skipping SFSQL setup, etc.
* added support for ISO 19115-2 (gmi) harvesting
* FGDC, Atom, and DIF are now core supported outputschema formats, and
do not need to be explicitly set in configuration
* added CIDR notation support for CSW transactions
* enhanced link support when harvesting OWS endpoints
* fix tighten Dublin Core writer when checking on dumping XML
* fixed harvesting logic for unsupported typenames
* fixed GetRecords typename handling to _not_ behave like a record
filter, but as a query model
* harvesting support for RDF Dublin Core
* fixed Harvest operation parameter checks in HTTP GET mode
* added timeout flag to pycsw-admin.py post_xml command
* continuous integration testing (using travis-ci)
* modular Python logging capability
* paver implementation for developer tasks

The full list of enhancements and bug fixes is available at
https://github.com/geopython/pycsw/issues?milestone=7&state=closed

This release also moves pycsw forward as an OSGeo project in incubation.

pycsw is an OGC CSW server implementation written in Python.

pycsw fully implements the OpenGIS Catalogue Service Implementation
Specification [Catalogue Service for the Web]. Initial development started
in 2010 (more formally announced in 2011). The project is certified OGC
Compliant, and is an OGC Reference Implementation.

pycsw allows for the publishing and discovery of geospatial metadata.
Existing repositories of geospatial metadata can also be exposed via
OGC:CSW 2.0.2, providing a standards-based metadata and catalogue component
of spatial data infrastructures.

pycsw is Open Source, released under an MIT license, and runs on all
major platforms (Windows, Linux, Mac OS X).

Source and binary downloads:
- ----------------------------------------

The source code is available at:

http://pycsw.org/download.html

Testers and developers are welcome.

The pycsw developer team.

http://pycsw.org/

_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlHRMFEACgkQ/NedwLUzIr5LhQCfd0F+yKnjtRlvBtROfoppjaSC
SK8AoJ7bGDZcX2sQZet6ktq5hASiO+ar
=+rxs
-----END PGP SIGNATURE-----

Buongiorno Paolo,
sono curioso, "complesso" secondo quali canoni? Questa email sa tanto di FUD :slight_smile:

Forse sarebbe piu' corretto dire "io preferisco PyCSW che secondo me è
piu' semplice da usare". Con lo stesso metro potrei dire, "GeoNetwork
è migliore di PyCSW perchè ha molte piu' funzionalità" e potrei anche
aggiungere "lo dimostra il fatto
che la maggior parte dei GeoPortali nazionali in EU e nel mondo lo usano" :wink:

Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

On Mon, Jul 1, 2013 at 9:31 AM, Paolo Cavallini <cavallini@faunalia.it> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Salve.
Nuovo rilascio di pycsw, reference implementation di ogc e valida alternativa al piu'
complesso GeoNetworks OS.
Feedback welcome.
Salluti.

- -------- Messaggio originale --------
Oggetto: [OSGeo-Discuss] pycsw 1.6.0 released
Data: Fri, 28 Jun 2013 21:26:03 +0300
Mittente: Angelos Tzotsos <gcpp.kalxas@gmail.com>
A: OSGeo Discussions <discuss@lists.osgeo.org>

The pycsw team announces the release of pycsw 1.6.0.

The 1.6.0 release brings numerous features, enhancements and fixes to the
codebase, including:

* Nabble community forum now available via OSGeo at
http://osgeo-org.1560.x6.nabble.com/pycsw-devel-f5055821.html
* fix broken connection in pycsw.admin.optimize_db
* native PostGIS geometry support
* new community section on website (http://pycsw.org/community.html)
* Web Accessible Folder (WAF) harvesting support
* added spatial ranking for spatial queries
* added lxml 3 support
* fixes for new OGC CITE tests
* added support for SOS 2.0.0 harvesting
* added support for SOS 1.0.0 harvesting
* added database specific unit tests
* added support for nested OGC Filter queries
* fixed ISO output/safeguarding extent elements
* fixed parameterization of OGC Filter queries
* fixed fulltext search to dump only XML element values
* added flexibility to pycsw.admin.setup_db to handle use cases from
calling applications, like specifying extra columns, skipping SFSQL setup, etc.
* added support for ISO 19115-2 (gmi) harvesting
* FGDC, Atom, and DIF are now core supported outputschema formats, and
do not need to be explicitly set in configuration
* added CIDR notation support for CSW transactions
* enhanced link support when harvesting OWS endpoints
* fix tighten Dublin Core writer when checking on dumping XML
* fixed harvesting logic for unsupported typenames
* fixed GetRecords typename handling to _not_ behave like a record
filter, but as a query model
* harvesting support for RDF Dublin Core
* fixed Harvest operation parameter checks in HTTP GET mode
* added timeout flag to pycsw-admin.py post_xml command
* continuous integration testing (using travis-ci)
* modular Python logging capability
* paver implementation for developer tasks

The full list of enhancements and bug fixes is available at
https://github.com/geopython/pycsw/issues?milestone=7&state=closed

This release also moves pycsw forward as an OSGeo project in incubation.

pycsw is an OGC CSW server implementation written in Python.

pycsw fully implements the OpenGIS Catalogue Service Implementation
Specification [Catalogue Service for the Web]. Initial development started
in 2010 (more formally announced in 2011). The project is certified OGC
Compliant, and is an OGC Reference Implementation.

pycsw allows for the publishing and discovery of geospatial metadata.
Existing repositories of geospatial metadata can also be exposed via
OGC:CSW 2.0.2, providing a standards-based metadata and catalogue component
of spatial data infrastructures.

pycsw is Open Source, released under an MIT license, and runs on all
major platforms (Windows, Linux, Mac OS X).

Source and binary downloads:
- ----------------------------------------

The source code is available at:

http://pycsw.org/download.html

Testers and developers are welcome.

The pycsw developer team.

http://pycsw.org/

_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlHRMFEACgkQ/NedwLUzIr5LhQCfd0F+yKnjtRlvBtROfoppjaSC
SK8AoJ7bGDZcX2sQZet6ktq5hASiO+ar
=+rxs
-----END PGP SIGNATURE-----
_______________________________________________
Gfoss@lists.gfoss.it
http://lists.gfoss.it/cgi-bin/mailman/listinfo/gfoss
Questa e' una lista di discussione pubblica aperta a tutti.
I messaggi di questa lista non hanno relazione diretta con le posizioni dell'Associazione GFOSS.it.
657 iscritti al 30.5.2013

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 01/07/2013 10:07, Simone Giannecchini ha scritto:

sono curioso, "complesso" secondo quali canoni? Questa email sa tanto di FUD :slight_smile:

per carita', lungi da me! se ha dato questa impressione, mi scuso e rettifico subito.
quando parlo di complessita' mi riferisco a:

* dimensione complessiva dell'applicazione
* quantita' e complessita' delle funzioni
* procedura di installazione e configurazione iniziale.

In ogni caso complesso !=peggiore.
PostGIS e' sicuramente piu' complesso di shapefile, nessuno credo si sogni di dire
che sia peggiore da nessun punto di vista.

Forse sarebbe piu' corretto dire "io preferisco PyCSW che secondo me è
piu' semplice da usare". Con lo stesso metro potrei dire, "GeoNetwork
è migliore di PyCSW perchè ha molte piu' funzionalità" e potrei anche
aggiungere "lo dimostra il fatto
che la maggior parte dei GeoPortali nazionali in EU e nel mondo lo usano" :wink:

non ho detto cosa preferisco, ho solo accennato alla complessita'.
sarebbe interessante (da qui la mia richiesta di feedback) avere piu' dati dagli
utenti : chi sa, dica.

Saluti.
- --
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlHRPX8ACgkQ/NedwLUzIr6ZDACfbkosmnWQiu8smxIdskHa8+jh
o5oAnRKsVe6r+8tcEzQHz4+5MnZ/zV/z
=96UF
-----END PGP SIGNATURE-----