Re: [QGIS-Developer] Support to loading GIS projects from an extended OWC geopackage in the QGIS core

2017-12-14 Thread yjacolin
Hello,
We just talked about your plugin today at the 5th meeting of French speaking 
QGIS user and the first feedback is it could be cool to have it natively in 
QGIS!
#qgisconffr :)
Y.
 Message d'origine De : doublebyte  Date 
: 14/12/2017  13:49  (GMT+01:00) À : qgis-developer@lists.osgeo.org Objet : 
[QGIS-Developer] Support to loading GIS projects from an extended OWC 
geopackage in the QGIS core 
Hello,

Maybe some of you are aware of the  "geopackage" plugin

 
.The initial goal of this plugin was to enable users to save their QGIS
projects, including style and associated resources
 in a extended geopackage -  the qgis geopackage extension
   -,
and load it onto another QGIS installation; on this approach, the project is
encoded as qgs, in a database table. Later the plugin was forked to support
a different geopackage exension -  the owc geopackage extension
   - ,
which is standards-based; in this  approach
  ,
the style is encoded as OGC:SLD and the project as OGC:OWS context. The goal
of this approach is to support the migration of GIS projects, as we can
implement this extension in any desktop or server side GIS (e.g.: ArcGIS
Desktop).

The fork was merged in August this year, and the latest release of the 
plugin    already contains
both extensions, covering both use cases of porting QGIS projects and
migrating GIS projects. Recently, it was added  support in the core to the 
"qgis geopackage extension"

 
, in the qgsogrprovider class. This means that if a user loads a geopackage
which was encoded using the "qgis geopackage extension", it will
automatically load the QGIS project from it. We think that it makes sense to
also add the  "ows geopackage extension" to the core; in that case, users
could load projects exported from other GIS software seamlessly, without
having to load the plugin. The mechanism would be very similar to what was
already implemented for the  "qgis geopackage extension".

Before preparing any Pull Request, we would like to understand first what is
the general feeling of the community about this feature; is this something
which seems useful and interesting to add to the QGIS core? If yes, we would
also appreciate any comments regarding any details the implementation.

Looking forward to hearing your feedback :-)

 Joana



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] 3.0 Documentation and branching

2017-03-07 Thread yjacolin


I agree with this also.
Y.


Envoyé depuis mon appareil Samsung

 Message d'origine 
De : Paolo Cavallini  
Date : 07/03/2017  07:52  (GMT+01:00) 
À : qgis-developer@lists.osgeo.org 
Objet : Re: [Qgis-developer] 3.0 Documentation and branching 

Il 07/03/2017 05:58, Nyall Dawson ha scritto:

> I think a better solution is to hook into the current
> [FEATURE]/[NEEDS-DOCS] hooks which auto-open issues on the
> documentation repo. We could *require* that all developers who push a
> new feature commit have to post on the corresponding documentation
> auto-opened issue with at least very rough notes about how the feature
> is supposed to work. The documentation team could then polish these
> up, add screenshots, etc (and merge when the timing is right for the
> team). This would also keep things as easy as possible for devs so
> that they (*cough*... i mean me *cough*) have no excuse not to do it!

Agreed fully.
Thanks Nyall.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] 3.0 Documentation and branching

2017-03-07 Thread yjacolin


Agreed, note that you can also use the visual changelog as reference when it 
already released and you are working on the documentation.
Y.


Envoyé depuis mon appareil Samsung

 Message d'origine 
De : Alexandre Neto  
Date : 07/03/2017  11:21  (GMT+01:00) 
À : DelazJ , Nyall Dawson  
Cc : qgis-developer  
Objet : Re: [Qgis-developer] 3.0 Documentation and branching 

Totally agree with Harrissou. A good description in the commit with the rigth 
tags  should be enough. 
Alex Neto

A ter, 7/03/2017, 10:06, DelazJ  escreveu:
Hi,

2017-03-07 5:58 GMT+01:00 Nyall Dawson :




I think a better solution is to hook into the current

[FEATURE]/[NEEDS-DOCS] hooks which auto-open issues on the

documentation repo. We could *require* that all developers who push a

new feature commit have to post on the corresponding documentation

auto-opened issue with at least very rough notes about how the feature

