This task is intended for discussing the Drupal 8 version of OpenLayers.

Issue fork openlayers-2361715

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Pol’s picture

I can't do this alone unfortunately, I'm looking for help !

m.stenta’s picture

@Pol: No worries, if it's needed it will happen! :-)

I'm working on a set of farm-management modules right now that leverage OpenLayers. I am eager to get them onto Drupal 8, so I'm also interested in helping to get all of their dependencies updated as well. Part of this process will involve getting outside funding from interested organizations. I will let you know if there are any developments!

Thanks for all the work you've done on OpenLayers!!

m.stenta’s picture

@Pol: How do you foresee the development of the 8.x branch in relation to the 7.x-3.x branch? I would assume that we would want to only port the 7.x-3.x, and not the 7.x-2.x, right? Would it make things difficult to start the 8.x before the 7.x-3.x is released (needing to maintain changes between the two branches)? If so, what are your current thoughts on 7.x-3.x? Can we potentially put together a [META] issue for organizing what's left to do on that? And also a [META] issue for the D8 conversion? I think it would help to get more folks involved if there was a clear plan and tasks laid out. I can help get that ball rolling if you want.

tormi’s picture

Status: Active » Closed (duplicate)
Related issues: +#2622398: [openlayers] Openlayers

Closing as a duplicate of #2622398: [openlayers] Openlayers.

tormi’s picture

Status: Closed (duplicate) » Active

Sry, didn't realize this is the roadmap issue ;)

Syntapse’s picture

Hi whats the latest on drupal 8 development? Is the intention full feature parity between d7 and d8? or a new UI/design for d8? I dont understand it fully yet but it looks to me as though the D7 code is already designed around symfony services etc. Is there scope/practice for/of code sharing?

Thanks,

Laurence

Pol’s picture

Hi,

The D8 version is "to be done".

You're right when you say the it uses Symfony, the "base code" could be the same in D7 and D8, this is why I'm using Service Container module as dependency.
To be honest, I don't know how to reproduce all these multisteps forms in D8, that's my main concern actually. I would need a bit of help.

Currently, I'm quite busy with Geocoder for D8 and D7 and unfortunately have no more free time these last days to work on this module, I hope to be back soon and release a 3.2 version.

m.stenta’s picture

Hi @Pol:

I don't know how to reproduce all these multisteps forms in D8, that's my main concern actually

Do you mean the forms for configuring all the various Ctools exportables?

What do you think about taking a different approach to those forms in D8? Is there any reason they need to be multi-step? I've always found that to be an extra layer of complexity that maybe isn't necessary. Most of the objects do not have very complicated configuration, so multi-step may be overkill.

Can you think of any specific reason why they are necessary? Or would you be open to considering a different approach in D8?

Pol’s picture

I'm absolutely open to any other solution... and help !

m.stenta’s picture

Cool! I'm eager to help with the D8 port! Perhaps we can discuss timing alongside other outstanding issues in the 7.x-3.x branch. Do you have any thoughts about if/how the two branches should be maintained in parallel?

zaporylie’s picture

Please count me in. I'm blocked with one project and probably will have to do it on D7 due to lack of D8 release of Openlayers module.

I believe I can dedicate some hours every week on port. Can help with PHP part.

m.stenta’s picture

@zaporylie Great!

Perhaps it would make sense to start an outline of the various pieces that are involved with this effort.

I'm busy this week and next week, but perhaps we could have an IRC meeting at some point after that to get the ball rolling?

juliencarnot’s picture

@all, not sure this is relevant but you might (or might not= be interested in recent progress from Geolocation Field, which is becoming map-provider/library "agnostic" and could maybe be a good option for coordinates input/storage, with active development for D8...

ressa’s picture

@juliencarnot: I just gave Geolocation Field a spin, and it is indeed very light weight and easy to set up. My main critique is that is based on GoogleMaps, and it doesn't seem possible to use another map provider, like OpenLayers, Leaflet, Polymaps ...

juliencarnot’s picture

@ressa: I'm not pro Google Maps either, but Geolocation Field is currently evolving to support other map providers (see link in my previous comment), for example with leaflet. Not saying it's ready yet or even that OpenLayers should become a submodule of Geolocation, but there might be options for capitalizing on features and enhancing choice...

ressa’s picture

That sounds great, I will follow those issues, and am looking forward to more provider options :-)

