[postgis-users] How to design a database for continents, countries, regions, cities and POIs?

Francois Hugues hugues.francois at irstea.fr
Mon Apr 9 05:22:07 PDT 2012

I think it could be better to have a table for each kind of object because they will have different attributes (for an example, in a matter of scale, a POI belong to a city, a city belong to a province which is part of a sub_region which is included into a state and the continent is composed of several states).


-----Message d'origine-----
De : postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-bounces at postgis.refractions.net] De la part de mkubenka
Envoyé : lundi 9 avril 2012 13:31
À : postgis-users at postgis.refractions.net
Objet : [postgis-users] How to design a database for continents, countries, regions, cities and POIs?

I'm brand new to GIS programming and I am designing a GIS application. Target
is to create system with continents, countries, regions (including states,
sub-regions, provinces), cities and places in cities. Each of this elements
will contain some text information and related stuff. As database we are
going to use PostgreSQL with PostGIS.

My question is how to design database for this system? I was thinking of 2
tables polygons and points, but I'm not sure if it's good way of thinking.

View this message in context: http://postgis.17.n6.nabble.com/How-to-design-a-database-for-continents-countries-regions-cities-and-POIs-tp4715669p4715669.html
Sent from the PostGIS - User mailing list archive at Nabble.com.
postgis-users mailing list
postgis-users at postgis.refractions.net

More information about the postgis-users mailing list