Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

The simplified result of many objects are topologically consistent, which means any two objects share a node in original datasets will share the same node in their simplified version. However, the topology preservation is a complicated issue for data simplification, more tests are needed. On

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

To make the whole cycle of data production in OpenStreetMap community to take advantage of the extension, I think many redesigns in server-side and client-side are needed. and I don't think a temporary ID for simplified object is a good practice because it brings extra work to maintain the

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

There are many things to do before the rtosm can actually work for the osm online data editing. 1. At server side, editing API must change to tell the client whether an object is simplified or not. 2. At client side, data editor must create new rules or re-program to use the rtosm served data.

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

Martin Koppenhoefer wrote 2016-11-17 14:39: 2016-11-17 11:08 GMT+01:00 Rory McCann : But... isn't there a danger that the mapper will load this simplified/reduced object in JOSM (etc), change the tags, then press upload? And then upload the simplified/reduced geometry?

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

2016-11-17 11:08 GMT+01:00 Rory McCann : > But... isn't there a danger that the mapper will load this > simplified/reduced object in JOSM (etc), change the tags, then press > upload? And then upload the simplified/reduced geometry? Which will make > the OSM data worse? >

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

On 17/11/16 03:23, RTOSM DOOPAS wrote: > 1. Initially, User opens JOSM/Potlatch to browse an overview map. > currently the data are shown in slippy maps which are rendered from > data to an imagery in advance at a rendering server. With rtosm, the > overview map can be a collection of simplified

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

Yes, Paul. The simplified object's geometry can't be edited but we can tell which object is simplified and which is not. in a client-side map, some objects are simplified and some are not. The un-simplified object can be edit. Let's imagine a use scenario: 1. Initially, User opens JOSM/Potlatch

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

On 11/16/2016 5:37 AM, RTOSM DOOPAS wrote: The rtosm map call (not that exact, but the framework is clear): [...] 6. send back the simplified objects to request. The purpose of the API and the apidb is for editing. How would someone edit the simplified object?

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

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

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

The simplified line is not 'saved' in the database, It is assembled from selected nodes on-the-fly. The rtosm extension will add several tables to the OSM API database and do some computation on the ways and relations to derive a weight for each node. The weight of each node will be used to

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

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

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

Yes, but after you do such a select, you can't save this simplified line back to OSM. Is it different from SELECT tags, ST_AsGeoJSON(ST_SimplifyPreserveTopology(ST_RemoveRepeatedPoints(way, 1000), 1)) from planet_osm_polygon where name='United States of America' and

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

Yes, osm2pgsql/imposm are very useful tool. While the osm2pgsql and imposm are used to import data from API Database to a PostGIS instance. With the PostGIS, user can perform tile rendering or geospatial computing. The purpose of the osm2pgsql/imposm is different. rtosm aims to make the API

Re: [OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

Hi! Have you tried osm2pgsql and/or imposm? What is the reason to do it over API db schema? вт, 15 нояб. 2016 г. в 19:27, RTOSM DOOPAS : > Hi, > > > > I have written a small extension for OSM API database to offer the > functionality of real-time simplification of objects

[OSM-dev] A PostgreSQL extension for real-time simplification of objects in OSM API database

Hi, I have written a small extension for OSM API database to offer the functionality of real-time simplification of objects (ways, relations) by node filtering during the query processing. The idea behind it is as followings: 1. For each spatial object such as way or relation, attach weight