awasson’s picture

@Pol, regarding the D8 port. The Drupal Sprint Weekend 2017 is coming up. Do you think you can leverage some development help during that? If you have a roadmap or something that can be picked away at, I'm sure we can make some progress.

Mav-im’s picture

Hi Pol,
I'm very familiar with 7.x-3.1 codebase because of developing the same module for ESRI maps. I've used your codebase a lot while working on it and like your approach with services containers.
As my current project seems to be moving to D8 in nearest future it would be very useful to have Openlayer ported to D8 too.
Anyway it would be very helpful for me to understand D8 bottlenecks.

oadaeh’s picture

Assigned: Unassigned » oadaeh

I have started working on a port of the Openlayers module to Drupal 8.

@Pol, if you will create a 8.x-3.x branch, I will start submitting patches against it.

As a bit of a disclaimer, I will not promise a complete, stable module, but I will do my best to at least provide a solid working/functional start that others can jump in on with bug fixes, etc.

Thank you.

oadaeh’s picture

Assigned: oadaeh » Unassigned

I got started on this, but I have not had the time necessary to do very much with it, so I'm dropping this ball.

awasson’s picture

I wonder if there is enough skilled interest to push this forward.

Maybe a Google hangout discussion to look at who is interested and how to organize the effort? Maybe just a list of those who are interested in contributing.

I've been developing in D8 since it released in November 2015. I have a fair bit of experience with the GMap module in D6 but I don't know Open Layers.

Andrew

dqd’s picture

Strange enough, there is an openlayers release under composer require drupal/openlayers including openlayers, openlayers_block, openlayers_views even if there is no release on the project page nor on the release details list nor under drush dl openlayers --select ...

Syntapse’s picture

@diqidoq does it work?

chipway’s picture

Hi @diqidoq,

I tried but I didn't found the one you talked about:

composer require drupal/openlayers
[InvalidArgumentException]
Could not find package drupal/openlayers at any version for your minimum-stability (stable). Check the package spelling
or your minimum-stability

Do you use some specific composer repo?

dqd’s picture

strange ... o.O

Just to make sure, that I haven't dreamed ...

$ drush pmi openlayers
 Extension        :  openlayers                                              
 Project          :  openlayersd8                                            
 Type             :  module                                                  
 Title            :  OpenLayers                                              
 Description      :  OpenLayers                                              
 Version          :  8.x-1.0                                                 
 Date             :  2017-10-25                                              
 Package          :  OpenLayers                                              
 Core             :  8.x                                                     
 PHP              :  5.5.9                                                   
 Status           :  not installed                                           
 Path             :  modules/contrib/openlayersd8                            
 Schema version   :  no schema installed                                     
 Requires         :  inline_entity_form:inline_entity_form                   
 Required by      :  openlayers_block, openlayers_examples, openlayers_views 
 Configure        :  None      

@laurencefass: I wasn't able to really test it but I remember that the field widget already appeared in manage display settings.

@chipway: well it depends on which repos you use for composer. There are different ways to install Drupal via composer and with different package sources, from what I remember. But TBH, I am not really a fan yet of the cluttered composer introduction. In the moment it causes more trouble than it solves. Especially when Composer and Drush gets in the mix the wrong way ...

Jon@s’s picture

Anyone used/tested this since? Is it usable?

omarlopesino’s picture

@digidoq what you downloaded with composer is this module https://www.drupal.org/project/openlayersd8

dqd’s picture

@mistermoper: I know. But I thought it's the tmp "work-around" repo of the project until the port is more partly in progress or more usable/testable in dev state. Since it chimes in automatically when using composer require drupal/openlayers. This becomes even more strange then...

knipnehpets’s picture

Thanks for the info that there is a (basic) implementation of openlayers for D8 at https://www.drupal.org/project/openlayersd8
Stating the obvious, now that it is there (and based on OL 4), wouldn't it be worth the Drupal OL community contributing to that instead?
For me as with others, Openalyers on D7 has been an absolutely central module with irreplaceable functionality, and is one of the reasons I've been slow to go over to D8.

Pol’s picture

Hello,

I wasn't aware of this... bravo!

Indeed, this should be part of this repo... I don't get why Andy created another project.

Syntapse’s picture

Thanks for the update. May I ask: in a paragraph or less: how will OLD8 compare to existing d8 mapping tools?

