[Qgis-developer] option to set a global padding for layer labeling

[G. Allegri]

This requirement stems from the concept of "metabuffer" in tile caching, a
mechanism commonly user to mitigate label artifacts around tiles' margins.

I suppose that adding such opton would be as simple as reducing the bbox
set inside QgsLabelingEngine::run by the required amount, and obviously
adding the setting to the layers' labeling settings UI.

What's your opinion?
giovanni
___
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] Are there plans to create a unique "Add layer" tool?

[Alexandre Neto]

Hi,

Some of my colleagues will be in Essen for QGIS Developers meeting. They
will bring this up, and try to get the opinion of other developers. I'm
sure everyone there will be interested in contributing with ideas for it.

So, let's wait for now.

Thanks for your work.

Stéphane Henriod  escreveu no dia quinta, 27/04/2017
às 09:42:

> Hi all
>
> I would be more than happy to help push this new feature forward but I am
> not really sure what is needed now?
>
> Alexandre, I think you mentioned that your company might be interested to
> implement this unique "Add layer" button. Does the Gdoc now contain
> sufficient information for you to move on and identify what can
> realistically be done? Or is there a need for more polishing?
>
> Thanks in advance!
>
> Stéphane
>
>
> Le vendredi 21 avril 2017, Stéphane Henriod  a
> écrit :
>
>> Done!
>>
>>
>> https://docs.google.com/document/d/1aMX9jOfl10q8oETRzOHSHnRpHCc7UJ1dDnCCq3VyTAY/edit?usp=sharing
>>
>>
>> “When you travel, remember that a foreign country is not designed to make
>> you comfortable. It is designed to make its own people comfortable." --
>> Clifton Fadiman
>>
>> 2017-04-20 14:47 GMT+06:00 Alexandre Neto :
>>
>>> Fine with me.
>>>
>>> Stéphane Henriod  escreveu no dia terça,
>>> 18/04/2017 às 05:46:
>>>
 Hi all

 Harrissou has quite intensively re-organised the doc, which is now,
 IMO, much clearer. Thanks for that!

 But lots of changes are in "suggestion mode". I'd like to accept all
 those changes to increase the clarity and readability. Any objection on
 this?

 Thanks and cheers

 Stéphane


 Le mercredi 12 avril 2017, Alexandre Neto  a
 écrit :

> Hi Stéphane,
>
> I believe it's a great starting point, very complete (I would not
> remember/consider some types of data).
>
> We still need to fill the second page and discuss the possible UI/UX
> implementation. Then, we will need some developers (I'm not a developer) 
> to
> consider the requests and filter what would be hard or impossible to 
> tackle.
>
> Our best chance to have this implemented is by doing baby steps. I
> would not consider more data format/providers than the ones we have in the
> manage layers toolbar in this first phase.
>
> Thanks!
>
> Stéphane Henriod  escreveu no dia terça,
> 11/04/2017 às 12:57:
>
>> Hi Alexandre
>>
>> this is indeed great!
>>
>> Is the gdoc as it is now helpful enough for you to design a possible
>> implementation? Or, if not, what other inputs / comments would be 
>> necessary?
>>
>> Cheers
>>
>> Stéphane
>>
>>
>> Le lundi 10 avril 2017, Alexandre Neto  a
>> écrit :
>>
>>> Hello all,
>>>
>>> At Boundless we are planning to put some development time in this
>>> "unified add layer" button/feature. As others already did, our idea was 
>>> to
>>> use the browser panel as a base for replacing most of the buttons and 
>>> add
>>> any capabilities that are still missing.
>>>
>>> So, let's work together to find what are those missing pieces, and
>>> how it would be the best way to implement it. We will put our thoughts 
>>> in
>>> the Google document. As soon we have it stabilized we can start 
>>> creating a
>>> QEP for it.
>>>
>>> Thanks,
>>>
>>> Alexandre Neto
>>>
>>> Stéphane Henriod  escreveu no dia quinta,
>>> 6/04/2017 às 12:14:
>>>
 Thanks Harrissou!

 I took the liberty to remove the first table (that I created) and
 to leave only yours. It is more complete anyway

 Cheers

 Stéphane


 Le mercredi 5 avril 2017, DelazJ  a écrit :

> I took the liberty to do some changes to the doc (especially add a
> new table with more detailed features on the existing tools + 
> comments).
> It's supposed to replace the table already drafted but I didn't go so 
> far
> without a review.
>
> 2017-04-05 10:36 GMT+02:00 DelazJ :
>
>> Hi Stéphane,
>> actually there's no more UX team (list). UX mailing list has been
>> shut down months ago because it used to refer to dev list for most of
>> decisions/advices so UX matters are now discussed either in the dev 
>> mailing
>> list (we maybe can keep this thread) or, I guess until QGIS3 
>> release, in
>> the qgis3_UIX_discussion repository.
>>
>>
>> Regards,
>> Harrissou
>>
>> 2017-04-05 10:19 GMT+02:00 Stéphane Henriod <
>> 

Re: [Qgis-developer] QGEP - right place to raise issues and discuss technical matters ?

[Matthias Kuhn]

Hi Michaël,

On 04/27/2017 11:51 AM, kimaidou wrote:
> Hi,
> 
> I have chosen to use the Github repository. Any feedback appreciated ;)
> I will probably add more issues, and ad PR. Please tell me if I need to
> stop !
> 
> https://github.com/QGEP/QGEP/issues/created_by/mdouchin
> https://github.com/QGEP/datamodel/pull/12#issuecomment-297654347

