WhereCampPDX Keynote

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    ESRI can’t open may of the data sharing standards that are becoming prevalent on the GeoWeb such as SpatiaLite, Atom and KML.

    Standards organizations
    “The ESRI Standard”

    Standards organizations are based on consensus.
    They are slow to adjust to changes in the marketplace.
    Follow don’t lead.
    GeoJSON, GeoRSS, KML, SpatiaLite are all examples

    Shapefiles are interop friendly right?

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    You start with the 3 amigos
    Add on some projection info and some metadata
    Then throw on some crazy ESRI index stuff that you may need

    So you zip up the shapefile....

    So you zip up the shapefile....

    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used

    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used

    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used

    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used

    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used

    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used

    Shapefiles are interop friendly right?

    The elephant in the room

    To access FGDB, you need ArcObjects

    Which besides licensing, you need to work with this

    We need an open spatial database

    SQLite
    If it is good enough for these guys

    SQLite
    If it is good enough for these guys

    SQLite
    If it is good enough for these guys

    SQLite
    If it is good enough for these guys

    SQLite
    If it is good enough for these guys

    It is good enough for this guy

    PostGIS and SQL Server 2008 support OGC SF SQL as well

    PostGIS and SQL Server 2008 support OGC SF SQL as well

    PostGIS and SQL Server 2008 support OGC SF SQL as well

    PostGIS and SQL Server 2008 support OGC SF SQL as well

    Community needs to drive new GIS standards.

    GeoJSON, GeoRSS are perfect examples. ESRI supports them.

    Community needs to drive new GIS standards.

    GeoJSON, GeoRSS are perfect examples. ESRI supports them.

    ESRI created their layer package just to solve this problem.
    Zip file (like KMZ)
    FGDB + ESRI Layer Symbology
    ESRI handler to automatically unzip and add to ArcMap

    ESRI created their layer package just to solve this problem.
    Zip file (like KMZ)
    FGDB + ESRI Layer Symbology
    ESRI handler to automatically unzip and add to ArcMap

    Styled Layer Descriptor/Symbology Encoding

    Styled Layer Descriptor/Symbology Encoding

    Styled Layer Descriptor/Symbology Encoding

    All community driven standards.
    No OGC
    Proprietary GIS support

    There are three types of spatial data

    There are three types of spatial data

    There are three types of spatial data

    How do you make sure that people can find your data when they need it most?

    People will pay for quality data when it is easy to do so.
    So much information is locked up behind doors because there is no way for people to monezite it.
    Give RSP Architects example of design studies

    The key takeaway from this is that the community will build maps on their own, even if you provide them.
    What you need to do is offer up your data in consumable formats such as GeoRSS, GeoJSON, KML, SpatiaLite so that the community can incorporate your data into these projects.

    The key takeaway from this is that the community will build maps on their own, even if you provide them.
    What you need to do is offer up your data in consumable formats such as GeoRSS, GeoJSON, KML, SpatiaLite so that the community can incorporate your data into these projects.

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    How does one share a huge spatial database?
    Talk about sharing GeoTIFF and MrSID

    Lets take one of the more popular vector GIS datasets - TIGER
    It is bigger than a small Honda Civic: 125 GB

    Lets take one of the more popular vector GIS datasets - TIGER
    It is bigger than a small Honda Civic: 125 GB

    Lets take one of the more popular vector GIS datasets - TIGER
    It is bigger than a small Honda Civic: 125 GB

    Lets take one of the more popular vector GIS datasets - TIGER
    It is bigger than a small Honda Civic: 125 GB

    Lets take one of the more popular vector GIS datasets - TIGER
    It is bigger than a small Honda Civic: 125 GB

    Lets take one of the more popular vector GIS datasets - TIGER
    It is bigger than a small Honda Civic: 125 GB

    Downloading TIGER is a huge PITA

    You can get down to the county, but sometimes that is too much data.
    San Bernardino County in California is larger than Massachusetts, Connecticut, Rhode Island, and Delaware combined.
    LA County would be a member of the G20.

    You have to download each county at a time which takes a long time.
    You have to download each county in each state!

    Truly open data formats allow users freedom of using the best software packages to get their work done.

    I’m looking at you FGDB

    We are seeing better data catalogs with generally open spatial data formats.
    They are still tied back into the old ways of sharing (FTP, Whole File Downloads)

    We are seeing better data catalogs with generally open spatial data formats.
    They are still tied back into the old ways of sharing (FTP, Whole File Downloads)

    We are seeing better data catalogs with generally open spatial data formats.
    They are still tied back into the old ways of sharing (FTP, Whole File Downloads)

    Archiving geo data is as important as sharing.

    American had fallen in love with Dharma and Greg

    Needless to say the project was a critical success.

    The project was stored in my personal data warehouse (a cd in the bottom of my drawer)

    My old computer with VB5, FoxPro and MapObjects 1.2 has been recycled

    Favorites, Groups & Events

    WhereCampPDX Keynote - Presentation Transcript

    1. Data Interoperability on the GeoWeb James Fee Evangelist
    2. If Sharing is Easy... http://www.flickr.com/photos/13586721@N05/3122021735/
    3. Why is it so hard to share spatial data?
    4. What about spatial data standards?
    5. Community Driven Standards
    6. Just give me a shapefile
    7. portland.shp portland.shx portland.dbf
    8. portland.shp portland.shx portland.dbf portland.prj portland.shp.xml
    9. portland.cpg portland.shp portland.atx portland.sbx portland.shx portland.sbn portland.dbf portland.ain portland.aih portland.prj portland.mxs portland.ixs portland.shp.xml
    10. portland.cpg portland.shp portland.atx portland.sbx portland.shx portland.sbn portland.dbf portland.ain portland.aih portland.prj portland.mxs portland.ixs portland.shp.xml
    11. Can We Come Up With a Standard?
    12. What would work?
    13. What would work? open database
    14. What would work? open database open symbology
    15. What would work? open database open symbology OGC support
    16. What would work? open database open symbology OGC support platform support
    17. ESRI’s File Geodatabase
    18. ESRI’s File Geodatabase
    19. So just give me a File Geodatabase
    20. So we need an open spatial database format
    21. I really want to get me some of that!
    22. ‣ All the benefits of Shapefiles ‣ Open ‣ Easy to use
    23. ‣ All the benefits of Shapefiles ‣ Open ‣ Easy to use ‣ None of the limitations ‣ Multiple files ‣ Limited field widths
    24. Problems with SQLite?
    25. Problems with SQLite? •No support from ESRI
    26. Problems with SQLite? •No support from ESRI •Still not well known in the community
    27. SpatiaLite
    28. SpatiaLite •Built on SQLite RDBMS
    29. SpatiaLite •Built on SQLite RDBMS •Just a file
    30. SpatiaLite •Built on SQLite RDBMS •Just a file •Portable - Works on Windows, Linux or Mac OS X
    31. SpatiaLite •Built on SQLite RDBMS •Just a file •Portable - Works on Windows, Linux or Mac OS X •Implements OGC Simple Features for SQL
    32. Community Driven Standards
    33. Community Driven Standards Users drive formats
    34. How do we share?
    35. Layer Package to the Rescue
    36. Layer Package to the Rescue
    37. What Works for the Layer Package
    38. What Works for the Layer Package •Compressed format shares well
    39. What Works for the Layer Package •Compressed format shares well •Includes symbology
    40. What Works for the Layer Package •Compressed format shares well •Includes symbology •Metadata and preview thumbnails
    41. What Works for the Layer Package •Compressed format shares well •Includes symbology •Metadata and preview thumbnails •Easy to create with ArcMap
    42. Problems with the Layer Package
    43. Problems with the Layer Package •Uses the closed ESRI Layer file for symbology
    44. Problems with the Layer Package •Uses the closed ESRI Layer file for symbology •Some files converted to closed File Geodatabase format
    45. Problems with the Layer Package •Uses the closed ESRI Layer file for symbology •Some files converted to closed File Geodatabase format •Undocumented
    46. We need symbology with our datasets
    47. Options:
    48. Options: SLD/SE
    49. Options: SLD/SE CSS
    50. Put my symbology in a sidecar!
    51. portland.sqlite portland.css
    52. Atom, GeoRSS, GeoJSON
    53. Atom, GeoRSS, GeoJSON SQLite Spatial SpatiaLite CSS for Symbology
    54. Making data discoverable
    55. Spatial Data Can Be
    56. Spatial Data Can Be Secure Sensitive Open
    57. Availability During Disasters
    58. Monetize Where Possible
    59. Picking Formats and Target Audience
    60. Picking Formats and Target Audience Photo used under creative commons from dotbenjamin
    61. Picking Formats and Target Audience Photo used under creative commons from dotbenjamin
    62. Citizen Participation San Diego Fires
    63. Sharing Large Datasets
    64. Sharing Large Datasets
    65. Sharing Large Datasets
    66. Sharing Large Datasets
    67. So what about vectors?
    68. So what about vectors?
    69. So what about vectors?
    70. So what about vectors? 125 GB
    71. Selecting Vectors to Download 1.Zoom to your area of interest 2.Draw polygon for selection 3.Query
    72. Vectors in WeoGeo
    73. Vectors in WeoGeo Com ing Soo n!
    74. What does data interoperability give us?
    75. Breaking Through Stacks
    76. Closed formats should be avoided
    77. Archiving Geo Data
    78. How Will People Use Your Data in 10 years?
    79. It Was 1998...
    80. James was coding up some cutting edge ESRI MapObjects and FoxPro Magic
    81. Data Archival Systems: 1999
    82. My Old Computer is Dead
    83. If only I had archived in a non-proprietary format...
    84. Ways to keep this from happening to with your data... Use Open Formats Use ETL Pray
    85. Fight for your right to use open spatial data standards
    86. Thank You James Fee email: jfee@weogeo.com twitter: @cageyjames blog: http://www.spatiallyadjusted.com mobile: 480.225.2287

    + James FeeJames Fee, 2 months ago

    custom

    825 views, 0 favs, 4 embeds more stats

    WhereCampPDX Keynote presentation on geodata format more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 825
      • 586 on SlideShare
      • 239 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 0
    Most viewed embeds
    • 222 views on http://www.spatiallyadjusted.com
    • 15 views on http://www.wherecamppdx.org
    • 1 views on http://translate.googleusercontent.com
    • 1 views on http://mapthink.textcube.com

    more

    All embeds
    • 222 views on http://www.spatiallyadjusted.com
    • 15 views on http://www.wherecamppdx.org
    • 1 views on http://translate.googleusercontent.com
    • 1 views on http://mapthink.textcube.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories