See http://gridlock.openplans.org:8080/hudson/job/geotools-trunk/862/changes
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win gre
Patch attached for GEOT 1615
Key: GEOT-1937
URL: http://jira.codehaus.org/browse/GEOT-1937
Project: GeoTools
Issue Type: Wish
Components: ext graph
Affects Versions: 2.5-M0, 2.4-RC0, 2.3.5
I was looking at SLD 1.0 today and ran into this:
> The default if neither an ExternalGraphic nor a Mark is specified is
> to use the default
> mark of a “square” with a 50%-gray fill and a black outline, with a
> size of 6 pixels,
> unless an explicit Size is specified. This definition allows a
See http://gridlock.openplans.org:8080/hudson/job/geotools-trunk/861/changes
Changes:
[jgarnett] document source of additional sld test files
[jgarnett] Update style interfaces after geoapi review; fix for SLDParser
problems as of GEOT-1935
--
[...trunca
> As a follow up to this review; I should check that your test data files
> were generated by you? test data does not have a header so we end up
> documenting it in a review.apt file.
Yes I generated the test data files based on the examples in the SLD Version
1.0.0 specifications.
--
Hi Emily; I have applied your patch for GEOT-1935 - we need to do this
one more time before we can nominate you for commit access. I am going
to ask another (non refractions) PMC member to review your next patch.
As a follow up to this review; I should check that your test data files
were gener
I have gone through the deprecated methods and sorted out what was
needed; I stubbed in a getDescription() method so that 2.5.x users would
have a non deprecated method to call. Ended up adding a few methods
"early" such as Font.getStyle(); so the Font.getFontStyle() method could
remain depreca
SimpleFeatureImpl$Attribute does not implement equals(Object)
-
Key: GEOT-1936
URL: http://jira.codehaus.org/browse/GEOT-1936
Project: GeoTools
Issue Type: Bug
Components:
Hi guys,
I was looking at your Geographic Metadata format proposal, but I need
some clarifications ...
First of all, correct me if I'm wrong, but I don't see ways to handle
the time yet.
Second thing let me do an example ... supposing that I would like to
represent a Compund CRS composed by a Geo
