Hey Jeff and others, Thanks for your reply.
So, first of all, Open Summer of Code is a yearly event organized by Open Knowledge Belgium. They gather a lot of students, they gather a lot of clients with a project (and funding for the project). During July, the students work in groups of around 4 on a project, I will be their coach. The client is a small heritage organization based in Flanders. They already had a project to map chimneys and old industrial buildings. Some are still existing, others are already torn down. Their map can be found here: http://www.erfgoedzuidwest.be/content/ik-xploreer-mee They noticed that adding and managing geodata is pretty hard, and they want a solution which does everything they need (which is an awful lot). For that, I had the idea to build upon OHM, and provide a custom iD-editor with at least: - Presets for chimneys, industrial buildings and similar - Custom WMS-layers (they have a few WMS'es with old aerial imagery, but I might add in some layers from https://play.osm.be/historischekaart.html as well) I personally have already some experience with tweaking iD (the company I work for has a custom iD as well) - but the students will have to do that ;) If there is still some time left, we might also polish some of the texts of OHM itself (because a lot of the things are still pointing towards OSM, not OHM). We'll see how far we'll get and how much of that is still needed by then, I didn't dive into the details of the proposed changes mentioned. For the workflow - the easiest would probably be to clone your repos, work on them within the team and do a PR when things are somewhat finished. At last, I'm also a little worried about one aspect: inputting data is one thing, but if it is not possible to get it back, it's all a little useless. For now, the *overpass*-instance seems to be down. Do plans exist to revive it? Or do other ways exist to get the data (e.g. loading via JOSM/QGIS/...)? And how easy is it to customize your slider-example? The client will definitely want to visualize all their data, both digitally and in print. And how well-supported is the project? Will it all be hosted for the coming years? We have a small budget for hosting as well, perhaps we can help a little bit their (although the details will be messy and we'll have to work something out with invoices and such...) So, I hope you guys have a clearer idea of our project now! I'll try to chime in on the next dev meeting, 12th of June at 10:00AM in Pacific Time (which is at 7 PM for me in Central European Time). And sorry for hijacking the mail thread a little, but previously, my mails got lost unless they were replies so... With kind regards and looking forward to an answer, Pieter Vander Vennet On 04.06.19 23:11, Jeff Meyer wrote: > Hi Pieter - > > That is awesome. If you'd like, you can make some mods to ID in our > repo here: https://github.com/OpenHistoricalMap. > > What presets did you have in mind? > > Jim, Seth - what's the best way for Pieter to help out here? > > Thanks, > Jeff > > > On Tue, Jun 4, 2019 at 1:38 PM Pieter Vander Vennet > <[email protected] <mailto:[email protected]>> wrote: > > Hello, > > I'm afraid my previous email has been lost into the void. > > I will be the coach for Open Summer Of Code coming july. A small > heritage organisation asked us to create 'some tool to make adding > heritage data easier'. > > I was planning to create an iD-fork for OHM with presets that they > would need - is that a good idea? > > The slider is pretty cool btw! > > On 01.06.19 00:36, Jeff Meyer wrote: >> Hi all - >> >> We had a good meeting this past Wednesday - thanks to all >> attendees: Bert de Brujin, Charlotte Wolter, Gregor Allenworth, >> Rob Warren, and Seth Fitzsimmons. >> >> Updates: >> >> - Gregor provided an overview of the _latest timeslider demo_ >> (see >> here: >> https://openhistoricalmap.github.io/openhistoricaltiles/mbgl-control-timeslider/demo/#15.000/49.55012/17.72994/1830,1800-1900) >> - Updates to the functionality include: >> -- _Greater tolerance for incomplete date tags_ (e.g. it works >> with just year tags in smart ways) >> -- _Support for negative dates_ (!) - this is a big deal, as >> normal database handling and internet date standards (ISO 8601) >> don't support this. Now, we can now go back into BCE - check this >> out: >> https://openhistoricalmap.github.io/openhistoricaltiles/mbgl-control-timeslider/demo/#15.998/29.97424/31.13004/-2493,-4000-2018 >> >> >> - Seth provided updates on: >> - _Border handling at both high and low zoom levels_ - this is >> different from how OSM handles borders, so this will be cool - >> you can get a preview of how this works with Maine's historical >> borders >> here: >> https://openhistoricalmap.github.io/openhistoricaltiles/mbgl-control-timeslider/demo/#6.247/45.93660/-67.31992/1784,1700-1900 >> - _Integrating the time slider with the rest of the OHM site_ >> (aka the "Rails app") in the next couple of weeks >> >> - Operating model updates >> -- Discussed how decision making process will work within the >> OHM community. >> -- Rob agreed to look at the updates we are proposing and if >> ok,,deploy them at some point in the near future. Changes can be >> found at: https://github.com/OpenHistoricalMap/ohm-website >> >> - Transition / launch strategy >> -- Bert had a good suggestion that we may want to run the new / >> vector tile-based site in parallel with the existing site while >> we prove its reliability. We'll be taking a look at how to make >> that possible. >> >> - Grant writing >> -- Charlotte offered to help write grant proposals to help fund >> OHM. This is awesome! I believe we'll need to do a few things >> before we can truly pursue funding: a) have a published >> governance model, b) have a site that shows more of the >> capabilities / applicability of this effort to 3rd parties, and >> c) some affiliation with a non-profit organization, either our >> own or an affiliate/sponsoring institution. >> -- I believe we can & should use the time that taking care of >> a, b, and c above will take to identify and strategize around >> sources of funding. Charlotte brought up Knight as a potential >> source. >> >> - Marketing updates >> -- Jeff had not much to report here, but will start writing >> how-to's. >> -- If anyone has or knows of particularly good examples to >> input to put into OHM, please let me know. We chould potentially >> feature them as case studies. >> >> As always, please let me know if you have any questions. >> >> Next meetings: >> 12 June, 10am PT, meet.google.com/bbn-yhvo-cps >> <http://meet.google.com/bbn-yhvo-cps> >> 26 June, 10am PT, meet.google.com/bbn-yhvo-cps >> <http://meet.google.com/bbn-yhvo-cps> >> >> Thanks, >> Jeff >> >> -- >> Jeff Meyer >> 206-676-2347 >> osm: Open Historical Map (OHM) >> <http://wiki.openstreetmap.org/wiki/Open_Historical_Map> / my OSM >> user page <http://www.openstreetmap.org/user/jeffmeyer> >> t: @OpenHistMap >> >> >> >> >> >> _______________________________________________ >> Historic mailing list >> [email protected] <mailto:[email protected]> >> https://lists.openstreetmap.org/listinfo/historic > > > > -- > Jeff Meyer > 206-676-2347 > osm: Open Historical Map (OHM) > <http://wiki.openstreetmap.org/wiki/Open_Historical_Map> / my OSM user > page <http://www.openstreetmap.org/user/jeffmeyer> > t: @OpenHistMap > > > >
<<attachment: pietervdvn.vcf>>
_______________________________________________ Historic mailing list [email protected] https://lists.openstreetmap.org/listinfo/historic
