At 2012-06-11 16:17, Mark Gray wrote:
it is also much better for being sure you are oriented when
you are out there and can see the buildings on the map line up
with real buildings. Address and POI information looks much better
with the context of the buildings they are associated with.
I can't
Hi,
On 06/12/12 01:17, Mark Gray wrote:
I think that one of the strengths of OSM is that people can map
what they are interested in
I wholeheartedly agree, and I would never get in the way of someone
mapping all building footprints in a city - if it is worth that much
effort to him then this
> On Mon, Jun 11, 2012 at 4:47 PM, Nathan Edgars II
> wrote:
>> I agree with this. But I'm not sure that there is a solution. You can use
>> XAPI/Overpass API to download only roads in an area, but you get conflicts
>> (or worse, you move a node and screw up something else without realizing it)
>>
>From a slightly different perspective, there are, in fact, many solutions,
each of which may be suboptimal in some respects. In any case, the
scalability issues arising as a result of data growth will need to be dealt
with.
Some benefits may be had looking for optimizations to apply to data
down
On 6/11/2012 7:17 PM, Mark Gray wrote:
On one hand, I share the frustration of having lots of new data in
an area making some of our tools slower and more difficult to use.
In my area a building footprint import slowed down most of the
mapping tools and land use polygons can get in the way of edi
On one hand, I share the frustration of having lots of new data in
an area making some of our tools slower and more difficult to use.
In my area a building footprint import slowed down most of the
mapping tools and land use polygons can get in the way of editing
roads.
On the other hand, I really
6 matches
Mail list logo
