[Geoserver-devel] Joining Jira Dev team

GeoServer GeoServer Developer
1

Hi,

We seem to have 148 “easy” tickets in the sprint category and I would say that we should not add any before we can clear a few bugs out of that bucket.

I would recommend this short list for Nadia:

https://osgeo-org.atlassian.net/browse/GEOS-8388

Feels easy, cascading WMTS should not change lower case “access_token” into upper case “ACCESS_TOKEN”. However, it may have some connections into general handling of KVP parameters.

https://osgeo-org.atlassian.net/browse/GEOS-7209

Make importer to take

“crs”: { “type”: “name”, “properties”: { “name”: “urn:ogc:def:crs:OGC:1.3:CRS84” } },

as a synonym to

“crs”: { “type”: “name”, “properties”: { “name”: “urn:ogc:def:crs:EPSG:4326" } },

Feels also easy but perhaps it can lead to deep waters about how to handle different ways for defining CRS and how it affects axis order.

If you can’t resolve those then comments about possible problems in KVP and CRS handling would be valuable as well.

-Jukka Rahkonen-

Lähettäjä: Torben Barsballe [mailto:tbarsballe@…3839…]
Lähetetty: 28. marraskuuta 2017 21:46
Vastaanottaja: Nadia Copeland <ncopeland@…3839…>
Kopio: geoserver-devel geoserver-devel@lists.sourceforge.net
Aihe: Re: [Geoserver-devel] Joining Jira Dev team

(attachments)

image001.png

···

Hello Nadia,

Welcome! The first thing to do would be to get a GeoServer development environment set up, see the Developer Guide. You’ll also want to familiarize yourself with the Project Procedures.

Bug Stomps happen the last Friday of each month; the next one is December 29 (which I expect will be sparsely attended due to the holidays). That said, you are welcome to contribute fixes whenever. The list of “simple” bugs that we use for the Bug Stomp is here, it is usually a good starting point: https://osgeo-org.atlassian.net/issues/?filter=11300

Torben

On Tue, Nov 28, 2017 at 11:18 AM, Nadia Copeland <ncopeland@…3839…> wrote:

Hello!

I have just subscribed to the newsletter and am interested in taking part in the bug stomps as recommended by a colleague.

I am studying to be a geospatial developer and have joined Boundless as a corporate concierge until I graduate and will move into a gis developer apprenticeship. Getting involved in the geo community and improving my skills through volunteer work and bug fixes is awesome to me! I am proficient in C# and Java and am learning Javascipt syntax.

Thank you and look forward to participating!

Best,

Nadia

–

Nadia Copeland

Corporate Concierge | Boundless

ncopeland@boundlessgeo.com

314.596.6171 (cell)

@boundlessgeo

BoundlessLogo

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

2

On Wed, Nov 29, 2017 at 4:56 PM, Rahkonen Jukka (MML) <
jukka.rahkonen@anonymised.com> wrote:

https://osgeo-org.atlassian.net/browse/GEOS-7209

Make importer to take

"crs": { "type": "name", "properties": { "name": "urn:ogc:def:crs:OGC:1.3:CRS84"
} },

as a synonym to

"crs": { "type": "name", "properties": { "name":
“urn:ogc:def:crs:EPSG:4326" } },

Feels also easy but perhaps it can lead to deep waters about how to handle
different ways for defining CRS and how it affects axis order.

That's indeed a case where OGC defined the first as lon/lat and the second
as lat/lon.
But maybe within the context of GeoJSON that difference can be ignored.

From the GeoJSON spec we implement (the older one, the new one is a bit

retarded and has not notion of CRS at all....):

A position is represented by an array of numbers. There must be at least
two elements, and may be more. The order of elements must follow x, y, z
order (easting, northing, altitude for coordinates in a projected
coordinate reference system, or longitude, latitude, altitude for
coordinates in a geographic coordinate reference system). Any number of
additional elements are allowed – interpretation and meaning of additional
elements is beyond the scope of this specification.

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 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 its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately 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 changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.