Join attributes by “locations” Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How to convert Shapefiles to 3D DXF?How to spatial join points attributes to layer with two (or more) overlapping buffers in QGIS?Join polylines between pointsCreating Direction data in QGIS between two layers?Why does QGIS algorithm 'Join attributes table' change the types of the shapefile attributes?Too many features in QGIS DXF import: 1 Feature per ColumnHow to export “solid” 3D objects from QGIS to DXF?QGIS 3.2 - Forcing column type when importing csvHow to join many points with lines?QGIS custom UTM CRS including zone number in coordinates?

Where is the Next Backup Size entry on iOS 12?

Does the Mueller report show a conspiracy between Russia and the Trump Campaign?

Delete free apps from library

What does it mean that physics no longer uses mechanical models to describe phenomena?

How can I save and copy a screenhot at the same time?

Why is a lens darker than other ones when applying the same settings?

Differences to CCompactSize and CVarInt

Is openssl rand command cryptographically secure?

Tannaka duality for semisimple groups

How does light 'choose' between wave and particle behaviour?

Monty Hall Problem-Probability Paradox

In musical terms, what properties are varied by the human voice to produce different words / syllables?

The Nth Gryphon Number

How do living politicians protect their readily obtainable signatures from misuse?

Simple Http Server

Printing attributes of selection in ArcPy?

NERDTreeMenu Remapping

What is the origin of 落第?

How much damage would a cupful of neutron star matter do to the Earth?

How to write capital alpha?

Random body shuffle every night—can we still function?

Does the Black Tentacles spell do damage twice at the start of turn to an already restrained creature?

Can an iPhone 7 be made to function as a NFC Tag?

Why datecode is SO IMPORTANT to chip manufacturers?



Join attributes by “locations”



Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How to convert Shapefiles to 3D DXF?How to spatial join points attributes to layer with two (or more) overlapping buffers in QGIS?Join polylines between pointsCreating Direction data in QGIS between two layers?Why does QGIS algorithm 'Join attributes table' change the types of the shapefile attributes?Too many features in QGIS DXF import: 1 Feature per ColumnHow to export “solid” 3D objects from QGIS to DXF?QGIS 3.2 - Forcing column type when importing csvHow to join many points with lines?QGIS custom UTM CRS including zone number in coordinates?



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








4















I got a DXF file with some height data which I can easly open in QGIS, the problem is when I import it to QGIS is that the "float" is separated from it's Integer. Instead of one point with 4.8 is there two points one with 4 and one with 8. And those points that is 5.0 does not have its "float" and is just "5". Like this:



Visualizing the data



Is there any tool in QGIS that I can use to combine the float and integer? The "float" is approximativ 1.7m south east of the integer.










share|improve this question

















  • 1





    There's the nearest neighbor join plugin, but I don't think it will distinguish between float points and integer points. So a point pair with values 3 and 7 will combine as 3,7 and 7,3. It looks like the float is always a offset by the same distance in the same direction, so maybe you can use the wedge_buffer() function with the intersects() function to figure out which points are floats and which are integers.

    – csk
    Apr 12 at 18:09

















4















I got a DXF file with some height data which I can easly open in QGIS, the problem is when I import it to QGIS is that the "float" is separated from it's Integer. Instead of one point with 4.8 is there two points one with 4 and one with 8. And those points that is 5.0 does not have its "float" and is just "5". Like this:



Visualizing the data



Is there any tool in QGIS that I can use to combine the float and integer? The "float" is approximativ 1.7m south east of the integer.










share|improve this question

















  • 1





    There's the nearest neighbor join plugin, but I don't think it will distinguish between float points and integer points. So a point pair with values 3 and 7 will combine as 3,7 and 7,3. It looks like the float is always a offset by the same distance in the same direction, so maybe you can use the wedge_buffer() function with the intersects() function to figure out which points are floats and which are integers.

    – csk
    Apr 12 at 18:09













4












4








4








I got a DXF file with some height data which I can easly open in QGIS, the problem is when I import it to QGIS is that the "float" is separated from it's Integer. Instead of one point with 4.8 is there two points one with 4 and one with 8. And those points that is 5.0 does not have its "float" and is just "5". Like this:



Visualizing the data



Is there any tool in QGIS that I can use to combine the float and integer? The "float" is approximativ 1.7m south east of the integer.










share|improve this question














I got a DXF file with some height data which I can easly open in QGIS, the problem is when I import it to QGIS is that the "float" is separated from it's Integer. Instead of one point with 4.8 is there two points one with 4 and one with 8. And those points that is 5.0 does not have its "float" and is just "5". Like this:



Visualizing the data



Is there any tool in QGIS that I can use to combine the float and integer? The "float" is approximativ 1.7m south east of the integer.







qgis qgis-3






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 12 at 9:29









axel_andeaxel_ande

761317




761317







  • 1





    There's the nearest neighbor join plugin, but I don't think it will distinguish between float points and integer points. So a point pair with values 3 and 7 will combine as 3,7 and 7,3. It looks like the float is always a offset by the same distance in the same direction, so maybe you can use the wedge_buffer() function with the intersects() function to figure out which points are floats and which are integers.

    – csk
    Apr 12 at 18:09












  • 1





    There's the nearest neighbor join plugin, but I don't think it will distinguish between float points and integer points. So a point pair with values 3 and 7 will combine as 3,7 and 7,3. It looks like the float is always a offset by the same distance in the same direction, so maybe you can use the wedge_buffer() function with the intersects() function to figure out which points are floats and which are integers.

    – csk
    Apr 12 at 18:09







1




1





