Transforming Coordinate Reference Systems using CloverETL – A
Use Case  Share this article:   The ETL process must make sure
that the systems in question always get the data in the correct
format and CRS. This is where a quick and simple solution comes
in handy.  Let’s see how this problem can be easily handled in
CloverETL by using a third-party conversion library plugged into
a CloverETL transformation.  Note: You can find more information
about the CRS used in North America here.  The Example  Let’s
demonstrate a solution to a data exchange problem between Google
Maps and an export for a New York tourist agency running their
own map. The export has to be encoded in a different CRS than
the one Google Maps uses.  A Google Maps Based System  Here,
we’re running a web application that allows the user to pick a
position on Google Maps and add a note to it. This information
is then stored in a database and, since Google Maps uses CRS WGS
84, we get latitude-longitude pairs.  (In the picture below, you
can see h