Re: [Talk-us] More on TIGER: Where it's likely safe to import
Okay, so I didn't do the density thing yet, but I've made some other additions to the TIGER green map that I think are worth mentioning. I squashed the greens and inverted the blacks so that the map is more legible, potentially easier to print, and less confusing in the difference between the no-editors and yes-editors areas. The URLs are all still the same and the map is here: http://www.openstreetmap.us/~migurski/green-means-go/ If you see any black tiles, clear your cache. The old version is now here: http://www.openstreetmap.us/~migurski/green-means-go-2013-01-03/ I'm starting to add SEO-friendly, single-geography views. I'm just getting started, using counties at first. Every county in the lower 48 will be accessible via a URL like one of these: http://www.openstreetmap.us/~migurski/green-means-go/Iowa/O'Brien-County.html http://www.openstreetmap.us/~migurski/green-means-go/California/Alameda-County.html http://www.openstreetmap.us/~migurski/green-means-go/Illinois/Cook-County.html http://www.openstreetmap.us/~migurski/green-means-go/California/San-Bernardino-County.html http://www.openstreetmap.us/~migurski/green-means-go/California/Riverside-County.html http://www.openstreetmap.us/~migurski/green-means-go/Arizona/Coconino-County.html http://www.openstreetmap.us/~migurski/green-means-go/Louisiana/East-Baton-Rouge-Parish.html http://www.openstreetmap.us/~migurski/green-means-go/New-York/New-York-County.html http://www.openstreetmap.us/~migurski/green-means-go/Virginia/Falls-Church-city.html The county views are open to suggestions, and quite low on detail for the moment. What should go on there? -mike. On Jan 6, 2013, at 5:51 PM, Michal Migurski wrote: Thanks Steve! I think that would be possible, yeah. I already use object density as one of the inputs here, and could use it to tweak the greens somewhat. The colors need a second pass. -mike. On Jan 4, 2013, at 3:00 PM, Steve Coast wrote: Mike Nice. Could you use relative object density per little square as a proxy for population density? I ask because all the bright green areas near me are forests or old milk farms. I don’t care. I want to see high density areas and attack those as a priority since that’s where people are and where they go... Steve From: Michal Migurski m...@teczno.com Sent: January 3, 2013 7:03 PM To: OpenStreetMap US Talk talk-us@openstreetmap.org Subject: Re: [Talk-us] More on TIGER: Where it's likely safe to import On Dec 17, 2012, at 12:40 PM, Michal Migurski wrote: On Dec 16, 2012, at 8:32 PM, Martijn van Exel wrote: Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ I have downloaded a copy and given it a beginning look. I'm new to parsing things of that magnitude; my first thought was to use the full history file for creations/modifications/deletions on nodes and add that to what I'm doing already for ways on the osm2pgsql tables. Does that sound reasonable? Over the holiday break, I've been grinding through the full history file. I'll write more about the process and publish some raw data, but the short version is that I've replaced the Green Means Go tiles with new versions that incorporate edits to the underlying nodes, address some of the feedback I've received, and show a slightly different map of the US. New map: http://www.openstreetmap.us/~migurski/green-means-go/ Old map: http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/ Charlotte Wolter and NE2 both pointed out that Florida should see a lot more post-import editing that I had originally shown, and in fact that's what the map now shows: http://www.openstreetmap.us/~migurski/green-means-go/#9/28.3213/-81.6257 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#9/28.3213/-81.6257 Urban fringe areas also show more edits, making them less attractive targets for blind imports: http://www.openstreetmap.us/~migurski/green-means-go/#10/37.7707/-122.3451 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#10/37.7707/-122.3451 I've also stripped away the US coastal territory based on NLCD water designation, per SteveC's suggestion. These massive edits to counties in Pennsylvania are interesting to me: http://www.openstreetmap.us/~migurski/green-means-go/#8/40.918/-77.146 -mike. michal migurski- contact info and pgp key: sf/cahttp
Re: [Talk-us] More on TIGER: Where it's likely safe to import
Thanks Steve! I think that would be possible, yeah. I already use object density as one of the inputs here, and could use it to tweak the greens somewhat. The colors need a second pass. -mike. On Jan 4, 2013, at 3:00 PM, Steve Coast wrote: Mike Nice. Could you use relative object density per little square as a proxy for population density? I ask because all the bright green areas near me are forests or old milk farms. I don’t care. I want to see high density areas and attack those as a priority since that’s where people are and where they go... Steve From: Michal Migurski m...@teczno.com Sent: January 3, 2013 7:03 PM To: OpenStreetMap US Talk talk-us@openstreetmap.org Subject: Re: [Talk-us] More on TIGER: Where it's likely safe to import On Dec 17, 2012, at 12:40 PM, Michal Migurski wrote: On Dec 16, 2012, at 8:32 PM, Martijn van Exel wrote: Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ I have downloaded a copy and given it a beginning look. I'm new to parsing things of that magnitude; my first thought was to use the full history file for creations/modifications/deletions on nodes and add that to what I'm doing already for ways on the osm2pgsql tables. Does that sound reasonable? Over the holiday break, I've been grinding through the full history file. I'll write more about the process and publish some raw data, but the short version is that I've replaced the Green Means Go tiles with new versions that incorporate edits to the underlying nodes, address some of the feedback I've received, and show a slightly different map of the US. New map: http://www.openstreetmap.us/~migurski/green-means-go/ Old map: http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/ Charlotte Wolter and NE2 both pointed out that Florida should see a lot more post-import editing that I had originally shown, and in fact that's what the map now shows: http://www.openstreetmap.us/~migurski/green-means-go/#9/28.3213/-81.6257 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#9/28.3213/-81.6257 Urban fringe areas also show more edits, making them less attractive targets for blind imports: http://www.openstreetmap.us/~migurski/green-means-go/#10/37.7707/-122.3451 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#10/37.7707/-122.3451 I've also stripped away the US coastal territory based on NLCD water designation, per SteveC's suggestion. These massive edits to counties in Pennsylvania are interesting to me: http://www.openstreetmap.us/~migurski/green-means-go/#8/40.918/-77.146 -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
Mike Nice. Could you use relative object density per little square as a proxy for population density? I ask because all the bright green areas near me are forests or old milk farms. I don’t care. I want to see high density areas and attack those as a priority since that’s where people are and where they go... Steve *From:* Michal Migurski m...@teczno.com *Sent:* January 3, 2013 7:03 PM *To:* OpenStreetMap US Talk talk-us@openstreetmap.org *Subject:* Re: [Talk-us] More on TIGER: Where it's likely safe to import On Dec 17, 2012, at 12:40 PM, Michal Migurski wrote: On Dec 16, 2012, at 8:32 PM, Martijn van Exel wrote: Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ I have downloaded a copy and given it a beginning look. I'm new to parsing things of that magnitude; my first thought was to use the full history file for creations/modifications/deletions on nodes and add that to what I'm doing already for ways on the osm2pgsql tables. Does that sound reasonable? Over the holiday break, I've been grinding through the full history file. I'll write more about the process and publish some raw data, but the short version is that I've replaced the Green Means Go tiles with new versions that incorporate edits to the underlying nodes, address some of the feedback I've received, and show a slightly different map of the US. New map: http://www.openstreetmap.us/~migurski/green-means-go/ Old map: http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/ Charlotte Wolter and NE2 both pointed out that Florida should see a lot more post-import editing that I had originally shown, and in fact that's what the map now shows: http://www.openstreetmap.us/~migurski/green-means-go/#9/28.3213/-81.6257 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#9/28.3213/-81.6257 Urban fringe areas also show more edits, making them less attractive targets for blind imports: http://www.openstreetmap.us/~migurski/green-means-go/#10/37.7707/-122.3451 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#10/37.7707/-122.3451 I've also stripped away the US coastal territory based on NLCD water designation, per SteveC's suggestion. These massive edits to counties in Pennsylvania are interesting to me: http://www.openstreetmap.us/~migurski/green-means-go/#8/40.918/-77.146 -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
On Dec 17, 2012, at 12:40 PM, Michal Migurski wrote: On Dec 16, 2012, at 8:32 PM, Martijn van Exel wrote: Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ I have downloaded a copy and given it a beginning look. I'm new to parsing things of that magnitude; my first thought was to use the full history file for creations/modifications/deletions on nodes and add that to what I'm doing already for ways on the osm2pgsql tables. Does that sound reasonable? Over the holiday break, I've been grinding through the full history file. I'll write more about the process and publish some raw data, but the short version is that I've replaced the Green Means Go tiles with new versions that incorporate edits to the underlying nodes, address some of the feedback I've received, and show a slightly different map of the US. New map: http://www.openstreetmap.us/~migurski/green-means-go/ Old map: http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/ Charlotte Wolter and NE2 both pointed out that Florida should see a lot more post-import editing that I had originally shown, and in fact that's what the map now shows: http://www.openstreetmap.us/~migurski/green-means-go/#9/28.3213/-81.6257 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#9/28.3213/-81.6257 Urban fringe areas also show more edits, making them less attractive targets for blind imports: http://www.openstreetmap.us/~migurski/green-means-go/#10/37.7707/-122.3451 http://www.openstreetmap.us/~migurski/green-means-go-2012-12-16/#10/37.7707/-122.3451 I've also stripped away the US coastal territory based on NLCD water designation, per SteveC's suggestion. These massive edits to counties in Pennsylvania are interesting to me: http://www.openstreetmap.us/~migurski/green-means-go/#8/40.918/-77.146 -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
Hi, On 12/17/12 04:02, Michal Migurski wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ I take offense at your wording (on the page): Where in the United States could government imports improve OpenStreetMap? - you might add data to OSM but will you improve OSM? It's not the same, and equating the two is a mistake that insiders should not make. The wording Green squares show places where data imports are unlikely to interfere with community mapping. is also misleading; it has been shown that imports can very well interfere with *future* community mapping of which you would, naturally, not find traces in the data you analysed. The correct wording is: Green squares show places where little or no community mapping has taken place in the past. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
Nice. Suggestions; - kill water somehow - Information density at low zoom levels implies that basically everywhere is green. But you zoom to the bay area and see this isn't the case. So, change the coloring? Modulate it by population density? Steve On Dec 16, 2012, at 8:32 PM, Martijn van Exel m...@rtijn.org wrote: OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
While I like the idea of being able to identify and possibly do imports for one-kilometer-square (why not miles?) chunks of the map, I think it needs to be accompanied with lots of cautionary language about assessing the area thoroughly before taking any such action. We could give people examples of what to look for to see if the area really is a TIGER desert, and what to check before making a move. May be it would be better if a group of squares are identified using criteria set up by the Data group or someone similarly experienced. Then, the square kilometers could be presented in a Maproulette kind of format, but with a chance to choose which one you take on. That way, you could choose square kilometers that are near where you are working anyway or near areas with which you are familiar. Best, Charlotte At 12:22 PM 12/17/2012, you wrote: Nice. Suggestions; - kill water somehow - Information density at low zoom levels implies that basically everywhere is green. But you zoom to the bay area and see this isn't the case. So, change the coloring? Modulate it by population density? Steve On Dec 16, 2012, at 8:32 PM, Martijn van Exel m...@rtijn.org wrote: OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady The Four Internet Freedoms Freedom to visit any site on the Internet Freedom to access any content or service that is not illegal Freedom to attach any device that does not interfere with the network Freedom to know all the terms of a service, particularly any that would affect the first three freedoms. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
On Dec 16, 2012, at 8:32 PM, Martijn van Exel wrote: OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. You're right, I've emphasized that up near the top, thanks. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ I have downloaded a copy and given it a beginning look. I'm new to parsing things of that magnitude; my first thought was to use the full history file for creations/modifications/deletions on nodes and add that to what I'm doing already for ways on the osm2pgsql tables. Does that sound reasonable? I'll check out your parser; what kinds of metrics does it produce? -mike. On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
On Dec 17, 2012, at 1:58 AM, Frederik Ramm wrote: Hi, On 12/17/12 04:02, Michal Migurski wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ I take offense at your wording (on the page): Where in the United States could government imports improve OpenStreetMap? - you might add data to OSM but will you improve OSM? It's not the same, and equating the two is a mistake that insiders should not make. The wording Green squares show places where data imports are unlikely to interfere with community mapping. is also misleading; it has been shown that imports can very well interfere with *future* community mapping of which you would, naturally, not find traces in the data you analysed. The correct wording is: Green squares show places where little or no community mapping has taken place in the past. How about something like this? Green squares show places where data imports are unlikely to conflict with past community mapping. I think in the case of the US, the previous government data is so bad relative to what's currently out there that a fresh import will necessarily improve OSM, if I can make the green areas more reflective of the true state of edited places. Full history is a means to this; I've got some off-list responses from people who don't think that their own mapping efforts are accurately reflected in the green squares. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
Information density: maybe a different grid for lower zoom levels, e.g. 5km, 10km, etc.? It would have the opposite effect of what's there now I think, which is look at all that green! -mike. On Dec 17, 2012, at 12:22 PM, Steve Coast wrote: Nice. Suggestions; - kill water somehow - Information density at low zoom levels implies that basically everywhere is green. But you zoom to the bay area and see this isn't the case. So, change the coloring? Modulate it by population density? Steve On Dec 16, 2012, at 8:32 PM, Martijn van Exel m...@rtijn.org wrote: OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
Agreed. What I *really* want is a version of this map that's tailored to meaningful jurisdictions, Census places and counties. It's one thing to see an all-over view but if you're a city GIS guy and you have a file of data that you want to input, it'd be useful for you to see just your specific area with some guidance on how to proceed: 1. How much is green vs. not green, and the likelihood of improvement. 2. OSM users who are responsible for existing work in your area. 3. Non-highway data in the area, e.g. POIs and such. Christine White from Esri, who attended SOTM-US in Portland, told me that at the annual user conference she gets a regular stream of these people approaching her with blobs of official data, a desire to donate it to OSM, and no knowledge about how to proceed or what effect it would have. We should help her and them! -mike. On Dec 17, 2012, at 12:39 PM, Charlotte Wolter wrote: While I like the idea of being able to identify and possibly do imports for one-kilometer-square (why not miles?) chunks of the map, I think it needs to be accompanied with lots of cautionary language about assessing the area thoroughly before taking any such action. We could give people examples of what to look for to see if the area really is a TIGER desert, and what to check before making a move. May be it would be better if a group of squares are identified using criteria set up by the Data group or someone similarly experienced. Then, the square kilometers could be presented in a Maproulette kind of format, but with a chance to choose which one you take on. That way, you could choose square kilometers that are near where you are working anyway or near areas with which you are familiar. Best, Charlotte At 12:22 PM 12/17/2012, you wrote: Nice. Suggestions; - kill water somehow - Information density at low zoom levels implies that basically everywhere is green. But you zoom to the bay area and see this isn't the case. So, change the coloring? Modulate it by population density? Steve On Dec 16, 2012, at 8:32 PM, Martijn van Exel m...@rtijn.org wrote: OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady The Four Internet Freedoms Freedom to visit any site on the Internet Freedom to access any content or service that is not illegal Freedom to attach any device that does not interfere with the network Freedom to know all the terms of a service, particularly any that would affect the first three freedoms. ___ Talk-us mailing list Talk-us@openstreetmap.org
Re: [Talk-us] More on TIGER: Where it's likely safe to import
On Dec 17, 2012, at 12:45 PM, Michal Migurski m...@teczno.com wrote: Information density: maybe a different grid for lower zoom levels, e.g. 5km, 10km, etc.? It would have the opposite effect of what's there now I think, which is look at all that green! I prefer modulating by population, since a sea of green in Wyoming (with apologies to those in Wyoming) really doesn't matter since nobody lives there. The question is, where is the population / edits ration low, not the absolute edits numbers. Maybe ask people from CloudMade what they did 3 years ago. Also, I wouldn't ask the question(s) in a vacuum. I suspect, but cannot confirm, that if you did a similar analysis of NT or TA data in the US you'd see exactly the same thing; a natural economic bias in the metrics to mapping places with high population density. Steve -mike. On Dec 17, 2012, at 12:22 PM, Steve Coast wrote: Nice. Suggestions; - kill water somehow - Information density at low zoom levels implies that basically everywhere is green. But you zoom to the bay area and see this isn't the case. So, change the coloring? Modulate it by population density? Steve On Dec 16, 2012, at 8:32 PM, Martijn van Exel m...@rtijn.org wrote: OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
On Dec 17, 2012, at 12:50 PM, Steve Coast wrote: On Dec 17, 2012, at 12:45 PM, Michal Migurski m...@teczno.com wrote: Information density: maybe a different grid for lower zoom levels, e.g. 5km, 10km, etc.? It would have the opposite effect of what's there now I think, which is look at all that green! I prefer modulating by population, since a sea of green in Wyoming (with apologies to those in Wyoming) really doesn't matter since nobody lives there. The question is, where is the population / edits ration low, not the absolute edits numbers. Maybe ask people from CloudMade what they did 3 years ago. Also, I wouldn't ask the question(s) in a vacuum. I suspect, but cannot confirm, that if you did a similar analysis of NT or TA data in the US you'd see exactly the same thing; a natural economic bias in the metrics to mapping places with high population density. I suspect the same, it makes sense given driving patterns and economic demand. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] More on TIGER: Where it's likely safe to import
I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] More on TIGER: Where it's likely safe to import
OK this is plain awesome. Great work Mike. One note of caution though - the title may suggest that you can just go ahead and import away, but folks would still have to follow the import guidelines and contact the OSM community at large, come up with a solid proposal and discuss that, even if there is no local community. I know it says it on the tin, but it's kind of tucked away at the bottom. Have you looked into full history planet parsing to get a fuller picture of editing history? I took a stab at full history user metrics some time ago using osmjs; https://github.com/mvexel/OSMQualityMetrics/blob/master/UserStats.js - this produces one set of metrics for the entire .osh file you feed it but it may prove useful for future work. I haven't touched this in a while but it should still work :/ On Sun, Dec 16, 2012 at 8:02 PM, Michal Migurski m...@teczno.com wrote: I pulled together some of the notes and imagery I've been posting here recently: http://www.openstreetmap.us/~migurski/green-means-go/ It's a map of 1km×1km squares covering the continental United States. Green squares show places where data imports are unlikely to interfere with community mapping. Raw data is linked at the bottom. Three things that would make this better: - Regular updates with archived older versions. - Renders for specific counties, intended for local GIS communities. - Some awareness of full planet history. The OSM-US server has data for regular updates. -mike. michal migurski- contact info and pgp key: sf/cahttp://mike.teczno.com/contact.html ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