There's the nearest neighbor join plugin, but I don't think it will distinguish between float points and integer points. So a point pair with values 3 and 7 will combine as 3,7 and 7,3. It looks like the float is always a offset by the same distance in the same direction, so maybe you can use the wedge_buffer() function with the intersects() function to figure out which points are floats and which are integers.

– csk
Apr 12 at 18:09





There's the nearest neighbor join plugin, but I don't think it will distinguish between float points and integer points. So a point pair with values 3 and 7 will combine as 3,7 and 7,3. It looks like the float is always a offset by the same distance in the same direction, so maybe you can use the wedge_buffer() function with the intersects() function to figure out which points are floats and which are integers.

– csk
Apr 12 at 18:09










1 Answer
1






active

oldest

votes


















2














Thanks for the comment!



To solve this problem, I first used the NNJoin plugin and joined all nearest neighbor. The "problem" is that also the points without the float got a joined value, to solve this I used the wedge buffer algoritm where I "targeted" the integer part (NW).
Img1
Now I used select by location and selected all "integer parts" so in the picture above the 5 close to 2 was selected but not the single 5 bellow. Then I updated the selected features of that layer and created a new column "not_int" and set it to 1.



Now I wanted to remove all "float" points so then I created a new wedged buffer (SE) and select by location with the new buffer. Then I deleted all selected rows.



Finally I updated the remaining point with this case statement CASE WHEN not_int THEN to_real("Height" +'.'+ "join_Height") ELSE to_real("Height") END



With this result:
img2






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "79"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f318582%2fjoin-attributes-by-locations%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    Thanks for the comment!



    To solve this problem, I first used the NNJoin plugin and joined all nearest neighbor. The "problem" is that also the points without the float got a joined value, to solve this I used the wedge buffer algoritm where I "targeted" the integer part (NW).
    Img1
    Now I used select by location and selected all "integer parts" so in the picture above the 5 close to 2 was selected but not the single 5 bellow. Then I updated the selected features of that layer and created a new column "not_int" and set it to 1.



    Now I wanted to remove all "float" points so then I created a new wedged buffer (SE) and select by location with the new buffer. Then I deleted all selected rows.



    Finally I updated the remaining point with this case statement CASE WHEN not_int THEN to_real("Height" +'.'+ "join_Height") ELSE to_real("Height") END



    With this result:
    img2






    share|improve this answer



























      2














      Thanks for the comment!



      To solve this problem, I first used the NNJoin plugin and joined all nearest neighbor. The "problem" is that also the points without the float got a joined value, to solve this I used the wedge buffer algoritm where I "targeted" the integer part (NW).
      Img1
      Now I used select by location and selected all "integer parts" so in the picture above the 5 close to 2 was selected but not the single 5 bellow. Then I updated the selected features of that layer and created a new column "not_int" and set it to 1.



      Now I wanted to remove all "float" points so then I created a new wedged buffer (SE) and select by location with the new buffer. Then I deleted all selected rows.



      Finally I updated the remaining point with this case statement CASE WHEN not_int THEN to_real("Height" +'.'+ "join_Height") ELSE to_real("Height") END



      With this result:
      img2






      share|improve this answer

























        2












        2








        2







        Thanks for the comment!



        To solve this problem, I first used the NNJoin plugin and joined all nearest neighbor. The "problem" is that also the points without the float got a joined value, to solve this I used the wedge buffer algoritm where I "targeted" the integer part (NW).
        Img1
        Now I used select by location and selected all "integer parts" so in the picture above the 5 close to 2 was selected but not the single 5 bellow. Then I updated the selected features of that layer and created a new column "not_int" and set it to 1.



        Now I wanted to remove all "float" points so then I created a new wedged buffer (SE) and select by location with the new buffer. Then I deleted all selected rows.



        Finally I updated the remaining point with this case statement CASE WHEN not_int THEN to_real("Height" +'.'+ "join_Height") ELSE to_real("Height") END



        With this result:
        img2






        share|improve this answer













        Thanks for the comment!



        To solve this problem, I first used the NNJoin plugin and joined all nearest neighbor. The "problem" is that also the points without the float got a joined value, to solve this I used the wedge buffer algoritm where I "targeted" the integer part (NW).
        Img1
        Now I used select by location and selected all "integer parts" so in the picture above the 5 close to 2 was selected but not the single 5 bellow. Then I updated the selected features of that layer and created a new column "not_int" and set it to 1.



        Now I wanted to remove all "float" points so then I created a new wedged buffer (SE) and select by location with the new buffer. Then I deleted all selected rows.



        Finally I updated the remaining point with this case statement CASE WHEN not_int THEN to_real("Height" +'.'+ "join_Height") ELSE to_real("Height") END



        With this result:
        img2







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 15 at 19:23









        axel_andeaxel_ande

        761317




        761317



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Geographic Information Systems Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f318582%2fjoin-attributes-by-locations%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            រឿង រ៉ូមេអូ និង ហ្ស៊ុយលីយេ សង្ខេបរឿង តួអង្គ បញ្ជីណែនាំ

            QGIS export composer to PDF scale the map [closed] Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Print Composer QGIS 2.6, how to export image?QGIS 2.8.1 print composer won't export all OpenCycleMap base layer tilesSave Print/Map QGIS composer view as PNG/PDF using Python (without changing anything in visible layout)?Export QGIS Print Composer PDF with searchable text labelsQGIS Print Composer does not change from landscape to portrait orientation?How can I avoid map size and scale changes in print composer?Fuzzy PDF export in QGIS running on macSierra OSExport the legend into its 100% size using Print ComposerScale-dependent rendering in QGIS PDF output

            PDF-ში გადმოწერა სანავიგაციო მენიუproject page