<div dir="ltr">Example of GeoJSON Jekyll template<br><div><br>Final<br><a href="http://state-hiu.github.io/hiu.state.gov/products/products.json">http://state-hiu.github.io/hiu.state.gov/products/products.json</a><br><br>Template<br></div><div><a href="https://raw.githubusercontent.com/state-hiu/hiu.state.gov/gh-pages/products/products.json">https://raw.githubusercontent.com/state-hiu/hiu.state.gov/gh-pages/products/products.json</a><br><br></div><div>Looks like it does not work with *.<a href="http://github.io">github.io</a> urls,only <a href="http://github.com">github.com</a>. For example.<br><br><a href="https://render.githubusercontent.com/view/geojson?url=http://state-hiu.github.io/hiu.state.gov/products/products.json">https://render.githubusercontent.com/view/geojson?url=http://state-hiu.github.io/hiu.state.gov/products/products.json</a><br><br>Tom, for now, I'm +1 for your approach for a map, since the yaml/template approach will require more coding effort. The yaml/template approach would help us render the providers in other "views" such as a table, so probably where we should end up.<br></div><div><br></div><div>Regards,<br></div><div>Patrick<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 22, 2016 at 7:40 AM, Tom Kralidis <span dir="ltr"><<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Patrick: thanks for the info. Any examples of this? Note that the<br>
proposed branch requires providers only update a single GeoJSON file<br>
directly on GitHub.<br>
<br>
I've since submitted a PR [1] which we can improve over time.<br>
<br>
..Tom<br>
<br>
[1] <a href="https://github.com/GeoNode/geonode.github.com/pull/38/files" rel="noreferrer" target="_blank">https://github.com/GeoNode/geonode.github.com/pull/38/files</a><br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Jul 21, 2016 at 11:54 PM, Patrick Dufour <<a href="mailto:pjdufour.dev@gmail.com">pjdufour.dev@gmail.com</a>> wrote:<br>
> You can render a geojson file via a jekyll template from yaml posts files.<br>
> That way users only need to make posts (yaml front matter + markdown<br>
> content) instead of raw html.<br>
><br>
> Regards,<br>
> Patrick<br>
><br>
><br>
> On Jul 21, 2016 8:53 PM, "Jeffrey Johnson" <<a href="mailto:ortelius@gmail.com">ortelius@gmail.com</a>> wrote:<br>
>><br>
>> +1<br>
>><br>
>> On Thursday, July 21, 2016, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com">tomkralidis@gmail.com</a>> wrote:<br>
>>><br>
>>> Oops forgot the branch!<br>
>>> <a href="https://github.com/tomkralidis/geonode.github.com/tree/providers" rel="noreferrer" target="_blank">https://github.com/tomkralidis/geonode.github.com/tree/providers</a><br>
>>><br>
>>><br>
>>><br>
>>> On Thu, Jul 21, 2016 at 8:50 PM, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com">tomkralidis@gmail.com</a>><br>
>>> wrote:<br>
>>> > I've created a branch which adds a provider page (lifting text from<br>
>>> > <a href="http://mapserver.org/community/service_providers.html" rel="noreferrer" target="_blank">http://mapserver.org/community/service_providers.html</a>) as well as a<br>
>>> > providers' map, the idea being getting a map overview of providers<br>
>>> > around the world, and clicking a point allows the user to click the<br>
>>> > provider link to the website/URL.<br>
>>> ><br>
>>> > The requirement would be foreach provider to provide:<br>
>>> > - company name<br>
>>> > - lat/long coordinates<br>
>>> > - URL<br>
>>> ><br>
>>> > Providers could then add their info via pull request by updating the<br>
>>> > providers/providers.geojson directly.<br>
>>> ><br>
>>> > Thoughts? I can PR this if folks think it's a good idea.<br>
>>> ><br>
>>> > On Thu, Jul 21, 2016 at 5:23 PM, Patrick Dufour<br>
>>> > <<a href="mailto:pjdufour.dev@gmail.com">pjdufour.dev@gmail.com</a>> wrote:<br>
>>> >> I think this is a great idea and would come in handy a lot! Maybe<br>
>>> >> also<br>
>>> >> include which countries they operate in, but might want to hold that<br>
>>> >> for<br>
>>> >> version 2. Would be easy to implement something in Jekyll using posts<br>
>>> >> and<br>
>>> >> an index.html page.<br>
>>> >><br>
>>> >> <a href="https://github.com/GeoNode/geonode.github.com/tree/master/faqs" rel="noreferrer" target="_blank">https://github.com/GeoNode/geonode.github.com/tree/master/faqs</a><br>
>>> >><br>
>>> >> Regards,<br>
>>> >> Patrick<br>
>>> >><br>
>>> >> On Mon, Jun 27, 2016 at 5:24 AM, Simone Giannecchini<br>
>>> >> <<a href="mailto:simone.giannecchini@geo-solutions.it">simone.giannecchini@geo-solutions.it</a>> wrote:<br>
>>> >>><br>
>>> >>> I would add also:<br>
>>> >>><br>
>>> >>> GeoSolutions <a href="http://www.geo-solutions.it" rel="noreferrer" target="_blank">http://www.geo-solutions.it</a><br>
>>> >>><br>
>>> >>> :)<br>
>>> >>><br>
>>> >>> Regards,<br>
>>> >>> Simone Giannecchini<br>
>>> >>> ==<br>
>>> >>> GeoServer Professional Services from the experts!<br>
>>> >>> Visit <a href="http://goo.gl/it488V" rel="noreferrer" target="_blank">http://goo.gl/it488V</a> for more information.<br>
>>> >>> ==<br>
>>> >>> Ing. Simone Giannecchini<br>
>>> >>> @simogeo<br>
>>> >>> Founder/Director<br>
>>> >>><br>
>>> >>> GeoSolutions S.A.S.<br>
>>> >>> Via di Montramito 3/A<br>
>>> >>> 55054 Massarosa (LU)<br>
>>> >>> Italy<br>
>>> >>> phone: <a href="tel:%2B39%200584%20962313" value="+390584962313">+39 0584 962313</a><br>
>>> >>> fax: <a href="tel:%2B39%200584%201660272" value="+3905841660272">+39 0584 1660272</a><br>
>>> >>> mob: <a href="tel:%2B39%20333%208128928" value="+393338128928">+39 333 8128928</a><br>
>>> >>><br>
>>> >>> <a href="http://www.geo-solutions.it" rel="noreferrer" target="_blank">http://www.geo-solutions.it</a><br>
>>> >>> <a href="http://twitter.com/geosolutions_it" rel="noreferrer" target="_blank">http://twitter.com/geosolutions_it</a><br>
>>> >>><br>
>>> >>> -------------------------------------------------------<br>
>>> >>> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003<br>
>>> >>> Le informazioni contenute in questo messaggio di posta elettronica<br>
>>> >>> e/o<br>
>>> >>> nel/i file/s allegato/i sono da considerarsi strettamente riservate.<br>
>>> >>> Il loro utilizzo è consentito esclusivamente al destinatario del<br>
>>> >>> messaggio, per le finalità indicate nel messaggio stesso. Qualora<br>
>>> >>> riceviate questo messaggio senza esserne il destinatario, Vi<br>
>>> >>> preghiamo<br>
>>> >>> cortesemente di darcene notizia via e-mail e di procedere alla<br>
>>> >>> distruzione del messaggio stesso, cancellandolo dal Vostro sistema.<br>
>>> >>> Conservare il messaggio stesso, divulgarlo anche in parte,<br>
>>> >>> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità<br>
>>> >>> diverse, costituisce comportamento contrario ai principi dettati dal<br>
>>> >>> D.Lgs. 196/2003.<br>
>>> >>><br>
>>> >>> The information in this message and/or attachments, is intended<br>
>>> >>> solely<br>
>>> >>> for the attention and use of the named addressee(s) and may be<br>
>>> >>> confidential or proprietary in nature or covered by the provisions of<br>
>>> >>> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New<br>
>>> >>> Data Protection Code).Any use not in accord with its purpose, any<br>
>>> >>> disclosure, reproduction, copying, distribution, or either<br>
>>> >>> dissemination, either whole or partial, is strictly forbidden except<br>
>>> >>> previous formal approval of the named addressee(s). If you are not<br>
>>> >>> the<br>
>>> >>> intended recipient, please contact immediately the sender by<br>
>>> >>> telephone, fax or e-mail and delete the information in this message<br>
>>> >>> that has been received in error. The sender does not give any<br>
>>> >>> warranty<br>
>>> >>> or accept liability as the content, accuracy or completeness of sent<br>
>>> >>> messages and accepts no responsibility for changes made after they<br>
>>> >>> were sent or for other risks which arise as a result of e-mail<br>
>>> >>> transmission, viruses, etc.<br>
>>> >>><br>
>>> >>><br>
>>> >>> On Fri, Jun 10, 2016 at 10:40 PM, Jeffrey Johnson<br>
>>> >>> <<a href="mailto:ortelius@gmail.com">ortelius@gmail.com</a>><br>
>>> >>> wrote:<br>
>>> >>> > James,<br>
>>> >>> ><br>
>>> >>> > We keep discussing adding a page to the website with commercial<br>
>>> >>> > providers, but haven't ever done it. There are actually a bunch<br>
>>> >>> > these<br>
>>> >>> > days. A partial list is below (in no particular order).<br>
>>> >>> ><br>
>>> >>> > If I am missing anyone (or you dont want to be included on future<br>
>>> >>> > versions of this list) please let me know.<br>
>>> >>> ><br>
>>> >>> > If someone is up for making a page out of this on the site, send a<br>
>>> >>> > PR<br>
>>> >>> > and we can merge it.<br>
>>> >>> ><br>
>>> >>> > Gesp <a href="http://www.gesp.it" rel="noreferrer" target="_blank">http://www.gesp.it</a><br>
>>> >>> > AllSpatial <a href="https://github.com/allspatial" rel="noreferrer" target="_blank">https://github.com/allspatial</a> (Michael Wagner)<br>
>>> >>> > LTS International <a href="http://www.ltsi.co.uk/" rel="noreferrer" target="_blank">http://www.ltsi.co.uk/</a><br>
>>> >>> > Prominent Edge <a href="http://prominentedge.com/" rel="noreferrer" target="_blank">http://prominentedge.com/</a><br>
>>> >>> > Piensa <a href="http://piensa.co/" rel="noreferrer" target="_blank">http://piensa.co/</a><br>
>>> >>> > ADPC <a href="http://adpc.net" rel="noreferrer" target="_blank">http://adpc.net</a><br>
>>> >>> > Terranodo <a href="http://terranodo.io" rel="noreferrer" target="_blank">http://terranodo.io</a> (full disclosure, this is my company)<br>
>>> >>> > AcuGIS <a href="https://www.acugis.com/" rel="noreferrer" target="_blank">https://www.acugis.com/</a><br>
>>> >>> > Kartoza <a href="http://kartoza.com/" rel="noreferrer" target="_blank">http://kartoza.com/</a><br>
>>> >>> > Geo Enviro Omega <a href="http://www.geo.co.id/" rel="noreferrer" target="_blank">http://www.geo.co.id/</a><br>
>>> >>> > Applied GeoSolutions <a href="http://www.appgeo.com/" rel="noreferrer" target="_blank">http://www.appgeo.com/</a><br>
>>> >>> > Boundless <a href="http://boundlessgeo.com/" rel="noreferrer" target="_blank">http://boundlessgeo.com/</a><br>
>>> >>> > Agrisoft <a href="http://www.agrisoft.co.id/" rel="noreferrer" target="_blank">http://www.agrisoft.co.id/</a><br>
>>> >>> > Team Geode Belgium <a href="http://opengeode.be/" rel="noreferrer" target="_blank">http://opengeode.be/</a><br>
>>> >>> > Geocent <a href="http://www.geocent.com/" rel="noreferrer" target="_blank">http://www.geocent.com/</a><br>
>>> >>> > Quantitative Engineering Design <a href="http://qed.ai" rel="noreferrer" target="_blank">http://qed.ai</a><br>
>>> >>> ><br>
>>> >>> > Note, Im sure there are plenty of individual developers on this<br>
>>> >>> > list<br>
>>> >>> > who could also help you.<br>
>>> >>> ><br>
>>> >>> > Hope that helps!<br>
>>> >>> ><br>
>>> >>> > Jeff<br>
>>> >>> ><br>
>>> >>> > On Fri, Jun 10, 2016 at 12:58 PM, James Adamson<br>
>>> >>> > <<a href="mailto:james@northwaterco.com">james@northwaterco.com</a>><br>
>>> >>> > wrote:<br>
>>> >>> >> How would I go about finding a programmer/developer that I can<br>
>>> >>> >> work<br>
>>> >>> >> with to<br>
>>> >>> >> design and implement an GeoNode supported site?<br>
>>> >>> >><br>
>>> >>> >><br>
>>> >>> >> _____________<br>
>>> >>> >> James K. Adamson, P.G.<br>
>>> >>> >> <a href="tel:%2B1.630.742.6836" value="+16307426836">+1.630.742.6836</a><br>
>>> >>> >> <a href="http://www.northwaterco.com" rel="noreferrer" target="_blank">www.northwaterco.com</a><br>
>>> >>> >><br>
>>> >>> >><br>
>>> >>> >> _______________________________________________<br>
>>> >>> >> geonode-devel mailing list<br>
>>> >>> >> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>>> >>> >> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>>> >>> >><br>
>>> >>> > _______________________________________________<br>
>>> >>> > geonode-devel mailing list<br>
>>> >>> > <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>>> >>> > <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>>> >>> _______________________________________________<br>
>>> >>> geonode-devel mailing list<br>
>>> >>> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>>> >>> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> geonode-devel mailing list<br>
>>> >> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>>> >> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
>>> >><br>
>>> _______________________________________________<br>
>>> geonode-devel mailing list<br>
>>> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
>>> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
</div></div></blockquote></div><br></div>