Here is the information from the "horses mouth" (Carl Reed) as dug
out of my mailbox from just under a year ago:
Prior to the June meetings, there was considerable email dialogue
regarding axis order and coordinate reference systems. During the
closing TC Plenary, we continued the dialogue.
Bryce L Nordgren a écrit :
If we agree than starting from now, "EPSG:whatever" should be understood as
being always
(longitude,latitude) axis order (as OGC decided recently in my understanding of
a recent
Jody's mail), then it is a new authority factory derived from the previous one
I wouldn'
> I can see how scaling solves the difference between the units in the two
> CRS's but it seems that if CRS1 has all its axes in one unit but CRS2
> has x,y in one unit and z in another then the transform has too few
> parameters. I'll grant it's probably a rare issue and therefore academic
> fro
Adrian Custer a écrit :
In a seven parameter transform, from CRS1 to CRS2, there are three
'shift' parameters in x,y,z, three 'rotate' parameters, and one
'scaling' parameter.
Doesn't this implicitly assume that all three axes in each CRS are using
the same unit? (NB obviously the two CRS's ca
Martin Desruisseaux <[EMAIL PROTECTED]> wrote on 05/23/2006
04:24:55 PM:
> If we agree than starting from now, "EPSG:whatever" should be
> understood as being always
> (longitude,latitude) axis order (as OGC decided recently in my
> understanding of a recent Jody's
> mail), then it is a new auth
hey all,
In a seven parameter transform, from CRS1 to CRS2, there are three
'shift' parameters in x,y,z, three 'rotate' parameters, and one
'scaling' parameter.
Doesn't this implicitly assume that all three axes in each CRS are using
the same unit? (NB obviously the two CRS's can have different
Jody Garnett wrote:
Well things are moving a bit faster now that I have Justin right here
to bother.
Cory I saw where you were stuck writing a feature collection test and
we have responded by:
- removing the power set of builders (FeatureBuilder,
FeatureCollectionBuilder, SmalFishBuilder, et
Bryce L Nordgren a écrit :
1] Addressing an encoding issue with an authority factory is now, and
forever will be, a hack. Many hacks, actually. Everywhere in the code.
I agree and hope to avoid such hack. The first step I'm considering is to make Geotools referencing
code a little bit more "
[EMAIL PROTECTED] wrote on 05/22/2006 05:18:00 PM:
> Openned a JIRA task
>
> http://jira.codehaus.org/browse/GEOT-854
>
>
> Comments welcome (especially any implication that may come to your mind).
>
>Martin.
Done.
Key points:
1] Addressing an encoding issue with an authority factory
Nope, its all good no matter how I run from eclipse. I have a feeling
its how the forking of the tests is configured. The tests fly by pretty
fast which makes me think they are sharing a VM. How are the tests
currently set up on trunk or 2.2.x?
-Justin
Cory Horner wrote:
Justin Deoliveira wr
Hey all,
Could someone explain the uses of CRS and transforms in the rendering
pipeline? I need a coarse overview of rendering as used by
uDig/streaming Renderer to understand:
(1) how we go from shapefile data to screen data
(2) what CRS's are stored in the rendering system
This is all prep wor
On 5/20/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
Jesse Eichar wrote:
> Hi Simone,
>
> I'm in agreement that this issue needs to be resolved. The problem is
> that I'm not 100% sure how to solve the problem. Do you have a
> suggestion? I apologize if you have put you suggestion in this email
Martin Desruisseaux wrote:
Jody Garnett a écrit :
We have a SoC application set up to do a 3D renderer based off of the
uDig rendering model. So perhaps we can combine forces or have your
students take over the work?
Our planed 3D renderer will not begin this summer. If it get realized,
it w
13 matches
Mail list logo
