I am going to go over your test cases and see if we can come up with a
different way of accomplishing the same goal.
My best through is to take the CRSEnvelope implementation (which already
represents Dimensions as recorded by a CoordinateReferenceSystem object along
with an extent along each d
Hi Jens:
There are a couple of good approaches (Andrea will have more suggestions I
suspect).
Can I just clarify if this is a general proposal or if it is intended for the
Google Summer of Code?
Jody
On 25/02/2010, at 7:17 AM, Jens wrote:
> Hi Jodi,
>
> I want to propose a 80% full implemen
HI Andrea:
The WMS Lab code was donated; I put some time into it last year before pulling
it from the tutorials (for the reasons you mention).
There is an earlier tutorial from 2006 I was wanting to replace - which simply
showed how to use the WMS API; retrieve a list of layers and make a GetMa
Hi,
today I had a look at WMSLab to see what was the issue reported
by a user on the users list.
After playing a bit with it, I'm wondering if it actually ever worked.
I have a patch that solves some of the issues, it's attached for
review.
Issues I've found:
- the raster symbolizer is created t
So I have gone over this patch ... and it really looks like a data structure
rather then an object.
As an example we have units and unitSymbol as a string; were possible we use a
real java Unit class (which knows its symbol). The extent is holding onto a
value as a String (an unparsed string si
Hi Bjorn; my mail filter caught this message into a "jira" folder so I am
joining the conversation late. We need to put any patches into both 2.6.x and
trunk. Thanks especially for including a patch with tests :-)
I see that open layers added a rotation parameter; is there any documentation I
LSA ha scritto:
> Interesting point, Jody!
>
> I am using it like the following:
> Transaction updateTrans = new
> DefaultTransaction("update");
> FeatureWriter writer =
> featureStore.getDataStore()
> .getFeatureWriter(featureStore.getDataStore().getTypeNames()[0],
> new
> FidFi
Interesting point, Jody!
I am using it like the following:
Transaction updateTrans = new
DefaultTransaction("update");
FeatureWriter writer =
featureStore.getDataStore()
.getFeatureWriter(featureStore.getDataStore().getTypeNames()[0],
new
FidFilterImpl(changedFeautureId2Feature.k
Can I ask how you are using transactions?
A lot of software edits a shapefile "in place"; GeoTools tends to write out the
whole thing again during the commit (into a separate file, and then rename the
files to swap them; and then remove the original).
There are seperate read and write locks in
Hi Sergey,
I don't know enough about shapefile locking to help, sorry. Hopefully
someone else here can assist.
Michael
> Hi Michael,
>
> Yes this is true, I am writing to the shapefile being rendered.
>
> Why this is a problem? A lot of software do this.
>
> I am just need a interactive rendere
10 matches
Mail list logo