I think that github is the right place indeed. I like the possibility to
keep discussins threaded, mark them as resolved, label them, search and
browse them. Are there some things for which you would prefer a mailing
list?

> I think we could use QGIS dev mailing list to discuss some matter
> related to QGEP, but only if there is an impact on QGIS (feature
> missing, etc.), as Matthias and other QGEP devs do sometimes.

For anything that's not wastewater specific business logic (so api,
performance, forms ...), the list is of course perfectly fine like for
any other plugin.

> 
>  
> 
> 
> Maybe we could discuss that at Essen, will you join?
> 
> 
> I won't attend this meeting, but I will be available for any online
> interaction ( irc, emails, wiki, webconf, etc.)
>  
> 
> 
> Matthias, Denis, any opinion ?>
> 
> Same question ;)

Yes, I'll be in Essen ;)

Cheers
Matthias


> 
> 
> Cheers,
> Michaël
> 
> 
> 
> 
> ___
> 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] release file after processing.runalg

[enrico chiaradia]

Hi Stefan and many thanks for your answer! but it seems not working :(
Here the new code. I replaced "tempOutput" with "output". Layer is 
correctly loaded and removed but "tempOutput" cannot be deleted.


import processing
import os

tempOutput = 'D:/test_alg/map_to_clip.tif'
maskFN = 'D:/test_alg/mask.shp'
output = 'D:/test_alg/clipped_map.tif'

algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
tempOutput,
maskFN,
"-",False,False,False,5,4,75,6,1,False,0,False,"",
output)

try:
# add to the map
tempLay = QgsRasterLayer(output, "tempLay")
if not tempLay.isValid(): raise Exception("Failed to load tempLay")
QgsMapLayerRegistry.instance().addMapLayer(tempLay) #

layermap = QgsMapLayerRegistry.instance().mapLayers()
for i, layer in layermap.iteritems():
  if layer.source() == output:
print 'layername',layer.source()
# Remove layer references
QgsMapLayerRegistry.instance().removeMapLayer(layer.id()) #

# Delete the file
os.remove(tempOutput)

except Exception as e:
print e




Il 27/04/2017 16:07, Stefan Kiefer ha scritto:

Hi enrico,
as far as I see from the reference you added the solution would be to add the result (resp. output) 
to a Layer instead "tempOutput". Then you remove that Layer, I suppose while removing the 
layer a reference on "tempOutput" ist released.

cheers

Stefan


enrico chiaradia  hat am 27. April 2017 um 15:13 
geschrieben:


Dear List,

I'd like to remove an existing file (see [tempOutput]) after it was used
by a geoalgorithm. The geoalgorithm works perfectly but after its
execution, the file [tempOutput] is locked.

Here a simple test script that returns "[Error 32] The process cannot
access the file because it is being used by another process:
'D:/test_alg/map_to_clip.tif'":

import processing
import os

tempOutput = 'D:/test_alg/map_to_clip.tif'
maskFN = 'D:/test_alg/mask.shp'
output = 'D:/test_alg/clipped_map.tif'

algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
  tempOutput,
  maskFN,
"-",False,False,False,5,4,75,6,1,False,0,False,"",
  output)

try:
  os.remove(tempOutput)
except Exception as e:
  print e

