If your database has (for example) LAT and LONG fields for a data point in each record, you will need to create a new calculated field whose result is a text string in the expected WKT format. The database must have the spatial data in a text field in WKT format. The same steps are valid for Windows and MAC OS. I am neither a GIS nor a Filemaker expert, and discovered this route after a lot of persistence and trial & error. Once set up, QGIS users will not need to have the Filemaker application. You will need to have the appropriate access and client software. The Filemaker database will need to be modified in order to set this up. Clicking the reload button on the toolbar of the attributes table will not trigger an update (bug?). Updated data in the database will only appear in the QGIS attributes table after you close and re-open the attributes table. This can be triggered by panning or zooming. Updated data in the database will mapped in QGIS only after your map is re-drawn. There are some useful hints on how to structure a FM database to speed up ODBC access here. This appears to be platform independant, and I get similar results on Windows and MAC OS (QGIS 3.6.1). If the two are separated by a slow network / internet connection and/or the FM database is big, with many links to other databases on the server or many joins within the same database, data refresh times are painful. The link can be quite slow, even if the database and QGIS are running on the same local machine. When the filemaker data changes, so does the data in QGIS. It is possible to set up a connection between the two that allows QGIS to read spatial data from a Filemaker database, without the intermediate CSV step. So my question is can QGIS connect with a FileMaker Pro database
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |