On 1/6/2013 7:30 AM, Alex Barth wrote:
This could be achieved e. g. by overlaying a light, opaque OSM highway layer
with a contrasting TIGER layer, only exposing TIGER 12 geometry where it
differs from OSM.
Here is a TIGER 12 vs OSM comparison. They cyan inner arc exists in
TIGER 12 but
On 1/6/2013 7:30 AM, Alex Barth wrote:
This could be achieved e. g. by overlaying a light, opaque OSM highway
layer with a contrasting TIGER layer, only exposing TIGER 12 geometry
where it differs from OSM.
Oops, forgot the link:
http://greenvilleopenmap.info/TIGER12vsOSM.jpg
Here is a
On Jan 6, 2013, at 11:28 AM, Ian Dees ian.d...@gmail.com wrote:
I've done this before and it works great for ~z10+. Some more processing
needs to be done for the lower zoom levels so that we can display an overview
to make it easier to find problematic areas.
Any particular thoughts on
On Jan 6, 2013, at 12:06 PM, Mike N nice...@att.net wrote:
On 1/6/2013 11:37 AM, Mike N wrote:
I like the idea of a TIGER 07 vs 12 comparison only being used as a
trigger. If you compare TIGER 12 vs OSM, it will highlight all the
TIGER 07 artifact roads that were removed because they were
On Mon, Jan 7, 2013 at 4:39 PM, Alex Barth a...@mapbox.com wrote:
On Jan 6, 2013, at 11:28 AM, Ian Dees ian.d...@gmail.com wrote:
I've done this before and it works great for ~z10+. Some more processing
needs to be done for the lower zoom levels so that we can display an
overview to make
On Jan 6, 2013, at 4:30 AM, Alex Barth wrote:
On Jan 4, 2013, at 3:33 PM, Richard Welty rwe...@averillpark.net wrote:
On 1/4/13 1:31 PM, Michal Migurski wrote:
Interesting—how would you characterize bad roads? One characteristic of
crappy TIGER data is road wiggliness, is that what you
Openstreetmap
Subject: Re: [Talk-us] identifying TIGER deserts
On Mon, Jan 7, 2013 at 4:39 PM, Alex Barth a...@mapbox.com wrote:
On Jan 6, 2013, at 11:28 AM, Ian Dees ian.d...@gmail.com wrote:
I've done this before and it works great for ~z10+. Some more processing
needs to be done
On Jan 4, 2013, at 3:33 PM, Richard Welty rwe...@averillpark.net wrote:
On 1/4/13 1:31 PM, Michal Migurski wrote:
Interesting—how would you characterize bad roads? One characteristic of
crappy TIGER data is road wiggliness, is that what you mean?
the tiger 2010/11/12 data is much better
On Sun, Jan 6, 2013 at 6:30 AM, Alex Barth a...@mapbox.com wrote:
On Jan 4, 2013, at 3:33 PM, Richard Welty rwe...@averillpark.net wrote:
On 1/4/13 1:31 PM, Michal Migurski wrote:
Interesting—how would you characterize bad roads? One characteristic
of crappy TIGER data is road wiggliness,
On 1/6/2013 7:30 AM, Alex Barth wrote:
This could be achieved e. g. by overlaying a light, opaque OSM highway layer
with a contrasting TIGER layer, only exposing TIGER 12 geometry where it
differs from OSM.
I like the idea of a TIGER 07 vs 12 comparison only being used as a
trigger. If
On 1/6/2013 11:37 AM, Mike N wrote:
I like the idea of a TIGER 07 vs 12 comparison only being used as a
trigger. If you compare TIGER 12 vs OSM, it will highlight all the
TIGER 07 artifact roads that were removed because they were in error or
no longer exist, but are still often in TIGER 12
On Jan 3, 2013, at 7:06 PM, Michal Migurski m...@teczno.com wrote:
On Jan 3, 2013, at 3:25 PM, Alex Barth wrote:
Mike (and anyone else interested in TIGER deserts):
Ruben, Ian and I would love to touch base over voice and see where we can
cooperate. Skype or Google Hangout would be
On Jan 4, 2013, at 1:33 AM, Alex Barth wrote:
On Jan 3, 2013, at 7:06 PM, Michal Migurski m...@teczno.com wrote:
Sounds great, I'm actually in the middle of publishing a followup to the
green-means-go map after ploughing through the full planet history dump.
Great Tue 1/8, 5PM Eastern.
On 1/4/13 1:31 PM, Michal Migurski wrote:
Interesting—how would you characterize bad roads? One characteristic
of crappy TIGER data is road wiggliness, is that what you mean?
the tiger 2010/11/12 data is much better for many of the bad tiger
areas. it'd be a bit of work to do
a comparison of
On Dec 20, 2012, at 2:19 PM, Michal Migurski m...@teczno.com wrote:
On Dec 19, 2012, at 5:39 PM, Ruben Lopez Mendoza wrote:
A few obvious steps stand out, including rendering a national version of
these maps. I'd also love to figure out whether it makes sense to join
forces with Mike
Russ Nelson nel...@crynwr.com writes:
Michal Migurski writes:
Also, what's the deal with the Massachusetts TIGER import?
Massachusetts had already made an improved version of the TIGER data,
so the decision was made to import that instead.
I'm not sure it's a version of the TIGER data,
On Dec 20, 2012, at 11:19 AM, Michal Migurski wrote:
next steps
A few obvious steps stand out, including rendering a national version of
these maps. I'd also love to figure out whether it makes sense to join
forces with Mike Migurski's Green Means Go map.
It'd also be interesting to
Michal Migurski writes:
Also, what's the deal with the Massachusetts TIGER import?
Massachusetts had already made an improved version of the TIGER data,
so the decision was made to import that instead.
--
--my blog is athttp://blog.russnelson.com
Crynwr supports open source software
521
On Dec 22, 2012, at 7:01 PM, Russ Nelson wrote:
Michal Migurski writes:
Also, what's the deal with the Massachusetts TIGER import?
Massachusetts had already made an improved version of the TIGER data,
so the decision was made to import that instead.
Ah, good to know. Any idea what the
Michal Migurski writes:
Ah, good to know. Any idea what the approximate date and importing
account were?
MassGIS Import somewhere around 10/13/07.
--
--my blog is athttp://blog.russnelson.com
Crynwr supports open source software
521 Pleasant Valley Rd. | +1 315-600-8815
Potsdam, NY
Hello all,
Ruben led out MapBox's analysis, the results of which you can see in his
previous message. While these maps do a fairly good job of identifying areas
that have and have not been edited, we're not entirely satisfied with their
ability to identify where TIGER ways just don't
On Dec 19, 2012, at 5:39 PM, Ruben Lopez Mendoza wrote:
We've worked out some kinks of our first attempt to identify TIGER deserts,
and produced maps a couple maps along the way.
…
I've captured all of this work - the postgres functions, shapefiles, and
tilemill projects in the a repo
We've worked out some kinks of our first attempt to identify TIGER deserts,
and produced maps a couple maps along the way.
Average version of all highway =* ways
https://tiles.mapbox.com/ruben/map/map-badetj1b#7.00/37.927/-78.466
Percent version 1, highwahy=* ways per gridcell
Before I log off for tonight, let me share this screenshot I just got from
Ruben (cc'ed) showing his progress on creating a slippy TIGER deserts map,
pretty much using Martijn's approach of binned average geometry versions. These
are first steps and there are still some math problems to iron
Are you guys using the way version number to determine TIGERness? This from
Andy Allan might be more effective:
--
-- TIGER edits case statement from
--
https://github.com/MapQuest/TIGER-Edited-map/blob/master/inc/layer-tiger.xml.inc
--
(case when osm_uid = '7168' --
Some context for the query below:
https://gist.github.com/4291608
I've been using this projection for everything, a spherical Albers to make it
possible to generate a slippy map in a conic projection:
+proj=aea +lat_1=29.5 +lat_2=45.5 +lat_0=23 +lon_0=-96 +x_0=0 +y_0=0
Hey team,
Over here at MapBox we were inspired by Martjin's great post on identifying
TIGER deserts[1], so we're attempting to effectively identify TIGER deserts for
the rest of the continental U.S. (sorry Hawaii + Alaska, you're next). The goal
is to create a slippy map from zoom level 2
That's great!
I've been thinking about some of the same things, inspired by Dennis Zielstra's
talk at SOTM-US. I'm looking at road lengths for 1x1 kilometer squares,
measuring OSM user count (post-import) vs. possibility for improvement between
2007 and 2012 TIGER/Line data:
GeoTIFF version of that data:
http://mike.teczno.com/img/osm-users-imports-2012-09.tif
On Dec 7, 2012, at 10:32 AM, Michal Migurski wrote:
That's great!
I've been thinking about some of the same things, inspired by Dennis
Zielstra's talk at SOTM-US. I'm looking at road lengths for
This would also fit in really well with the data steward notion. Part
of the idea that we've been toying with for this is to have data
dashboards for the stewarded areas to support targeted fixing /
improving and to build a stronger local discussion and community
around data information
I was just working on some user stories for the data steward idea,
feel free to comment / add. I hope this will fit into the discussion
around TIGER deserts and updates.
https://docs.google.com/presentation/d/1mgKHtP9drx_rCXy_y3PPx_ZIBRLs1ASViorzpeOUZ0o/edit
On Fri, Dec 7, 2012 at 11:38 AM,
Absolutely, yeah.
I chose a raster approach to the data I was working with because I imagined it
would be easiest to adapt to arbitrary jurisdictions, whether adopt-a-pixel or
masked by a county boundary. Easy to track buckets of data over time that way,
too.
-mike.
On Dec 7, 2012, at 10:38
On Fri, Dec 7, 2012 at 1:25 PM, Paul Norman penor...@mac.com wrote:
How do you identify this? I know that some of the biggest improvements I've
made to TIGER data in remote areas was to delete half of the data. If the
TIGER2012 data hasn't changed a naive comparison will say that the 2012
Thanks!
I agree about a regularly-updated map. For this one, I used the up-to-date
osm2pgsql database that Ian Dees is maintaining on the OSM-US server we have
living in Oregon, an awesome resource for USian OSM things. =)
I re-projected everything to spherical albers, and then iterated over
Something else that would be cool for the US OSM server is a tilecache
proxy of publicly available, kosher data sources
On Fri, Dec 7, 2012 at 5:07 PM, Michal Migurski m...@teczno.com wrote:
Thanks!
I agree about a regularly-updated map. For this one, I used the up-to-date
osm2pgsql
35 matches
Mail list logo