I also found a solution on the web [1] but it doesn't work for me :( If
I understand correctly, the trick is to load the file as layer and then
release it. Here its implementation:

import processing
import os

tempOutput = 'D:/test_alg/map_to_clip.tif'
maskFN = 'D:/test_alg/mask.shp'
output = 'D:/test_alg/clipped_map.tif'

algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
  tempOutput,
  maskFN,
"-",False,False,False,5,4,75,6,1,False,0,False,"",
  output)

try:
  # add to the map
  tempLay = QgsRasterLayer(tempOutput, "tempLay")
  if not tempLay.isValid(): raise Exception("Failed to load tempLay")
  QgsMapLayerRegistry.instance().addMapLayer(tempLay) #

  layermap = QgsMapLayerRegistry.instance().mapLayers()
  for i, layer in layermap.iteritems():
print 'layername',layer.source()
if layer.source() == tempOutput:
  # Remove layer references
  QgsMapLayerRegistry.instance().removeMapLayer(layer.id()) #
  # Delete the file
  os.remove(tempOutput)

except Exception as e:
  print e

I didn't find any other solution for the moment. Any suggestion is
really very appreciate!

Thanks

enrico


[1]
https://gis.stackexchange.com/questions/93143/can-not-delete-file-after-using-runalg-function



___
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] release file after processing.runalg

[Stefan Kiefer]

Hi enrico,
as far as I see from the reference you added the solution would be to add the 
result (resp. output) to a Layer instead "tempOutput". Then you remove that 
Layer, I suppose while removing the layer a reference on "tempOutput" ist 
released.

cheers

Stefan

> enrico chiaradia  hat am 27. April 2017 um 15:13 
> geschrieben:
> 
> 
> Dear List,
> 
> I'd like to remove an existing file (see [tempOutput]) after it was used 
> by a geoalgorithm. The geoalgorithm works perfectly but after its 
> execution, the file [tempOutput] is locked.
> 
> Here a simple test script that returns "[Error 32] The process cannot 
> access the file because it is being used by another process: 
> 'D:/test_alg/map_to_clip.tif'":
> 
> import processing
> import os
> 
> tempOutput = 'D:/test_alg/map_to_clip.tif'
> maskFN = 'D:/test_alg/mask.shp'
> output = 'D:/test_alg/clipped_map.tif'
> 
> algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
>  tempOutput,
>  maskFN,
> "-",False,False,False,5,4,75,6,1,False,0,False,"",
>  output)
> 
> try:
>  os.remove(tempOutput)
> except Exception as e:
>  print e
> 
> I also found a solution on the web [1] but it doesn't work for me :( If 
> I understand correctly, the trick is to load the file as layer and then 
> release it. Here its implementation:
> 
> import processing
> import os
> 
> tempOutput = 'D:/test_alg/map_to_clip.tif'
> maskFN = 'D:/test_alg/mask.shp'
> output = 'D:/test_alg/clipped_map.tif'
> 
> algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
>  tempOutput,
>  maskFN,
> "-",False,False,False,5,4,75,6,1,False,0,False,"",
>  output)
> 
> try:
>  # add to the map
>  tempLay = QgsRasterLayer(tempOutput, "tempLay")
>  if not tempLay.isValid(): raise Exception("Failed to load tempLay")
>  QgsMapLayerRegistry.instance().addMapLayer(tempLay) #
> 
>  layermap = QgsMapLayerRegistry.instance().mapLayers()
>  for i, layer in layermap.iteritems():
>print 'layername',layer.source()
>if layer.source() == tempOutput:
>  # Remove layer references
>  QgsMapLayerRegistry.instance().removeMapLayer(layer.id()) #
>  # Delete the file
>  os.remove(tempOutput)
> 
> except Exception as e:
>  print e
> 
> I didn't find any other solution for the moment. Any suggestion is 
> really very appreciate!
> 
> Thanks
> 
> enrico
> 
> 
> [1] 
> https://gis.stackexchange.com/questions/93143/can-not-delete-file-after-using-runalg-function
> 
> 
> 
> ___
> 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] processing modeler: join attributes table

[Martin Landa]

Hi,

we are trying to join attribute table with another table in processing
modeler (using "Join attributes table" algorithm), but it fails:

