Yesterday I sent this to user's list, but I think is most suitable here.
Note that I've created a patch which solves the problem, please have a
look at it.
I've been working on 2.5.x branch.
Original message:
--
Hello list,
I'm writing a DBF file using a code like this:
DbaseFileHeader
just writing the
header in the close method).
Would you consider including this changes in GeoTools?
Best regards,
César
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
César Martínez Izquierdo
GIS developer
- - - - - - - - - - - - - - - - - -
e patient. I've opened an issue in JIRA so that it doesn't
get forgotten:
http://jira.codehaus.org/browse/GEOT-2794
Regards,
César
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
César Martínez Izquierdo
GIS developer
- - - - - - - - - -
accept this contribution, as it is
currently the main blocker for going forward.
Best regards,
César Martínez Izquierdo
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
César Martínez Izquierdo
GIS developer
- - - - - - - - - - - - - - - - -
d
>
> If you have any questions, ask away :-)
>
> Cheers
> Andrea
>
>
> On Fri, Feb 23, 2018 at 3:24 PM, César Martínez Izquierdo
> wrote:
>>
>> Hi,
>>
>> We are evaluating using Geotools as the basis for our CRS management
>> libraries on gvSIG
so this change will imply some method signature modifications on that
API.
Best regards,
César Martínez
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
César Martínez Izquierdo
GIS developer
- - - - - - - - - - - - - - - - - -
; jsr363 and jsr275 in a project leads to many problems because both use the
>> javax.measure package and some identical class names. I guess it would have
>> been easier if jsr363 used another package, but because of these issues I
>> stopped working on the migration.
>&
CRSs). I'd then add tests cases
for them.
Best regards,
César Martínez
On 4 March 2018 at 09:59, Andrea Aime wrote:
> Hi Cesar,
> the referencing module second name is indeed "painful". Nothing new there
> I'm afraid :-)
>
> Cheers
> Andrea
>
>
> On
today and have made the following proposal:
>> - https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363
>>
>> So far no surprises, we will be in tomorrows GeoTools meeting if there are
>> any questions, and would like to proceed with a pull request this week.
>
196/2003.
>>
>> The information in this message and/or attachments, is intended solely for
>> the attention and use of the named addressee(s) and may be confidential or
>> proprietary in nature or covered by the provisions of privacy act
>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>> Code).Any use not in accord with
exist). So it
seems we are coming closer to completing the migration.
César
On 5 April 2018 at 17:01, César Martínez Izquierdo wrote:
> Hi, I've created a branch for working on Geoserver adaptation:
> https://github.com/dispiste/geoserver/tree/jsr363_units
>
> I've also
> On Thu, Apr 5, 2018 at 6:17 PM, César Martínez Izquierdo
> wrote:
>>
>> Hi again,
>>
>> Geoserver is properly compiling and passing tests now in the branch,
>> using:
>> mvn -fn clean install
>>
>> There is only one compil
mmediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender does
> not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for change
its utility class to make upgrading easier:
>
> * unit.getName() --> Units.toName( unit );
> * Unit.valueOf(unitString) --> Units.valueOf( unitString ); // our current
> search and replace is quite long
>
>
>
> --
> Jody Garnett
>
> On 5 April 2018 at 10:21, César
ifferent way (a Hint was
suggested in the past, see [2]). Note that I am still not offering myself
to implement it, but I might do it depending on the expected amount of work
to do so.
Does it sound reasonable for you?
Best regards,
César Martínez
[1]
http://osgeo-org.1560.x6.nabble.com/UniqueV
15 matches
Mail list logo