Timeline for Unable to transform from EPSG:3857 to UTM in Geotools
Current License: CC BY-SA 3.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2016 at 7:56 | vote | accept | Daniel Cerecedo | ||
| Feb 16, 2016 at 19:06 | comment | added | Ian Turton | Your coordinates are almost certainly in wgs84 lat/lon hence my use of wgs to utm to convert to meters followed by utm to google | |
| Feb 16, 2016 at 16:46 | comment | added | Daniel Cerecedo | @iant I'm not sure what I'm missing. When looking to your code you create the polygon and transform it from UTM -> Google Maps -> UTM. My frontend uses GMaps for input, so I assume the coordinates I get from GMaps are in EPSG:3857 (assumption). I need to convert to UTM to make some transient geometric calculations in meters. Then I'm transforming from GMaps CRS to WGS84 and storing the polygon because mongodb uses WGS84 for spatial queries. Is it that what I'm getting from GMaps are not coordinates in EPSG:3857, as your code implies? Thanks for your ongoing support! | |
| Feb 16, 2016 at 11:32 | comment | added | Ian Turton | CoordinateReferenceSystem wgs84 = CRS.decode("EPSG:3857 ", true); is wrong(ish) in that 3587 is not WGS84 so your coordinates are on Null Island (well outside the UTM zone you are using). Look carefully at how my code builds the polygons. | |
| Feb 16, 2016 at 11:20 | history | edited | Daniel Cerecedo | CC BY-SA 3.0 |
added 5176 characters in body
|
| S Feb 12, 2016 at 21:07 | history | bounty ended | CommunityBot | ||
| S Feb 12, 2016 at 21:07 | history | notice removed | CommunityBot | ||
| Feb 10, 2016 at 9:33 | answer | added | Ian Turton | timeline score: 1 | |
| Feb 9, 2016 at 21:07 | history | tweeted | twitter.com/StackGIS/status/697164946283634688 | ||
| S Feb 4, 2016 at 19:41 | history | bounty started | Daniel Cerecedo | ||
| S Feb 4, 2016 at 19:41 | history | notice added | Daniel Cerecedo | Draw attention | |
| Feb 2, 2016 at 20:31 | comment | added | Daniel Cerecedo |
Hi @mkennedy, thanks for pointing the mistake in the post. Just edited to add the correct wsg84 projection and updated the `toMeters' transformation. This mistake has been because of several tests I have done and left the bad value. I just explicitly confirm that with this parameters the error is the one I posted.
|
|
| Feb 2, 2016 at 20:28 | history | edited | Daniel Cerecedo | CC BY-SA 3.0 |
Corrected the wgs84 to EPSG:3857 and the corresponding transformation
|
| Feb 2, 2016 at 19:53 | comment | added | mkennedy | Why are you mixing UTM zone 30 and Michigan Central state plane zone? OH, you've got a mistake in your code somewhere, instead of 3857, you've got 3587, NAD83 (NSRS2007) / Michigan Central. | |
| Feb 2, 2016 at 19:35 | comment | added | Daniel Cerecedo |
@iant that's the output of utm.toWKT(). Can you give more clues of what you expect or how to obtain it? Thanks!
|
|
| Feb 2, 2016 at 19:33 | history | edited | Daniel Cerecedo | CC BY-SA 3.0 |
corrected format
|
| Feb 2, 2016 at 18:46 | comment | added | Ian Turton | I don't think that's a utm transform | |
| Feb 2, 2016 at 18:44 | comment | added | Daniel Cerecedo | @iant just edited the question wit required info | |
| Feb 2, 2016 at 18:44 | history | edited | Daniel Cerecedo | CC BY-SA 3.0 |
added UTM projection and transformation dumps
|
| Feb 2, 2016 at 18:36 | comment | added | Ian Turton | Can you dump the wkt of the utm projection into the question please | |
| Feb 2, 2016 at 17:26 | review | First posts | |||
| Feb 2, 2016 at 17:45 | |||||
| Feb 2, 2016 at 17:25 | history | asked | Daniel Cerecedo | CC BY-SA 3.0 |