Jody Garnett ha scritto:
> Where are you at with this one David? It has been six days - are you
> putting it to a vote? do you have enough feedback etc?
> My own preference (collaborate at the geotools level) is too much work
> even if the end result would be nice.
>
> Just as with the REST api I
David Winslow ha scritto:
>>> Disabling the feature is as simple as neglecting to define any layout files.
Can this be used to package up the "watermark" functionaltiy in a cleaner
form.
>>> The existing watermark configuration is already interpreted as an extra
>>> 'static image' decora
Jody Garnett ha scritto:
>> The configuration is completely orthogonal to the org.geoserver.catalog
>> classes, much as templates and permissions are. Decoration layouts are
>> defined in XML files, which can be referenced by name in a format option
>> as described in both the GSIP and the wiki pa
Jody Garnett ha scritto:
> Okay so you no exposure to the configuration system. Do you have plans
> for a user interface contribution then - or is the advice to modify
> these xml files.
Here you're hitting a pain point for the configuration.
Even in trunk we have API to deal with catalog itself,
Hi David,
you have my +1
(sorry for the delay, very busy in this period)
---
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584 980933
fax: +39 0584 983027
mob:+39 3
Justin Deoliveira ha scritto:
> I have been thinking about how to approach the resource publishing split
> lately and wanted to dump my thoughts to start some conversation and
> perhaps come to a general consensus on approach before any formal
> proposals etc..
Sorry for my late reply, but here go
Hi,
before releasing the next trunk alpha do we want to switch all
jdbc datastores to the -ng version of them?
Seems kind of fitting as those datastores should be the way
of the future, so better start dealing with them day in day
out as we work towards making 2.0 stable?
Cheers
Andrea
--
Andrea
Hi,
I've been tasked to go through the i18n stuff for Wicket again. But I
think we need to lay down the ground rules before I edit any further.
1) Our i18n framework?
http://jira.codehaus.org/browse/GEOS-2707 mentions the need to document
"our custom i18n framework (how to use it)"
What is m
David Winslow wrote:
> On Tue, 2009-04-07 at 10:08 +1000, Jody Garnett wrote:
>> Where are you at with this one David? It has been six days - are you
>> putting it to a vote? do you have enough feedback etc?
>
> Yes, let's put it to a vote. From last week's IRC meeting, I believe I
> have a +1 fr
On Tue, 2009-04-07 at 09:04 +0200, Andrea Aime wrote:
> David Winslow ha scritto:
> >>> Disabling the feature is as simple as neglecting to define any layout
> >>> files.
> Can this be used to package up the "watermark" functionaltiy in a
> cleaner form.
> >>> The existing watermark con
> Chicken and egg. We cannot get a contract unless we restrict the
> scope enough to make it fundable. An ideal solution usually has a larger
> scope but there is no one interested in shelling out that much money
> (the ideal solution being to have a multi-renderer rendering system).
Hi Andrea - I
Hi Andrea I believe it was part of ironing out the module system (ie a
difference between a community module and a core contribution). Let me
check:
- http://geoserver.org/display/GEOS/GSIP+22+-+Community+Modules
Apparently I stand corrected; i will stop looking for this when
reviewing future GSIP
+1, let's go for it!!
Andrea Aime wrote:
> Hi,
> before releasing the next trunk alpha do we want to switch all
> jdbc datastores to the -ng version of them?
> Seems kind of fitting as those datastores should be the way
> of the future, so better start dealing with them day in day
> out as we work
Thanks Andrea. Screenshots are very helpful for those who aren't ready to
build their own trunk. :)
Q: Are we going to replace the MIME types in that pull down list with more
human-readable entries? Or perhaps have the MIME types in parentheses (or as
tooltips?)
I've not been following the
Sounds good; can we make them part of the default geotools build as well then?
Andrea I started looking into event support for jdbc-ng last night;
but am still a few evenings away.
Jody
PS. I also looked at some BSD sqlite driver; I wonder if we can start
looking at spatialite support?
On Tue, Ap
Hi Andrea
At the moment I try to implement an universal DataStore supporting
Hints.GEOMETRY_DISTANCE.
The configuration is read from an XML file (Default Implementation)
Each pregeneralized feature type (or vector pyramid) has the following
properties
1) distance
2) name of the geometry p
Arne Kepp wrote:
> Hi,
>
> I've been tasked to go through the i18n stuff for Wicket again. But I
> think we need to lay down the ground rules before I edit any further.
>
>
> 1) Our i18n framework?
>
> http://jira.codehaus.org/browse/GEOS-2707 mentions the need to document
> "our custom i18n
Jody Garnett wrote:
> Sounds good; can we make them part of the default geotools build as well then?
> Andrea I started looking into event support for jdbc-ng last night;
> but am still a few evenings away.
>
> Jody
> PS. I also looked at some BSD sqlite driver; I wonder if we can start
> looking
Hi Christian; please view geotools as the data access layer.
Organizing the live connections (ie datastores) into a catalog or
registery is something each application can figure out on its own;
even if they just use a singleton.
Here is the user guide on the subject:
-
http://docs.codehaus.org/di
Hey guys, I just checked out the new UI, and it looks really great.
Definitely a large improvement over the struts stuff, way more usable.
Most everything seems to work decently, so I'm wondering why we're
calling the next release alpha2? Alpha to me implies little more than a
working prototyp
+1 for spatialite ( I was one of those folks :-) ).
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob:+39 333 812
Jody Garnett ha scritto:
> Sounds good; can we make them part of the default geotools build as well then?
I find it hard to push them for graduation when they're still not able
to replace 1-1 the old jdbc datastores. What we still miss are:
- events (something only uDig is using afaik)
- efficient
Chris Holmes ha scritto:
> Hey guys, I just checked out the new UI, and it looks really great.
> Definitely a large improvement over the struts stuff, way more usable.
>
> Most everything seems to work decently, so I'm wondering why we're
> calling the next release alpha2? Alpha to me implies l
I came upon a page on the OGC website of registered products, and lo and behold:
http://www.opengeospatial.org/resource/products#The%20Open%20Planning%20Project
Only GeoServer 1.3 and 1.5? Should this be made up to date and (and kept up
with new releases etc)?
Thanks,
Mike Pumphrey
OpenGeo - h
Hmmm... Ok, if we are switching to postgis-ng then that's sufficient
reason for me to go with alpha.
Andrea Aime wrote:
> Chris Holmes ha scritto:
>> Hey guys, I just checked out the new UI, and it looks really great.
>> Definitely a large improvement over the struts stuff, way more usable.
>>
Mike Pumphrey ha scritto:
> Thanks Andrea. Screenshots are very helpful for those who aren't ready to
> build their own trunk. :)
>
> Q: Are we going to replace the MIME types in that pull down list with more
> human-readable entries? Or perhaps have the MIME types in parentheses (or as
> to
You have to pay to get each new version certified. We'll probably do it
for 2.0, but doesn't seem worth it to pay a few hundred dollars for
every release.
Mike Pumphrey wrote:
> I came upon a page on the OGC website of registered products, and lo and
> behold:
>
> http://www.opengeospatial.or
>
> One thing that I also seemed to know about alphas are they are not
> feature complete. And 2.0 is not, given that community schema is
> not working right now.
>
> My vote is to call it still alpha. Also consider that we're
> discussing switching from jdbc datastores to jdbc-ng ones
> for thi
Justin Deoliveira ha scritto:
>
>>
>> One thing that I also seemed to know about alphas are they are not
>> feature complete. And 2.0 is not, given that community schema is
>> not working right now.
>>
>> My vote is to call it still alpha. Also consider that we're
>> discussing switching from jdbc
Hmm. I think that menu is likely to be used by standard users as well as
developers. If I wanted to get a shapefile output, I would need to navigate
this menu and I would only find SHAPE-ZIP, which someone may not know is a
zipped shapefile. Okay maybe not the best example, but I still think
Mike Pumphrey ha scritto:
> Hmm. I think that menu is likely to be used by standard users as well as
> developers. If I wanted to get a shapefile output, I would need to navigate
> this menu and I would only find SHAPE-ZIP, which someone may not know is a
> zipped shapefile. Okay maybe not th
[
http://jira.codehaus.org/browse/GEOS-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Aime reopened GEOS-1008:
---
Reopening to change the type of issue (so that it will pop up in the roadmap)
> GetFeatureInfo should take into
Add "friendly" names to "All formats" dropdown list on preview page
---
Key: GEOS-2836
URL: http://jira.codehaus.org/browse/GEOS-2836
Project: GeoServer
Issue Type: Improvement
Done:
http://jira.codehaus.org/browse/GEOS-2836
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Andrea Aime wrote:
> Mike Pumphrey ha scritto:
>> Hmm. I think that menu is likely to be used by standard users as well
>> as developers. If I wanted to get a shapefile output, I would need to
I had read the user guide.
The principle is the same as the directory data store but the the
requirements are more complex.
1) Need to specify the generalization distance for each set of precalculated
geometries.
2) No restriction to file based data stores, reading from any data store
should
Consolidating feedback based on some discussion in #toppdzn :
* Big +1 on having the MIME types in that dropdown be more human
readable.
* Rollie's been curating a set of GeoSilk icons for styler, which
includes icons to indicate vector-based / rasterized output. It'd be
nice to use these in
Christopher Patterson ha scritto:
> Consolidating feedback based on some discussion in #toppdzn :
>
> * Big +1 on having the MIME types in that dropdown be more human readable.
Ok, ok, I'll look into it.
> * Rollie's been curating a set of GeoSilk icons for styler, which
> includes icons to ind
Christian Müller ha scritto:
> I had read the user guide.
> The principle is the same as the directory data store but the the
> requirements are more complex.
> 1) Need to specify the generalization distance for each set of
> precalculated geometries.
> 2) No restriction to file based data stores
>> * Let's add "Title" as a column
>
> That can be quite long, how can I fit it into the table?
> (Quite long: one row long)
>
Well, having it listed here will probably help make people put less long
Titles on their layers. Which they probably should, since it's used in
other UI's, like Geo
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/931/changes
Changes:
[aaime] Killing the old preview page
[aaime] Layer preview as first level menu item
[aaime] Factored out a shared icon factory
[aaime] GEOS-2717, Icons for layers page
--
[...
On Apr 7, 2009, at 1:05 PM, Christopher Patterson wrote:
> Consolidating feedback based on some discussion in #toppdzn :
>
> * Big +1 on having the MIME types in that dropdown be more human
> readable.
> * Rollie's been curating a set of GeoSilk icons for styler, which
> includes icons to indicate
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/932/changes
Changes:
[aaime] Serializable!
[aaime] Renaming MapPreviewPage2 to MapPreviewPage
--
[...truncated 3783 lines...]
[INFO] -
Hi Andrea:
I updated the page with my +1 vote; along with anything other votes I
found in this thread.
> Also, I would like Jody to point us at the scalebar decoration
> code udig is using if possible?
The code for scalebar and north arrow are here:
-
http://svn.refractions.net/udig/udig/trunk/
>> * Rollie's been curating a set of GeoSilk icons for styler, which
>> includes icons to indicate vector-based / rasterized output. It'd be
>> nice to use these in the 'Type' column instead of the strings "Vector"
>> and "Raster". We could include tooltip text to clarify for newer users
>> via the
>> I had read the user guide.
Good.
>> The principle is the same as the directory data store but the the
>> requirements are more complex.
>> 1) Need to specify the generalization distance for each set of
>> precalculated geometries.
>> 2) No restriction to file based data stores, reading from an
Hey Jody,
I'd love to collaborate on a more fleshed out GeoSilk set. This one
has been generated on an as needed basis starting at the geospatial
sprint in Bolsena last year and was sort of a rushed creature of
necessity. As you observed, and the readme attests, it's an effort to
bring th
I assume you have read the information on the uDig imagery?
- http://udig.refractions.net/confluence/display/DEV/Imagery
- http://udig.refractions.net/confluence/display/DEV/Icons
I would start by making sure you have a similar guideline for the
geosilk work (icon naming convention etc).
Next up I
Thanks for the rational Andrea:
Let me try again; can we include them in the default build (ie not
requiring a -Dall flag). I understand that graduation may be a ways
off; GeoServer is already depending on several "unsupported" modules
such as directory datastore.
>From my standpoint I try and en
Jody Garnett ha scritto:
>>> I am looking for a way to integrate into geoserver without special coding.
>>> Any idea ?
>
> Three Ideas:
> a) patch up the Repository api to match what geoserver has on now;
> hopefully backing it onto that new catalog? This is a lot of work :-(
> May but be the eas
Jody Garnett ha scritto:
> Thanks for the rational Andrea:
>
> Let me try again; can we include them in the default build (ie not
> requiring a -Dall flag). I understand that graduation may be a ways
> off; GeoServer is already depending on several "unsupported" modules
> such as directory datasto
50 matches
Mail list logo
