t, fast, gives correct result and
>> even it is simple, such tool probably does not exist in other
>> open source GIS. Perhaps soon will, but OJ was the first.
>>
>> -Jukka Rahkonen-
>>
>>> -Alkuperäinen viesti-----
>>> Lähettäjä: Michaël Michaud [m
> > Vastaanottaja: OpenJump develop and use
> > Aihe: Re: [JPP-Devel] Tool for swithing x and y coordinates
> > of features
> >
> > Hi Jukka,
> >
> > > After this introduction I wonder if it could be possible to
> > convert the whole layer with Open
ä: Michaël Michaud [mailto:michael.mich...@free.fr]
>> Lähetetty: 15. marraskuuta 2011 2:04
>> Vastaanottaja: OpenJump develop and use
>> Aihe: Re: [JPP-Devel] Tool for swithing x and y coordinates
>> of features
>>
>> Hi Jukka,
>>
>>> After this introductio
Hi Benjamin,
Have you ever considered BeanshellEditor (bsheditor4jump)?
http://geo.michaelm.free.fr/OpenJUMP/resources/
I write/test all my scripts with this interface.
I used an old version of jEdit, and I suppose it would not be too hard
to add other languages like JRuby
Michaël
Le 15/11/2
ree.fr]
> Lähetetty: 15. marraskuuta 2011 2:04
> Vastaanottaja: OpenJump develop and use
> Aihe: Re: [JPP-Devel] Tool for swithing x and y coordinates
> of features
>
> Hi Jukka,
>
> > After this introduction I wonder if it could be possible to
> convert the whole la
Beanshell is a very nice tool.
I used JRuby in OpenJUMP to create the complete list of PlugIns (see
another mail on this list). I've added the Ruby source code to the code
paste: https://gist.github.com/1361280
I think the normal development workflow with scripts such as Beanshell
or JRuby in Ope
wow!
I should really consider to learn
(a) more about Beanshell (never used it)
(b) coordinate filter
I would have programmed it as plugin... with probably consuming way more
time.
stefan
PS: can we find a spot for that on the wiki, or better adding it to
built-in the Beanshell functions?
Am
Hi Jukka,
> After this introduction I wonder if it could be possible to convert the whole
> layer with OpenJUMP so that the result would keep all the attributes but have
> all the coordinates in reversed x and y coordinate order? So this
> LINESTRING (6610069.234 170739.665, 6606506.505 184937.7
Hi,
With GML3 it is rather common that some part of the data exchange chain does
not handle correctly the coordinate axis ordering. For example this point has
north coordinate 6972331.694 but many programs convert it to shapefile point
with north coordinate 296562.816. This is a common trouble