"""
Running Join attributes table [2/2]

Parameters: INPUT_LAYER
=/tmp/processingb49e46d91a8d4997a4d2c2b0a2e31e7c/94a754a43e4a4074bcbd79714a0eebcf/OUTPUTALGQGISUNION1.shp,
INPUT_LAYER_2 =/home/landa/Documents/YFSG/hydrologie/hydrologie/vzorek1/hpj.shp,
TABLE_FIELD =HPJ, TABLE_FIELD_2 =HPJ

Failed

Error executing algorithm Join attributes table
QgsFeature.setGeometry(QgsGeometry): argument 1 has unexpected type
'NoneType' See log for more details
"""

The parameters should be fine - the both tables (attribute table and
CSV table contain column 'HPJ'). It's possible to join CSV table file
with attribute table manually in QGIS without any problems. It seems
to be a bug in processing modeler, can you confirm it?

Thanks, Martin

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
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] release file after processing.runalg

[enrico chiaradia]

Dear List,

I'd like to remove an existing file (see [tempOutput]) after it was used 
by a geoalgorithm. The geoalgorithm works perfectly but after its 
execution, the file [tempOutput] is locked.


Here a simple test script that returns "[Error 32] The process cannot 
access the file because it is being used by another process: 
'D:/test_alg/map_to_clip.tif'":


import processing
import os

tempOutput = 'D:/test_alg/map_to_clip.tif'
maskFN = 'D:/test_alg/mask.shp'
output = 'D:/test_alg/clipped_map.tif'

algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
tempOutput,
maskFN,
"-",False,False,False,5,4,75,6,1,False,0,False,"",
output)

try:
os.remove(tempOutput)
except Exception as e:
print e

I also found a solution on the web [1] but it doesn't work for me :( If 
I understand correctly, the trick is to load the file as layer and then 
release it. Here its implementation:


import processing
import os

tempOutput = 'D:/test_alg/map_to_clip.tif'
maskFN = 'D:/test_alg/mask.shp'
output = 'D:/test_alg/clipped_map.tif'

algRes = processing.runalg("gdalogr:cliprasterbymasklayer",
tempOutput,
maskFN,
"-",False,False,False,5,4,75,6,1,False,0,False,"",
output)

try:
# add to the map
tempLay = QgsRasterLayer(tempOutput, "tempLay")
if not tempLay.isValid(): raise Exception("Failed to load tempLay")
QgsMapLayerRegistry.instance().addMapLayer(tempLay) #

layermap = QgsMapLayerRegistry.instance().mapLayers()
for i, layer in layermap.iteritems():
  print 'layername',layer.source()
  if layer.source() == tempOutput:
# Remove layer references
QgsMapLayerRegistry.instance().removeMapLayer(layer.id()) #
# Delete the file
os.remove(tempOutput)

except Exception as e:
print e

I didn't find any other solution for the moment. Any suggestion is 
really very appreciate!


Thanks

enrico


[1] 
https://gis.stackexchange.com/questions/93143/can-not-delete-file-after-using-runalg-function




___
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] Plugin [1180] cartogram3 approval notification.

[noreply]

Plugin cartogram3 approval by pcav.
The plugin version "[1180] cartogram3 2.99.4" is now approved
Link: http://plugins.qgis.org/plugins/cartogram3/
___
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] QGEP - right place to raise issues and discuss technical matters ?

[kimaidou]

Hi,

I have chosen to use the Github repository. Any feedback appreciated ;)
I will probably add more issues, and ad PR. Please tell me if I need to
stop !

https://github.com/QGEP/QGEP/issues/created_by/mdouchin
https://github.com/QGEP/datamodel/pull/12#issuecomment-297654347

2017-04-21 11:44 GMT+02:00 kimaidou :

> Hi Régis,
>
> Thanks for your answer !
>
> 2017-04-14 16:16 GMT+02:00 Régis Haubourg :
>
>> Hi Michaël,
>> nice to see more people join the water application fest :).
>>
>> good question, and we could ask the same for similar projects like QWAT
>> and the others ready to launch.
>>
>> Your point is that we miss mailing list / IRC or other channels dedicated
>> to those projects ?
>>
>
> I had 2 questions in mind ;
> * ask for permission to report issues in the QGEP github repository.
> * ask if there is a dedicated and open mailing list for QGEP, or if I
> should instead use QGIS-dev mailing list to discuss some subject.
>
> I do not want to pollute the github issues with "newbie" questions or
> discussions, so I was asking QGEP maintainers their opinion about it.
>
>
>>
>> My guess is that it is up to each Steering comitee to decide if they want
>> to open those channels.
>>
>
> Yep !
>
>
>>
>> My personal opinion is a big yes, still we need to avoid opening *yet
>> another list of channels* when current cluttering is quite high (mails,
>> irc, gitter, matrix, git pr and issues, wikis) It's a real challenge for us
>> to avoid communication gaps.
>>
>
> I think we could use QGIS dev mailing list to discuss some matter related
> to QGEP, but only if there is an impact on QGIS (feature missing, etc.), as
> Matthias and other QGEP devs do sometimes.
>
>
>
>>
>> Maybe we could discuss that at Essen, will you join?
>>
>
> I won't attend this meeting, but I will be available for any online
> interaction ( irc, emails, wiki, webconf, etc.)
>
>
>>
>> Matthias, Denis, any opinion ?
>>
>
> Same question ;)
>
>
> Cheers,
> Michaël
>
___
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] Plugin [995] dzetsaka : Classification tool approval notification.

[noreply]

Plugin dzetsaka : Classification tool approval by pcav.
The plugin version "[995] dzetsaka : Classification tool 2.4.3" is now approved
Link: http://plugins.qgis.org/plugins/dzetsaka/
___
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] Plugin [903] PostTelemac approval notification.

[noreply]

Plugin PostTelemac approval by pcav.
The plugin version "[903] PostTelemac 1.0.1" is now approved
Link: http://plugins.qgis.org/plugins/PostTelemac/
___
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] Are there plans to create a unique "Add layer" tool?

[Stéphane Henriod]

Hi all

I would be more than happy to help push this new feature forward but I am
not really sure what is needed now?

Alexandre, I think you mentioned that your company might be interested to
implement this unique "Add layer" button. Does the Gdoc now contain
sufficient information for you to move on and identify what can
realistically be done? Or is there a need for more polishing?

Thanks in advance!

Stéphane


Le vendredi 21 avril 2017, Stéphane Henriod  a
écrit :

> Done!
>
> https://docs.google.com/document/d/1aMX9jOfl10q8oETRzOHSHnRpHCc7U
> J1dDnCCq3VyTAY/edit?usp=sharing
>
>
> “When you travel, remember that a foreign country is not designed to make
> you comfortable. It is designed to make its own people comfortable." --
> Clifton Fadiman
>
> 2017-04-20 14:47 GMT+06:00 Alexandre Neto  >:
>
>> Fine with me.
>>
>> Stéphane Henriod > > escreveu no dia
>> terça, 18/04/2017 às 05:46:
>>
>>> Hi all
>>>
>>> Harrissou has quite intensively re-organised the doc, which is now, IMO,
>>> much clearer. Thanks for that!
>>>
>>> But lots of changes are in "suggestion mode". I'd like to accept all
>>> those changes to increase the clarity and readability. Any objection on
>>> this?
>>>
>>> Thanks and cheers
>>>
>>> Stéphane
>>>
>>>
>>> Le mercredi 12 avril 2017, Alexandre Neto >> > a écrit :
>>>
 Hi Stéphane,

 I believe it's a great starting point, very complete (I would not
 remember/consider some types of data).

 We still need to fill the second page and discuss the possible UI/UX
 implementation. Then, we will need some developers (I'm not a developer) to
 consider the requests and filter what would be hard or impossible to 
 tackle.

 Our best chance to have this implemented is by doing baby steps. I
 would not consider more data format/providers than the ones we have in the
 manage layers toolbar in this first phase.

 Thanks!

 Stéphane Henriod  escreveu no dia terça,
 11/04/2017 às 12:57:

> Hi Alexandre
>
> this is indeed great!
>
> Is the gdoc as it is now helpful enough for you to design a possible
> implementation? Or, if not, what other inputs / comments would be 
> necessary?
>
> Cheers
>
> Stéphane
>
>
> Le lundi 10 avril 2017, Alexandre Neto  a
> écrit :
>
>> Hello all,
>>
>> At Boundless we are planning to put some development time in this
>> "unified add layer" button/feature. As others already did, our idea was 
>> to
>> use the browser panel as a base for replacing most of the buttons and add
>> any capabilities that are still missing.
>>
>> So, let's work together to find what are those missing pieces, and
>> how it would be the best way to implement it. We will put our thoughts in
>> the Google document. As soon we have it stabilized we can start creating 
>> a
>> QEP for it.
>>
>> Thanks,
>>
>> Alexandre Neto
>>
>> Stéphane Henriod  escreveu no dia quinta,
>> 6/04/2017 às 12:14:
>>
>>> Thanks Harrissou!
>>>
>>> I took the liberty to remove the first table (that I created) and to
>>> leave only yours. It is more complete anyway
>>>
>>> Cheers
>>>
>>> Stéphane
>>>
>>>
>>> Le mercredi 5 avril 2017, DelazJ  a écrit :
>>>
 I took the liberty to do some changes to the doc (especially add a
 new table with more detailed features on the existing tools + 
 comments).
 It's supposed to replace the table already drafted but I didn't go so 
 far
 without a review.

 2017-04-05 10:36 GMT+02:00 DelazJ :

> Hi Stéphane,
> actually there's no more UX team (list). UX mailing list has been
> shut down months ago because it used to refer to dev list for most of
> decisions/advices so UX matters are now discussed either in the dev 
> mailing
> list (we maybe can keep this thread) or, I guess until QGIS3 release, 
> in
> the qgis3_UIX_discussion repository.
>
>
> Regards,
> Harrissou
>
> 2017-04-05 10:19 GMT+02:00 Stéphane Henriod  >:
>
>> Hi all
>>
>> there have been a few additions in the Gdoc already (not sure
>> from whom) but I don't know if this is already sufficient for 
>> developers to
>> take this up?
>>
>> Also, I am not sure how to reach out to the UX team. Through a
>> separate 

Re: [Qgis-developer] Bugs on mapinfo tab files editing

[Matthias Kuhn]

Sorry,

I actually meant to send this link:

http://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis/

Regards
Matthias

On 4/27/17 8:10 AM, Matthias Kuhn wrote:
>
> Hi Pedro,
>
> Welcome to QGIS and thanks for reporting these bugs. As a first step,
> it is very important to be even aware of them. As a second step,
> someone will need to actually look into and take care of it. This
> normally happens by either the one who opened the issue having the
> capacity and know-how to fix it, by hoping that someone else will jump
> in and do it or by contacting one of the many companies that offer
> commercial support and will guide you through the bugfixing process.
>
> A list for companies providing professional support can be found here:
> https://www.qgis.org/en/site/forusers/commercial_support.html
>
> If you are interested in reading more about how the get things
> changed, have a look at the following blog post which covers more details:
> http://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis-a-follow-up/
>
> Thanks for following up on this
> Matthias
>
> On 4/27/17 1:55 AM, Pedro Camargo wrote:
>> Hi,
>>  I little while ago I reported two bugs (16451 and 16449)
>> regarding the corruption of Mapinfo tab files when they are edited in
>> QGIS (it happens very single time and for every single file).
>>
>>We used to do all our work using Mapinfo, so all our data is
>> maintained in that format.We are currently trying hard to move
>> everything to QGIS, but this bug with mapinfo files has been an
>> important deterrent for us. This brings me to a few questions:
>>
>> - Fixing bugs like that are a priority in the QGIS development?
>> - How can we (as a company) assist in resolving those bugs?
>>
>> Cheers,
>> Pedro
>>
>>
>> ___
>> 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 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] Bugs on mapinfo tab files editing