knipnehpets’s picture

@laurencefass Re #31: There no d8 (or d7) mapping tool I know of that can even approach the power of the layered visualisations & enduser-interface that are possible with Openlayers. I suppose the Leaflet implementation would suit most users; I use it for simpler stuff.

AndyLicht’s picture

Hi, we can port it to the openlayers project. No problem, but i need support to merge it. At the weekend, i will make some video tutorials, how to use these module, but only in german. sorry my english isn´t very well.

Syntapse’s picture

thanks i will stay subscribed and help with testing along the way. given recent charges introduced by google, openlayers will be vital to the O/S community moving forward. D7 is very powerful map tool it would great (essential?) to see a port to D8.

zerogravity86’s picture

I would love to use Openlayers in Drupal8. Why is there so little progress. Can anyone point out the current difficulties for the port?

zaporylie’s picture

I believe it's mostly lack of time.

bradjones1’s picture

Yes - the main blocker would be a sponsor for development or volunteer bandwidth.

zerogravity86’s picture

Is there a plan for the migration in terms of core tasks that are open for basic mapping functionality, nice to have sub modules or groups of functionality that could be encapsulated.

I have never been part of any port, and wonder what tasks would be involved in this one to allow for the most important mapping functionalities.

Has anything been ported to the https://www.drupal.org/project/openlayersd8 project yet, which has a roadmap published on its page?

make the entity gui sexy, so not gis experts can also create maps
make the controlbar more independently from css
create a documentation for administration and developer
make views working
add vector tiles like wfs
add content type as layer to map
add entity for styling
add entity for projection

bradjones1’s picture

@zerogravity86 I'm not familiar with the maintainers of either this or the other project, however Drupal being a largely volunteer-driven project, your question about next steps would be, who is going to take this on? A module with complex functionality like this, especially if you want a "sexy" UI, is probably a month or two of full-time work for a qualified developer. If you're interested in sponsoring that work, I'm sure there are individuals or shops that would be interested in helping. Otherwise, a port would go from a ticket like this, to sub-tasks that are agreed-upon by people who plan to do that work, probably with some consultation in Drupal Slack or other regular meetings.

Sorry to basically re-iterate what I've said before, but a wish list is only helpful in so far as there are individuals with the bandwidth to execute it.

AndyLicht’s picture

Hi,
i will publish a new version of the openlayersd8 module in the next two months. the new version will support openlayers 6.1.1 and also feature styling. If you only want to use a simple map, maybe to show a location, please use geofield with leaflet or the geolocation module. The big target of my interpretation of the module is to get a rich GIS tool. I do everything in my own free time. It would be great to test the version 2.0 and help me with the documentation, because my english is not very well.
At the moment you can add wms and drupal resources to the map, some simple controls.
I´ve implemanted also a widget for geolocation_geometry, it will be submodule of geolocation, which supports postgis. So i hope it would be possible to use some more spatial opperations in the future.
best regards

MaryAleb’s picture

Hi @AndyLicht,
Are you still working on this openlayer8?

Thanks

MaryAleb’s picture

Hi guys,

We are willing to fund some one for working on the openlyer8 module and get it work. Please let me know if you are intersted.
MyEmail address: malebrahim@symphony3.com . Thanks

stelmo’s picture

Hello AndyLicht

I would like to help in whatever is needed.

nuez’s picture

I've been working on a Drupal 8/9 version too: Since this module was built to cover the needs of specific client work, I decided not to use the openlayersd8 module, unfortunately.

I'm not sure if the module is mature and flexible enough to be published as a Drupal module on DO.org, (tried to keep it as configurable as possible)

Please see for code and instructions here: https://gitlab.com/nuezio/drupal-openlayers
And a working example here: https://openlayers.nuez.io/

Feedback is welcome. If the maintainers of the openlayers module think this could be a good starting point for the D8/9 version of this module then I'm happy to facilitate things.

ken-g’s picture

Version: 7.x-3.x-dev » 8.x-4.x-dev

Changing version to 8.x-4.x-dev.

steinmb’s picture

Title: Port to Drupal 8 » Port to Drupal 9/10/11

Orkut Murat Yılmaz made their first commit to this issue’s fork.

Orkut Murat Yılmaz’s picture

I just came across this.

It looks nice, at first sight.