Just a note that if anyone is looking for spatial address information for geocoding purposes, https://openaddresses.io/ is an interesting looking project (it only has very specific coverage regions though)...
On Wed, 23 Sep 2020 at 16:20, Nicolas Cadieux <[email protected]> wrote: > Hi, > Do you have coordinates (x,y) in that csv? You can generate the > geometries from that. If not, you will need to find a database for that. > What were you planing on using for the geospatial info? > > Nicolas Cadieux > > Le 23 sept. 2020 à 10:17, Erich Purpur <[email protected]> a écrit : > > > Thank you again for your response. I understand what you suggest but it > won't work in this case unfortunately. > > I only have a .csv file, which has an address and all the other > information too. There is no other layer. > > -Erich > > On Wed, Sep 23, 2020 at 10:12 AM Nicolas Cadieux < > [email protected]> wrote: > >> >> Hi, >> >> To do this, you need two files. If they are csv, you can use that. If >> you are limited in what you can do, just save a geopackage. You will need >> one file with the addresses (that you have) and one file, or a data base >> with the georeferenced information. Do you have that? If not what where >> you planing to use to find the geographic positions of the objects? >> >> A csv is a vector layer if it’s georeferenced or a database if it’s not. >> You may be limited in what you can do but export it to a for at that QGIS >> can write to like geopackage or SpatiaLite which is the same thing but with >> not spatial info. >> >> Nicolas Cadieux >> >> Le 23 sept. 2020 à 08:52, Erich Purpur <[email protected]> a écrit : >> >> >> Hi Nicolas- >> >> The issue is that I have data in a .csv file. Each row has an address. >> Both the 'join attributes by location' and 'join attributes by field value' >> tool specify that it joins vector layers. But I don't have a vector layer. >> >> -Erich >> >> On Tue, Sep 22, 2020 at 7:41 PM Nicolas Cadieux < >> [email protected]> wrote: >> >>> Hi, >>> >>> Why not just use "Join Attributes by Location" or "Join Attributes by >>> Field Value" in Processing? If you have inconsistent results, I would look >>> at your data base. Are you using unique fields? Do you have duplicate >>> shapes or shape collections (MultiPoints, Mulit...)? What method are you >>> using? intersects, within... ? >>> >>> Nicolas >>> On 2020-09-22 7:19 p.m., Erich Purpur wrote: >>> >>> Hi all- >>> >>> Geocoding is the one process I am still doing in ArcPro. Most of the >>> QGIS geocoding tutorials I have found recommend using the Geocoding tool in >>> MMQGIS but I have really struggled to get consistent results. >>> >>> Does anyone have an alternative Geocoding plugin or other tool they >>> use? It doesn't have to be within QGIS, an external tool would be fine. >>> >>> Thank you, >>> >>> Erich Purpur >>> >>> _______________________________________________ >>> Qgis-user mailing [email protected] >>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user >>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user >>> >>> _______________________________________________ > Qgis-user mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________ Qgis-user mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
