[udig-devel] Using the project infrastructure correctly

[Robbie Jameson]

Hi,

I'm trying to build functionnality on top of udig, using the layers in a
project as a source of data. In some way though, the functionnality needs to
have access to specific layers that represent specific business objects
(e.g. roads, houses, etc).

I'm trying to establish a good design for:

1. Functionnality that initially creates the project with the correct layers
ordered in the right manner, styled using the API.

2. Functionnality that allows the rest of my code to access the specific
layers using their business meaning, without having to know about the
project or how many layers are in it. For example, a class would ask some
other one for the "roads layer", and then do some work with it.

3. Functionnality for retrieving from a layer items by looking them up based
on an id string attribute attached to each feature in the layer. I see to
alternatives, either use a filter, but I can't find anything about how they
work (and whether the stuff is actually coded yet), or create a map with ids
pointing to each feature in the layer, built lazily the first time the
information is requested.

Furthermore, I keep on having bugs with M7 when trying to save layers that
have been created from scratch at runtime. Has anyone encountered this issue
or know whether it has been fixed recently?


Thanks in advance,

Robbie