Re: [OSM-talk] Summer of Code 2014
Le 15/02/2014 00:41, Rob Nickerson a écrit : Osmose QA tool do this job. Perhaps I am not aware of everything that Osmose can do, but my basic understanding is that it provides an in browser view of errors already in OSM. What I was trying to propose in (1) and (2) was a really slick, really simple tool that allows the user to load in two datasets (e.g. original and updated file from a government department, or a government file and an OSM extract) and it shows you the big differences in a really simple intuitive way. For (3) I am proposing a mobile friendly way of getting people out on the ground to verify data provided by a government and load it in to OSM (either there and then via mobile, or back at home on their computer). Osmose also do this. It's not quite evident, you have to map field with tags. Sometime you have to parse text field to map into many osm tags. You have to select a projection, and guess it when you don't know witch. I even see OpenData file with different projections without indicator! You have to choose a reference tag/field and/or, or if any, choose a conflation distance and tags. With Osmose you have to write a mapping configuration, the result is : - found OSM data not in reference OpenData file - found non integrated data in OSM, integration can be achevied by a JOSM remote link - suggest integration of OpenData on OSM object, addition/coorection of tag can be achieved by a JOSM link - an augmented OpenData file by OSM, with OSM data not in reference file and with OSM new tags Look at slide 14-17 of my talk at last SotM : http://fr.slideshare.net/FredericRodrigo/20130906-sotmbirminghamosmose Regards, Frédéric. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Summer of Code 2014
Le 11/02/2014 22:29, Rob Nickerson a écrit : Some ideas: 1. Tools to compare OSM data against the available external data set. One recent blog post on this by SK53 http://sk53-osm.blogspot.co.uk/2014/02/looking-for-footpaths-in-hickling-notts.html 2. We need to be asking for not just full datasets but also regular change-sets. If we cannot get a change-set from the data supplier then we need to be keeping a copy of any imported data and creating comparison tools between the original imported data and the updated data from that government/organisation. 3. More data conflation tools. Not all data can be imported in bulk. We need to look at developing more tools to allow for piecemeal imports from the local community. For example the Android app Vespucci *could* be extended/forked to allow the following work flow: 3a. A new import dataset is added to a holding database. 3b. On the ground mappers can can then view this database on the ground using Vespucci on their tablet/phone 3c. For each element they mark it as verified or incorrect, and if necessary change the tags or geometry using the tools already built into Vespucci. At this stage Vespucci has not shown any other OSM data, just the holding database layer. This makes it easier to use in areas of high data density. 3d. If the data is just nodes then Vespucci searches for potential matches in the OSM data. Is one is found the user is asked how to merge the two. If not found then the node is imported into OSM. 3e. For ways the user can either work with Vespucci to merge/import the data, or they can log in when back home using JOSM or ID and work with these editing tools to merge the verified data from the holding database. Osmose QA tool do this job. Look at this, last tow section at menu. http://osmose.openstreetmap.fr/fr/map/?zoom=6item=level=1,2,3 Mainly items are in France. Btw, the French region of Aquitaine (country around Bordeaux), have funded work to integrate into osmose more OpenData on this territory, I will do this in march. For addresse integration we have also a specific tool : http://addr.openstreetmap.fr/ Osmose can be a base work for this thematic. The OpenData part of Osmose is done as generic, so add new opendata set is simple. Btw, if you interested in add OpenData set to Osmose for integration or validation/gardeange of already integrated data, just ask. Frédéric. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Summer of Code 2014
Osmose QA tool do this job. Perhaps I am not aware of everything that Osmose can do, but my basic understanding is that it provides an in browser view of errors already in OSM. What I was trying to propose in (1) and (2) was a really slick, really simple tool that allows the user to load in two datasets (e.g. original and updated file from a government department, or a government file and an OSM extract) and it shows you the big differences in a really simple intuitive way. For (3) I am proposing a mobile friendly way of getting people out on the ground to verify data provided by a government and load it in to OSM (either there and then via mobile, or back at home on their computer). Happy to do some mock-ups if you like, but can't help much with (3). Longer term I *might* be able to tackle 1 and 2 but it would take me ages to get to grips with it all. Regards, Rob ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Summer of Code 2014
As in previous years, I think some further work on kothic-js would be good. Client side rendering considerably reduces server overheads for setting up your own mapping website, so ideas such as making it leaflet 0.7 compatible (appears to only work with 0.5.x or below atm), or client side caching (indexeddb etc) would be good. The latter would also allow interactivity to be added to the maps. I'll put it on the wiki at some point. I don't know the kothic codebase in enough detail and also time is tight for me so not sure if I'd be able to mentor it, but as an idea I think it's good. Nick -Rob Nickerson rob.j.nicker...@gmail.com wrote: - To: talk@openstreetmap.org From: Rob Nickerson rob.j.nicker...@gmail.com Date: 11/02/2014 09:35PM Subject: Re: [OSM-talk] Summer of Code 2014 Hi All, I tried to send the following idea to the imports mailing list the other day, but turns out I wasn't registered to post there. I guess it fits well with Summer of Code so I will add it to the wiki, but not being a developer I can't mentor anyone. snip So my question is: How do we improve our import work flows so that it is easier to keep imported or merged data up to date? Some ideas: 1. Tools to compare OSM data against the available external data set. One recent blog post on this by SK53 http://sk53-osm.blogspot.co.uk/2014/02/looking-for-footpaths-in-hickling-notts.html 2. We need to be asking for not just full datasets but also regular change-sets. If we cannot get a change-set from the data supplier then we need to be keeping a copy of any imported data and creating comparison tools between the original imported data and the updated data from that government/organisation. 3. More data conflation tools. Not all data can be imported in bulk. We need to look at developing more tools to allow for piecemeal imports from the local community. For example the Android app Vespucci *could* be extended/forked to allow the following work flow: 3a. A new import dataset is added to a holding database. 3b. On the ground mappers can can then view this database on the ground using Vespucci on their tablet/phone 3c. For each element they mark it as verified or incorrect, and if necessary change the tags or geometry using the tools already built into Vespucci. At this stage Vespucci has not shown any other OSM data, just the holding database layer. This makes it easier to use in areas of high data density. 3d. If the data is just nodes then Vespucci searches for potential matches in the OSM data. Is one is found the user is asked how to merge the two. If not found then the node is imported into OSM. 3e. For ways the user can either work with Vespucci to merge/import the data, or they can log in when back home using JOSM or ID and work with these editing tools to merge the verified data from the holding database. Any other ideas? RobJN ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Summer of Code 2014
Hi everyone! Kate and I are working on an application for OpenStreetMap to join the Summer of Code again in 2014. We've participated for several years, and I'm looking forward to a successful year. Should we be accepted, we'll need some great ideas to attract the best students. If you've got an idea for something that could be tackled by an undergraduate student in a few months during the Summer, please head over to the ideas page and add it: http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas Again, if you have great ideas, please add them so we can get great students. If you're near a university, I encourage you to recruit for us. Students will be paid to do great work, so track down your favorite students and remind them to apply when student applications open up later this year. Thanks! Feel free to send me an e-mail with questions, Ian ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Summer of Code 2014
Hi All, Another thing to note is part of the application is our ideas page. So to be accepted we need a great ideas page. Unfortunately the timeline on this is short as the appliication is due on Friday. It is especially helpful to mention ways they can contribute to already existing OSM projects. Often we've had project that were brand new and I'm not sure we really succeeding in bringing many students into the community that way. Best, -Kate On Tue, Feb 11, 2014 at 9:38 PM, Ian Dees ian.d...@gmail.com wrote: Hi everyone! Kate and I are working on an application for OpenStreetMap to join the Summer of Code again in 2014. We've participated for several years, and I'm looking forward to a successful year. Should we be accepted, we'll need some great ideas to attract the best students. If you've got an idea for something that could be tackled by an undergraduate student in a few months during the Summer, please head over to the ideas page and add it: http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas Again, if you have great ideas, please add them so we can get great students. If you're near a university, I encourage you to recruit for us. Students will be paid to do great work, so track down your favorite students and remind them to apply when student applications open up later this year. Thanks! Feel free to send me an e-mail with questions, Ian ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Summer of Code 2014
Hi All, I tried to send the following idea to the imports mailing list the other day, but turns out I wasn't registered to post there. I guess it fits well with Summer of Code so I will add it to the wiki, but not being a developer I can't mentor anyone. snip So my question is: How do we improve our import work flows so that it is easier to keep imported or merged data up to date? Some ideas: 1. Tools to compare OSM data against the available external data set. One recent blog post on this by SK53 http://sk53-osm.blogspot.co.uk/2014/02/looking-for-footpaths-in-hickling-notts.html 2. We need to be asking for not just full datasets but also regular change-sets. If we cannot get a change-set from the data supplier then we need to be keeping a copy of any imported data and creating comparison tools between the original imported data and the updated data from that government/organisation. 3. More data conflation tools. Not all data can be imported in bulk. We need to look at developing more tools to allow for piecemeal imports from the local community. For example the Android app Vespucci *could* be extended/forked to allow the following work flow: 3a. A new import dataset is added to a holding database. 3b. On the ground mappers can can then view this database on the ground using Vespucci on their tablet/phone 3c. For each element they mark it as verified or incorrect, and if necessary change the tags or geometry using the tools already built into Vespucci. At this stage Vespucci has not shown any other OSM data, just the holding database layer. This makes it easier to use in areas of high data density. 3d. If the data is just nodes then Vespucci searches for potential matches in the OSM data. Is one is found the user is asked how to merge the two. If not found then the node is imported into OSM. 3e. For ways the user can either work with Vespucci to merge/import the data, or they can log in when back home using JOSM or ID and work with these editing tools to merge the verified data from the holding database. Any other ideas? RobJN ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
