[postgis-users] Is there a MapInfo to PostGIS/PostgreSQL loader?

Bo Victor Thomsen bo.victor.thomsen at gmail.com
Sun Sep 1 10:02:13 PDT 2019


Shao -

You are correct to assume, that schemas is a fundamental concept in 
relational database technology. But it's not a concept limited to 
PostGIS but is used throughout all database parts. Allmost all 
literature about PostGIS assumes you have some basic knowledge of 
PostgreSQl (relational SQL databases).

You can simply visualize the entire database as a set of /containers/ 
called /schemas/. Each schema (container) contains a set of object like 
tables, indexes, views, functions and others. The benefit of dividing 
the database into schemas is - among other benefits - that you can 
divide all the database objects in logical chunks in a orderly fashion.

As an /example/: You can define security in a database at the schema 
level and not the table level. Instead of administer all the individual 
tables you work with security on the schema level and afterward place 
each of the tables in the relevant schema. This radically minimize the 
workload associated with security administration.

If you compare a database to a file-system: The tables would be the 
files. The schemas would be the directories where the files reside in.

Take a look at this article 
https://www.lifewire.com/definition-of-a-schema-in-a-database-1019262

Den 31-08-2019 kl. 22:58 skrev Shaozhong SHI:
> Hi,
> Interesting.
> Surely, the fundamental is how the data is stored in postgresql and 
> how it is accessed.
>
> If you come across more detailed articles, please let me know.
>
> In postgis, the term schema is prominent, but it is not well explained 
> or used.
> Regards,
> Shao
>
> On Saturday, 31 August 2019, Bo Victor Thomsen 
> <bo.victor.thomsen at gmail.com <mailto:bo.victor.thomsen at gmail.com>> wrote:
>
>     Shao -
>
>     If you want to visualize spatial data in a Postgres/PostGIS
>     database using MapInfo as the viewing program you have to:
>
>       * Create a schema / table in : *MAPINFO.MAPINFO_MAPCATALOG. *
>       * Populate it with information about your spatial tables in the
>         Postgres database. It contains approximately the same
>         information that's stored in the normal
>         *public.geometry_columns* view plus some extra MapInfo
>         specific information.
>
>     MapInfo uses this table to get information about the different
>     spatial tables in the database, so it has to be present and
>     populated with the correct information.
>
>     If you use OGR2OGR to upload spatial data to Postgres, OGR2OGR
>     *won't***create or populate the *MAPINFO.MAPINFO_MAPCATALOG*
>     meta-table for you. However,  the Easyloader upload program is
>     capable of that. Finally, you can create and populate the
>     *MAPINFO.MAPINFO_MAPCATALOG* table manually.
>
>     You can download the Easyloader program from the Pitney Bowes
>     MapInfo Web site (Free download)
>
>     I suggest you read (and understand) the following article from the
>     MapInfo knowledge base:
>     http://support.pitneybowes.com/VFP05_KnowledgeWithSidebarHowTo?id=kA180000000PNiiCAG
>     <http://support.pitneybowes.com/VFP05_KnowledgeWithSidebarHowTo?id=kA180000000PNiiCAG>
>
>     -- 
>     Med venlig hilsen / Kind regards
>
>     Bo Victor Thomsen
>     aestasGIS Denmark
>
>
>     Den 31-08-2019 kl. 17:41 skrev Shaozhong SHI:
>>     Hi, Jeff,
>>     Thanks.  We can upload and visualise in qgis.
>>     But, I wonder where upload can include metadata.
>>     If you use qgis, you can use the data, but when you click on
>>     properties, you cannot find metadata.
>>     How to upload metadata into postgis/postgresql?
>>     Regards,
>>     Shao
>>
>>     On Friday, 30 August 2019, Jeff Norville <jeff at jnorville.com
>>     <mailto:jeff at jnorville.com>> wrote:
>>
>>         Hi Shao,
>>
>>         I generally use QGIS to visualize postgis / postgresql loads
>>         - but mostly because it's free. But if you're using MapInfo
>>         it seems the EasyLoader may be the way forward - there are
>>         some posts about this over on gis.stackexchange.com
>>         <http://gis.stackexchange.com>, including this guide:
>>         https://www.slideshare.net/peterhorsbollmoller/mapinfo-professional-120-and-sql-server-2008
>>         <https://www.slideshare.net/peterhorsbollmoller/mapinfo-professional-120-and-sql-server-2008>
>>
>>         Best,
>>         Jeff
>>
>>         On Tue, Aug 27, 2019 at 9:03 PM Shaozhong SHI
>>         <shishaozhong at gmail.com <mailto:shishaozhong at gmail.com>> wrote:
>>
>>             Hi, Tonis,
>>             We will bear that in mind.
>>             A friend of mine says that the problem is not being able
>>             to visualize what got into postgre.
>>             Regards,
>>             Shao
>>
>>             On Tuesday, 27 August 2019, Tõnis Kärdi
>>             <tonis.kardi at gmail.com <mailto:tonis.kardi at gmail.com>> wrote:
>>
>>                 Hi,
>>
>>                 one option would be to use ogr2ogr. And I can't
>>                 remember exactly but I think MapInfo's EasyLoader
>>                 could do that very fine aswell.
>>
>>                 All the best,
>>                 Tõnis
>>
>>                 On 27.08.19 15:44, Paolo Cavallini wrote:
>>
>>                     Not that I know of, but you can use ogr or QGIS
>>                     for this.
>>                     Cheers.
>>
>>                     On 27 August 2019 15:14:06 EEST, Shaozhong SHI
>>                     <shishaozhong at gmail.com
>>                     <mailto:shishaozhong at gmail.com>> wrote:
>>
>>                         Hi,
>>                         Is there a MapInfo to PostGIS/PostgreSQL
>>                     loader?  For instance, use
>>                         psql.exe or something like that?
>>
>>                         Regards,
>>
>>                         Shao
>>
>>
>>                     -- 
>>                     Sorry for being short
>>
>>                     _______________________________________________
>>                     postgis-users mailing list
>>                     postgis-users at lists.osgeo.org
>>                     <mailto:postgis-users at lists.osgeo.org>
>>                     https://lists.osgeo.org/mailman/listinfo/postgis-users
>>                     <https://lists.osgeo.org/mailman/listinfo/postgis-users>
>>
>>                 _______________________________________________
>>                 postgis-users mailing list
>>                 postgis-users at lists.osgeo.org
>>                 <mailto:postgis-users at lists.osgeo.org>
>>                 https://lists.osgeo.org/mailman/listinfo/postgis-users
>>                 <https://lists.osgeo.org/mailman/listinfo/postgis-users>
>>
>>             _______________________________________________
>>             postgis-users mailing list
>>             postgis-users at lists.osgeo.org
>>             <mailto:postgis-users at lists.osgeo.org>
>>             https://lists.osgeo.org/mailman/listinfo/postgis-users
>>             <https://lists.osgeo.org/mailman/listinfo/postgis-users>
>>
>>
>>     _______________________________________________
>>     postgis-users mailing list
>>     postgis-users at lists.osgeo.org  <mailto:postgis-users at lists.osgeo.org>
>>     https://lists.osgeo.org/mailman/listinfo/postgis-users  <https://lists.osgeo.org/mailman/listinfo/postgis-users>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users

-- 
Med venlig hilsen / Kind regards

Bo Victor Thomsen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20190901/f109d18d/attachment.html>


More information about the postgis-users mailing list