Hi all I have seen that quite a few people had a look at this feature description but only few commented or modified it. Can I assume that most agree with the description as it is and would support / welcome such an implementation?
If no major concern, I would love to ask a quote to a few devs by the end of this week so that we can quickly evaluate the financial options. Thanks a lot in advance! Stéphane Le jeudi 12 janvier 2017, Stéphane Henriod <[email protected]> a écrit : > Hi all > > upon advice from Andreas, I started a formal description of the > requirements for such a feature: > > https://docs.google.com/document/d/1cDemM2m88_mbs65sYzfBbVdHI_ObOjf_ > i35ne3OKsRs/edit?usp=sharing > > Please, anyone interested, do check, comment, add, correct,... Once we > have a "final" version, I will inquire a more precise financial estimation. > Then let's see how we can move forward! > > Thanks and cheers > > Stéphane > > > Le jeudi 12 janvier 2017, Stéphane Henriod <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> a écrit : > >> Hi Alexandre >> >> (also posting on user-) >> >> I 100% agree with you and I would love to somehow give back to QGIS (I >> did already, but at a small scale). >> >> I mostly wanted to know if I am the only one to wish for this feature. >> Apparently not the case: many have expressed the same wish! >> >> Now funding: I would love to have a rough idea what "not very expensive" >> means. If there are any dev around who could have the interest / skills to >> implement this feature, can we somehow go concrete and work together on a >> feature description and tentative budget? The situation is obviously very >> different if we talk about 1.000 or 20.000€ >> >> Cheers >> >> Stéphane >> >> >> Le jeudi 12 janvier 2017, Alexandre Neto <[email protected]> a >> écrit : >> >>> Hello Stéphane, >>> >>> IMHO, since it seems that you are not able/willing to sponsor the >>> feature yourself, sounds like a good opportunity for a small crowdfunding. >>> >>> That way you would be able to contribute back to QGIS by giving your >>> time in finding a developer able to do it, setting up the crowdfunding, >>> advertise it, pay for part of it and so on. >>> >>> It looks like a simple feature. it should not be very expensive (much >>> less than an ArcGIS license for sure), and if you think many people need >>> this, then the money will be easy to raise. >>> >>> Alexandre Neto >>> >>> Stéphane Henriod <[email protected]> escreveu no dia quarta, >>> 11/01/2017 às 11:37: >>> >>>> One last message for today (sorry for spamming!) >>>> >>>> It seems that this feature would actually be wished by "many" people >>>> (see the ticket and the talks on user-). I just gave a try to 2.99-nightly >>>> and, as far as I can see, nothing has been done in this direction (yet?). >>>> >>>> I am wondering if there are massive challenges that I am overlooking or >>>> if this could be implemented quite easily. In any case, do you think this >>>> is a request that can be taken on to 3.0? >>>> >>>> Thanks a lot to all the devs here... I feel quite bad for asking for a >>>> new feature while not having the competences to contribute a tiny bit to >>>> its development but I really feel this is one of the few major missing >>>> features in QGIS right now (and will be happy to help on the feature >>>> requirements, the tests, etc.). >>>> >>>> All the best! >>>> >>>> Stéphane >>>> >>>> >>>> Le mercredi 11 janvier 2017, Stéphane Henriod <[email protected]> >>>> a écrit : >>>> >>>>> Hi again >>>>> >>>>> it seems that the requirements are related (although not 100% similar) >>>>> to this other open (and assigned) ticket: >>>>> http://hub.qgis.org/issues/14449 >>>>> >>>>> I really hope to see this very needed feature in a coming version of >>>>> QGIS and happy to help wherever I can! >>>>> >>>>> Cheers >>>>> >>>>> Stéphane >>>>> >>>>> >>>>> Le mardi 10 janvier 2017, Stéphane Henriod <[email protected]> a >>>>> écrit : >>>>> >>>>>> Hi >>>>>> >>>>>> let me move here a request that has been shortly discussed on the >>>>>> user-mailing list: >>>>>> http://lists.osgeo.org/pipermail/qgis-user/2017-January/038793.html >>>>>> http://lists.osgeo.org/pipermail/qgis-user/2017-January/038795.html >>>>>> http://lists.osgeo.org/pipermail/qgis-user/2017-January/038801.html >>>>>> >>>>>> and for which a ticket is open: >>>>>> http://hub.qgis.org/issues/14845 >>>>>> >>>>>> I was said that some work has been done in this direction for 3.0 but >>>>>> I don't know if it completely covers the feature request >>>>>> >>>>>> ---------------------- >>>>>> >>>>>> When styling a discrete or boolean raster, there seems to be no >>>>>> direct method, only a few workarounds. The feature I dream of would do >>>>>> the >>>>>> following: >>>>>> >>>>>> - A new render type "Discrete raster" >>>>>> - One button allows to fetch all unique values form the raster >>>>>> (with a warning message if there are more than XXX unique values) >>>>>> - A color ramp is applied by default >>>>>> - I can multi-select values and apply them the same style and / >>>>>> or the same label >>>>>> - I can remove values. The pixels with those values will simply >>>>>> not be displayed >>>>>> - I can save my color map and load an existing color map >>>>>> >>>>>> So pretty much like the ArcGIS implementation: >>>>>> http://resources.arcgis.com/en/help/main/10.1/index.html#/re >>>>>> presenting_unique_categories_such_as_land_use/009t00000074000000/ >>>>>> >>>>>> The current limitations I see (in 2.14): >>>>>> >>>>>> - The discrete values must be entered manually, which is a pain >>>>>> for a raster with many unique values (or if I don't know in advance >>>>>> what >>>>>> all values are) >>>>>> - If I click on *Classify*, QGIS will choose X values (based on >>>>>> the number of classes and the classification method (continuous or >>>>>> equal >>>>>> interval)), which no longer match the "exact" values of my raster. It >>>>>> doesn't really make sense to classify a discrete rendering >>>>>> - Although it is currently possible to style discrete rasters, >>>>>> the procedure is not really intuitive for beginners >>>>>> >>>>>> ---------------------- >>>>>> >>>>>> Is this a feature that is envisioned for 3.0? Is there anything I can >>>>>> do to support it? (except coding it myself, since I don't have the skills >>>>>> for that...) >>>>>> >>>>>> Thanks a lot in advance >>>>>> >>>>>> Cheers >>>>>> >>>>>> Stéphane >>>>>> >>>>>> >>>>> >>>>> -- >>>>> >>>>> “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 >>>>> >>>>> >>>> >>>> -- >>>> >>>> “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 >>>> >>>> _______________________________________________ >>>> Qgis-developer mailing list >>>> [email protected] >>>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >>>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> >>> -- >>> Alexandre Neto >>> --------------------- >>> @AlexNetoGeo >>> http://sigsemgrilhetas.wordpress.com >>> http://gisunchained.wordpress.com >>> >> >> >> -- >> >> “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 >> >> > > -- > > “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 > > -- “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
_______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
