Sounds good to me - I'm quite in to automatic creation of metadata.
One thing we could consider is making a shapefile.xml - the ESRI metadata
format thing. I think we should still have the request.txt, but could also
auto populate a metadata file with some of the same information.
Ultimately what I'd be interested in is a way to more effectively populate a
shapefile.xml. In GeoNode we store a lot of metadata and give users a way
to edit it all through the web, along with extracting from their user
profile. We use GeoServer for all our shapefile generation, so it'd be nice
to be able to get it to also produce a shapefile.xml.
But that's obviously not immediately relevant to this, so +1 on these
changes, though agree it could be nicer to be in one file.
On Mon, Oct 25, 2010 at 6:00 PM, Andrea Aime
<[email protected]>wrote:
> Hi,
> I'm looking into making some changes into the shape-zip output format to
> improve
> traceability and output customization and I'd like to pass them by the
> community before
> going down and implement them.
>
> Traceability of the outputs is important in some circles: people want
> the files to contain
> information about where the files come from, when they were generated, and
> how.
>
> To satisfy this requirements we want to make the zip file name
> configurable so that
> it might contain a company name and the ISO date of the request.
> The same goes for the single shapefiles in it, they would have to
> contain the company
> name, the ISO date of the request and of course the name of the layer.
>
> In order to support traceablity instead I want to add a new file that
> contains the actual
> WFS request, as a URL in case of a GET request, as a XML dump in case
> of a POST request.
> This new file will be added to the lot of files contained in the zip file.
>
> To satisfy the above and keep a general approach I want to roll out a
> handful of new
> freemarker templates:
> - shapezip.ftl: will generate the zip file name given the request
> time, the list of layers requested
> - shapefile.ftl: will generate the shapefile name given the request
> time and the layer name
> - shapedesc.ftl: will generate the request description file name
>
> People can then place those freemarker in the usual workspace
> hierarchy (for the shapezip.ftl
> we'll use the first layer as a reference in case of a multilayer request).
>
> If no templates are to be found the code will just use the current
> naming strategies and name
> the request description file as request.txt
>
> Opinions?
>
> Cheers
> Andrea
>
> -----------------------------------------------------
> Ing. Andrea Aime
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584962313
> fax: +39 0584962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -----------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America
> contest
> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in
> marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