is supposed to work. The documentation team could then polish these

up, add screenshots, etc (and merge when the timing is right for the

team). This would also keep things as easy as possible for devs so

that they (*cough*... i mean me *cough*) have no excuse not to do it!


You are right, Nyall. 
However, I do not think that they later need to add information in the 
auto-opened issue in Doc repository. By default the generated issue is 
populated with all the information in the commit. So a really descriptive 
commit to QGIS repository with those tags should be enough. There are some very 
good (from a doc writer pov of course) commits where you only need to find the 
right place in the doc and copy paste the description with minor adjustments. 
Unfortunately, they are currently far from being the majority. On the other 
side, there still are many with simply the title (which sometimes can be 
helpful) or do use a dev language (too much cryptic?).

Also note that a verbose commit benefits to the Changelog team, when time 
comes

Harrissou


Nyall



___

Qgis-developer mailing list

Qgis-developer@lists.osgeo.org

List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer-- 
Alexandre 
Neto-@AlexNetoGeohttp://sigsemgrilhetas.wordpress.comhttp://gisunchained.wordpress.com

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] 3.0 Documentation and branching

2017-03-06 Thread yjacolin


It seems we find a consensus here? Richard are you ok with this:* create 
release-2_18 branch* adapt features tracker if needed* made release-2_18 branch 
the default one* forward porting by contributor or by alexandre
I can't do this before the end of the week as I am on trip for QGIS training. 
Could someone create the branch?
Sorry if I am too fast to conclude. Feel free to give your opinion if necessary.
Thanks.
Y.


Envoyé depuis mon appareil Samsung

 Message d'origine 
De : DelazJ  
Date : 06/03/2017  15:26  (GMT+01:00) 
À : Matthias Kuhn  
Cc : qgis-developer  
Objet : Re: [Qgis-developer] 3.0 Documentation and branching 


2017-03-06 15:20 GMT+01:00 Matthias Kuhn :


Sorry, I explained badly. Pull requests are perfectly fine and desirable

and should be the standard way to contribute for everyone (including

devs). What I wanted to say is that commits (and therefore pull

requests) are preferable over issues because they are written in rst and

not md, unlike issues.


I can't disagree this time!
 

Matthias



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Outline/border -> stroke?

2017-02-19 Thread yjacolin


Raymond,
You can use variable to change color at once everywhere you set up the 
parameter to use it!
Y.


Envoyé depuis mon appareil Samsung

 Message d'origine 
De : Raymond Nijssen  
Date : 18/02/2017  11:15  (GMT+01:00) 
À : qgis-developer@lists.osgeo.org 
Objet : Re: [Qgis-developer] Outline/border -> stroke? 

+1 for stroke

+0 for opacity/transparency, but let's pick one of them for QGIS overall.

+1 for not using  black, but please make it a really dark gray because I 
think maps look crappy when the outline color gets lighter than the fill 
color. (As I notice sometimes in another desktop GIS...)

Besides, talking about this subject, I would love a tool for changing 
all the black stuff in map composers to another color. Texts, scale 
bars, frames, everything at once. Or does this already exist?

Regards,
Raymond



On 18-02-17 08:26, Tim Sutton wrote:
> Hi
>
> +1 from me too to switch to "stroke" and charcoal instead of black.
>
> Regards
>
> Tim Sutton
> Co-founder of Kartoza
> QGIS project chairman
>
> On 07 Feb 2017, at 12:42 PM, Tom Chadwin  > wrote:
>
>> Definitely "stroke", both because it is the standard term in graphics
>> software, and also because neither "border" nor "outline" make any
>> sense in
>> a line.
>>
>> I agree that a dark grey would be a better choice of default stroke than
>> black:
>>
>> https://www.google.co.uk/webhp?sourceid=chrome-instant=1=2=UTF-8#q=never+use+black+in+design
>>
>> Tom
>>
>>
>>
>> -
>> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
>> --
>> View this message in context:
>> http://osgeo-org.1560.x6.nabble.com/Outline-border-stroke-tp5306671p5306709.html
>> Sent from the QGIS - Developer mailing list archive at Nabble.com
>> .
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org 
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>

-- 
Terglobo
Fahrenheitstraat 1
5223 BJ 's-Hertogenbosch
06 25 31 49 83
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] RE : thanks for the HF

