-
Notifications
You must be signed in to change notification settings - Fork 73
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
Unknown projection: longlat #111
Comments
hi @Tom3652, how is proj4j added into the project? also what version is the project dependent on? |
Hello @pomadchin !
I have also tried an older version that doesn't use the separated package Don't hesitate if you need more information ! |
🤔 hmm, that indeed does look like the packages separation affected somehow the build. Unfortunately the projects im using proj4j in did not suffer anything (https://github.com/locationtech/geotrellis/blob/master/project/Dependencies.scala#L77-L78) Could you check the dep tree to ensure the proj4j-epsg resources folder is properly pulled? |
The only idea I can come up is that no projection files in the classapatch are causing this error |
Thanks for pointing it out, it's not code relevant then, only configuration somehow. Yes well the files seem to be here :
However is it possible that it has something to do with release / debug mode ? I have a |
If it works in the studio but not in a shape of a package => that's definitely smth related to packaging. // I haven't dealt with Androd for quite some time |
Thanks for your reply, at least i know this something related to this, i will try to figure it out and post a solution here when i found one. |
Great! Feel free to drop here anything; I'll try to help u as much as I can! |
Thank you very much, really apreciated ! |
Oh i see thank you ! Will dig deeper |
Looking closer now.
Registry is declared over there and it is purely in mem Wondering what happens to the project init on your app side. Definitely need to be a reproducible example to assist further :/ |
Thank you very much, i had not followed the in mem insight you gave me but indeed there is defintely no "reason" it happens Will run more tests and see if i can debug it further, until forking the project and add some debug logs if i have to 😅 |
Oh, in mem is that this registry is just a HashMap filled in in the object constructor. Wondering how the debug mode may affect it 🤔 |
Alright i am getting closer, i have logged this :
And i am getting |
It really makes me wonder if the commented lines at the begining of this method are actually very useful in release mode :
Because it seems there is an issue with
|
Hello @pomadchin , do you think it might be a bug now ? Do you think this might be happening because of the |
@Tom3652 if that's possible to generate a reproducible example that could be some bug that just got revealed by resources in different packages 👍 |
@pomadchin i can't reproduce it for now but i know a real factor that causes the issue : When i set the Kotlin version of my app to When i set them to the latest version : Using Gradle 8.4 distribution instead of 7.5.1, it simply doesn't work. So the conclusion is that the newest version of Gradle / Kotlin compiling files is changing maybe the way I will try to make reproductible example when i have the time, but for now my project is saved by rolling back to older version of Kotlin and Gradle ! 🙏🏼 |
That's interesting, I'd be curious to see diff in the bytecode ha. |
Hi friends! I suspect that the issue is to do with the addition of R8, replacing Proguard for code optimisation. R8 appears to be more aggressive than Proguard, and perhaps it is for this reason that your projection classes are missing at runtime. I'm far from an expert on the matter, but hopefully you'll have similarly good luck by adding the following incantation to your This should keep all projection classes from being optimised into oblivion. If know at compile time which projections you'll need and you wish to save a few bytes, you can probably instead choose to only keep the projections you'll need. e.g. I hope this helps! |
hey @dprks ! It seems to be working with the pro-guard rule, thank you very much ! |
Thanks for the package !
When i try to transform EPSG:2154 i am getting this error :
Unkown projection: longlat
From this method :
I am using this method to call the transform :
The entire error message i have is :
Error transforming lat 43.094308831666566 - Ing 5.825118781666667 Unknown projection: longlat
So i have checked that my lat - lng were correct and it actually works fine sometimes, sometimes i have the error.
Can i know more why i have this error and how can i fix it please ?
The text was updated successfully, but these errors were encountered: