-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Captain's Log #69
Comments
I've been trying lately to write a successful test for different CRS. It kind of works but I've more or less ended up writing parts of Proj4Leaflet which, even the version for leaflet 1.0 beta does't really properly work. All the vectors are now displayed fine in a couple of different coordinate systems (that I am familiar with) (that's the 2770 and 2100). I have some issues though mainly with tile requests. I hope everything will be resolved soon. |
Obviously I won't make the 1.3 milestone. So I am going to move all milestones a month. There are a lot of features available on the developer branches but I don't wont to release them without proper testing. So I'll take my time, any help will be appreciated. |
I managed to write a test for EPSG:2100 it can be found at https://elasticrash.github.io/Angular.io.MapViewer/example/#/prj |
documentation is completely, out of date. so before I make any changes to the repository, I will first bring that up to date. |
My plans before moving to any changes are:
|
The past week I moved houses, the new house is still full with unopened boxes. My pc is still not plugged. So development will be slowed down significantly for the next two weeks |
examples were updated to use the next release, in order to demonstrate custom crs projections |
I've been busy lately consulting for a really big Angular 2 project. So I am only spending like 1/5 of the time I used to spend on this project. This will propably go on for the next three months. I am really close on releasing a really good update. But I need extented testing before I publish it. |
currently building the library's website while improving angular cli compatibility issues |
Minor release but huge update, I got around to properly build my library in both umd and esm. Structure changed a lot as well as some minor logic and depedencies. Function wise is identical |
I am creating this issue, mainly for writing how some things are progressing
The text was updated successfully, but these errors were encountered: