[OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database
rtosmdb at gmail.com
Wed Nov 16 13:51:27 UTC 2016
No modify on geometry. No modify on the 63 tables/sequences an
OpenStreetMap API Database holds.
Only some auxiliary tables are created along the existing tables.
all the simplified objects are created on-the-fly during the query processing.
Yes, and absolutely, simplify object by geometric characteristics is
not that fine for cartographers. but as long as there are requirements
for simplified spatial object, a hand-crafted simplified object can
also be incorporated into the extension, which means the weight of
nodes is given by human not by some computational geometry algorithms.
On Wed, Nov 16, 2016 at 6:41 PM, Christoph Hormann <chris_hormann at gmx.de> wrote:
> On Wednesday 16 November 2016, RTOSM DOOPAS wrote:
>> In short, rtosm is about to extend the OSM API to make it support
>> viewing and editing data at any scale directly from database.
> The OSM API's main purpose is two way data transfer in small chunks.
> Since you modify the geometry this rules out any editing and
> transferring data back.
> For rendering/viewing your concept hinges on the idea that dropping
> nodes is a good way to simplify geometries for rendering purposes which
> is not generally the case. Or in other words - you assume that your
> error metric accurately describes the perceptual error when viewing the
> rendered geometry (which is evidently not the case).
> Christoph Hormann
> dev mailing list
> dev at openstreetmap.org
More information about the dev