Re: [OSM-talk] [OSM-dev] Land Information New Zealand (LINZ) - Openstreetmap import first pass
That's super great! Excited to hear that. On Tue, Jun 30, 2009 at 7:34 AM, Joe Richardsjoefis...@yahoo.com wrote: I've been working on the LINZ data import, on attribution/legal as well as the actual import. The LINZ data I have is actually via the NZ Open GPS project and is in Polish Map (.mp) format, which seems to use Garmin types for its features. I've hacked around with a few other scripts and have created a python script which creates .osm files, and then imported them into a local postGIS instance I run at home. From there I've generated tiles using Mapnik and uploaded them to a dev server for your perusal Upload is still in progress but most are there already (starting in the north and working south). It's just south of Christchurch already and I have gone and rendered Dunedin, Queenstown and Glenorchy ahead of time. If you find zoom 16 is not visible then zoom out a bit until you find the available tiles. As mentioned all of the north island is done. http://linz.dev.openstreetmap.org/~JoeRichards/ Notes: * import was done on a basic world map (from vmap0) to provide coastlines where they were missing * some large rivers have a lot of detail, but some seem to be missing altogether (e.g. Lower Hutt river) - this was also missing in the NZOGPS dataset, not sure why * tiles are still being generated and uploaded now (Tue 30th June), but all of the north island to 16 zoom levels is done as well as the Tasman... South of Christchurch is still being uploaded (although some tiles are there at lower zoom levels) * I think most of the road types (primary, secondary, trunk) etc might be completely off, including the link roads. Please send me any specific instances or comments on this * No attempt made to support anything like turn restrictions or relations since this was missing from the original dataset * Roundabouts seem to have an issue as well, where their parts are missing * large lakes such as Lake Wakatipu near Queenstown were split across two datasets, and as such as not showing up * central cities seem to have more detail in the existing OSM data (except perhaps some missing street names) but rural areas have less... This is ok, but your thoughts are welcome on how to merge these * parcel boundaries (cadastral) information, showing property boundaries, shapes, and house numbers will be imported separately, ie are to-do * Department of Conservation parks, national parks, reserves etc are also to-do, although some are present in the current dataset. * No data is merged with current OSM data, so this is really to spot problems before we attempt merging. It has been suggested we might use the java-based RoadMatcher for this. Your comments are welcome. * Thanks to Geofabrik.de for allowing me to use their compare javascript I will also put up the .osm files generated by the script so you can check out whether the data is there, but just incorrectly tagged. Please feedback to me anything you see, especially if it is incorrect. Since the plan is to merge this with the existing Openstreetmap data, missing features that are in OSM are less of an issue than features that should be in the imported dataset but are not (and hence are missing on both). Source (GPL) is here http://trac.openstreetmap.org/browser/applications/utils/import/linz2osm/mp2osm_linz_jr.py Anything in the code marked as TODO or FIXME requires special attention and verification. Enjoy and feel free to comment! ___ dev mailing list d...@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev -- anselm 415 215 4856 http://hook.org ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] OSMHQ (Open Street Map High Quality): Viable Alternative For The National Map Corps
osm has a viral license? On Wed, Sep 3, 2008 at 11:39 AM, Sunburned Surveyor [EMAIL PROTECTED] wrote: Of course, some surveyors may prefer that their work be under a Copyleft license. That's fine, and I certainly wouldn't want to discourage anyone from contributing directly to OSM in that case. But if given a choice some would choose PD, please consider providing them a workspace where such a choice isn't compromised. I'm not that familiar with the licensing issues related to OSM, but I hope to become more familiar with them. As a result, I am hesitant to comment on this. It sounds similar to the GPL versus LGPL debate that goes on in the open source world. I'll subscribe to the OSM license mailing list and post some more quesitons of mine there. Landon On Wed, Sep 3, 2008 at 10:12 AM, Nathan Vander Wilt [EMAIL PROTECTED] wrote: On Sep 2, 2008, at 7:47 AM, Sunburned Surveyor wrote: Nate, What data are you talking about? Do you mean the actual vector geometry created as part of the mapping, or do you mean the extra stuff, like the metadata and the photos? Not sure exactly what you're asking, but I see I was a bit unclear myself below. In my first paragraph, I was referring to all the data that is produced via federal money (e.g. USGS, NASA, Census Bureau, CIA, NOAA...) and is thus in the public domain. There's a lot of great US and world datasets from these agencies that have enabled, or at least got started, a lot of neat stuff because of the generous (non-)license Federal (and some state???) works are under. In my second paragraph, I was referring to the data that you hope to encourage Corps members to continue to collect. If they are willing to continue having their work placed in the public domain, it might be best to keep it totally separate from OSM. If surveyors start with public domain base maps such as TIGER, revised with their own GPS traces, there can be no questions as to whether they are a derived work of a virally licensed dataset like OSM. (See http://lists.openstreetmap.org/pipermail/talk/2008-May/025912.html for an example of the FUD spread on the idea of extracting PD data back out of OSM.) Of course, some surveyors may prefer that their work be under a Copyleft license. That's fine, and I certainly wouldn't want to discourage anyone from contributing directly to OSM in that case. But if given a choice some would choose PD, please consider providing them a workspace where such a choice isn't compromised. Have you been able to get into contact with any now-restless surveyors? lf so, and you'd like assistance in the matter, I know there are at least a few others on this list of similar mind with regards to the licensing problems. thanks, -natevw On Wed, Aug 20, 2008 at 10:40 AM, Nathan Vander Wilt [EMAIL PROTECTED] wrote: On Aug 19, 2008, at 12:22 PM, Sunburned Surveyor wrote: Note: This message will probably be of the most interset to OSM mappers in the United States. I was very disappointed in the recent shut down of the National Map Corps. This shutdown prompted me to consider if OSM could be a viable alternative to the former federally sponsored base mapping of the United States. I started to put down some of my thoughts on paper. I realized that it wouldn't take a great deal of changes to have OSM fill this much needed role. I started to put together some suggested procedures and other ideas that would increase the quality of OSM data and allow it to provide base map layers for a traditional GIS. I'll be trying out some of these ideas and procedures on a OSM mapping project near my home in Stockton, California. Here in the US, we have the wonderful benefit of a great deal of public domain map data, because of
Re: [OSM-talk] Australia has Google Street View!
And using contacts or glasses is a derived work too... the vendor could have twisted the photons to inject 'lye' street into your vision. a On Tue, Aug 5, 2008 at 9:26 AM, Matthias Julius [EMAIL PROTECTED]wrote: Stephen Gower [EMAIL PROTECTED] writes: On Tue, Aug 05, 2008 at 10:36:14AM +0200, Erik Johansson wrote: On Tue, Aug 5, 2008 at 9:40 AM, Stefan Holst [EMAIL PROTECTED] wrote: On Tue, 2008-08-05 at 11:58 +1000, Joseph Gentle wrote: Good for filling in all the missing street names. Interesting question. Are we allowed to use street view images [...] [...] And since they are facts and not *indexed* in a database so it should be ok. That argument surely applies to aerial images also, and yet consensus is that getting facts from them would create a derived work incompatible with our licence. Well, if reading a road sign from a picture is creating a derived work of that picture than looking up a word in a dictionary also creates a derived work of that dictionary. Matthias ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- anselm 415 215 4856 http://hook.org http://makerlab.com http://meedan.net ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] New kind of 3D maps.
I figured this was the next step in general ... time to get openvoxelspace.org or something On Thu, May 29, 2008 at 4:01 PM, Erik Johansson [EMAIL PROTECTED] wrote: 3D maps of Stockholm was just released on the web, and my head just exploded. You need Java 1.5 http://hitta.se/3d/3d_splash.aspx check Jag godkänner villkoren If you can't see it, think of it as a highres Voxel landscape, with an even higher resolution texture on it. They do this by using aerial imagery, not laser. -- /emj ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk -- anselm 415 215 4856 http://hook.org http://makerlab.com ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] POIs from wikipedia
Maybe somebody should start the pragmatic street maps project - a On Jan 7, 2008 2:41 PM, Richard Fairhurst [EMAIL PROTECTED] wrote: Robin Paulson wrote: while i was looking up some info on wikipedia [1], i noticed that a lot of pages have a lat/lon value to describe their location; this strikes me as something we could use to increase the amount of data in OSM These are almost certainly derived from Google Maps et al, therefore unsuitable for OSM. cheers Richard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
