I was about to start on writing a new datastore to read Excel
spreadsheets as one of my students needs to support very novice users
in GeoServer and feels they may not be able to work with a database.
I was sure there was a tutorial on writing new datastores but all I
can find is http://docs.geoto
I think that is all we have... Jody started it at foss4g but like it says is
unfinished. THe older tutorials reference old api so you are probably better
off with his one. It also uses the newer content data astore which is much
easier to subclass than any of the abstract datastore alternatives.
-
On Thu, Sep 30, 2010 at 11:41 AM, Justin Deoliveira
wrote:
> I think that is all we have... Jody started it at foss4g but like it says is
> unfinished. THe older tutorials reference old api so you are probably better
> off with his one. It also uses the newer content data astore which is much
> ea
All the jdbc-ng datastores use ContentDataStore as a base. A good example
that i wrote in geoserver was a python wrapper datastore, That is that Jody
used as the base of his csv example:
http://svn.codehaus.org/geoserver/trunk/src/community/python/src/main/java/org/geoserver/python/datastore
On T
Hey Ian; in the codebase I have the working FeatureSource; I have just not
caught up on the tutorial text. Would you student like to join the geotools
devel list and collaborate on this one?
Writing a tutorial is 1/2 the effort for me if there is someone around to check
(even better if they don
The 2.7-M3 release of GeoTools does not contain the gt-directory jar (I
checked in the -bin.zip archive as well as on the OSGeo Maven repository.)
Is this intentional? Should I refer to this module by a different name now?
--
David Winslow
OpenGeo - http://opengeo.org/
---
I don't think that is a supported module? Only the supported modules are
included in the release archives. I do try and publish everything out to maven
however.
Reasoning: The GeoTools PMC is only taking responsibility for publishing code
that has been reviewed and meets our project policies an
Ah, I didn't bother checking if it was unsupported. I just assumed it
should be available since the 2.7-M2 version was available on the Maven repo
(and I'm just using that for now, no big deal.)
Would it be reasonable to get this added to the repository, or should I just
wait for the next release
It should of been published I guess; normally during release I do a deploy with
-Dall on; Justin did the last release perhaps he takes different steps.
You could check out the tag and deploy the unsupported modules if you wish.
Currently we do not have a road map so I cannot advice waiting for t
I just committed some changes in app-schema to trunk and stable
(GEOT-3217, Tara Athan's shapefile handling fixes). Since these changes,
running the gt-app-schema tests on stable results in this file being
created (an index, perhaps):
modules/library/sample-data/src/main/resources/org/geotools/
Nope, it is just the symptom of an improvement.
The .fix file is an old geotools specific trick to keep feature ids
stable in face of feature
deletion. The file is not actually needed until you edit the
shapefile, but once it's there
the reader has to assume it contains the feature id mappings and
11 matches
Mail list logo
