Hi Francois (and others)
I was looking for an automatic process, not using a 3rd party app, and
converting the shapefilewriter into a postgis(or spatialDB) writer with
I dont want to use another component to reach inside geonetworks DB, I would
prefer GN to do this itself, and it would then manage deletes/updates
I dont want to read the shapefile as it stands (ref #2), as there is not
enough information in it, and my geoserver instance seems to loose its
connection to the shapefile each time GN writes to it.
So my requirements look like this:
basic info (spatial and ~5 simple feilds, and link to actual GN record) via
geoserver, and extra info available in GN.
Does anyone else share this usecase?
How would you like our changes reflected in the architecture?
Francois Prunayre wrote:
> 2009/12/23 <Terry.Rankine@...>:
>> Hi all
>> I share part of that need. I would like to be able to convert the spatial
>> index shapefile writer into an extra spatial index table, with the 5 most
>> common metadata node entries (title, author, date, what ever I want from
>> the metadata) and the spatial extent.
> You should be able to do that using Talend Spatial ETL, see this
> tutorial to extract info from the database  and join with the
>> I would like to be able to have entries in this new table only if the
>> user says publish to externals.
>> We want geoserver to server all published content out as simple features
>> with more info than the shape file has and links back to the real data
>> inside geonetworks framework.
> See this tutorial  for GeoServer publication.
>> I am very interested in having the shapefile index not a shapefile but a
>> spatialDB, and some examples on extracting and then populating columns in
>> the new table from geonetworks data.
>> Merry Christmas
>> Terry Rankine
>> From: Miguel Angel Manso (UPM) [m.manso@...]
>> Sent: Thursday, 24 December 2009 3:36 AM
>> To: geonetwork-devel@...
>> Subject: [GeoNetwork-devel] Some ideas to discuss
>> Dear to all list members,
>> First of all, i want to wish you merry Christmas.
>> Recently i've finished my PhD, and i have some time and ideas about
>> Geonetwork new possibilities.
>> Most of us promote metadata creation in order to enable datasets
>> discovery and use. Then metadata enable other functions such as data
>> evaluate and access.
>> This point of view is the most commond, however metadata is a good mean
>> to mantain an inventory.
>> I'm planning to use GeoNetwork as an inventory of proposals using Dublin
>> Core metadata profile or core of ISO19139.
>> In this inventory, users can attach their proposals to points, lines and
>> At this moment, GeoNetwork store BoundingBox of metadata in a shapefile.
>> Some comments has been posted to list two months ago (David Neufeld &
>> Francois Prunayre).
>> In these posts, suggest to use Oracle, MySQL or PostGIS spatial
>> capabilities to avoid the use of shapefiles.
>> My suggest go one step forward. I propose Not only store rectangular
>> polygon but irregular polygons, multipoints and multilines.
>> This is possible in theory and ISO standard enable to define spatial
>> extent as a geometry.
>> The problem is that shapefiles don't enable to store in same file
>> different types of geometries. This can be avoided if we use other type
>> of stores such as Oracle, PostGIS and MySQL.
>> I share with cited members that its complex to resolve in a commond mean
>> the use of these databases. I don't know geotools status on Oracle
>> spatial, but i see that GeoServer can access to Oracle and offer
>> features and maps be mean of pluggings or extensions.
>> I leave the idea on the table, waiting for comments and criticism.
>> Best regards and merry cristmas.
>> Miguel Ángel Manso Callejo.
>> Mercator Working Group.
>> Technical University of Madrid.
>> Autovia de Valencia Km 7.5 Madrid 28031
>> Tfno: 34 91 336 6487 - Fax: 34 91 336 7932
>> Email: m.manso@...
>> __________ Información de ESET NOD32 Antivirus, versión de la base de
>> firmas de virus 4713 (20091223) __________
>> ESET NOD32 Antivirus ha comprobado este mensaje.
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and
>> Join now and get one step closer to millions of Verizon customers
>> GeoNetwork-devel mailing list
>> GeoNetwork OpenSource is maintained at
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> Join now and get one step closer to millions of Verizon customers
> GeoNetwork-devel mailing list
> GeoNetwork OpenSource is maintained at
View this message in context: http://n2.nabble.com/Some-ideas-to-discuss-tp4210230p4248385.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.