2014-10-05 Thread yjacolin
A big +1 from me. It was again an awesome hackfest.

Y.

 Message d'origine 
De : Matteo Ghetta matteo.ghe...@gmail.com 
Date :05/10/2014  14:18  (GMT+01:00) 
A : qgis-developer qgis-developer@lists.osgeo.org 
Objet : [Qgis-developer] thanks for the HF 

hi all,
just to say thanks for the awesome days of the essen hf!

a special thanks to otto and all those contribute to the incredible 
organization!

see you soon!!

Matteo___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] RE : Re: QGIS Web Client improvements

2014-01-03 Thread yjacolin
Hello


Rather a SLD specification which add some new parameters to WMS services.

Y.


Envoyé depuis un mobile Samsung

 Message d'origine 
De : aperi2007 aperi2...@gmail.com 
Date :  
A : rldhont rldh...@gmail.com 
Cc : QGIS Developer Mailing List qgis-developer@lists.osgeo.org 
Objet : Re: [Qgis-developer] QGIS Web Client improvements 
 
On 03/01/2014 15:47, rldhont wrote:

 Yes, but you can query the style in SLD and have the CLASS name.

 Others clients like mapfish use it

 Regards,
 René-Luc D'Hont
Hi,

Is really interst this information.
I don't know this option.

Is a wms specs request ?

Thx,

Andrea.

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Help translating Qgis documentation into french

2011-11-13 Thread yjacolin
Hello Kimaidou,

I am curently finishing one of the last file. See 
http://wiki.osgeo.org/wiki/Doc_qgis_fr for a list of files. I need to check the 
foreword chapter as Christophe tell me on Francophone ML that he didn't finish 
it. You can check it will help surely.

After the next release (1.8) of the documentation there will be a big work to 
migrate documentation to RST. Help will be welcome.

Y.

- Mail original -
De: kimaidou kimai...@gmail.com
À: qgis-developer qgis-developer@lists.osgeo.org
Envoyé: Dimanche 13 Novembre 2011 14:38:55
Objet: [Qgis-developer] Help translating Qgis documentation into french


Hi devs,


I would like to contribute to Qgis documentation in French. I invite people 
already involved in the french translation to answer this email if there is 
some space for another volunteer...


Regards
Kimaidou
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Help translating Qgis documentation into french

2011-11-13 Thread yjacolin
Hello Jean-ROC,

Yep. Otto will give more information I think but here is a synthesis:
* first we move to github and test the new process
* we publish the 1.8 release of the doc, translation process begin
* changes LaTeX to RST occurs in master.

RST file will be converted to odt file or HTML with a style specific to QGIS 
(it is really easy,
we just need to edit an odt file, create our style and uses this file as 
value of the --stylesheet flag). From odt we could thus create pdf, doc file. 
etc.

I will test really soon this process for the gdal-ogr documentation and so will 
contact you for the cover ;)

Y.
- Mail original -
De: MORREALE Jean Roc jr.morre...@enoreth.net
À: qgis-developer@lists.osgeo.org
Envoyé: Dimanche 13 Novembre 2011 16:12:29
Objet: Re: [Qgis-developer] Help translating Qgis documentation into french

Regarding RST, has any decision been made at the hackfest ?

Le 13/11/2011 15:24, yjaco...@free.fr a écrit :
 Hello Kimaidou,

 I am curently finishing one of the last file. See
 http://wiki.osgeo.org/wiki/Doc_qgis_fr for a list of files. I need to
 check the foreword chapter as Christophe tell me on Francophone ML
 that he didn't finish it. You can check it will help surely.

 After the next release (1.8) of the documentation there will be a big
 work to migrate documentation to RST. Help will be welcome.

 Y.

 - Mail original - De: kimaidoukimai...@gmail.com À:
 qgis-developerqgis-developer@lists.osgeo.org Envoyé: Dimanche 13
 Novembre 2011 14:38:55 Objet: [Qgis-developer] Help translating Qgis
 documentation into french


 Hi devs,


 I would like to contribute to Qgis documentation in French. I invite
 people already involved in the french translation to answer this
 email if there is some space for another volunteer...


 Regards Kimaidou
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer