[udig-dev] [udig-devel] Using a non-standard CRS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[udig-dev] [udig-devel] Using a non-standard CRS

From: Іван В <ivanvydai@xxxxxxxxx>
Date: Thu, 16 Jun 2016 14:34:59 +0300
Delivered-to: udig-dev@xxxxxxxxxxxxxxxx
List-archive: <https://locationtech.org/mhonarc/lists/udig-dev>
List-help: <mailto:udig-dev-request@locationtech.org?subject=help>
List-subscribe: <https://locationtech.org/mailman/listinfo/udig-dev>, <mailto:udig-dev-request@locationtech.org?subject=subscribe>
List-unsubscribe: <https://locationtech.org/mailman/options/udig-dev>, <mailto:udig-dev-request@locationtech.org?subject=unsubscribe>

Hello colleagues, Frank,

Code from old thread below was not submitted to global uDig repository: http://lists.refractions.net/pipermail/udig-devel/2009-April/014658.html

Can this submit be done now?

Currently I'm talking only about isLatLong method fix that I'm facing on master branch code for my custom CRS.

Best regards,

Ivan

Follow-Ups:
- Re: [udig-dev] [udig-devel] Using a non-standard CRS
  - From: Frank Gasdorf

Prev by Date: [udig-dev] When is the next release from the current master?
Next by Date: Re: [udig-dev] [udig-devel] Using a non-standard CRS
Previous by thread: [udig-dev] When is the next release from the current master?
Next by thread: Re: [udig-dev] [udig-devel] Using a non-standard CRS
Index(es):
- Date
- Thread

Back to the top