Re: [mapserver-users] Make PROJECTION mandatory?
Hi, My point is that defaults may be fine as long as everything goes right. But when you need to find out what goes wrong it is much easier if projections are explicitly set. Especially if you are at your customers site or you are trying to give help through the mailing list when the mapfile and the errors are written by somebody else. Jeff is obviously looking the world from the same perspective as I. But as an admin or almost plain orthophoto WMS I somehow thought that there are only raster and vector layers and setting a projection that is matching the data cannot make any harm. But Steve was worried about legends, does it mean that legends and scalebars etc. are somehow converted into layers which are also receiving projection as a heritage from somewhere? Documentation does not mention anything about projections with legends https://mapserver.org/mapfile/legend.html. Certainly I did not mean that users should be required to give fake projections for them. There seems to be also other kind of artificial layers like charts, contours, and heatmaps. I am not sure if they have any native projection or not. -Jukka Rahkonen- -Alkuperäinen viesti- Lähettäjä: mapserver-users Puolesta Mark Volz Lähetetty: maanantai 27. huhtikuuta 2020 23.04 Vastaanottaja: mapserver-users@lists.osgeo.org Aihe: Re: [mapserver-users] Make PROJECTION mandatory? Hello, Just to add in my two cents to this. 1) I don’t think we should have to specify a projection at the and level if they are the same as that would seem redundant to me. However, it should be allowed if a user wants to specify the projection at both levels. 2) Perhaps it would be good form (but not required) to allow "PROJECTION NONE" to explicitly specify to any client that the scalebar, legend, static map, etc is not intended to be projected onto a particular part of the earth. Thanks! Sincerely, Mark Volz, GISP -Original Message- From: mapserver-users On Behalf Of mapserver-users-requ...@lists.osgeo.org Sent: Monday, April 27, 2020 2:28 PM To: mapserver-users@lists.osgeo.org Subject: mapserver-users Digest, Vol 147, Issue 28 SWHHS/LYON/LINCOLN COUNTY SECURITY NOTICE: This email originated from an external sender. Exercise caution before clicking on any links or attachments and consider whether you know the sender. For more information please contact IT support. Send mapserver-users mailing list submissions to mapserver-users@lists.osgeo.org To subscribe or unsubscribe via the World Wide Web, visit https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.osgeo.org%2fmailman%2flistinfo%2fmapserver-users=E,1,fH9yaFFHC2_hvkuwIMW4WrKaU9eZJWHW-VBcTfuFNHtxAKC1CQ1YicwS_o8K66nDz-TFd_kUsnyr34KSeIFWFFqs6Om-QpVBRYIz7MhLrI8qRYKTuY-bonA-VgwP=1 or, via email, send a message with subject or body 'help' to mapserver-users-requ...@lists.osgeo.org You can reach the person managing the list at mapserver-users-ow...@lists.osgeo.org When replying, please edit your Subject line so it is more specific than "Re: Contents of mapserver-users digest..." Today's Topics: 1. Re: Make PROJECTION mandatory? (Basques, Bob (CI-StPaul)) -- Message: 1 Date: Mon, 27 Apr 2020 19:16:52 + From: "Basques, Bob (CI-StPaul)" To: Steve Lime , Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Message-ID: Content-Type: text/plain; charset="utf-8" All, I can second Steve’s idea. We were using Mapserver for years before we needed to pay attention to projections, because all of our data wasin our local coordinate system. We now work projection across all map services for all layers, either by explicitly stating the projection or having it scripted at the web server call. Some cases it won’t matter, if ever, and others it will be instrumental in getting a site working with many and varied projected datasets being combined. I would agree that it should be a topic more prominently displayed/noted in the documentation. Bobb From: mapserver-users On Behalf Of Steve Lime Sent: Monday, April 27, 2020 1:21 PM To: Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Think Before You Click: This email originated outside our organization. I would prefer to pursue as a documentation/communication exercise first. It's not that I don't agree that PROJECTION blocks are generally recommended but making them required and introducing artificial projections to deal with cases when projections aren't used (embedded legends, scale bars and other static map elements) will touch a lot of code. It's also a major breaking change that would potentially break a large percentage of mapfiles going forward. --Steve On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna mailto:jmcke...@ga
Re: [mapserver-users] Make PROJECTION mandatory?
Very subtle Jeff. :c) I was thinking about a "Gotcha" page in the documentation. There a few of these same sort of MapServer gothchas that could be included up high in the docs table of contents. Bobb -Original Message- From: mapserver-users On Behalf Of Jeff McKenna Sent: Monday, April 27, 2020 3:30 PM To: mapserver-users@lists.osgeo.org Subject: Re: [mapserver-users] Make PROJECTION mandatory? Think Before You Click: This email originated outside our organization. I do look forward to approving pull requests from all of the people talking now of doc updates ;) I really look forward to this. :) -jeff -- Jeff McKenna MapServer Consulting and Training Services https://gatewaygeo.com/ On 2020-04-27 5:04 p.m., Mark Volz wrote: > Hello, > Just to add in my two cents to this. > > 1) I don’t think we should have to specify a projection at the and > level if they are the same as that would seem redundant to me. > However, it should be allowed if a user wants to specify the projection at > both levels. > 2) Perhaps it would be good form (but not required) to allow "PROJECTION > NONE" to explicitly specify to any client that the scalebar, legend, static > map, etc is not intended to be projected onto a particular part of the earth. > > Thanks! > Sincerely, > Mark Volz, GISP > > -Original Message- > From: mapserver-users On > Behalf Of mapserver-users-requ...@lists.osgeo.org > Sent: Monday, April 27, 2020 2:28 PM > To: mapserver-users@lists.osgeo.org > Subject: mapserver-users Digest, Vol 147, Issue 28 > > SWHHS/LYON/LINCOLN COUNTY SECURITY NOTICE: > This email originated from an external sender. Exercise caution before > clicking on any links or attachments and consider whether you know the > sender. For more information please contact IT support. > > > Send mapserver-users mailing list submissions to > mapserver-users@lists.osgeo.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.osgeo.org%2f > mailman%2flistinfo%2fmapserver-users=E,1,fH9yaFFHC2_hvkuwIMW4WrKaU9e > ZJWHW-VBcTfuFNHtxAKC1CQ1YicwS_o8K66nDz-TFd_kUsnyr34KSeIFWFFqs6Om-QpVBR > YIz7MhLrI8qRYKTuY-bonA-VgwP=1 > or, via email, send a message with subject or body 'help' to > mapserver-users-requ...@lists.osgeo.org > > You can reach the person managing the list at > mapserver-users-ow...@lists.osgeo.org > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of mapserver-users digest..." > > > Today's Topics: > > 1. Re: Make PROJECTION mandatory? (Basques, Bob (CI-StPaul)) > -- > > Message: 1 > Date: Mon, 27 Apr 2020 19:16:52 + > From: "Basques, Bob (CI-StPaul)" > To: Steve Lime , Jeff McKenna > > Cc: Mapserver > Subject: Re: [mapserver-users] Make PROJECTION mandatory? > Message-ID: > > tlook.com> > > Content-Type: text/plain; charset="utf-8" > > All, > > I can second Steve’s idea. We were using Mapserver for years before we > needed to pay attention to projections, because all of our data wasin our > local coordinate system. We now work projection across all map services for > all layers, either by explicitly stating the projection or having it scripted > at the web server call. Some cases it won’t matter, if ever, and others it > will be instrumental in getting a site working with many and varied projected > datasets being combined. > > I would agree that it should be a topic more prominently displayed/noted in > the documentation. > > Bobb > > > From: mapserver-users On > Behalf Of Steve Lime > Sent: Monday, April 27, 2020 1:21 PM > To: Jeff McKenna > Cc: Mapserver > Subject: Re: [mapserver-users] Make PROJECTION mandatory? > > Think Before You Click: This email originated outside our organization. > > I would prefer to pursue as a documentation/communication exercise first. > It's not that I don't agree that PROJECTION blocks are generally recommended > but making them required and introducing artificial projections to deal with > cases when projections aren't used (embedded legends, scale bars and other > static map elements) will touch a lot of code. It's also a major breaking > change that would potentially break a large percentage of mapfiles going > forward. > > --Steve > > On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna > mailto:jmcke...@gatewaygeomatics.com>> wrote: > Hi Jukka, > > I personally consider defining PROJECTION b
Re: [mapserver-users] Make PROJECTION mandatory?
I do look forward to approving pull requests from all of the people talking now of doc updates ;) I really look forward to this. :) -jeff -- Jeff McKenna MapServer Consulting and Training Services https://gatewaygeo.com/ On 2020-04-27 5:04 p.m., Mark Volz wrote: Hello, Just to add in my two cents to this. 1) I don’t think we should have to specify a projection at the and level if they are the same as that would seem redundant to me. However, it should be allowed if a user wants to specify the projection at both levels. 2) Perhaps it would be good form (but not required) to allow "PROJECTION NONE" to explicitly specify to any client that the scalebar, legend, static map, etc is not intended to be projected onto a particular part of the earth. Thanks! Sincerely, Mark Volz, GISP -Original Message- From: mapserver-users On Behalf Of mapserver-users-requ...@lists.osgeo.org Sent: Monday, April 27, 2020 2:28 PM To: mapserver-users@lists.osgeo.org Subject: mapserver-users Digest, Vol 147, Issue 28 SWHHS/LYON/LINCOLN COUNTY SECURITY NOTICE: This email originated from an external sender. Exercise caution before clicking on any links or attachments and consider whether you know the sender. For more information please contact IT support. Send mapserver-users mailing list submissions to mapserver-users@lists.osgeo.org To subscribe or unsubscribe via the World Wide Web, visit https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.osgeo.org%2fmailman%2flistinfo%2fmapserver-users=E,1,fH9yaFFHC2_hvkuwIMW4WrKaU9eZJWHW-VBcTfuFNHtxAKC1CQ1YicwS_o8K66nDz-TFd_kUsnyr34KSeIFWFFqs6Om-QpVBRYIz7MhLrI8qRYKTuY-bonA-VgwP=1 or, via email, send a message with subject or body 'help' to mapserver-users-requ...@lists.osgeo.org You can reach the person managing the list at mapserver-users-ow...@lists.osgeo.org When replying, please edit your Subject line so it is more specific than "Re: Contents of mapserver-users digest..." Today's Topics: 1. Re: Make PROJECTION mandatory? (Basques, Bob (CI-StPaul)) -- Message: 1 Date: Mon, 27 Apr 2020 19:16:52 + From: "Basques, Bob (CI-StPaul)" To: Steve Lime , Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Message-ID: Content-Type: text/plain; charset="utf-8" All, I can second Steve’s idea. We were using Mapserver for years before we needed to pay attention to projections, because all of our data wasin our local coordinate system. We now work projection across all map services for all layers, either by explicitly stating the projection or having it scripted at the web server call. Some cases it won’t matter, if ever, and others it will be instrumental in getting a site working with many and varied projected datasets being combined. I would agree that it should be a topic more prominently displayed/noted in the documentation. Bobb From: mapserver-users On Behalf Of Steve Lime Sent: Monday, April 27, 2020 1:21 PM To: Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Think Before You Click: This email originated outside our organization. I would prefer to pursue as a documentation/communication exercise first. It's not that I don't agree that PROJECTION blocks are generally recommended but making them required and introducing artificial projections to deal with cases when projections aren't used (embedded legends, scale bars and other static map elements) will touch a lot of code. It's also a major breaking change that would potentially break a large percentage of mapfiles going forward. --Steve On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna mailto:jmcke...@gatewaygeomatics.com>> wrote: Hi Jukka, I personally consider defining PROJECTION blocks at the MAP level and all LAYERs mandatory, in my day-to-day work, for each and every mapfile. If you do not specify all of these, MapServer makes assumptions and you are just asking for trouble downstream through WMS clients etc. (your users) I also do not rely on any PROJECTION AUTO magic either, for my paying clients. These are all nice tricks but in critical production environments I stay away from them; instead, find the source projection, and define the MAP projection block and all LAYER projection blocks. I'm not sure this answers your questions, but this was my 'gut reaction' to your message. I believe we have the same thinking here. -jeff -- Jeff McKenna MapServer Consulting and Training Services https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fgatewaygeo.com%2f=E,1,uRKu6N_CiiNLLVVq0e47_QXUkZM4g9vqte-aBcbYyDH1b7WnS1Ln_b1a9kqHV0iwGwOUs3KazTLN-kMthOESPP3PB65XPBsYDNo99uct63RwastB0y4d0JpRk50,=1 On 2020-04-27 10:36 a.m., Rahkonen Jukka (MML) wrote: Hi, Recent Mapserver buids requi
Re: [mapserver-users] Make PROJECTION mandatory?
Hello, Just to add in my two cents to this. 1) I don’t think we should have to specify a projection at the and level if they are the same as that would seem redundant to me. However, it should be allowed if a user wants to specify the projection at both levels. 2) Perhaps it would be good form (but not required) to allow "PROJECTION NONE" to explicitly specify to any client that the scalebar, legend, static map, etc is not intended to be projected onto a particular part of the earth. Thanks! Sincerely, Mark Volz, GISP -Original Message- From: mapserver-users On Behalf Of mapserver-users-requ...@lists.osgeo.org Sent: Monday, April 27, 2020 2:28 PM To: mapserver-users@lists.osgeo.org Subject: mapserver-users Digest, Vol 147, Issue 28 SWHHS/LYON/LINCOLN COUNTY SECURITY NOTICE: This email originated from an external sender. Exercise caution before clicking on any links or attachments and consider whether you know the sender. For more information please contact IT support. Send mapserver-users mailing list submissions to mapserver-users@lists.osgeo.org To subscribe or unsubscribe via the World Wide Web, visit https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.osgeo.org%2fmailman%2flistinfo%2fmapserver-users=E,1,fH9yaFFHC2_hvkuwIMW4WrKaU9eZJWHW-VBcTfuFNHtxAKC1CQ1YicwS_o8K66nDz-TFd_kUsnyr34KSeIFWFFqs6Om-QpVBRYIz7MhLrI8qRYKTuY-bonA-VgwP=1 or, via email, send a message with subject or body 'help' to mapserver-users-requ...@lists.osgeo.org You can reach the person managing the list at mapserver-users-ow...@lists.osgeo.org When replying, please edit your Subject line so it is more specific than "Re: Contents of mapserver-users digest..." Today's Topics: 1. Re: Make PROJECTION mandatory? (Basques, Bob (CI-StPaul)) -- Message: 1 Date: Mon, 27 Apr 2020 19:16:52 + From: "Basques, Bob (CI-StPaul)" To: Steve Lime , Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Message-ID: Content-Type: text/plain; charset="utf-8" All, I can second Steve’s idea. We were using Mapserver for years before we needed to pay attention to projections, because all of our data wasin our local coordinate system. We now work projection across all map services for all layers, either by explicitly stating the projection or having it scripted at the web server call. Some cases it won’t matter, if ever, and others it will be instrumental in getting a site working with many and varied projected datasets being combined. I would agree that it should be a topic more prominently displayed/noted in the documentation. Bobb From: mapserver-users On Behalf Of Steve Lime Sent: Monday, April 27, 2020 1:21 PM To: Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Think Before You Click: This email originated outside our organization. I would prefer to pursue as a documentation/communication exercise first. It's not that I don't agree that PROJECTION blocks are generally recommended but making them required and introducing artificial projections to deal with cases when projections aren't used (embedded legends, scale bars and other static map elements) will touch a lot of code. It's also a major breaking change that would potentially break a large percentage of mapfiles going forward. --Steve On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna mailto:jmcke...@gatewaygeomatics.com>> wrote: Hi Jukka, I personally consider defining PROJECTION blocks at the MAP level and all LAYERs mandatory, in my day-to-day work, for each and every mapfile. If you do not specify all of these, MapServer makes assumptions and you are just asking for trouble downstream through WMS clients etc. (your users) I also do not rely on any PROJECTION AUTO magic either, for my paying clients. These are all nice tricks but in critical production environments I stay away from them; instead, find the source projection, and define the MAP projection block and all LAYER projection blocks. I'm not sure this answers your questions, but this was my 'gut reaction' to your message. I believe we have the same thinking here. -jeff -- Jeff McKenna MapServer Consulting and Training Services https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fgatewaygeo.com%2f=E,1,uRKu6N_CiiNLLVVq0e47_QXUkZM4g9vqte-aBcbYyDH1b7WnS1Ln_b1a9kqHV0iwGwOUs3KazTLN-kMthOESPP3PB65XPBsYDNo99uct63RwastB0y4d0JpRk50,=1 On 2020-04-27 10:36 a.m., Rahkonen Jukka (MML) wrote: > Hi, > > Recent Mapserver buids require PROJ and GDAL > https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html. That > means that every Mapserver can support PROJECTION blocks both at the > MAP level and within LAYER. And because there are no more builds > without Proj suppo
Re: [mapserver-users] Make PROJECTION mandatory?
All, I can second Steve’s idea. We were using Mapserver for years before we needed to pay attention to projections, because all of our data wasin our local coordinate system. We now work projection across all map services for all layers, either by explicitly stating the projection or having it scripted at the web server call. Some cases it won’t matter, if ever, and others it will be instrumental in getting a site working with many and varied projected datasets being combined. I would agree that it should be a topic more prominently displayed/noted in the documentation. Bobb From: mapserver-users On Behalf Of Steve Lime Sent: Monday, April 27, 2020 1:21 PM To: Jeff McKenna Cc: Mapserver Subject: Re: [mapserver-users] Make PROJECTION mandatory? Think Before You Click: This email originated outside our organization. I would prefer to pursue as a documentation/communication exercise first. It's not that I don't agree that PROJECTION blocks are generally recommended but making them required and introducing artificial projections to deal with cases when projections aren't used (embedded legends, scale bars and other static map elements) will touch a lot of code. It's also a major breaking change that would potentially break a large percentage of mapfiles going forward. --Steve On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna mailto:jmcke...@gatewaygeomatics.com>> wrote: Hi Jukka, I personally consider defining PROJECTION blocks at the MAP level and all LAYERs mandatory, in my day-to-day work, for each and every mapfile. If you do not specify all of these, MapServer makes assumptions and you are just asking for trouble downstream through WMS clients etc. (your users) I also do not rely on any PROJECTION AUTO magic either, for my paying clients. These are all nice tricks but in critical production environments I stay away from them; instead, find the source projection, and define the MAP projection block and all LAYER projection blocks. I'm not sure this answers your questions, but this was my 'gut reaction' to your message. I believe we have the same thinking here. -jeff -- Jeff McKenna MapServer Consulting and Training Services https://gatewaygeo.com/ On 2020-04-27 10:36 a.m., Rahkonen Jukka (MML) wrote: > Hi, > > Recent Mapserver buids require PROJ and GDAL > https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html. That > means that every Mapserver can support PROJECTION blocks both at the MAP > level and within LAYER. And because there are no more builds without > Proj support there is no real need for writing mapfiles without > PROJECTION blocks. Therefore I suggest that such mapfiles should be > considered invalid in the future. If it is for some reason too strict > requirement, what if we at least edit the documentation > https://mapserver.org/mapfile/projection.html so that it really > encourages users to write the PROJECTION blocks. GetCapabilities could > also show something like > > > Having layers without PROJECTION saves users from writing this much text: > > “PROJECTION "init=epsg:3857" END > > but when the user meets any problem with accessing data or rendering the > first thing to check is the projection. In the mailing list it means one > more question-answer round before getting closer to the real problem – > if the problem was not in the projection, as it very often is. > > If source data are in local coordinate system it would be better to > define also that explicitly with a special keyword like PROJECTION “LOCAL”. > > Would other user consider making projection compulsory rather as an > improvement or inconvenience? > > -Jukka Rahkonen- > > > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org> > https://lists.osgeo.org/mailman/listinfo/mapserver-users > ___ mapserver-users mailing list mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org> https://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Make PROJECTION mandatory?
I would prefer to pursue as a documentation/communication exercise first. It's not that I don't agree that PROJECTION blocks are generally recommended but making them required and introducing artificial projections to deal with cases when projections aren't used (embedded legends, scale bars and other static map elements) will touch a lot of code. It's also a major breaking change that would potentially break a large percentage of mapfiles going forward. --Steve On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna wrote: > Hi Jukka, > > I personally consider defining PROJECTION blocks at the MAP level and > all LAYERs mandatory, in my day-to-day work, for each and every mapfile. > If you do not specify all of these, MapServer makes assumptions and > you are just asking for trouble downstream through WMS clients etc. > (your users) > > I also do not rely on any PROJECTION AUTO magic either, for my paying > clients. > > These are all nice tricks but in critical production environments I stay > away from them; instead, find the source projection, and define the MAP > projection block and all LAYER projection blocks. > > I'm not sure this answers your questions, but this was my 'gut reaction' > to your message. I believe we have the same thinking here. > > -jeff > > > > -- > Jeff McKenna > MapServer Consulting and Training Services > https://gatewaygeo.com/ > > > > On 2020-04-27 10:36 a.m., Rahkonen Jukka (MML) wrote: > > Hi, > > > > Recent Mapserver buids require PROJ and GDAL > > https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html. That > > means that every Mapserver can support PROJECTION blocks both at the MAP > > level and within LAYER. And because there are no more builds without > > Proj support there is no real need for writing mapfiles without > > PROJECTION blocks. Therefore I suggest that such mapfiles should be > > considered invalid in the future. If it is for some reason too strict > > requirement, what if we at least edit the documentation > > https://mapserver.org/mapfile/projection.html so that it really > > encourages users to write the PROJECTION blocks. GetCapabilities could > > also show something like > > > > > > Having layers without PROJECTION saves users from writing this much text: > > > > “PROJECTION "init=epsg:3857" END > > > > but when the user meets any problem with accessing data or rendering the > > first thing to check is the projection. In the mailing list it means one > > more question-answer round before getting closer to the real problem – > > if the problem was not in the projection, as it very often is. > > > > If source data are in local coordinate system it would be better to > > define also that explicitly with a special keyword like PROJECTION > “LOCAL”. > > > > Would other user consider making projection compulsory rather as an > > improvement or inconvenience? > > > > -Jukka Rahkonen- > > > > > > ___ > > mapserver-users mailing list > > mapserver-users@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/mapserver-users > > > > > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Make PROJECTION mandatory?
Hi Jukka, I personally consider defining PROJECTION blocks at the MAP level and all LAYERs mandatory, in my day-to-day work, for each and every mapfile. If you do not specify all of these, MapServer makes assumptions and you are just asking for trouble downstream through WMS clients etc. (your users) I also do not rely on any PROJECTION AUTO magic either, for my paying clients. These are all nice tricks but in critical production environments I stay away from them; instead, find the source projection, and define the MAP projection block and all LAYER projection blocks. I'm not sure this answers your questions, but this was my 'gut reaction' to your message. I believe we have the same thinking here. -jeff -- Jeff McKenna MapServer Consulting and Training Services https://gatewaygeo.com/ On 2020-04-27 10:36 a.m., Rahkonen Jukka (MML) wrote: Hi, Recent Mapserver buids require PROJ and GDAL https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html. That means that every Mapserver can support PROJECTION blocks both at the MAP level and within LAYER. And because there are no more builds without Proj support there is no real need for writing mapfiles without PROJECTION blocks. Therefore I suggest that such mapfiles should be considered invalid in the future. If it is for some reason too strict requirement, what if we at least edit the documentation https://mapserver.org/mapfile/projection.html so that it really encourages users to write the PROJECTION blocks. GetCapabilities could also show something like Having layers without PROJECTION saves users from writing this much text: “PROJECTION "init=epsg:3857" END but when the user meets any problem with accessing data or rendering the first thing to check is the projection. In the mailing list it means one more question-answer round before getting closer to the real problem – if the problem was not in the projection, as it very often is. If source data are in local coordinate system it would be better to define also that explicitly with a special keyword like PROJECTION “LOCAL”. Would other user consider making projection compulsory rather as an improvement or inconvenience? -Jukka Rahkonen- ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Make PROJECTION mandatory?
Hi, Recent Mapserver buids require PROJ and GDAL https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html. That means that every Mapserver can support PROJECTION blocks both at the MAP level and within LAYER. And because there are no more builds without Proj support there is no real need for writing mapfiles without PROJECTION blocks. Therefore I suggest that such mapfiles should be considered invalid in the future. If it is for some reason too strict requirement, what if we at least edit the documentation https://mapserver.org/mapfile/projection.html so that it really encourages users to write the PROJECTION blocks. GetCapabilities could also show something like Having layers without PROJECTION saves users from writing this much text: "PROJECTION "init=epsg:3857" END but when the user meets any problem with accessing data or rendering the first thing to check is the projection. In the mailing list it means one more question-answer round before getting closer to the real problem - if the problem was not in the projection, as it very often is. If source data are in local coordinate system it would be better to define also that explicitly with a special keyword like PROJECTION "LOCAL". Would other user consider making projection compulsory rather as an improvement or inconvenience? -Jukka Rahkonen- ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
