ke, 2005-05-11 kello 09:09 -0400, Moisan Yves kirjoitti:
> Hi Kai,
>=20
> I want to join my voice to Sean's and reiterate that your work is
> quite impressive and will definitely help make Zope/Plone a compelling
> web mapping environment. I'm thrilled! =20
Glad to hear.
[...]
> I meant to start my site over anew with ATCT and set it up with
> PrimaGIS with Plone 2.1, but I found out yesterday that Plone 2.1 has
> been delayed to August so I'll now take the upgrade path from Plone
> 2.0, ramp it up to 2.0.5 and hopefully get the right versions of all
> products to have a PrimaGIS test site going soon. Once I have got
> that set up, I will be in a postion to come with constructive comments
> on the evolution of PrimaGIS.
I'm looking forward to this.
> A few points I would like to investigate :
>=20
> 1) Would it be possible to reference an ATCT to a polygon or line
> (instead of just a point location; or maybe use some sort of
> [computed?] centroid for a line/polygon ??)
It's not implemented at the moment, but it feels natural to develop
PrimaGIS in this direction to support other types than POINT. It should
be quite straight-forward to extend the functionality of
PrimaGISDataLayer to support this.=20
> 2) How can content types that are "natively georeferenced", that is
> that carry along with them geoinfo in the form of arttributes (e.g. a
> WKT representation, a bbox ...) be integrated in PrimaGIS ?
This shouldn't be a problem either. We do need a interface for these
"natively georeferenced" objects I think, but it shouldn't be to
complex. At the moment any objects that support the getX(), getY(),
Title() and Description() should work.
Basicly what we need are methods for accessing the location data
(coordinates) and other geoinfo and method(s) for accessing some
(meta)data about the object that can be shown in the JS-popups. The data
shown in the popup doesn't have to be limited to dull plaintext as in
the demo, but could include any rich content, such as images, videos,
etc. Again, I feel that a common interface is needed. Any thoughts on
this?
Another thing I would like to discuss is the location of the PrimaGIS
related geodata (such as proxy objects and native geoaware objects).
Currently the PrimaGISDataLayer objects (that implement the ILayerProxy
and IFeatureStoreProxy interfaces and interact with ZCO) just define a
traversable path (presumably to a Folder) that contains the actual
geodata. I thought about refactoring this so, that PrimaGISDataLayer
would become folderish and would contain the geodata objects to have
better data encapsulation.
With the proxy-object approach I think this is sensible since the proxy
objects are not used per se, but if we want to allow arbitrary (natively
geoaware) objects to be usable with PrimaGIS, it wouldn't be too nice to
force people to move their objects under the PrimaGISDataLayers just to
have them be usable in the map. In this case it would be much better to
have the geoaware content objects stay where they they should be
content-wise and just tell PrimaGISDataLayer where to look for them. How
do you feel?
I'll drop by #zco later tonight, so we can discuss these things.
cheers,
Kai=20
--=20
Kai H=E4nninen mobile:+358-44-541 9567
Software engineer www.mbconcert.fi
MB Concert Ky kai...@mb...
|
