Document property data store in user manual
-------------------------------------------
Key: GEOS-3385
URL: http://jira.codehaus.org/browse/GEOS-3385
Project: GeoServer
Issue Type: Task
Components: Documentation
Reporter: Ben Caradoc-Davies
Assignee: Ben Caradoc-Davies
Property data store needs some user documentation.
{code}
-------- Original Message --------
Subject: Re: [Geoserver-devel] Properties data store
Date: Tue, 25 Aug 2009 14:51:24 +0800
From: Andrea Aime
To: Caradoc-Davies, Ben (E&M, Kensington)
CC: Gabriel Roldan, Geoserver-devel, Rob Atkinson
Ben Caradoc-Davies ha scritto:
I would very much like to see the property data store retained in its
current form. In addition to being exceptionally useful for pedagogical
purposes, I can imagine intermediate-level users adding a one-point or
two-point layer with some markers to a map, some bit of static data that
is not handy in a database but they would like to serve to improve their
maps. I can imagine little python scripts creating property files. Sure
these things can grow to inefficient proportions, but just because a
tool can be misused does not mean we should take it away.It should be documented. We have made a lot of use of property file data
stores, so I am in a position to document them. If you agree to keep it
I will document it.
Summing up a bit about the idea of keeping the property data store.
Pros:
- interesting tool for anybody that wants to fiddle with external
scripts (only text manipulation required)
- easy to understand
- tendency to pop back in as a dependency, so keeping it is the
least resistance path in the long run
Cons:
- does not scale up
- confusing for end users
- lacks end user documentation
- fragile parsing
The first cons, scalability, should not really be a concern imho,
if we only shipped high performance sources we should remove ArcGrid as
well (raster data represented as text).
Actually on osgeo-discuss someone was asking for a simple text
format to store vector data (not GML). It seems to have its own
sweet spot.
The last three cons could be addressed by better documentation and
some love on the DataUtilities method that is parsing the file contents.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
--
Ben Caradoc-Davies
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira