Re: [GRASS-user] Searching EPSG database [RESOLVED]

[Jeff McKenna]

On 2021-09-29 8:21 p.m., Rich Shepard wrote:

On Wed, 29 Sep 2021, Rich Shepard wrote:

I registered with epsg.org but when I enter a state's name in the 
search box

and click the 'GO' button nothing changes; displayed is the entire list
starting with Aruba.


I used spatialreferences.org instead. When I enter a state's name in their
search box a list of all projection codes is presented.




Please note that spatialreferences.org is no longer maintained.  If you 
want a fancy search, use https://epsg.io   (but remember, epsg.org has 
the guaranteed search results in terms of searching the actual EPSG 
database source - see my previous message on this)


-jeff


--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Which EPSG code for location default?

[Jeff McKenna]

On 2021-09-23 8:55 a.m., Jeff McKenna wrote:

NAD83 / UTM zone 10N + NAVD88


It could also be that no one yet has submitted this to the EPSG geodetic 
committee, for inclusion (UTM zone 10N with that vertical datum). *hint* 
*maybe you should*  (PS I've submitted several, just use the mindset 
"well someone has to")


So.all of my answers to you are very unhelpful, ha.

But that's all I've got for you now.

-jeff



--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Which EPSG code for location default?

[Jeff McKenna]

Hi Rich,

Taking a look at your output, my brain said "good question", ha.

Usually the key line to look for is the "AUTHORITY:" line, which yours 
lacks.


So the usual next step is to start searching on https://epsg.io for the 
text "UTM zone 10N".


But more recently the official EPSG homepage includes a search tool that 
does a live search on its own database (giving guaranteed 
accurate/uptodate responses):


- goto https://epsg.org
- click the top menu: EPSG Dataset/Text Search
- enter: UTM zone 10N and press "Go"
- gives a response of 12 items

EPSG:26910 does look somewhat similar :)

Hope that gives you some hints... (at least on the official EPSG code 
perspective)


-jeff




--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/




On 2021-09-22 7:49 p.m., Rich Shepard wrote:

Applying gdalsrsinfo to a shapefile's .prj produced these results:

PROJ.4 : +proj=utm +zone=10 +datum=NAD83 +units=m +vunits=m +no_defs

