Как там было в сказке,
про цепочку действий, которые необходимо
было выполнить для получения молока от
коровки?
And the next thing you
know, you're at the zoo, shaving a yak, all so you can wax your car.
обзор
инструментов, упрощающих загрузку
векторных картографических данных
проекта OpenStreetMap в СУБД PostgreSQL
how to get data out of OpenStreetMap
and into a database, and realized that it’s possible no one’s
really explained a full range of current options in the past few
years. Like a lot of things with OSM, information about this topic is
plentiful but rarely collected in one place, and often consists of
half-tested theories, rumors, and trace amounts of accurate fact
based on personal experience earned in a hurry while at the point of
loaded
yak.
At first glance, OSM data and
Postgres (specifically PostGIS) seem like a natural, easy fit for one
another: OSM is vector data, PostGIS stores vector data. OSM has
usernames and dates-modified, PostGIS has columns for storing those
things in tables. OSM is a worldwide dataset, PostGIS has fast
spatial indexes to get to the part you want. When you get to OSM’s
free-form
tags, though, the row/column model of Postgres stops making sense
and you start to reach for linking tables or advanced features like
hstore.
…
Use Osmosis if you’re
interested in data. Start with Osm2pgsql if you want to render maps.
Move to Imposm once you know exactly what you want.
Как справедливо замечено,
есть много информации на тему загрузки
данных из OSM в PostGIS,
но вся она неравномерно размазана
по интернетам. А тут хорошая попытка
достичь кумулятивного эффекта. Одобрямс.
Комментариев нет:
Отправить комментарий