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 t

Re: [OSM-dev] iD 2.0.0 always start in whole world view

Thanks markus! we’re tracking this on https://github.com/openstreetmap/iD/issues/3588 This is a bug in the code that hands off control from the openstreetmap-website code to iD which runs in an iframe.. > On Nov 16, 2016, at 6:26 PM, markus sc

[OSM-dev] iD 2.0.0 always start in whole world view

Hoi, great that iD 2.0.0 already is available on osm.org! :-) But I encountered a problem: When I click on the ``edit with iD'' link in keepright.at, the new iD 2.0.0 on osm.org does not (as before) zoom to the given location but always starts in the minimal zoom level, showing the whole world.

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 cha

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 determ

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 o

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 boundary='administrative';