[glideplan_swproj] Re: state borders visualisation
- From: Ales Zita <ala.zita@xxxxxxxxx>
- To: glideplan_swproj@xxxxxxxxxxxxx
- Date: Mon, 20 Feb 2012 17:11:12 +0100
Hi
My understanding was that it's the vector data drawing that makes the
loading times so slow at the moment. I'm not sure how it works within osge,
but i can imagine that you either have to access all the relevant
resolution tiles (or create them), which would be slow or you have to have
the elevation data to draw it correctly- slow as well. Last possible way of
drawing the vector data I can think of is to draw the data onto an very
large (worldwide) image layer with apropriate resolution (imho slow).
You have to draw one very complicated textured polygon after all.(I
mean the earth)
Am I missing something here ?
But if I do and it is not the case, then I agree as well.
Creating our own vector drawing tool would be the best way to draw on the
surface.
A.
2012/2/20 Mária Vámošová <maria.vamosova@xxxxxxxxx>
> In the next few days, I plan to get into creating an image and
> elevation tiles handler, so I'll update you also on the model layer
> creation.
>
> Maria
>
> 2012/2/20 Mária Vámošová <maria.vamosova@xxxxxxxxx>:
> > Kuba is right, writing our own Model Layer creator would be probably
> > the best option.
> > I found some discussion posts about that (although this is pretty old):
> >
> >
> http://forum.osgearth.org/Example-of-how-to-use-ModelLayer-td5764539.html
> >
> > But that would not work on airspaces, since they are 3D.
> >
> > On 20 February 2012 14:16, Kuba Marek <blue.cube@xxxxxxxxx> wrote:
> >>> Hi
> >>>
> >>> Just to remind you, if you want to draw it manually, you have to draw
> >>> it & add as a image layer, otherwise the "get elevation" problem all
> >>> over again ...:0)
> >>>
> >>> A.
> >>
> >> +1 for drawing it ourselves.
> >>
> >> And why would we have to draw it as image layer? It should work as
> >> vector data -- the same way that the state boundaries are done now,
> >> right?
> >>
> >> And drawing vector data on the map surface would also be better for
> >> turnpoints and airfields, imo.
> >>
> >> K
>
> To visit archive or unsubscribe, follow:
> //www.freelists.org/list/glideplan_swproj
>
Other related posts:
