Hi Siddharth,
> Suppose I have a layer in epsg:4326 belonging to India... now I have
> converted it into EPSG:24380 by using coordinate transform plugin,
> the ogcwkt representation of EPSG:24380 is
Sorry, I'm not sure how the coordinate transformation plugin works
exactly, but if coordinates di
Hi Michael,
Suppose I have a layer in epsg:4326 belonging to India... now I have
converted it into EPSG:24380 by using coordinate transform plugin,
the ogcwkt representation of EPSG:24380 is
PROJCS["Kalianpur 1975 / India zone IIb",GEOGCS["Kalianpur
1975",DATUM["Kalianpur_1975",SPHEROID["Everest
siddharth raghuvanshi a écrit :
> Hi,
>
> How is the spatial query related to distance is being carried on?? As
> far as I have seen, jts topology suite resolves distance related
> queries only by using the coordinates & has nothing to do with the srs
> of the layer. So, how is OpenJump managing
Hi,
How is the spatial query related to distance is being carried on?? As far as
I have seen, jts topology suite resolves distance related queries only by
using the coordinates & has nothing to do with the srs of the layer. So, how
is OpenJump managing it??
If projection of the layer is in EPSG:4
Hi,
I had a look into the code and tested it : works fine!
Thanks you Landon
Michaël
Stefan Steiniger a écrit :
>> Do you want me to make these changes to my patch and then commit again?
>>
>
> no its fine
> stefan
>
>
>> SS
>>
>>
>> On Fri, Mar 13, 2009 at 9:27 AM, Stefan Steiniger wr
>
> Do you want me to make these changes to my patch and then commit again?
no its fine
stefan
> SS
>
>
> On Fri, Mar 13, 2009 at 9:27 AM, Stefan Steiniger wrote:
>> I checked your code visually.. looks good
>>
>> But I have two comments:
>>
>> 1) you replaced
>> -if (createLayer) {
>> by
Stefan,
I apologize about the bracket change. That is an almost unconcious
habbit of mine, and wasn't done intentionally.
I ususally only initialize my member variables in a constructor. I
also initialize local variables within a method. However, if I don't
see a problem with initializing the boo
I checked your code visually.. looks good
But I have two comments:
1) you replaced
-if (createLayer) {
by
+if (createLayer)
+{
however, we should avoid this bracket style and use the previous one
(also used by Jon, Martin, Michael and myself)
2) I wonder if it makes sense to always
Stefan wrote: "On the LinearRing thing.. that is solved (I did fix it
on the weekend -
and closed the bug report)."
Sweet.
I'll get the commit in right now.
SS
On Thu, Mar 12, 2009 at 2:51 PM, Stefan Steiniger wrote:
> Hei Landon,
>
> thank you and pls. commit. If there is a problem I/we will
Hei Landon,
thank you and pls. commit. If there is a problem I/we will find it after
the commit.
On the LinearRing thing.. that is solved (I did fix it on the weekend -
and closed the bug report).
stefan
Sunburned Surveyor wrote:
> I have fixed the spatial query bug. If the user chooses not to
I have fixed the spatial query bug. If the user chooses not to create
a new layer for the features selected as a result of the query, a
"normal" JUMP selection is created in the source layer. This allows
the user to delete the selected features IF THE LAYER IS EDITABLE. In
this scenario the feature
Thanks for the clarification Stefan and Michael. I now understand that
it is only possible to "copy" features from the selection, and not to
"cut" them, as I had thought. I will look at the code today on my
lunch break to see what can be done about this.
Landon
On Mon, Mar 9, 2009 at 2:11 AM,
> (1) in fact, I'm not sure if having the same feature in several layers
> (without clone) is a good or a dangerous idea. I think it could be nice
> to have a kind of "view" (like in database) to be able to work easily on
> a small part of a large featurecollection or to apply different styles
Hi,
Here are some hints about the pb
It happens because the selection is done on "cloned" features, not on
source features
You can see it on line 199 in SpatialQueryExecutor.
Just removing the clone part of the function will fix the bug... but it
will have a side effect that may be considered a
I think it is a bug - since you can not delete the selected features
stefan
Sunburned Surveyor schrieb:
> Before I examined the source code for the spatial query bug, I decided
> to see if I could duplicate the incorrect behavior.
>
> I was not able to do this.
>
> I successfully executed a spa
Before I examined the source code for the spatial query bug, I decided
to see if I could duplicate the incorrect behavior.
I was not able to do this.
I successfully executed a spatial query and was able to copy & cut the
resulting selection from the source layer, pasting the selected
features to
16 matches
Mail list logo
