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 Thu,
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 relatio
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.
s JOSM/Potlatch need to change to
adapt the rtosm served data.
On Thu, Nov 17, 2016 at 3:49 AM, Paul Norman wrote:
>
> On 11/16/2016 5:37 AM, RTOSM DOOPAS wrote:
>>
>> The rtosm map call (not that exact, but the framework is clear):
>>
>> [...]
>> 6. send
Wed, Nov 16, 2016 at 6:41 PM, Christoph Hormann 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
> boundary='administrative';
>
> In osm2pgsql imported with --hstore-all key?
>
> ср, 16 нояб. 2016 г. в 7:30, RTOSM DOOPAS :
>>
>> Yes, osm2pgsql/imposm are very useful tool.
>>
>> While the osm2pgsql and imposm are used to import data from API
>
ing and editing data at any scale directly from database.
On Wed, Nov 16, 2016 at 6:36 AM, Darafei "Komяpa" Praliaskouski
wrote:
> Hi!
>
> Have you tried osm2pgsql and/or imposm? What is the reason to do it over API
> db schema?
>
> вт, 15 нояб. 2016 г. в 19:27,
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 va
8 matches
Mail list logo
