So I'm finding that I can render a 1/2 hour video (~ 1.2GB mpeg source) to WMV9 at high bitrate (1500-2000 Kpbs) in about 1/2 hour elapsed time, for a 300-500MB upload, or... at low bitrate (target=500Kbps) in about 1.5 hours elapsed time, for about a 75-150 MB upload. Question is: which mode will get all of the SOTM.US videos uploaded quicker? :)

I think I'm going to take the option that saves my upload quota, so that I can start helping with the Girona videos as soon as I finish the US videos.

Tenth and final session video from SOTM.US Day 1 has been converted and uploaded:

http://vimeo.com/channels/128913

Got up at 3:00 AM (in California) because I wasn't done packing. Then the cab driver that took my call decided to pull the chute and never showed up, and the replacement guy kept getting lost. So I missed my flight, spent three hours at OAK wishing there was someplace to sleep :)

But then it all turned good: on my rescheduled hops I had first, the exit seat on an A319 with no seat in front of me so I could stretch my legs out completely, and then the second hop I had a whole row to myself. And at nightfall I was able to shoot some great video out the plane window of lightning in the clouds.

Yes, it's hot here :)

ATL/SotM.us, here I come.

I should have spent these six hours packing to move, but I'm pleased: got PostGIS running, managed to import some shapefiles, and also some OSM data, all for use in a GIS client I use to prep data for OSM.

VGI [Volunteered Geographic Information] is sometimes termed *asserted* geographic information, in that its content is asserted by its creator without citation, reference, or other authority.

-- Michael Goodchild, http://www.ncgia.ucsb.edu/projects/vgi/docs/position/Goodchild_VGI2007.pdf

http://forum.manifold.net/forum/t91596.9

OK, it's a very small sample set but I think he does have some valid concerns.

I recently moved to a new place on the edge of town against the hills, and there are ten users within 4km of me and all but a couple have signed up in the past three or four months. I wonder why this cluster?

While playing with my GIS software, I discovered that the USGS had released 1/9-arcsecond NED data for my county. This data is generated from LIDAR scans and has a resolution of about 1/3 meter in x/y/z.

After much trimming and fiddling to reduce the data size, I created 0.25m contour lines and picked those that looked "best" for the water body outlines. I then used the same GIS software to simplify the lines, reducing some of them from over 1000 points to less than 200 but still maintaining nice curves. I the used Ian Dees' shp2osm package (java, not the perl stuff in svn) to convert to .osm, and used josm to create relations for the islands and some other cleanup.

It was quite a bit of work; now that I have a better handle on the process I'll have to try it in other areas to see if it's useful for "production" mapping. But it was a worthwhile exercise. (I should try to come up with some before/after images to upload).

*phew* I just traced over 200 miles of the Hetch Hetchy Aqueduct/pipeline, using USGS DRG, Urban Area, and Yahoo satellite; all the way from the head in Tuolmne to the terminus at Crystal Springs Reservoir, including pipelines 3 and 4 around the south of the Bay.

I'm not sure if this was easier than finding all the right NHD data, pulling it together, and converting to .shp and then to .osm.

Just like potato chips (crisps): once I get started fixing TIGER data, it's hard to know when to stop :)

Been tracing out the details of Fremont (California) Central Park, in JOSM, from Terraserver USGS Urban Area orthophotography. I'll still have to go over there and validate some of the features, but this saves a huge amount of time.

Am I overdoing it by showing all ten soccer fields (football pitches)?

I hadn't touched OSM for several months, and am quite pleased at the new rendering schedule. I'll still use orp.pl from time to time to check how my JOSM work might look, but it's no longer critical. And JOSM keep getting better and better. I'm impressed.

I picked up a Garmin eTrex Vista Hcx last week, as my Zumo 550 just wasn't going to cut the mustard in areas without USGS Urban Area coverage; the tracklog sample rate is too rough. On the Vista I set the tracklog interval to 1 second; a 19-mile bicycle ride gave me a track with over 9,000 points, over 1GB in size :)

It turns out that another tool I own (ExpertGPS) does a good job of simplifying and manipulating GPX tracks, so I reduced that to 122KB and about 1,000 points. At that level I didn't feel so bad about converting it to an OSM layer (in JOSM) and uploading it. (I did clean it up a bit). Although it most cases so far I've been tracing my routes in JOSM on the USGS Urban Area map, I think this might be my new M.O.

Subject of today's mapping: Alameda Creek Trail, beginning at Coyote Hills and including at the other end a trip through Quarry Lakes Regional Rec Area in Fremont.

Using Yahoo imagery and Potlatch to map some motorsports racetracks that I frequent. The first is Thunderhill Raceway Park:

http://www.openstreetmap.org/?lat=39.54439&lon=-122.32224&zoom=15&layers=B000FTF

The other for today is Reno Fernley Raceway:

http://www.openstreetmap.org/?lat=39.54068&lon=-119.24182&zoom=16&layers=B000FTF

(These links will show little or nothing until the renderers catch up.)

Yesterday, obtained GPS trace via bicycle of part of the trails in Coyote Hills Regional Park. Converted that to data layer in JOSM and cleaned up. Adding more that I didn't cover, via USGS Urban orthophoto. Getting the trails on top of the levees is requiring a good deal of manual cleanup of the ponds and marshes so that I don't have people riding through water :)

Cleaning up BART, UPRR, Amtrak rails in Hayward and Union City.

Working on Harder Road, from 880 up to CSUEB/Hayward (my neighborhood)