OGC WKT2:2018 :
COMPOUNDCRS["NAD83 / UTM zone 10N + NAVD88 height",
     PROJCRS["NAD83 / UTM zone 10N",
     BASEGEOGCRS["NAD83",
     DATUM["North American Datum 1983",
     ELLIPSOID["GRS 1980",6378137,298.257222101,
     LENGTHUNIT["metre",1]],
     ID["EPSG",6269]],
     PRIMEM["Greenwich",0,
     ANGLEUNIT["Degree",0.0174532925199433]]],
     CONVERSION["UTM zone 10N",
     METHOD["Transverse Mercator",
     ID["EPSG",9807]],
     PARAMETER["Latitude of natural origin",0,
     ANGLEUNIT["Degree",0.0174532925199433],
     ID["EPSG",8801]],
     PARAMETER["Longitude of natural origin",-123,
     ANGLEUNIT["Degree",0.0174532925199433],
     ID["EPSG",8802]],
     PARAMETER["Scale factor at natural origin",0.9996,
     SCALEUNIT["unity",1],
     ID["EPSG",8805]],
     PARAMETER["False easting",50,
     LENGTHUNIT["metre",1],
     ID["EPSG",8806]],
     PARAMETER["False northing",0,
     LENGTHUNIT["metre",1],
     ID["EPSG",8807]],
     ID["EPSG",16010]],
     CS[Cartesian,2],
     AXIS["(E)",east,
     ORDER[1],
     LENGTHUNIT["metre",1,
     ID["EPSG",9001]]],
     AXIS["(N)",north,
     ORDER[2],
     LENGTHUNIT["metre",1,
     ID["EPSG",9001,
     VERTCRS["NAVD88 height",
     VDATUM["North American Vertical Datum 1988"],
     CS[vertical,1],
     AXIS["gravity-related height (H)",up,
     LENGTHUNIT["metre",1,
     ID["EPSG",9001]

The data are the Columbia River and southern Washington state.

It's been a couple of decades since I last dug into proj and I'd appreciate
being pointed to a document that will teach me which of the several EPSG
codes above is the one to which I want to apply to PROJ_INFO in the
PERMANENT mapset.

TIA,

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user



___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Pulling source changes from github

[Jeff McKenna]

Hi Rich,

This is likely due to the default branch name changing to 'main' 
(instead of 'master').  I documented the steps for the MapServer 
community at 
https://github.com/MapServer/MapServer/wiki/Renamed-Default-Branch


But you can likely just issue the following commands in your local machine:

  git branch -m master main
  git fetch origin
  git branch -u origin/main main
  git remote set-head origin -a


(maybe Vashek wrote more details in a previous message here, but this is 
my input, ha)


-jeff




--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/





On 2021-09-15 4:54 p.m., Rich Shepard wrote:

The host for grass source code has changed. When I issue a 'git pull'
request it fails:
$ git pull
Your configuration specifies to merge with the ref 'refs/heads/master'
from the remote, but no such ref was fetched.

What do I need to change here, and where do I change it, to pull changes to
my local installation?

TIA,

Rich


___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] wingrass server is down

[Jeff McKenna]

Thanks Martin, I'm one of your longtime WinGRASS users, and I really 
appreciate the effort you put in to maintain it, and its server host.


Have a nice weekend,

-jeff



On 2020-11-20 10:29 a.m., Martin Landa wrote:

Dear all,

wingrass.fsv.cvut.cz is down (the server died completely). WinGRASS
binaries (including addons) are currently not available.

I will inform you about progress. Martin




--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Selecting EPSG from ogrinfo output; input from command line

[Jeff McKenna]

On 2020-08-16 4:50 p.m., Rich Shepard wrote:

1.) Which EPSG code do I use to create a new location in which to import
this file? And should this be the first step?


This is EPSG:2927   see: http://epsg.io/2927

-jeff




--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/





___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Status of pdal-2.1 support? [RESOLVED]

[Jeff McKenna]

On 2020-05-27 1:34 p.m., Rich Shepard wrote:

On Wed, 27 May 2020, Rich Shepard wrote:


If the issue is in v.in.pdal please let me know and I'll try to fix it.


All issues resolved. I rebuilt and re-installed (in order) proj7, geos,
gdal, libgeotiff, and libspatialite. I think it was either libgeotiff or
libspatialite not being rebuilt that caused make to fail.

Rich


Yes, I am also on the pdal list and it is interesting that everything I 
said here is correct - PDAL does not depend on PROJ, it is GDAL who 
links to PROJ, as well as my earlier warning to focus on GeoTIFF and 
Spatialite libs linking to PROJ.


So it seems I am not as crazy as you think ;)

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/


___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Status of pdal-2.1 support? [UPDATE]

[Jeff McKenna]

On 2020-05-26 9:54 a.m., Rich Shepard wrote:

On Tue, 26 May 2020, Jeff McKenna wrote:

GDAL (and its PROJ support) handles the GDAL spatial referencing 
stuff, so

that's why (I believe) PDAL isn't listed on that page.


jeff,

PDAL is the Point Data Abstraction Library and equivalent to GDAL, the
Geospatial Data Abstraction Library for raster and vector data.



Rich,

All of my messages were/are in regards to PDAL; in fact PROJ is not a 
listed dependency of PDAL - GDAL is however.  That explains why you do 
not see PDAL on the projects page for PROJ6 support.


(I also distribute/compile PDAL for Windows users, through MS4W, so I am 
more than aware of your pain, ha, but on a harder level than unix ;)


-jeff




--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Status of pdal-2.1 support? [UPDATE]

[Jeff McKenna]

On 2020-05-26 9:39 a.m., Rich Shepard wrote:

On Tue, 26 May 2020, Maris Nartiss wrote:

After upgrading to proj-7 you forgot to recompile all libraries 
linking to
proj. If you are running a system with pre-built packages, go bark on 
your

GIS package maintainer.


Māris,

Each time proj, geos, or gdal is upgraded I rebuild the entire stack in 
that

order. So, when I upgraded to proj7 I rebuilt geos-3.8.1-x86_64-1_SBo and
gdal-3.0.4-x86_64-1_SBo. Is there another library dependent on proj?




Not sure in terms of GRASS specifically, but keep an eye open for PROJ 
required in GeoTIFF and Spatialite libs as well.


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/




___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Status of pdal-2.1 support? [UPDATE]

[Jeff McKenna]

On 2020-05-26 8:10 a.m., Jeff McKenna wrote:

On 2020-05-25 6:37 p.m., Rich Shepard wrote:

On Mon, 25 May 2020, Jeff McKenna wrote:


Here's the recorded status for the adoption of PROJ throughout projects:
https://github.com/OSGeo/PROJ/wiki/proj.h-adoption-status


Jeff,

Thanks! If I read this correctly GRASS has adopted proj7 and the 
future but
it's PDAL (which I assume is shown in the list as PDL) that's hanging 
things

up. Sigh.

Stay well,


Hey Rich!

PROJ is actually not a dependency of PDAL.



GDAL (and its PROJ support) handles the GDAL spatial referencing stuff, 
so that's why (I believe) PDAL isn't listed on that page.


-jeff




--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Status of pdal-2.1 support? [UPDATE]

[Jeff McKenna]

On 2020-05-25 6:37 p.m., Rich Shepard wrote:

On Mon, 25 May 2020, Jeff McKenna wrote:


Here's the recorded status for the adoption of PROJ throughout projects:
https://github.com/OSGeo/PROJ/wiki/proj.h-adoption-status


Jeff,

Thanks! If I read this correctly GRASS has adopted proj7 and the future but
it's PDAL (which I assume is shown in the list as PDL) that's hanging 
things

up. Sigh.

Stay well,


Hey Rich!

PROJ is actually not a dependency of PDAL.

Good to chat again with you.

-jeff




--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Status of pdal-2.1 support? [UPDATE]

[Jeff McKenna]

On 2020-05-25 5:29 p.m., Rich Shepard wrote:

On Mon, 25 May 2020, Rich Shepard wrote:


I understand that work's in progress to support pdal-2.1 ...


Mea culpa! It's support for proj 7 that's holding up the build. How's that
coming along?



Here's the recorded status for the adoption of PROJ throughout projects: 
https://github.com/OSGeo/PROJ/wiki/proj.h-adoption-status


-jeff


--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/





___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Wiki page update(s)

[Jeff McKenna]

On 2018-08-15 11:09 AM, Rich Shepard wrote:

On Wed, 15 Aug 2018, Markus Neteler wrote:


Editing requires to have (requested) a Wiki account. Please register
there.


Markus,

   Looking at the main wiki page
 I see neither a link to 
edit a

page nor a place to log in with my osgeo account. Please point me to the
proper places.

TIA,



Hi Rich,

In the top-right corner you should see links for "Log-in / Request account"

Please fill out the request-account page, and then you can also send me 
a direct email to let me know of this, as I can then approve your 
request manually (as we have many spam requests).  Sorry for the hassle.


-jeff



___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] [GRASS-dev] SSL Certificate

[Jeff McKenna]

On 2018-07-28 6:41 AM, Markus Neteler wrote:

On Sat, Jul 28, 2018 at 11:38 AM, Jeff McKenna
 wrote:
...

I hope the new SSL certificate for all of the sites including
grasswiki.osgeo.org was helpful, and worth my mistake.

Again, I am very sorry.

-Jeff McKenna


Wiki, CMS are back online, I checked transifex as well (auto-fetch).

Seems we are back on stage!

Markus




phew!!!

-jeff

___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] SSL Certificate

[Jeff McKenna]

Yes sorry this was me.

I hope the new SSL certificate for all of the sites including 
grasswiki.osgeo.org was helpful, and worth my mistake.


Again, I am very sorry.

-Jeff McKenna



On 2018-07-28 2:22 AM, Markus Neteler wrote:

Hi Huidae, all,
(CC lists)

Huidae Cho mailto:gras...@gmail.com>> schrieb am 
Sa., 28. Juli 2018, 03:20:


Hi Markus,

Not sure if you noticed this. I'm getting an SSL certificate error
when accessing grass.osgeo.org <http://grass.osgeo.org>.


grass.osgeo.org <http://grass.osgeo.org> uses an invalid security
certificate.

The certificate is only valid for the following names:
mapserver.org <http://mapserver.org>, www.mapserver.org
<http://www.mapserver.org>

Error code: SSL_ERROR_BAD_CERT_DOMAIN

Is it just me?

Huidae
-- 
Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP

Open Source GIS Developer, GRASS GIS Development Team


I also realized that yesterday and escalated it to OSGeo-SAC.

In fact, a SAC member had messed the certificate accidentally up and 
fixed it later.


Please report of you find any OSGeo site still causing troubles.

Best
Markus





___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Importing NAIP from WMS?

[Jeff McKenna]

I guess I cheated here and used d.wms (gui) instead of an r.in.wms 
command.  Anyway, I tried :)


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/



On 2017-07-04 10:54 AM, Jeff McKenna wrote:
Followup:  I was able to get the NAIP California WMS service working 
with GRASS, here were my steps:


- installed winGRASS 7.3-dev from 
https://wingrass.fsv.cvut.cz/grass73/x86_64/


- followed steps in the manual to execute a GetCapabilities request:

- in "Console" tab, executed this command:

  r.in.wms -c 
url=https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer? 



- then used the "Add web service layer" menu item in GRASS:

- File/Map display/Add web service layer

- in the "Server" box enter: 
https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer? 
and click "Connect"


- wait for GetCapabilities to be parsed

- you should see a new dialogue window below open, with a layer listed

- click on the layer, select "EPSG:4326" as your source projection 
(assuming you have setup a GRASS location for that projection), select 
"png", and press "Add Layer"


- the California image should appear in your map display

- note that I used another WMS service to load the world continents 
(such as http://demo.mapserver.org/cgi-bin/wms?) and then zoomed into 
California extents that way, so I could see that layer


- should look like: https://pasteboard.co/GznOi0u.png

Hope that helps!  Have a good week (and happy late Canada Day!!)

-jeff





___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Importing NAIP from WMS?

[Jeff McKenna]

Followup:  I was able to get the NAIP California WMS service working 
with GRASS, here were my steps:


- installed winGRASS 7.3-dev from 
https://wingrass.fsv.cvut.cz/grass73/x86_64/


- followed steps in the manual to execute a GetCapabilities request:

   - in "Console" tab, executed this command:

 r.in.wms -c 
url=https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer?


- then used the "Add web service layer" menu item in GRASS:

   - File/Map display/Add web service layer

   - in the "Server" box enter: 
https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer? 
and click "Connect"


   - wait for GetCapabilities to be parsed

   - you should see a new dialogue window below open, with a layer listed

   - click on the layer, select "EPSG:4326" as your source projection 
(assuming you have setup a GRASS location for that projection), select 
"png", and press "Add Layer"


- the California image should appear in your map display

- note that I used another WMS service to load the world continents 
(such as http://demo.mapserver.org/cgi-bin/wms?) and then zoomed into 
California extents that way, so I could see that layer


- should look like: https://pasteboard.co/GznOi0u.png

Hope that helps!  Have a good week (and happy late Canada Day!!)

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/



On 2017-07-04 9:41 AM, Jeff McKenna wrote:

Hi Jeshua,

I haven't tested r.in.wms yet, but I can help you to learn about the WMS 
layers:


- as the r.in.wms manual[1] states, you must always look at the 
capabilities of the WMS service to get the layer names


- a list of NAIP services can be found at 
https://gis.apfo.usda.gov/arcgis/rest/services/NAIP/


- clicking on the NAIP/California service, on the resulting page there 
will be a small "WMS" link in the top left of the page, this is the 
GetCapabilities for that service, click it 
(https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer?request=GetCapabilities=WMS) 



- look for a   parameter in that response.  Unfortunately 
ArcGIS services are awful for metadata, so you can see here that the 
layer is named "0"  (lovely, so very helpful, ha).


- if you want another way to find your WMS layer names, use that service 
in QGIS and click on the "Add WMS layer" button, create a new 
connection, and use this for the URL: 
https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer? 



Hope that helps.

[1] https://grass.osgeo.org/grass73/manuals/r.in.wms.html

-jeff




___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Importing NAIP from WMS?

[Jeff McKenna]

Hi Jeshua,

I haven't tested r.in.wms yet, but I can help you to learn about the WMS 
layers:


- as the r.in.wms manual[1] states, you must always look at the 
capabilities of the WMS service to get the layer names


- a list of NAIP services can be found at 
https://gis.apfo.usda.gov/arcgis/rest/services/NAIP/


- clicking on the NAIP/California service, on the resulting page there 
will be a small "WMS" link in the top left of the page, this is the 
GetCapabilities for that service, click it 
(https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer?request=GetCapabilities=WMS)


- look for a   parameter in that response.  Unfortunately 
ArcGIS services are awful for metadata, so you can see here that the 
layer is named "0"  (lovely, so very helpful, ha).


- if you want another way to find your WMS layer names, use that service 
in QGIS and click on the "Add WMS layer" button, create a new 
connection, and use this for the URL: 
https://gis.apfo.usda.gov/arcgis/services/NAIP/California_2016_60cm/ImageServer/WMSServer?


Hope that helps.

[1] https://grass.osgeo.org/grass73/manuals/r.in.wms.html

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/








[1] https://grass.osgeo.org/grass73/manuals/r.in.wms.html



On 2017-07-03 9:32 PM, Jeshua Lacock wrote:


Greetings,

Is it possible to import NAIP data using the USDA WMS server with r.in.wms?

Instructions how to use their WMS server is here:

https://www.fsa.usda.gov/Assets/USDA-FSA-Public/usdafiles/APFO/2013_apfo_web_service_931.pdf

To download the NAIP for say California, its not clear to me what to specify 
for the layer(s) name(s).

Whatever I have tried I get a message:

"Unable to import pyGRASS: grass_gis.7.2.1 not found.”

I’m not sure if that has anything to do with not being able to get any data to 
download or I just don’t know what I am doing.


Thanks,

Jeshua Lacock
Founder/Engineer
<3DTOPO.com>
GlassPrinted.com



___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] REMINDER: Call for Workshops/Tutorials for FOSS4G2011

[Jeff McKenna]

Hello GRASS community,

Just a quick update that we haven't received any abstracts for GRASS
workshops or tutorials yet, and the deadline is the 30th.  So please
head to the online form to submit: http://2011.foss4g.org/workshops

Also, an important note is that if your workshop submission is not
accepted as a workshop, it will be considered for as a tutorial instead.

-Workshop Committee FOSS4G2011



**
Denver, CO, USA. 14 January 2011. The Free and Open Source Software for
Geospatial (FOSS4G) conference is pleased to announce the Call for
Workshops and Tutorials for the 2011 conference, being held September 12
- 16, 2011, in Denver, CO, USA. FOSS4G is the premier international
conference focused on open source geospatial software. Users and
developers are encouraged to present their latest projects and software
to demonstrate the power of open source geospatial solutions through a
series of workshop sessions and tutorial presentations. Sessions may
cover systems that are solely open source, or a combination of open and
closed source solutions.

Workshops
-

Workshops are 3 hour hands-on experiences with participants following
along with the instructor, working directly with the application under
discussion. All workshop rooms will be equipped a projector, and with
computers for participants to use. Instructors will need to discuss
pre-installation requirements with the Conference Organizing Committee
if required.

Workshops are expected to require considerable effort to create, with
past experience showing that three days of preparation per hour of
presentation are required to produce a high quality workshop.
Additionally you will be expected to develop material for attendees to
take home with them, such as handouts, workbook, CD-ROMs, etc. Due to
the effort involved in producing and presenting a workshop, instructors
will receive a single complimentary registration to the conference for
delivering a workshop.

Tutorials
-

Tutorials are 90 minute sessions during the regular presentations
portion of the conference. Tutorial rooms will not be equipped with
computers. However, presenters may make use of delegate laptops and the
FOSS4G LiveDVD. Preference will be given to hands-on tutorials. Any
hands-on aspects to a tutorial will be the responsibility of the
presenter and needs to be described in the tutorial description.
Presenters making use of the LiveDVD will be expected to contribute to
testing pre-releases to ensure material and software is properly
installed. To discuss your requirements for LiveDVD, please contact the
LiveDVD community: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us

Topics of Interest
--

All submissions will be considered, but particular interest will be
shown in the following topics:

* Practical Introductions to FOSS4G software
* Interoperability / Spatial Data Infrastructure
* Integration between open and closed source solutions
* Free and open geospatial data
* Performance tuning

Application form


Follow this link to submit your proposals:
http://2011.foss4g.org/workshops Please add a 300 word abstract, in
plain text format (pasting a text with style markup could make the
process fail). The deadline for workshop / tutorial submissions is
January 30.

Communication
-

All workshop and tutorial applicants are encouraged to use the workshop
mailing list to ask questions to the workshop committee:
http://lists.osgeo.org/mailman/listinfo/conference-workshops

General FOSS4G 2011 questions and discussion should occur on the main
conference mailing list: http://lists.osgeo.org/mailman/listinfo/foss4g2011



___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Fwd: [OSGeo-Discuss] FOSS4G 2009: One week extension to Workshops and Tutorial abstract submissions

[Jeff McKenna]

I would also mention that there still has not been any GRASS submissions 
(and GRASS should obviously be well represented here).  The deadline for 
abstracts is March 9th (http://www.osgeo.org/foss4g2009/press_release_6).


-jeff



--
Jeff McKenna
FOSS4G Consulting and Training Services
http://www.gatewaygeomatics.com/



Markus Neteler wrote:

-- Forwarded message --
From: Cameron Shorter cameron.shor...@gmail.com
Date: Sun, Mar 1, 2009 at 11:50 PM
Subject: [OSGeo-Discuss] FOSS4G 2009: One week extension to Workshops
and Tutorial abstract submissions
To: OSGeo Discussions disc...@lists.osgeo.org


Sydney, Australia. 2 March 2009.

In response to requests from presenters, the deadline for the FOSS4G
2009 workshop and tutorial abstract submissions has been extended by
one week, to Monday 9 March 2009. If you are considering submitting a
workshop, please notify your intent by emailing the Workshop/Tutorial
coordinator, Mark Leslie m a r k . l e s l i e AT l i s a s o f t . c
o m


  About FOSS4G

FOSS4G, held 20-23 October 2009 in Sydney, Australia, is the
international gathering of tribes for open source geospatial
communities. The theme for the FOSS4G 2009 conference will be User
Driven. Users and developers are encouraged present their latest
projects and software to demonstrate the power of Open Source for
system integration through a series of workshop sessions and tutorial
presentations. Session participants should expect to see presentations
on both geospatial open source and propriety software integration
along with pure open source solutions.


  Workshops

Workshops are expected to be a hands-on experience with participants
following along with the instructor, working directly with the
application under discussion. All workshop rooms will be equipped with
computers (two students sharing one system) to support this vision.
Workshop computers will pre-installed with a basic image containing
standard packages running in a Windows XP environment. A projector
will be provided for each computer room for use within a workshop.
Instructors will need to discuss pre-installation requirements with
the Conference Organising Committee if required.

Workshops are expected to require considerable effort to create, with
past experience showing that three days of preparation per hour of
presentation are required to produce a high quality workshop.
Additionally you will be expected to develop material for attendees to
take home with them, such as handouts, workbook, CD-ROMs etc. Due to
the effort involved in producing and presenting a workshop,
instructors will receive a single complementary registration to the
conference for delivering a workshop.

All workshop submissions will be considered, but particular interest
will be shown in the following topics:

  * Practical Introduction to 
  * Integrating Open Source
  * Spatial Data Privacy and Security


  Tutorials

Tutorial rooms will not be equipped with computers, however presenters
may optionally make use of delegate laptops and the FOSS4G LiveDVD.

At least 80% of delegates are expected to be carrying a laptop and
FOSS4G LiveDVDs will be given to all delegates.

Preference will be given to hands-on tutorials.

Any hands-on aspects to a tutorial will be the responsibility of the
presenter and needs to be described in the tutorial description.
Presenters making use of the Live DVD or Climate Change Integration
Plugfest (CCIP) will be expected to contribute to testing pre-releases
to ensure material and software is properly installed. To discuss your
requirements for LiveDVD, please contact the organising committee:
http://2009.foss4g.org/contacts/.

All tutorial submissions will be considered, but particular interest
will be shown in the following topics:

  * Practical introductions
  * Interoperability
  * Spatial data accuracy
  * Spatial data privacy
  * Spatial data security
  * System implementation
  * Data migration



Submission instructions and templates are available at
http://2009.foss4g.org/workshops/ and
http://2009.foss4g.org/tutorials/.

The deadline for workshop / tutorial submissions is March 2, 2009.


  FOSS4G 2009 Highlights

*The Climate Change Integration Plugfest (CCIP)*: FOSS4G will launch
the OGC's Climate Change Integration Plugfest (CCIP), which
demonstrates standards based interoperability between Open Source and
Proprietary geospatial applications. It consists of a server with
multiple virtual machines, each installed with geospatial applications
offering standards based web services. All web services will
demonstrate a common dataset, and will be accessed by a range of
geospatial client applications installed on client computers.
http://external.opengis.org/twiki_public/bin/view/ClimateChallenge2009/WebHome

Presenters are encouraged (but not mandated) to make use of scenarios
and on-site data from the Climate Change Integration Plugfest

Re: [GRASS-user] how can import ecw's in grass databse

[Jeff McKenna]

Regarding ECW and GDAL on windows, a thread on that recently occurred  
on the FWTools list: http://lists.maptools.org/pipermail/fwtools/2008-April/001213.html


-jeff




On 5-May-08, at 2:17 AM, [EMAIL PROTECTED] wrote:


Hi List,

I need to import ecw Rasters in my grass database,
but it won't work. (gdal not supported ecw in my grass 6.0 version)

What will the easiest way to do this?
Must I compile gdal with ecw support ot is there another way?

geog


___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user