http://geo.openplans.org:9090/continuum/buildResult.action?buildId=144&projectId=1
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configurat
In "Image I/O metadata for multidimensional coverage" document
> 5. ImageIO MetaData for Multidimensional Coverages overview
> ---
> In order to be able to describe a Multidimensional Coverage (or
> ND-Coverage), we need to introduce the con
Hi Martin; one of the things we are chasing up with Raj and the OSGeo
foundation is the
ability to get into the process a bit more.
Right now this email is interesting in a social sense (yeah something
happening with
image metadata, and even better you are pleased with it). But the
details are
Andrea Aime wrote:
> Jody Garnett ha scritto:
>> Andrea Aime wrote:
>>> I understand. Yet I feel we lack a middle ground allowing to represent
>>> associations in an efficient way, the same way deegree did.
>> (In my benefit/complexity table this whole multiplicity thing is a
>> good tipping point
General note: some nodes begin with a lower case, and some other nodes
begin with a upper case. It may be worth to clarify what is the policy
for lower/upper cases. In "GML in JPEG 2000" specification, I have the
feeling that lower case is used for attributes and upper case used for
classes.
Page
Daniele Romagnoli from Geosolution recently send us a document on
Coverage I/O metadata. It sound like a very good draft to me. In the
next bunch of emails, I'm going to comment some sections. I will send
separated emails for different issues in order to create distinct
threads.
For this email, I
On page 17, we can read (talking about IIOMetadataFormat constraints):
> For our purposes we will try to respect as much as possible these rules, but
> we might need to
> violate some of them to produce a useful metadata structure. It is worth to
> point out that ImageIO
> would not complain ab
Page 16 introduces the concept of "Basic Stream metadata" in addition of
"Stream metadata". This new metadata level is not mentionned in the
introduction.
Do we expect "Basic stream metadata" to be returned by the "flat" or the
"smart" image reader? If they are expected to be returned by the "flat
On Friday 07 September 2007 08:50:01 Andrea Aime wrote:
> Jody Garnett ha scritto:
> > Andrea Aime wrote:
> >> I understand. Yet I feel we lack a middle ground allowing to represent
> >> associations in an efficient way, the same way deegree did.
> >
> > (In my benefit/complexity table this whole m
Ciao Jody,
my bad the document did not float around from the start, I think there
was a misunderstanding between me, Martin and Daniele. But let's put
things in context :-).
Since I started working with OGC standards more or less 3.5 years ago
I noticed that while there was an adopted Grid Cover
SurfaceImpl.transform( crs, transform ) ignores provided transform
--
Key: GEOT-1484
URL: http://jira.codehaus.org/browse/GEOT-1484
Project: GeoTools
Issue Type: Bug
C
http://geo.openplans.org:9090/continuum/buildResult.action?buildId=147&projectId=86
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070
Hi folks,
As you may know uDig uses the GeoAPI jars with Generics however I'm
getting an odd error when running the following code:
Id fidFilter=(Id) filter;
Set ids = new HashSet
(fidFilter.getIdentifiers());
for (Iterator iter = ids.iterator();
iter.hasNext();) {
http://geo.openplans.org:9090/continuum/buildResult.action?buildId=152&projectId=1
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070m
14 matches
Mail list logo
