Re: [Talk-us] Import discussions
On 6/11/2012 10:54 AM, Alan Mintz wrote: Personally, I wish that all those that want to import building outlines would first think about the existing street network (this, after all, being OpenSTREETMap). So much of the US is still unedited TIGER 2005 data - mis-aligned, poorly connected, stale-named, and missing lots of new construction from the peak to the end of the housing boom. I'll agree with this. I'm not sure of the value of building outlines until someone actively uses or updates them. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] User adding hidden and non-official Interstate ref tags
I've just notice that the user SD Mapman has added in the ref tags several hidden Interstates and removed what was originally in those tags (example: ref=US 27 ref=I 124). It seems he's done this for all of the hidden Interstates.http://www.openstreetmap.org/user/SD%20Mapman/edits?page=5 He's also added I-49 ref tags in MO, even though the Interstate there isn't official yet till later this year. (should be on page 1 and page 2 of his edits atm) He also added the I-74 tags back to the Laurinburg, NC bypass of US-74. I haven't heard anything about NCDOT getting permission to put the shields back up yet on that segment (I personally was lucky enough to travel that section while the shields were still up). I've sent him a message on this subject already and gave him a link to talk-us. Hopefully, he'll come on here and talk about his edits on this subject. In the meantime, who here wants to play fix the ref tags? lol. --James ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Seeing things you don't care about in the database
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 editing roads. 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) when nodes are shared with other non-downloaded features. This can happen directly (road passing through a building or the IMO bad practice of using roads as landuse borders) or indirectly (e.g. road - parking lot - building - landuse). ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Seeing things you don't care about in the database
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 download implementation, which would allow increasing the download sizes for JOSM. I use the web based editors for very simple/very small areas as they're significantly slower than JOSM. It is certainly possible to split feature storage into separate layers, but it would make conflict checking and conflation (much) more complex, and ideally would be shared nothing across the layers. Still, at some point, a data partitioning scheme may be required as size continues to increase. If editing with JOSM, subsets of features can be turned off for display purposes to help focus on the current task, but all data still needs to be loaded locally, so not very helpful in densely featured areas. On Mon, Jun 11, 2012 at 4:47 PM, Nathan Edgars II nerou...@gmail.comwrote: 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 editing roads. 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) when nodes are shared with other non-downloaded features. This can happen directly (road passing through a building or the IMO bad practice of using roads as landuse borders) or indirectly (e.g. road - parking lot - building - landuse). __**_ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.**org/listinfo/talk-ushttp://lists.openstreetmap.org/listinfo/talk-us -- John Novak 585-OLD-TOPOS (585-653-8676) ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Seeing things you don't care about in the database
On Mon, Jun 11, 2012 at 4:47 PM, Nathan Edgars II nerou...@gmail.com 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) when nodes are shared with other non-downloaded features. This can happen directly (road passing through a building or the IMO bad practice of using roads as landuse borders) or indirectly (e.g. road - parking lot - building - landuse). One option would be for every object returned from an API query to have a complete/incomplete flag. This flag would be set if an object (e.g. a node) is part of another object that has not been downloaded because it's not on the same layer. If the editor sees such an object being modified, it pulls all the parent elements from the API. Cheers ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