[Matthias Kuhn]

Hi Pedro,

Welcome to QGIS and thanks for reporting these bugs. As a first step, it
is very important to be even aware of them. As a second step, someone
will need to actually look into and take care of it. This normally
happens by either the one who opened the issue having the capacity and
know-how to fix it, by hoping that someone else will jump in and do it
or by contacting one of the many companies that offer commercial support
and will guide you through the bugfixing process.

A list for companies providing professional support can be found here:
https://www.qgis.org/en/site/forusers/commercial_support.html

If you are interested in reading more about how the get things changed,
have a look at the following blog post which covers more details:
http://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis-a-follow-up/

Thanks for following up on this
Matthias

On 4/27/17 1:55 AM, Pedro Camargo wrote:
> Hi,
>  I little while ago I reported two bugs (16451 and 16449)
> regarding the corruption of Mapinfo tab files when they are edited in
> QGIS (it happens very single time and for every single file).
>
>We used to do all our work using Mapinfo, so all our data is
> maintained in that format.We are currently trying hard to move
> everything to QGIS, but this bug with mapinfo files has been an
> important deterrent for us. This brings me to a few questions:
>
> - Fixing bugs like that are a priority in the QGIS development?
> - How can we (as a company) assist in resolving those bugs?
>
> Cheers,
> Pedro
>
>
> ___
> 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